Build new components and patterns that help teams meet WCAG 2.2

[dav-idc]

What

Timeline: Unknown start time, but aim to publish by September 2023
Priority level: 4 – what improves accessibility for many services
Category: Areas the team is best-positioned to handle

Potential tasks

• Research which components and patterns will have unique considerations for WCAG 2.2 and don’t currently exist on the GOV.UK Design System
• Prioritise new components and patterns that are likely to save service teams’ effort when preparing their service for WCAG 2.2

Epic lead

Not yet assigned

Why

New criteria introduced in WCAG 2.2 bring new challenges for service teams. It's more effective to build a set of new components and patterns centrally, to help all teams meet WCAG 2.2.

One new criterion that has a significant potential for newly-relevant components is the draft of 3.3.7: Accessible authentication.

Who needs to work on this

interaction designers, developers, accessibility specialist, user researcher, content designers, and more.

Who needs to review this

GOV.UK Design System working group, general design system community

Done when

Component and pattern work

Preview Give feedback

1. Explore ways to improve our approach to WCAG 2.2 'focus not obscured' govuk-design-system#3006
   WCAG 2.2 accessibility epic +3
2. Create Password input component to help teams meet WCAG 2.2 #4063
   11 of 17
   WCAG 2.2 accessibility epic passwords +4
   
3. Rationalise our approach to styling focus states govuk-design-system#3007
   0 of 4
   WCAG 2.2 accessibility design epic +4
   
4. Get the password input component and guidance into a publishable state govuk-design-system#3454
   19 of 19
   epic +1
   

   

[dav-idc]

Update: we're exploring whether the time is right to start work on a net-new component for WCAG 2.2: a 'show/hide password' component. It will likely be added as a component, which will enhance our existing password pattern.

[dav-idc]

It seems the time draws near! We've converted this to be a 'main epic', and it'll hold a variety of epics inside it.

Each of those epics will be listed inside this issue, and are likely to be based around a particular new component or pattern that benefits WCAG 2.2 efforts.

First up will likely be:

• Create Password input component to help teams meet WCAG 2.2 #4063