Accessibility Checker FAQ — Your Questions Answered

General Questions About Accessibility Checkers

What is an accessibility checker?

An accessibility checker is a software tool that automatically evaluates websites, applications, or digital documents against established accessibility standards like WCAG 2.2. It scans for common barriers that may prevent people with disabilities from using your content effectively. The tool flags issues such as missing alt text, low color contrast, improper heading structure, and keyboard navigation problems, providing developers and content creators with actionable insights to fix them .

How does an accessibility checker work?

Accessibility checkers work by analyzing the underlying code and structure of a web page. They use rule engines like axe-core or HTML CodeSniffer to test against WCAG success criteria . The tool renders pages similarly to how a browser would, then evaluates elements against accessibility rules. Results are categorized by severity (critical, serious, or minor) and mapped to specific WCAG guidelines, making it easy for teams to prioritize fixes .

What is the difference between automated and manual accessibility testing?

Automated testing uses software to scan for code-level issues and can catch 30-40% of accessibility problems . It excels at identifying missing attributes, invalid ARIA, and common violations. Manual testing involves human evaluators using assistive technologies like screen readers to assess user experience, meaningful content, and complex interactions that automated tools cannot evaluate . A comprehensive accessibility strategy combines both approaches .

Can I scan my entire website at once?

Yes, many accessibility checkers offer full-site scanning capabilities. However, some tools are designed for page-by-page audits while you're working on specific content . For comprehensive coverage, look for tools that support crawling entire domains, including subpages and staging environments .

What is the difference between WCAG 2.1 and WCAG 2.2?

WCAG 2.2 is an extension of WCAG 2.1, adding nine new success criteria to address emerging accessibility needs. Key additions include requirements for focus indicators that are not obscured, minimum target size for interactive elements (24x24 CSS pixels), alternatives for dragging movements, accessible authentication, consistent help mechanisms, and redundant entry provisions . The update focuses particularly on users with cognitive disabilities, low vision, and motor impairments.

What does WCAG Level AA mean?

WCAG Level AA is the compliance target most courts, regulators, and organizations reference. It represents the standard for removing significant barriers to web accessibility, addressing the most common issues faced by people with disabilities . Level AA is what regulatory bodies like the U.S. Department of Justice require for ADA Title II compliance and what the European Accessibility Act (EAA) references .

Is my website legally required to be accessible?

Yes, if your business serves the public in the United States, the European Union, or Canada. Courts have consistently ruled that websites are places of public accommodation under ADA Title III . In 2024, the U.S. Department of Justice issued a final rule requiring state and local governments to comply with WCAG 2.1 Level AA by April 2026 . The European Accessibility Act became enforceable on June 28, 2025 .

What is the difference between ADA, Section 508, EAA, and AODA?

• ADA Title III applies to public accommodations (businesses open to the public) in the United States.
• Section 508 applies to U.S. federal agencies and organizations receiving federal funding.
• EAA (European Accessibility Act) applies to digital products and services sold in the EU market.
• AODA (Accessibility for Ontarians with Disabilities Act) applies to organizations operating in Ontario, Canada.

All four reference WCAG as the technical standard, with ADA Title II now requiring WCAG 2.1 Level AA .

How often should I scan my website for accessibility?

Every time you ship new code — or at minimum, with every build through CI/CD integration . Regular scanning helps maintain compliance and catch new issues early. Manual testing should happen before releases, when adding new features, and periodically (quarterly) for regression testing .

Can an accessibility checker guarantee my website is fully accessible?

No. Automated tools can only catch a subset of WCAG success criteria. A page with no automated findings may still have accessibility problems that require human judgment. If you need official certification or proof of compliance, that requires a qualified accessibility audit conducted by human experts .

Technical Questions About Scanning

What is authenticated scanning?

Authenticated scanning allows accessibility checkers to test pages behind login walls — areas like dashboards, portals, customer accounts, and checkout flows that public scanners can't access . The tool maintains a login session to crawl protected content, ensuring comprehensive coverage of user journeys that require authentication.

Can I scan staging environments?

Yes, most accessibility checkers support scanning staging and development environments. This is a best practice for implementing a "shift-left" approach, where accessibility is addressed early in the software development lifecycle rather than as an afterthought . Testing in staging helps catch issues before they reach production.

Why does my scan show different results from different tools?

