-
Notifications
You must be signed in to change notification settings - Fork 0
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
Conduct + implement changes for accessibility audit #131
Comments
Hey @ShannonTrust - good question! |
I think that would be a good idea, @cyberteenie, and possibly something we should consider doing every 6 to 12 months. Happy for you to go ahead with the audit when you get a chance. |
Great! We will put that into the pipeline. :) |
Hi @ShannonTrust. The good news is that there is nothing major! Mainly small tidy up actions that we can complete within the next month. Although they are all small changes, they require us to manually go through the website page by page. I reckon this will take around 3 days of development time, up to a maximum of 5. After making those changes, we will definitely meet the WCAG 2.2 AA level. AAA level is a bit more in depth, and may require a further estimate for enhancements, which we can provide after ensuring we first meet AA. Let me know if you have any questions! |
Hi @cyberteenie, thanks so much for the in depth review. It's good to know where the changes are being made :) If you need anything help with anything, let me know! |
Ask your question here.
I've been wanting to sort out an accessibility statement since you did the accessibility audit for us last year but it keeps slipping down my to do list. Do you have any tips of what we could include in it based on the audit you did for us? What level of WCAG do we meet? Any support would be really appreciated.
Screenshots or a link to a Loom Recording
No response
The text was updated successfully, but these errors were encountered: