Automated accessibility tools are a useful first step, but they can’t catch every issue—particularly those affecting keyboard navigation, screen reader behavior, or overall user experience for people with disabilities. That’s where manual testing becomes essential.
By manually testing your content—using keyboards, screen readers, and other assistive technologies—you gain valuable insight into how real users interact with your site. This ensures your website is not only compliant with accessibility standards, but also inclusive and truly user-friendly.
Explore how users who use assistive technologies experience the web—and learn how to design with them in mind.
Try a Quick Keyboard Test
Some users interact with technology using only a keyboard—no mouse. Test your interface the same way: put the mouse aside and navigate using just the keyboard. Use these keys to move through all interactive elements (like links, buttons, and form fields):
Tab– To move forwardShift + Tab– To move backwardEnter/Return– Follows a link, activates (presses) a buttonSpacebar– Toggles checkbox values, activates buttonsArrow Keys– Scrolls content, moves/selects radio buttons within a group, sometimes moves between interactive menu items or tab panels.
What to Look For:
- Can you see where the focus is?
- Each element should show a visible focus indicator (like a border or color change) when selected.
- Is the indicator easy to see and does it have good contrast with the background?
- Can you reach everything?
- All interactive elements—links, buttons, menus, and form fields—should be accessible with the keyboard alone.
- Is the navigation order logical?
- Focus should move in a sensible order, usually top to bottom and left to right.
Keyboard testing is a quick but powerful way to uncover accessibility barriers that automated tools miss. It helps ensure your content is not only technically compliant, but also takes a meaningful step toward a more inclusive and user-friendly digital experience for everyone.
Use Desktop Screen Readers
Explore how screen reader users interact with content on both Windows and macOS. Use keyboard commands and gestures to navigate and understand the structure of a page.
Windows
- JAWS (Job Access With Speech): A widely used commercial screen reader with extensive capabilities for navigating and interacting with digital content using speech and Braille. JAWS requires a paid license, but MU provides free licenses for students, faculty, and staff.
- NVDA (NonVisual Desktop Access): A powerful, open-source screen reader for Windows, NVDA is widely used for both everyday access and accessibility testing. It supports speech and Braille output and offers many of the same features as commercial tools like JAWS—at no cost. Maintained by an active global community, NVDA is an excellent option for developers and testers ensuring screen reader compatibility.
macOS
- VoiceOver: Apple’s built-in screen reader, available on all Macs running the MacOS. VoiceOver supports speech, Braille, and gesture-based navigation, making it an essential tool for both users and accessibility testing on Apple platforms. Since it’s included at no extra cost with all Apple devices, it’s a widely available option for testing screen reader compatibility across iOS and macOS environments.
Evaluation Resources
- Harvard’s Getting Started Testing with JAWS
- Step-by-step guidance on using JAWS to test web accessibility, including keyboard shortcuts and common testing workflows.
- Harvard’s Getting Started Testing with NVDA
- A practical guide to using NVDA for accessibility testing, with tips for setup, navigation, and troubleshooting.
- Harvard’s Getting Started Testing with VoiceOver
- Instructions for using VoiceOver on macOS for accessibility evaluation, including navigation commands and testing tips.
Try Mobile Assistive Technologies
Mobile accessibility is just as important as desktop. iOS and Android devices include powerful built-in tools that allow developers and testers to evaluate mobile content for users with visual impairments.
Built-in Screen Readers
iOS: VoiceOver
VoiceOver is Apple’s built-in screen reader for iPhone and iPad. It provides gesture-based navigation, speech feedback, and Braille display support.
Helpful Links:
Android: TalkBack
TalkBack is Android’s screen reader, offering spoken feedback, Braille support, and gesture navigation.
Helpful Links:
Best Practice: For the most accurate Android testing, use a Google Pixel device. Pixels run the latest Android versions with up-to-date TalkBack features and no manufacturer modifications.
Zoom & Magnification
Users with low vision often rely on screen magnification and zoom features in addition to screen readers.
iOS
- Using Zoom on iPhone or iPad
- Enable full-screen or window zoom using double-tap and drag gestures.
Android
- Use Magnification on Android
- Temporarily zoom in anywhere on the screen using built-in gestures.
Developer Tip: Don’t Disable Zoom
Disabling zoom creates barriers for users with low vision or visual impairments. Always allow pinch-to-zoom, unless your design includes built-in, accessible scaling features.
To keep your content accessible:
- Do Use: <meta name=”viewport” content=”width=device-width, initial-scale=1″>
- Sets the page to match the device’s screen width and allows users to zoom.
- Avoid Using: <meta name=”viewport” content=”user-scalable=no, maximum-scale=1″>
- Prevents users from enlarging content and creates significant accessibility issues.
Restricting zoom prevents users from enlarging content, making it difficult—or impossible—for some people to read or navigate your site. It also fails to meet WCAG 2.1 standards. Learn more about the viewport meta tag on MDN.
Need Help?
Manual accessibility testing provides a thorough and accurate understanding of how accessible your digital content is to all users. For additional support or guidance, contact the IT Accessibility Center at itaccessibility@missouri.edu.