Different accessibility engines use different rule sets and algorithms to detect issues. For example, axe-core and HTML CodeSniffer may highlight different aspects or assign varying severity levels to the same issue . This is why it's recommended to use multiple tools or select a comprehensive checker that combines multiple rule engines.

What causes scan errors like 403, 404, or 500?

Common scan errors include:

• 403 Forbidden — Your website may be blocking the checker's IP address (e.g., via Cloudflare or a firewall) .
• 404 Not Found — The URL entered may be invalid or the page doesn't exist .
• 500 Internal Server Error — A critical issue occurred on your site; try again after a few minutes .
• 503 Service Unavailable — Your website is temporarily unavailable .
• Timeout (504 or 30000ms) — Your website is taking too long to load .

How do I fix a "Your Website Is Blocking Our Tool" error?

If your website uses security technologies like Cloudflare or custom firewalls, it may block the accessibility checker from scanning. You can whitelist the tool's IP address using a custom header or disable the limitation temporarily. Check your hosting provider's documentation for firewall settings .

What is a sitemap and why does it help scanning?

A sitemap is an XML file that lists all pages on your website, helping crawlers discover and index content efficiently . Using a sitemap for scanning can significantly speed up the process because the checker doesn't need to crawl dynamically to find pages. This is particularly helpful for large websites .

Why are scan results sometimes cached?

Some accessibility checkers cache results to improve performance. In certain tools, you may need to resave a page or use a "clear issues" button to refresh the scan data . Caching can sometimes cause issues to persist even after you've fixed them. If you encounter this, try saving the page again or clearing the tool's cache .

Can I integrate accessibility scanning into my CI/CD pipeline?

Yes, many modern accessibility checkers support CI/CD integration, allowing you to run automated scans with every build. This "shift-left" approach ensures accessibility is addressed throughout development rather than as a final step . It helps catch issues early, reducing remediation costs and preventing compliance issues at launch.

Compliance & Legal Questions

What standards do accessibility checkers test against?

Most comprehensive accessibility checkers test against multiple standards, including WCAG 2.2, ADA Title III, Section 508, EAA (European Accessibility Act), and AODA. Results are cross-referenced to these standards, so you know exactly which regulations each issue affects.

What is the DOJ rule on ADA Title II?

In 2024, the U.S. Department of Justice issued a final rule requiring state and local governments to meet WCAG 2.1 Level AA standards for web content and mobile apps by April 2026 . This applies to all state and local government organizations, including public higher education institutions .

What is the European Accessibility Act (EAA)?

The European Accessibility Act (EAA) is an EU directive requiring digital products and services to be accessible to people with disabilities. It became enforceable on June 28, 2025 . The EAA covers e-commerce websites, banking services, e-books, electronic communications, and transport services sold in the EU market. Microenterprises with fewer than 10 employees and annual turnover ≤ €2 million are exempt from service requirements.

What are the penalties for accessibility non-compliance?

Penalties vary by regulation and jurisdiction. ADA lawsuits can result in settlements of $5,000 to $20,000 plus attorney fees for typical cases, with more complex cases settling for significantly more . EAA penalties vary by EU member state and can include fines, mandatory remediation, and restrictions on selling non-compliant products in the EU market.

What is a "conforming alternate version"?

A conforming alternate version is an alternative way to provide accessibility when it's not possible to make the original content directly accessible due to technical or legal limitations . However, people with disabilities should have equal access to content in the same place and same format whenever possible. Alternate versions are only allowed when there's a technical or legal limitation .

What exceptions exist for accessibility compliance?

The ADA Title II rule lists exceptions including archived web content, preexisting conventional electronic documents, content posted by a third party, individualized or password-protected documents, and preexisting social media posts . However, the use of exceptions is limited and must be carefully justified.

Can I use an accessibility overlay to become compliant?

No. Accessibility overlays offer limited, surface-level adjustments but do not address underlying issues in code, structure, or content . They often miss the majority of WCAG violations and can interfere with assistive technologies that users already rely on. In 2024, 25% of digital accessibility lawsuits involved websites that had accessibility widgets or overlays installed .

Are third-party components my responsibility for accessibility?

Yes. The precedent set by Payan v. Los Angeles Community College District (2021) indicates that organizations are responsible for third-party materials . If you use third-party components that aren't accessible, document the issues, report them to the vendor, and consider alternatives. If the component is essential, explore workarounds or custom implementations .

Remediation & Fixing Issues

