Web & App Accessibility | Accessibility at Arizona

What this page helps you do

Plan and build Arizona sites and applications that meet WCAG 2.2 AA and Title II expectations.
Choose the right Quickstart components, patterns, and testing tools for your stack.
Know when to escalate issues, request exceptions, or coordinate with Procurement and Accessibility PMO.

Executive summary

All UA digital properties, including mobile apps, must meet WCAG 2.2 AA. Align your roadmap with the Title II deadlines, implement Quickstart components as designed, and document any fundamental alteration claims with alternative access plans.

Reference theTitle II brieffor scope, dates, and expectations.
Use Quickstart’s accessible components and shared snippets (`skip-link-snippet`, `focus-management`, `web-keyboard`).
Integrate automated and manual testing (axe, Accessibility Insights, JAWS/NVDA/VoiceOver/TalkBack).
Engage Procurement early when selecting third-party widgets or SaaS platforms.

If you only do one thing:run a keyboard-only walkthrough of your next feature before it ships.

Quick wins (5–10 minutes each)

Four high-impact checks you can do before any release. Each links to the authoritative source.

Keyboard walkthrough

Put your mouse aside. Tab through the page—can you reach and activate every control? Is focus always visible?

3 min

WebAIM: Keyboard Accessibility

Check form labels

Every input needs a programmatic label. Run axe or WAVE to find unlabeled fields.

2 min

W3C: Form Labels

Fix vague link text

Replace "click here" and "read more" with descriptive text that makes sense out of context.

5 min

WebAIM: Link Text

Verify color contrast

Text needs 4.5:1 ratio (or 3:1 for large text). Use WebAIM's contrast checker or browser DevTools.

2 min

WebAIM: Contrast Checker

Minimum, better, best for web & apps

Minimum:Public-facing sites and applications avoid blocking barriers (keyboard traps, missing alt text on key images, inaccessible menus, uncaptioned required media).
Better:Teams adopt Quickstart components and patterns, run automated and basic manual tests before releases, and address findings within planned sprints.
Best:Accessibility requirements are part of definition of done, CI enforces checks, design and code reviews include disabled user feedback, and exception processes are documented and rare.

Quickstart & component patterns

Navigation & bypass

Implement skip links, consistent nav order, and visible focus states.

Skip link snippet

Keyboard interaction

Follow roving tabindex and composite component guidance.

Keyboard guidance

Focus management

Send focus to dialogs, alerts, and error summaries predictably.

Focus playbook

Color & motion

Use contrast-safe palettes, respect prefers-reduced-motion, avoid flashing.

Color guidance

Form experiences

Explicit labels, inline errors, ARIA relationships, and accessible help.

Do/Don’t library

Content structure

Headings, landmarks, tables, and lists that follow `heading-basics`.

Heading basics

WCAG 2.2 AA checklist

Principle	Criteria highlights	UA implementation
Perceivable	Text alternatives, captions, contrast, reflow, dragging movements (2.5.7/2.5.8).	Use shared media guidance, color tokens, and responsive layouts with rem units.
Operable	Keyboard, pointer gestures, focus visible, target size, bypass blocks.	Adopt skip link snippet, roving tabindex, `min-height` hit areas 44px.
Understandable	Consistent navigation, error identification, input assistance.	Link to `shared/do-dont.md` patterns, add summary boxes, keep nav order static.
Robust	Names/roles/states, status messages, accessible APIs.	Use native HTML whenever possible; test with multiple screen readers.

Download the full checklist or import into your team’s issue tracker.

Download checklist

Testing toolkit

Automated:axe DevTools, Accessibility Insights CLI, Storybook a11y add-on.
Manual keyboard:Tab/Shift+Tab/Enter/Space/Escape flows per `web-keyboard` guidance.
Screen readers:JAWS, NVDA, VoiceOver, TalkBack; include Fusion/ZoomText for magnification.
Contrast & visuals:TPGi CCA, UA design tokens, prefers-reduced-motion QA.
Reference material:WebAIM checklistsandDeque axe DevTools guides.

SeeTesting Toolkitfor scripts, logging templates, and CI recipes.

Mobile apps

Title II now explicitly covers mobile apps. Follow themobile roadmapto inventory apps, schedule audits, and remediate issues.

VoiceOver expectations

Support rotor navigation, Dynamic Type, high-contrast mode.

Apple guidance

TalkBack expectations

Ensure on-screen instructions announce properly, provide custom actions, respect large text.

Google guidance

Companion web flows

When apps open web views, inherit Quickstart components and retest with JAWS/NVDA.

Mobile app guide

Exception & equivalency process

Document why meeting a criterion would be a fundamental alteration or undue burden.
Outline the alternative access plan (who to contact, what formats, response times).
Route request through Accessibility PMO, Legal, and Executive Sponsor for approval.
Review annually and retire once resolved.

Use the consultation form to start an exception review and store decisions in the governance log.

Training & community

Arizona Digital developer guild (bi-weekly).
WCAG 2.2 code labs (monthly).
Mobile accessibility deep dives (quarterly).

Need help? Request a consultation.

Request consultation

Learn from the source

We curate guidance—these organizations set the standards. Bookmark them for deep dives.

Standards

W3C WCAG 2.2– The global standard
ARIA Authoring Practices– Component patterns
ADA.gov Web Guidance– Title II rules

Testing Tools

Deque axe– Automated testing
Accessibility Insights– Microsoft
WAVE– WebAIM browser tool

Learning

WebAIM– Articles & resources
Deque University– Courses
web.dev Accessibility– Google