Keyboard Navigation
Verify menus, forms, dialogs, and interactive controls can be accessed and operated without a mouse.
Accessibility Testing and Section 508 Evaluation
Accessibility testing works as a repeatable workflow. The goal is to validate interaction patterns and make usability part of every release cycle.
Read accessibility review processAccessibility Review Process
-
Define Scope
Pick the page, flow, component, or release path being evaluated.
-
Run Checks
Use automated tools to catch common issues quickly.
-
Test Manually
Validate keyboard access, focus order, labels, and interaction states.
-
Prioritize Fixes
Rank issues by severity, frequency, and impact on task completion.
-
Retest
Confirm fixes, document patterns, and prevent regressions.
Testing Methods
Screen Readers
Review content and workflows using assistive technologies to confirm labels, headings, and announcements are communicated correctly.
Tabbed Focus Order
Evaluate tab order and focus visibility to support predictable navigation across pages and applications.
Forms
Assess labels, instructions, validation messages, and error handling for accessibility and usability.
Color Contrast
Review text, controls, and visual indicators against WCAG contrast requirements.
Section 508 and WCAG
Evaluate pages and workflows against applicable Section 508 requirements and relevant WCAG success criteria.
What to Test
- Readable text, contrast, zoom behavior, and visual hierarchy.
- Keyboard access, focus visibility, skip links, and logical tab order.
- Labels, headings, structure, and assistive technology support.
Workflow Signals
- Issue blocks a core task or prevents completion.
- Interaction works visually but fails through keyboard or screen reader use.
- Fix can become a reusable pattern across future pages.
Quick Wins
- Add descriptive form labels and error messages.
- Make focus states visible and easy to follow.
- Check contrast before visual design is finalized.