Quick Start Guide | Accessibility at Arizona

Know what you need?Jump directly:

Making a document accessible Testing a website Accessible course in Brightspace Adding captions to video Buying software Reporting a barrier

1What are you working with?

Document Word, PowerPoint, PDF, Google Docs Website or App Web pages, web apps, mobile apps Course Content Brightspace, Panopto, lectures Video or Audio Recordings, podcasts, live events Buying Something Software, SaaS, hardware Report a Barrier Found something inaccessible

2Documents: What type?

Word Document PowerPoint PDF Google Docs/Slides Excel/Spreadsheet

Making Documents Accessible

Here's your quick checklist:

Before sharing any document:

Used heading styles (not just bold text) Added alt text to images Used sufficient color contrast Made link text descriptive (not "click here") Ran Accessibility Checker (Review Check Accessibility)

Detailed guides:

Download accessible templates

2Web/App: What's your role?

For Developers & Technical Teams Building or fixing Content Author Adding content to CMS Tester/QA Checking for issues

Developer: Building Accessible Web

Essential developer checklist:

Semantic HTML (proper headings, lists, landmarks) All images have alt text Forms have labels Keyboard accessible (Tab, Enter, Escape work) Visible focus indicators Color contrast 4.5:1 minimum Tested with screen reader

Your tools:

WAVEoraxe DevTools— Browser extensions
NVDA— Free screen reader for testing
Full tools comparison

Complete developer guide

Content Author: CMS Best Practices

When adding content:

Use heading styles for sections Add alt text to every image Write descriptive link text Add captions to videos Use lists for lists (not just dashes)

Content creator guide

Tester: Checking for Accessibility

Automated scan:RunWAVEor axe DevTools
Keyboard test:Tab through the entire page
Screen reader:Test withNVDA
Visual:Zoom to 200%, check contrast

Full testing guide

2Course Content

Making Courses Accessible

Brightspace course checklist:

Module pages use heading styles All images have alt text Videos have accurate captions Documents are accessible (not scanned PDFs) Quiz questions have sufficient time Accessibility statement in syllabus

Key resources:

Complete faculty guide

2Video/Audio

Making Media Accessible

Video accessibility:

Captions added (auto-captions edited for accuracy) Transcript available for audio-only content Audio descriptions for visual-only content (if needed) Good audio quality (clear speech)

How to caption:

Panopto:Auto-generates captions—review and edit for accuracy
Zoom:Enable live captions or request CART
YouTube:Use auto-captions, then edit

Captioning guide

2Buying Technology

Accessible Procurement

Before purchasing:

Request VPAT from vendor Review VPAT for WCAG 2.1/2.2 AA conformance Ask about accessibility roadmap Request demo with screen reader if possible Include accessibility requirements in contract

Key questions to ask vendors:

"Do you have a current VPAT?"
"What WCAG version and level do you conform to?"
"What's your accessibility roadmap for known issues?"

Procurement guide

2Report a Barrier

Reporting Accessibility Barriers

Found something inaccessible? Report it and we'll follow up.

Include in your report:

URL or location of the issue
What you were trying to do
What went wrong
Screenshots if possible

Report options:

We respond within2 business days.

Still not sure?

No worries!Email usand describe what you're trying to do. We'll point you in the right direction.

Quick jump to common scenarios