Accessibility Review Pull Request Template

Accessibility Review PR Template

Accessibility (a11y) is a critical quality dimension that is often overlooked in PR reviews. This template provides a structured framework for evaluating the accessibility impact of UI changes, ensuring compliance with WCAG guidelines.

Template Structure

## Description
<!-- Describe the changes and their accessibility impact. -->

## WCAG Compliance Level
- [ ] Level A (minimum)
- [ ] Level AA (recommended)
- [ ] Level AAA (enhanced)

## Accessibility Checklist

### Perceivable
- [ ] All images have meaningful alt text
- [ ] Videos have captions or transcripts
- [ ] Color is not the sole means of conveying information
- [ ] Text has sufficient contrast ratio (4.5:1 for normal, 3:1 for large)
- [ ] Content is readable at 200% zoom

### Operable
- [ ] All functionality is keyboard accessible
- [ ] Focus order is logical and intuitive
- [ ] Focus indicators are visible
- [ ] No keyboard traps exist
- [ ] Timed content can be paused or extended

### Understandable
- [ ] Form labels are clear and descriptive
- [ ] Error messages are helpful and specific
- [ ] Navigation is consistent across pages
- [ ] Language is declared in HTML

### Robust
- [ ] Valid HTML (no duplicate IDs)
- [ ] ARIA attributes are used correctly
- [ ] Custom components have appropriate roles
- [ ] Works with assistive technologies

## Screen Reader Testing
<!-- Results from testing with VoiceOver, NVDA, or JAWS. -->

## Keyboard Navigation
<!-- Describe the keyboard flow through the component. -->

## Related Issues
<!-- Closes #(issue number) -->

WCAG Four Principles

The checklist is organized around WCAG's four principles: Perceivable, Operable, Understandable, and Robust (POUR). This structure helps contributors systematically evaluate accessibility.

Screen Reader Testing

The Screen Reader Testing section asks for actual results from assistive technology testing, not just a checkbox. Contributors should describe what the screen reader announces and whether the experience is usable.

Keyboard Navigation

Documenting the keyboard flow (Tab order, Enter to activate, Escape to dismiss, arrow keys for navigation) helps reviewers verify that keyboard-only users can use the component.

ARIA Best Practices

The checklist includes ARIA-specific items because ARIA attributes are commonly misused. Using the wrong role or missing required ARIA properties can make a component less accessible than having no ARIA at all.