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
DOCUMENTATION: Add an accessibility statement #1443
Comments
W3C's WAI has some background and a generator that could be used:
There's also a minimal example which may be good place to begin https://www.w3.org/WAI/planning/statements/minimal-example/ Also as discussed, would be good to add an "Accessibility" principle at https://latest.visual-framework.dev/guidance/, and from there we could describe a process by which sites should create their accessibility statement. |
As discussed in #1443 and the VF-UX clinics, this introduces some text about accesibility in the VF, and adds a section to the README.md template.
Thinking about an accessibility statement, I wonder if it would be better for this to live as part of the EMBL.org website (much like we do for the privacy statement). |
As discussed in #1443 and the VF-UX clinics, this introduces some text about accessibility in the VF, and adds a section to the README.md template.
Leaving this link here: https://latest.visual-framework.dev/guidance/accessibility/ |
After the latest VF/UX chat I think we decided on vying for AAA where possible on new components and making sure existing things are A or AA compliant.
We should probably add some form of ‘statement’ to the docs site.
I found this example: https://www.gov.uk/government/publications/sample-accessibility-statement/sample-accessibility-statement-for-a-fictional-public-sector-website
The text was updated successfully, but these errors were encountered: