Testing Web Pages for Accessibility

Our content management system, Omni Update / Modern Campus, has a built-in page check that catches accessibility issues before you publish a page.

But if you maintain a website outside of the main Binghamton website, you need to ensure that it is also accessible. There are a number of free automated tools to help check the accessibility of your wepbage. 

WAVE (Web Accessibility Evaluation Tool)

Developed by WebAIM, WAVE is one of the most intuitive tools because it provides visual feedback directly on the webpage.

Best For:

Visual learners, content editors, and quick page audits.

Key Features:

• Visual Overlays: Injects icons into your page to show exactly where errors (like missing alt text) or features (like ARIA landmarks) are located.
• Contrast Tools: A dedicated sidebar to check color contrast ratios and test "what if" color changes in real-time.
• Structure View: Displays the heading hierarchy to ensure the page follows a logical outline.

Availability:

Online Tool: Paste a URL at wave.webaim.org.

Extensions: Available for Chrome, Firefox, and Edge. Unlike the online tool, the extensions can test password-protected or local (intranet) pages.

Native Browser DevTools (No Installation Required)

Most modern browsers have sophisticated accessibility auditing built right into their "Inspect Element" consoles.

Alternative Accessibility Extensions beyond WAVE

If WAVE doesn’t catch everything, these industry-standard extensions are excellent additions to your toolkit. These are free, but some features may only be available in a paid version. 

axe DevTools (by Deque)

The axe DevTools extension is widely considered the industry standard for developers due to its "zero false-positive" philosophy. If axe flags an issue, it is almost certainly a real-world accessibility violation.

Browsers: Chrome, Firefox, and Edge.

Key Features:

• Automated Snippets: Highlights the exact piece of code causing the issue and provides a "Fix Share" link to send to teammates.
• Intelligent Guided Tests (IGT): (Available in Pro) Uses a wizard-like interface to help you manually test complex components like modals and menus that automated scans often miss.
• No False Positives: Designed to reduce "noise" so developers don't waste time chasing non-existent bugs.

Best For: Frontend developers who need a reliable, "no-nonsense" tool that integrates directly into the development workflow.

Accessibility Insights (by Microsoft)

Accessibility Insights is a powerful tool designed to help you solve accessibility issues before you ship your code. It focuses heavily on the user experience of people who navigate via keyboard.

Browsers: Chrome and Edge. (Also available as a standalone Windows/Android app).

Key Features:

• FastPass: A lightweight, three-step process that includes an automated check, a tab-stop visualizer, and a check for "needs review" items.
• Ad Hoc Tools: Provides specialized toggles to view the "Accessibility Tree," check for high-contrast issues, or see how a page looks without CSS.
• Visual Landmarks: Overlays the page with ARIA landmark labels (like main, nav, and footer) to ensure the page structure is meaningful to screen readers.

Best For: QA testers and developers who want a structured, guided path to verify keyboard navigation and ARIA implementation.

ARC Toolkit (by TPGi)

ARC Toolkit is a professional-level extension that mirrors the rules used by the enterprise-level ARC Platform. It is particularly known for its speed and how it handles complex page structures.

Browsers: Chrome, Firefox, and Edge.

Key Features:

• Structure-Specific Audits: Unlike tools that scan the whole page at once, ARC allows you to toggle specific tests (e.g., only check Images, or only check Headings).
• Visual Tab Order: One of its standout features is a "Tab Order" tool that draws a physical line on the screen showing the exact path a keyboard user takes through your site.
• Zeroing in on Elements: Clicking a result in the ARC panel instantly takes you to that specific line of code in the "Elements" tab.

Best For: Developers who want to isolate specific components or verify keyboard navigation flow.

IBM Equal Access Accessibility Checker

This is an open-source tool that provides a very structured, "step-by-step" approach to fixing issues. It is highly regarded for its clear remediation guidance.

Browsers: Chrome, Firefox, and Edge.

Key Features:

• Role-Based Views: You can filter results based on whether you are a Developer (who needs code fixes) or an Auditor (who needs to report compliance).
• "Checklist" Approach: It breaks down findings into "Violations," "Items to Review," and "Recommendations," helping you prioritize what to fix first.
• Exportable Reports: Easily generates spreadsheet or PDF reports, which is a lifesaver for documenting accessibility progress for stakeholders.

Best For: Teams that need to track compliance over time or require clear instructions on how to fix a specific WCAG violation.

Quick Reference Tool Comparison

Automatic Checkers only catch about 40% of accessibility issues

No automated tool can catch 100% of accessibility issues on a webpage. A tool might tell you an image has "alt text," but it can't tell you if that text actually describes the image accurately. Manual testing with a keyboard and screen reader is always recommended.

Resources for doing a manual accessibility check:

• WebAIM Quick Reference Guide: combines using WAVE and manual testing techniques.
• Manual Accessibility Testing: Learning module from web.dev

ITS can manually test your website

Submit an Accessibility Audit request.