Resources
Resources for accessibility, recommended by the instructor or by class members. Nothing here is required reading. If you would like to suggest a resource for this page, email it to the instructor.
Prerequisites: HTML, the command line, and git
- MDN: Learn web development
- MDN: Accessibility
- Software Carpentry: The Unix Shell
- Software Carpentry: Version Control with Git
- The Missing Semester of Your CS Education
Screen readers
- NVDA
- VoiceOver User Guide
- WebAIM: Using VoiceOver to Evaluate Web Accessibility
- WebAIM: Using NVDA to Evaluate Web Accessibility
- WebAIM: Keyboard accessibility
Standards and specifications
- WCAG 2.2, and the Quick Reference, which filters the success criteria by level and lists techniques and documented failures for each. Use the Quick Reference to fill in Assignment 2’s WCAG column.
- Understanding WCAG 2.2. Gives the intent behind each criterion with examples. Read the relevant page when a criterion’s wording does not decide your case.
- WebAIM’s WCAG 2 Checklist. Restates the A and AA criteria in plain language, one line each.
- ARIA Authoring Practices Guide. Start with Read Me First, which explains why adding ARIA to an element usually makes it worse. The patterns give the roles and keyboard interactions for composite widgets such as grids and tree views, and the keyboard interface practices explain roving
tabindexandaria-activedescendant. Assignment 3 needs both. - ARIA in HTML states which roles and attributes are permitted on which HTML elements, and Using ARIA states the five rules of ARIA use.
- Accessible name (MDN). Where an element’s announced name comes from, and the order the browser checks the sources in. Most voice control failures are name failures.
- a11ysupport.io. Records which screen reader and browser pairs actually implement a given ARIA feature. A feature can be in the spec and unsupported in the pair you are testing.
- W3C WAI Tutorials. Worked markup for page structure, menus, images, tables, and forms.
- DOJ rule on web accessibility under ADA Title II and Section508.gov. What US law requires of state and local governments and of federal agencies. Both bear on Assignment 2’s graduate prompt about conformance as a regulatory instrument.
Testing tools
- Chrome DevTools accessibility reference
- Firefox Accessibility Inspector
- axe DevTools
- pa11y
- WAVE
- WebAIM contrast checker
- W3C Easy Checks
Design practice and patterns
- Inclusive Components
- A Complete Guide To Accessible Front-End Components
- The A11Y Project checklist
- Microsoft Inclusive Design toolkit
Blogs
Non-visual and multimodal design
Disability justice
- 10 Principles of Disability Justice
- Leaving Evidence (Mia Mingus)
- Disability Visibility Project (Alice Wong)