Web Developer Accessibility Resources
As web developers, you are required to ensure that all visitors to Tufts websites have equal access, no matter how they’re accessing said websites.
What is Web Dev Accessibility?
Creating websites that allow everyone to see and find the content on them.
- For example, someone without a mouse should be able to tab through your site.
- Many of the guidelines are things you should be doing already, like adding page titles and alt text.
- Check out “Web Dev Accessibility at a Glance” for a quick look at what this means and how easy this is.
WCAG are the web content accessibility standards published by W3C.
The standards are split into 3 sections:
- A: Required to meet minimum WCAG standards (e.g. every site has a page title).
- AA: Recommended for comprehensive inclusiveness (e.g. text can be resized up to 200%). This is the level of compliance required by Tufts.
- AAA: Stretch goals for total inclusiveness (e.g. low or no background audio).
Check out “WCAG at a glance” for a quick look at the WCAG principles.
What other information should I know right now?
- Tufts requires its websites to be AA compliant.
- Check the other pages in this section to learn about what that entails and how you can meet it. (With that said, many Tufts webpages currently don’t meet even A standards)
Here is a 1 page checklist with A standards that you can print and hang up.
- Please note that this checklist alone is not enough, as Tufts requires AA standard implementation. You can’t just hang it up and say you’re finished!
- The checklist is designed to ensure that you can start immediately meeting the absolute minimum compliance by law, while you start implementing the more involved AA standards.
- Essentially, if you start using this checklist today, you’ll have fewer things to retroactively fix as you work towards AA compliance.