User:Montehurd/accessibility

I'm using this page to aggregate some notes I've taken regarding accessibility.

Introduction
The best accessibility introduction I've found is compiled by the Australian government and may be found here.

Perspectives
These short videos are an excellent place to start when thinking about accessibility improvements.

WCAG
The W3C Web Content Accessibility Guidelines (WCAG) outline best practices for designing website which are "perceivable, operable, understandable, and robust".

Another good summary of the W3C WCAG document.

WAI-ARIA
The Web Accessibility Initiative - Accessible Rich Internet Applications (WAI-ARIA) provides ways for web applications to interface with assistive technologies.

A basic intro with emphasis on using semantic elements vs plain DIVs for everything. "An important point about WAI-ARIA attributes is that they don't affect anything about the web page, except for the information exposed by the browser's accessibility APIs (where screenreaders get their information from). WAI-ARIA doesn't affect webpage structure, the DOM, etc., although the attributes can be useful for selecting elements by CSS."

Development
Extremely well produced 30 part technical web development accessibility series.

I highly recommend using the playback speed keyboard shortcuts mentioned below - you'll save so much time by watching the series at even 1.25 speed. And you'll be using an accessibility feature!

Toolkits
As referenced above, the Australian government's wide-ranging, detailed and polished accessibility website has sections for managers, designers and developers.

axe-core
axe is open source, well maintained and relatively easy to set up and use.

Framework repo

In-depth tutorial video

Another great tutorial video

axe-webdriverjs
"Provides a chainable aXe API for Selenium's WebDriverJS and automatically injects into all frames."

Framework repo

Tutorial video

axe-cli
Framework repo

Tutorial video

axe browser extensions
Chrome

Firefox

Accessibility is for everyone
Everyone can benefit from rich accessibility features.

Keyboard shortcuts
Keyboard shortcuts are a great example. As part of this research I've started using the following keyboard shortcuts (on macOS).

Wikipedia
Control-Option-G to open the Wikidata item for an article was neat!

Control-Option-P to show edit preview is handy. Fully dismiss the preview with the escape key.

Youtube
As I've watched various accessibility videos these shortcuts have proved immensely convenient.

Safari
Command-Shift-R Opens a very nice "Reader mode".

Phabricator tickets
T2477 Access key issues

Tickets tagged with "accessibility"

T232638 Accessibility checks for GrowthExperiments extension

Wikipedia Projects
WikiProject Accessibility

Articles with accessibility problems

Articles with color accessibility problems

Accessibility section in Wikipedia Manual of Style

Accessibility and usability cleanup

Accessibility guide for developers

NVDA for Windows
Project home

Really good TEDx talk

Extensions

Keyboard reference

Demo installing and using for development

Apple VoiceOver
Overview

macOS VoiceOver training may be found at:

"System Preferences > Accessibility > Open VoiceOver training"

macOS has a simple VoiceOver toggle - hold Command and triple-click the Touch ID button

Editing
Can we give editors instant feedback on whether their edits introduce any accessibility issues?

Automation
Can we add (or encourage adding) tests for all extensions so developers can easily know if their work is accessible?

Template usage auditing
Can we audit what accessibility issues templates already exist, how widely they are used, and how their usage is distributed?

Articles issues auditing
Can we audit all articles for their accessibility "scores" (maybe just a count of aXe violations detected?) to get a sense for how widespread article issues are? If this number is greater than the number of articles with accessibility-related templates it may provide an opportunity to use accessibility-related templates more widely.