These resources supplement Drupal’s accessibility documentation. Start with standards and official guidance, then choose practical resources for the task, audience, and jurisdiction.

Consider each source’s authority, purpose, status, ownership, and review date. Implementation guidance does not replace a standard. Tool results do not determine conformance. Inclusion here is not Drupal project endorsement.

Standards and official guidance

• W3C Accessibility Standards Overview: WCAG, ATAG, UAAG, WAI-ARIA, and related work.
• Web Content Accessibility Guidelines (WCAG) 2.2: current W3C Recommendation for web content.
• Understanding WCAG 2.2: intent and user benefits of each success criterion.
• WCAG 2.2 Techniques: informative examples, not conformance requirements.
• Authoring Tool Accessibility Guidelines (ATAG) 2.0: accessible authoring interfaces and support for accessible output.
• ARIA Authoring Practices Guide: design patterns and examples for common widgets.
• WAI Tutorials: page structure, menus, images, tables, forms, and carousels.
• Making Audio and Video Media Accessible: captions, transcripts, audio description, sign language, and media players.

Evaluation and user research

• WCAG Evaluation Methodology: evaluating a defined website scope.
• Selecting Web Accessibility Evaluation Tools: capabilities, limitations, and selection criteria.
• W3C Web Accessibility Evaluation Tools List: filterable directory without W3C endorsement.
• Involving Users in Evaluating Web Accessibility: combining disabled-user testing with standards-based evaluation.
• Accessibility Conformance Testing Rules Format: a consistent format for limited test rules.
• The A11Y Project checklist: practical community guidance, not a conformance standard.

Testing tools

Automated tools find some failures and flag other conditions for review. They cannot determine accessibility. Confirm findings manually and document the affected people, task, requirement, test conditions, and rule.

• axe-core: open-source rules engine used by Drupal core tests.
• Accessibility Insights: automated and guided manual assessment.
• IBM Equal Access Accessibility Checker: browser and development-tool integrations.
• WAVE: findings and review prompts shown in page context.
• Pa11y: open-source command-line and dashboard tools.

See How to do an accessibility review for the complete Drupal review process.

Practical implementation guidance

• DWP Accessibility Manual: role-based guidance, testing, and team processes.
• U.S. Web Design System accessibility guidance: components, project responsibilities, and testing.
• Government of Canada Digital Accessibility Toolkit: bilingual guidance for digital-service teams.
• AccessibleEU: European resources, training, and policy information.
• WebAIM: established implementation, training, and evaluation resources.

Law and policy

• W3C Web Accessibility Laws and Policies: international policy index.
• Section508.gov: United States federal ICT guidance.
• Accessibility Standards Canada: federal standards and accessibility research.

These links are not legal advice. Confirm the requirements for your organization and jurisdiction.

Assistive technology documentation

• NVDA: free and open-source Windows screen reader.
• VoiceOver User Guide for Mac: Apple’s built-in screen reader.
• TalkBack Help: Google’s Android screen reader.
• JAWS Quick Start Guide: commercial Windows screen reader.

Choose combinations based on users, supported platforms, and risk. One product result does not represent every user.

Drupal accessibility community

• Join the #accessibility channel in Drupal Slack.
• Attend Drupal accessibility office hours for discussion and contribution support.

Emerging work

• WCAG 3 Introduction: early draft that does not replace WCAG 2.2.
• Accessible Perceptual Contrast Algorithm (APCA): evolving research, not a current Drupal conformance requirement or replacement for WCAG 2.x contrast testing.