Accessibility for Giants
The primary goal of this project will be to provide various examples of how to make websites more accessible, with some failing examples followed by how to fix them.
Hopefully, as these become more usable, this can be a resource to support producing more accessible websites for everyone.
- Resources are supporting tools and links to support greater accessibility
- Wiki is the core resource that provides examples and fixes for common accessibility problems
Accessibility?
The main goal of accessibility is to make sure that everyone can use the website, regardless of any disabilities they may have.
The added benefit of this is that it also makes the website easy to use for everyone else. Whether that's seeing well contrasted text in bright sunlight, or having room for error when trying to click buttons in a moving vehicle, every change made to support accessibility will also make the website easier to use.
This site won't aim to reach WCAG 2.2 AA (opens in a new tab), and won't be the primary tool for reaching it either. But it will help to get a simple, readable, starting point that helps to add some basic accessibility to sites.
What are these page titles?
The layout of the folders and page titles are based on the headings / sections in the Accessibility Insights for Web (opens in a new tab) extension, which QA Teams can use for the testing of Accessibility requirements for a consistent approach across the team.
An example can be seen in the "Run the automated checks" (opens in a new tab) section of the documentation that helps visualise those headings, and these are nice, sensible groupings of the WCAG requirements.