The A11Y Project: Web Accessibility Resources and Guides

TalkBack is assistive technology that helps users with visual disabilities access native mobile applications and the web by providing audible and haptic responses to touchscreen gestures. It is the default screen reader software included on Google touchscreen devices running Android. TalkBack is part of the Android Accessibility Suite (which also includes Accessibility Menu, Select to Speak, and Switch Access), and comes pre-installed on devices running Android 9 or greater. This guide covers TalkBack version 13.1.

A numeronym is a word where the first and last letters are kept while the middle letters are replaced by a count of the omitted letters. For example, 'a11y' represents 'accessibility' (11 letters in the middle), 'i18n' represents 'internationalization' (18 letters), and 'l10n' represents 'localization' (10 letters). This differs from abbreviations (like FYI) and acronyms (like HTML).

This collection provides guides on ARIA (Accessible Rich Internet Applications) roles, states, and properties. These are predefined attributes used to describe elements that may not exist natively in browsers or may not be understood by screen readers and other assistive technologies. The collection includes: 1) An in-depth guide to ARIA roles by Duncan Jimbo, 2) ARIA states introduction by Alex Brenon, and 3) ARIA properties introduction by Alex Brenon.

Video resource by Michele Williams explaining what 'making technology accessible' means. Covers how people use their computing devices and the diversity of disability in technology. Provides foundational understanding of accessibility concepts for anyone building or designing digital products.

Orca is a free, open-source screen reader developed under the GNOME project. Many Linux distributions include it by default. This guide covers using Orca on the GNOME desktop environment with Ubuntu 20.04 LTS. Note that there may be variations when using different desktop environments or Linux distributions—consult your distribution's documentation for specific guidance.

VoiceOver is a screen-reading tool built into Apple iOS that helps users navigate and interact with their iPhone without needing to see the screen. It responds to gestures (single tap, double tap, etc.) and audibly communicates information about selected items, including hints, values, and traits. First introduced in 2009, VoiceOver is included in every iOS release.

A video resource from M.A.W. Consulting, LLC designed for technology professionals (current and future). The video covers: the definition of accessibility, an introduction to assistive technology, an overview of the Web Content Accessibility Guidelines (WCAG), and considerations for tech professionals across various lifecycle roles. It serves as foundational content for understanding inclusive design.

An independent accessibility consultant works with organizations of all sizes to improve digital accessibility. Responsibilities include: guiding organizations to build an accessibility culture, training staff, and auditing digital assets. The work involves changing how organizations and their people think about disabled people and accessibility.

The Spotlight page showcases community members contributing to web accessibility. Each profile highlights the individual's professional background in areas such as frontend development, product design, accessibility consulting, research, and inclusive design. Visitors can read brief introductions and follow links to full biographies for each featured member.

ARIA does not have perfect support. Compatibility issues arise from combinations of: operating system type and version, browser type and version, assistive technology type and version, and any user modifications to these. Writing ARIA code does not guarantee it will work as intended—similar to expecting modern JavaScript to work on Internet Explorer 11. Problems compound when multiple ARIA-dependent parts interact, or when newer ARIA features interact with older ones. Many assistive technology users specifically use older versions for stability. Unlike other compatibility issues, assistive technology problems can completely lock users out of a digital experience.

The A11Y Project strives to be Web Content Accessibility Guidelines 2.1 (WCAG) AA compliant. WCAG is an open standard for determining accessibility, and AA compliance is considered good support for a website geared towards a global audience.