For a small set of WCAG 2.2 assessment entries, we're ready to start making changes to govuk-frontend and the design system website guidance content. These changes will align our elements with new criteria in WCAG 2.2.
This selection of entries are good to being work on because:
They're fairly straightforward and discretely scoped
They can be handled by content designers, interaction designers and developers
They won't require too much additional 'discovery' accessibility research or testing needed.
Who needs to work on this
Accessibility specialist (creating the issues)
Content designers, developers and interaction designers (actioning the issues)
What
Create issues for the Design System elements that have been assessed as ready for development work.
Note: this work previously included content work tickets, but that has now been moved to its own epic. https://github.com/alphagov/govuk-design-system/issues/2729
The entries for each element can be found in the internal 'WCAG assessments of DS elements' spreadsheet.
Why
For a small set of WCAG 2.2 assessment entries, we're ready to start making changes to govuk-frontend and the design system website guidance content. These changes will align our elements with new criteria in WCAG 2.2.
This selection of entries are good to being work on because:
Who needs to work on this
Accessibility specialist (creating the issues)
Content designers, developers and interaction designers (actioning the issues)
Who needs to review this
Product manager