Skip to content
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

Open
ShannonTrust opened this issue Jul 11, 2024 · 5 comments
Open

Conduct + implement changes for accessibility audit #131

ShannonTrust opened this issue Jul 11, 2024 · 5 comments
Assignees
Labels
enhancement New feature or request sla

Comments

@ShannonTrust
Copy link
Collaborator

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

@ShannonTrust ShannonTrust added question Further information is requested sla labels Jul 11, 2024
@cyberteenie
Copy link
Member

Hey @ShannonTrust - good question!
To be honest, since there have been changes since last year, I think the best thing to do would be to run a very lightweight accessibility audit to ensure that the accessibility statement is up to date and that there isn't anything big that we are overlooking. Are you happy for us to take a couple of hours to do so?

@ShannonTrust
Copy link
Collaborator Author

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.

@cyberteenie cyberteenie changed the title Accessibility statement Conduct accessibility audit Jul 11, 2024
@cyberteenie cyberteenie added enhancement New feature or request and removed question Further information is requested labels Jul 11, 2024
@cyberteenie
Copy link
Member

Great! We will put that into the pipeline. :)

@cyberteenie
Copy link
Member

Hi @ShannonTrust.
I have completed the accessibility audit and have stored it in our Shared Notion.

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!

@ShannonTrust
Copy link
Collaborator Author

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!

@cyberteenie cyberteenie changed the title Conduct accessibility audit Conduct + implement changes for accessibility audit Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request sla
Projects
None yet
Development

No branches or pull requests

4 participants