What are the most common accessibility violations?

According to WebAIM data, common issues include missing alt text, insufficient color contrast, missing form labels, keyboard navigation failures, improper heading structure, and incorrect ARIA usage . Keyboard accessibility failures appear in 88% of lawsuits, followed by insufficient page landmarks (88%) and screen reader incompatibility (74%) .

What are AI-powered fixes?

AI-powered fixes provide copy-paste-ready code for each accessibility violation, cutting remediation time from hours to minutes. AI generates context-aware, WCAG-compliant code suggestions tailored to your framework (HTML, React, or Vue) . This allows developers to apply fixes without researching solutions from scratch.

How do I fix missing alt text?

Alt text should be concise (ideally no more than 150 characters), meaningful, and descriptive within the context of the page . For example, instead of "image of a dog," write "A golden retriever playing fetch in a park." Use a period at the end. For decorative images, use empty alt text (alt="") to hide them from screen readers.

How do I fix low color contrast?

Ensure text meets WCAG minimum contrast ratios: 4.5:1 for small text and 3:1 for large text (18pt/24px or 14pt/18.5px bolded) . Use tools like the WebAIM Contrast Checker to test your colors. Avoid common problematic combinations like red/green, red/blue, or blue/purple .

How do I fix heading hierarchy issues?

<p> Headings should follow a logical, sequential order without skipping levels . The most important heading is level 1 (<h1>), and the least important is level 6 (<h6>). Avoid skipping from <h2> to <h4> — this can confuse screen reader users navigating your content . Each page should have exactly one <h1> that describes the main topic . </p>

How do I fix keyboard accessibility issues?

Ensure all interactive elements are reachable and usable with only a keyboard. Users should be able to tab through links, buttons, and forms in a logical order . Focus indicators must be clearly visible and not obscured by fixed headers . Test your site by navigating with the Tab key only — no mouse allowed .

How do I fix missing form labels?

Every form field must have an associated label using the <label> element or aria-label attribute . Required fields should be clearly indicated with both color and text (like an asterisk) . Error messages must be specific and helpful, explaining how to fix the problem.

How do I fix descriptive link text?

Link text should clearly describe the link destination or purpose. Avoid generic text like "click here" or "learn more" — these are meaningless when read out of context by screen readers . For example, write "Read our accessibility guide" instead of "Click here to read our guide."

Business & Team Questions

Who should be responsible for accessibility testing?

Accessibility requires commitment from the entire organization :

• Designers focus on color contrast, navigation hierarchy, and keyboard-accessible interactions.
• Developers write semantic HTML and proper ARIA, and integrate automated testing into CI/CD pipelines.
• QA Testers leverage automated tools and perform manual testing with assistive technologies.
• Accessibility Experts translate regulations into actionable strategies and lead training sessions .

How do I prioritize accessibility issues?

Focus on issues by severity: Critical issues (blocking functionality) first, followed by Serious (major barriers) and Minor issues . Prioritize critical user paths (checkout, signup, core features), pages with highest traffic, and recently changed components . Automated testing provides a baseline; prioritize manual testing on the most important flows .

How long does an accessibility audit take?

Most audits take 5-10 business days depending on website size and complexity. A comprehensive audit combines automated scanning, manual code review, and user testing by people with disabilities . The deliverable includes a prioritized roadmap for fixes.

How much does accessibility remediation cost?

Costs vary by website size and current state. Proactive remediation typically costs $2,500-$10,000 for an audit plus $5,000-$20,000 for technical fixes . This is often comparable to or less than a single lawsuit settlement, which can range from $5,000 to $20,000 plus attorney fees . Investing in proactive compliance is cost-effective compared to litigation.

Should every team member know accessibility testing?

Developers should know basic keyboard and automated testing. QA should have deeper manual and screen reader testing skills. Having at least one accessibility specialist on the team — or access to one — helps for complex issues . Building accessibility knowledge across the organization creates a culture of inclusion.

How do I create an accessibility training program?

Effective training includes understanding WCAG principles, hands-on experience with assistive technologies, practical remediation exercises, and ongoing learning resources . Accessibility experts can lead training sessions and develop organizational standards to embed accessibility across teams . The "shift-left" approach emphasizes proactive inclusion from the start.

Start Testing Today

Still have questions? Our team of accessibility experts is here to help. Use our free accessibility checker to get started, or contact us for a comprehensive audit.