We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We should use the latest internal accessiblity spreadsheets to do an accessiblity pass and update our accessiblity statement
Our last update was 23 June 2022, and WCAG 2.2 compliance is due in October.
We have an updated accessibility statement with test evidence.
for audit @mitz-lad @claireduxs76
for content update @martinwake
The text was updated successfully, but these errors were encountered:
Will put out the updates for review.
Then assume we can update the WCAG documents before we do the Macbook testing.
Sorry, something went wrong.
htmlandbacon
No branches or pull requests
What
We should use the latest internal accessiblity spreadsheets to do an accessiblity pass and update our accessiblity statement
Why
Our last update was 23 June 2022, and WCAG 2.2 compliance is due in October.
Done when
Updated accessibility compliance documentation
Other tasks
Outcomes
We have an updated accessibility statement with test evidence.
Who needs to know about this
for audit @mitz-lad @claireduxs76
for content update @martinwake
Anything else
The text was updated successfully, but these errors were encountered: