Accessibility 101Popular

Your foundational guide to understanding digital accessibility—what it means, why it matters, and how to get started.

Reading time: 10 minutes

Pro tip:Already know the basics? Jump straight toGuides by Roleto find resources for your specific role.

Start here: 3 things you can do today

No expertise needed. Each action takes 5 minutes or less and makes a real difference.

Check your next document

Before sharing any Word or PowerPoint file, go toReview Check Accessibilityand fix the top issues.

5 min

How to use the checker

Try keyboard-only navigation

Put your mouse aside and Tab through a webpage. Can you reach everything? Is focus visible? This is how many users navigate.

3 min

Why keyboard access matters

Add alt text to an image

Right-click any image in a document or on your website. Add a brief description of what it shows. Screen readers announce this.

30 sec

How to write good alt text

What is digital accessibility?

Digital accessibility means designing and building websites, applications, documents, and digital content so thateveryone can perceive, understand, navigate, and interactwith them—regardless of ability or disability.

This includes people who:

Key insight:Accessibility benefits everyone. Captions help non-native speakers. Keyboard navigation helps power users. Clear content helps everyone under stress.

Why accessibility matters

Educational equity

Every student deserves equal access to course materials, learning platforms, and academic resources—without having to ask for special treatment.

Legal compliance

Title II of the ADA requires public universities to provide accessible digital experiences. Non-compliance results in complaints, lawsuits, and reputational damage.

Better design

Accessible design is better design. Constraints breed creativity, and inclusive products work better for everyone.

WCAG 2.2: The global standard

TheWeb Content Accessibility Guidelines (WCAG)are the international standard for digital accessibility. Arizona aligns toWCAG 2.2 Level AA.

WCAG is organized around four principles—often calledPOUR:

Principle What it means Example
Perceivable Content must be presentable in ways users can perceive Images have alt text; videos have captions
Operable Users must be able to operate the interface All features work with keyboard; no time limits without controls
Understandable Content and operation must be understandable Clear labels; predictable navigation; error messages explain fixes
Robust Content must work with current and future technologies Valid HTML; proper ARIA usage; compatibility with assistive tech

Explore WCAG 2.2 highlights

Title II and the April 2026 deadline

In April 2024, the U.S. Department of Justice published theTitle II Web and Mobile Accessibility Rule, requiring state and local government entities—including public universities—to make web content and mobile apps accessible.

Key deadlines for Arizona

  • April 24, 2026:All public-facing web content and mobile apps must conform to WCAG 2.1 Level AA
  • Internal systems:Must also meet accessibility standards
  • Archived content:Limited exceptions with specific criteria

Read the full Title II brief

Quick wins: Start here

You don't need to be an expert to make a difference. These five actions address the most common accessibility issues:

  1. Add alt text to images
    Describe what the image conveys. If it's decorative, mark it as such. If it's complex (like a chart), provide a longer description.
  2. Use real headings
    Don't just make text bold and big. Use Heading 1, Heading 2, etc. This creates a navigable structure for screen reader users.
  3. Write descriptive link text
    Instead of "Click here," write "Download the 2026 accessibility report (PDF)." Links should make sense out of context.
  4. Ensure color contrast
    Text should have at least 4.5:1 contrast ratio against its background. Use theWebAIM Contrast Checkerto verify.
  5. Add captions to videos
    Auto-captions are a start, but must be reviewed and corrected. Target 99% accuracy for educational content.

See the full Do/Don't guide

How to test for accessibility

Accessibility testing combines automated tools with manual review:

Automated testing

Tools likeaxe DevTools,WAVE, andAccessibility Insightscatch about 30-40% of accessibility issues—things like missing alt text, low contrast, and missing form labels.

Explore testing tools

Manual testing

Keyboard testing:Can you complete all tasks using only Tab, Enter, Space, and arrow keys?

Screen reader testing:Does content make sense when read aloud by NVDA, JAWS, or VoiceOver?

Remember:Automated tools are necessary but not sufficient. A page can pass all automated tests and still be inaccessible.

Common assistive technologies

Understanding how people use assistive technology helps you build better experiences:

Technology Used by How it works
Screen readers Blind and low vision users Reads content aloud and announces interface elements; navigates via headings, landmarks, and links
Screen magnifiers Low vision users Enlarges portions of the screen; users see only part of the page at once
Speech recognition Motor disability users Controls computer with voice commands; requires visible, named interface elements
Switch devices Users with severe motor disabilities Limited buttons to navigate sequentially; requires efficient keyboard navigation
Braille displays Deafblind users Converts text to refreshable braille; requires properly structured content

Learn more about assistive technology

Common myths debunked

Myth: "Accessibility is only for blind users"

Reality: Accessibility benefits people with many different disabilities—motor, cognitive, hearing, visual—as well as people using mobile devices, slow connections, or dealing with temporary situations like a broken arm or bright sunlight.

Myth: "Accessibility is expensive and time-consuming"

Reality: Building accessibility in from the start adds minimal cost. Retrofitting inaccessible content is expensive. The most cost-effective approach is to do it right the first time.

Myth: "No one with disabilities uses our site"

Reality: About 1 in 4 adults in the U.S. has a disability. Many disabilities are invisible. If your site is inaccessible, people with disabilities simply can't use it—so you wouldn't know they tried.

Myth: "AI/automation will solve accessibility"

Reality: AI tools help with some tasks (like generating alt text drafts), but human judgment is still essential. Automated testing catches only 30-40% of issues. Overlays and widgets that claim to "fix" accessibility often make things worse.

Learn from the source

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

Ready to dive in?

I know my role

Jump to resources tailored for students, faculty, staff, developers, and more.

Find resources for...

I'm not sure yet

Answer a few quick questions and we'll point you in the right direction.

Take the quiz

I need help now

Have a question or hit a barrier? We're here for you.

Get help