-
Notifications
You must be signed in to change notification settings - Fork 334
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create and publish documentation for DAC Audit 2023 #3814
Comments
Blog posts that relate to an accessibility audit: |
Accessibility statement changesDrafted in July 2023 accessibility statement update google document. Committed to the GOV.UK Design System website in this pull request. |
We've also added some component specific usability information to the file upload component |
Messaged DAC today (Tuesday 17 October 2023) to find out if we could get an alternate version of the report in a more accessible format. Side note: We carparked 'How we might talk about our audits' in our Design Sprint in Summer 2023 to revisit at a later date when we have a place on the website where it can live |
What
This ticket completes work related to the DAC audit 2023 and how we share results of the audit more publicly.
Why
This WCAG 2.2 audit supports our efforts to #3040.
As we approach the publishing date for WCAG 2.2, we want to ensure our existing govuk-frontend elements are meeting all WCAG 2.1 AA criteria. The only way to pass WCAG 2.2 AA is to also meet all criteria in WCAG 2.1 AA (with one exception, where a criterion is being removed).
We're doing other work to assess where updates are needed to align elements with the 9 new WCAG 2.2 criteria, but we likely don't have capacity to run an internal audit across all of the existing 78 WCAG criteria.
Who needs to work on this
@CharlotteDowns, @davidc-gds
Who needs to review this
@stevenjmesser
Done when
Tasks
The text was updated successfully, but these errors were encountered: