Essential Accessibility Testing Checklist
Introduction
This is a quick, practical checklist for evaluating the accessibility of a web site or application. It focuses on the core areas that have the biggest impact on real users—people who navigate with a keyboard, rely on screen readers, zoom their displays, or need clear structure and contrast to understand content. Each item includes a simple “Do / Why / Check” format so you can review pages quickly and consistently.
Remember, the overall goal isn’t perfection; it’s all about progress, ensuring that your site or application is accessible by everyone.
Want to learn more?
All category headings in this checklist are linked to our A11Y Audio and technology accessibility glossary pages for further learning. You can also get more information and explore examples and techniques using the following direct links to each category in our comprehensive enhanced Web Accessibility Testing Guide.
- Alt text
- Captions
- Color contrast
- Duplicate links
- Focusable elements
- Form labels
- Headings
- Keyboard navigation
- Lists
- Magnification and reflow
- Meaningful Links
- Screen reader pronunciation
- Sign‑on and login pages
- Skip Links
Screen Reader Testing
Screen readers give you a direct sense of how blind and low‑vision users experience your site. You don’t need to be an expert—just open the screen reader, set your mouse or trackpad aside, and navigate using only the keyboard. Listen for clarity, order, and missing information. Even a few minutes of testing can reveal issues that aren’t visible on the screen.
Which screen reader should you use?
- For Windows, you can use Microsoft Narrator already part of Windows, or for a more robust testing experience, download the free NVDA screen reader.
For Mac and iOS devices, use Apple’s onboard VoiceOver screen reader. Finally, TalkBack is native to all modern Android devices.
Captions
Do: Provide accurate, complete captions for all videos.
Why: Captions give access to spoken content and important sounds.
Check: Are words correct, timed well, and include sound cues?
Color contrast
Do: Ensure text meets at least 4.5:1 contrast.
Why: Low contrast makes text unreadable for many users.
Check: Use a contrast checker; adjust colors if the text looks faint.
Magnification / reflow
Do: Zoom to 200–400% and confirm the layout still works.
Why: Many users enlarge text to read comfortably.
Check: Page reflows to one column and nothing overlaps or disappears.
Meaningful links
Do: Use short, descriptive link text that makes sense alone.
Why: Users often navigate by links out of context.
Check: Replace “Click here” with the actual destination or action.
Duplicate links
Do: Remove or merge links that go to the same place.
Why: Duplicate links create clutter for keyboard and screen reader users.
Check: Image + title linking to the same URL? Combine them.
Alt text
Do: Add short, purpose‑based alt text; mark decorative images as decorative.
Why: Screen reader users rely on alt text to understand images.
Check: Does every meaningful image have a brief purpose description?
Headings
Do: Use real headings in order (H1 → H2 → H3).
Why: Helps assistive tech users skim and navigate quickly.
Check: Does the page read like an outline with no skipped levels?
Lists
Do: Use real list formatting (bulleted/numbered).
Why: Assistive tech reads lists as structured groups.
Check: Avoid typing dashes or numbers manually.
Focusable elements
Do: Ensure all interactive items show a visible focus outline.
Why: Keyboard users need to see where they are on the page.
Check: Tab through—does focus move logically and stay visible?
Keyboard navigation (Including dropdown menus)
Do: Ensure all interactive elements—including dropdown menus—can be fully operated using only the keyboard.
Why: Many users cannot or do not use a mouse, and keyboard‑only access is essential for equal usability.
Check: Can users navigate, open, and operate all controls (including dropdowns) using Tab, Shift+Tab, Enter, Space, and Arrow keys?
Skip links
Do: Include a “Skip to main content” link at the top.
Why: Let keyboard users bypass repeated navigation.
Check: Press Tab on page load—does the skip link appear first?
Form labels
Do: Give every field a clear, programmatically linked label.
Why: Screen readers announce labels so users know what to enter.
Check: Click the label—does it activate the field? If not, correct it.
Sign‑on and login pages
Do: Ensure all login fields, labels, and error messages are fully accessible to screen readers and keyboard users.
Why: Inaccessible login pages can completely block users with disabilities from accessing your service.
Check: Can users complete the entire login process using only the keyboard with clear screen‑reader feedback?
Accessibility isn’t about checking boxes — it’s about making sure every person can use and enjoy what you build. This checklist gives you the essentials to spot common barriers quickly and fix them with confidence. Even small improvements make a meaningful difference for your entire audience, and each step you take helps create a more accessible web experience for everyone. The Technology Accessibility Team is always available for consultation on accessibility best practices and resources for faculty and staff. We look forward to working with you soon!