WCAG 2.2 AA updates to guidance to comply, and help teams to comply, with new criteria

[calvin-lau-sig7]

What

Update component and pattern guidance to include any new requirements service teams need to follow to comply with WCAG 2.2 AA.

This epic specifically covers component and pattern guidance that needs to be added, such as specific instructions and requirements for particular components.

This also covers 'styles' however audit seems to show it as mostly unaffected, except for focus states which is currently being drafted.

This comes under: #3040 and will be done alongside: #2448

About 54 updates in total:

Epic lead

Calvin

Why

WCAG 2.2 is set to be published in 2023. As such, we hope to bring the GOV.UK Design System website in line with WCAG 2.2 criteria within 9 months of the publish date.

Who needs to work on this

Accessibility specialist, Content designers, interaction designer

Who needs to review this

Developers, interaction designers

Tasks

Preview Give feedback

1. Audited components and patterns to check for WCAG 2.2 AA compliance — Google Sheet: WCAG 2.2 assessment of DS elements
2. Brief written for new content to be added (job stories) — Google Doc: WCAG 2.2 content updates
3. "First 15" Content drafted, including proposed copy and location
4. "First 15" Draft reviewed by accessibility expert
5. Finalise and upload "first 15" WCAG 2.2 edits #3063
   16 of 16
   WCAG 2.2 guidance +2
   
6. "Next 30" Content drafted, including proposed copy and location
7. "Next 30" Draft reviewed by accessibility expert
8. Finalise and upload "next 30" WCAG 2.2 edits #3064
   36 of 36
   WCAG 2.2 guidance +2
   

   
9. "October edits" 11 content pieces drafted, reviewed and added to PR #3276
   10 of 10
   WCAG 2.2 guidance +2
   
10. Get WCAG 2.2 updates ready to replicate across all pages #3304
    accessibility +1
    

    
11. Replicate WCAG 2.2 changes across all pages #3302
    WCAG 2.2 accessibility design guidance +4
    

    
12. Preparation for team review of WCAG 2.2 content updates #3338
    +0
    

    
13. Distributed team review of WCAG 2.2 updates #3311
    WCAG 2.2 +1
    

    
14. Rebase with GOV.UK Frontend v5.0 (see https://gds.slack.com/archives/C011V7RAAKY/p1701695706964249?thread_ts=1701694882.286329&cid=C011V7RAAKY)
15. Published to production (live website)

'DUPLICATED' issues that were already in our doc

Preview Give feedback

1. WCAG 2.2 guidance update: Footer || Consistent Help #3008
   WCAG 2.2 accessibility +2
   
2. WCAG 2.2: Contact a department or service team ‖ Consistent Help #2882
   WCAG 2.2 accessibility contact dept or service team +3
3. WCAG 2.2: Question pages ‖ Redundant entry #2866
   WCAG 2.2 accessibility question pages +3
   
4. WCAG 2.2: Create accounts ‖ Redundant Entry #2878
   WCAG 2.2 accessibility create accounts +3
5. WCAG 2.2: Page template/footer ‖ Consistent Help #2871
   WCAG 2.2 accessibility footer page template +4

[calvin-lau-sig7]

Re: how we highlight this new content to users, a few of us working on this agreed we'll want to create some sort of 'summary page' to index and show this content. Use case is for teams that want to know what changes they need to make to existing work to comply with WCAG 2.2.