Scan Module For: Accessibility

Make your site easier for everyone to use. The Accessibility module runs 117 automated checks based on WCAG 2.2—the official guidelines for making websites accessible to everyone. It finds common problems like missing alt text, broken ARIA, low color contrast, and unclear link text. Automated testing can't catch everything, so BetaSweep also points out areas that need a person to review.

Accessibility Scan Module Details

  • Full-site Accessibility scan

    Scan your entire site, a single page, or a custom list of URLs. BetaSweep finds pages from your sitemap automatically, with options to exclude paths, filter by page type, or use a different sitemap for staging and localhost sites. No need to enter URLs or test pages one at a time.

    Because BetaSweep runs on your computer, you can scan localhost, staging environments, and other sites that aren't publicly accessible.

  • Run 117 automated accessibility checks

    Powered by axe-core, the same accessibility engine used by Microsoft, Google, and the U.S. government. Each issue is tied to a specific WCAG 2.2 rule and includes a plain-language explanation, tips, and guidance for fixing the problem.

    Every result includes the WCAG success criterion, affected HTML element, and axe-core rule, giving developers the technical detail they need to investigate and fix the issue.

  • Scan against WCAG 2.2 levels

    Choose Level A, AA, or AAA—three levels of accessibility requirements, from basic to the most demanding. Level AA is the most widely used standard and covers most accessibility requirements. Level AAA includes stricter requirements for organizations that want to go further.

  • Test both desktop and mobile

    Scan your site at both desktop and mobile screen sizes. Some accessibility problems only appear at certain screen sizes, such as issues with responsive layouts, hidden content, or mobile navigation.

  • Find image accessibility issues

    Find images that are missing alt text—a short description that tells people what an image shows. BetaSweep also finds alt text that uses the filename, repeats across multiple images, or doesn't correctly identify a decorative image. Good alt text helps people using screen readers understand your images.

  • Find color contrast issues

    Find text that's tough to read because it doesn't have enough contrast with the background. Contrast is the difference between the color of your text and the color behind it. Use the built-in color contrast adjuster to try different colors and see the WCAG contrast ratio right in the report.

  • Check links and navigation

    Find vague link text such as “click here,” empty links, missing skip links, and other problems that can make your site harder to understand or navigate. A skip link lets keyboard users jump past repeated navigation and get straight to the main content. BetaSweep also checks whether important navigation elements can be reached using a keyboard.

  • Check buttons and interactive controls

    Find problems with buttons, links, and other interactive elements that can make them difficult to use with screen readers or other assistive technology. This includes invalid ARIA attributes—extra code added to interactive elements to help assistive technology understand what they are and how they work.

  • Check headings and page structure

    Make sure your headings and page structure make sense. For example, if your main heading is followed by a level-four heading, you may be skipping important sections in between. A clear structure helps people using screen readers move through your content and jump straight to the section they're looking for.

  • Check tables for accessibility issues

    Find problems that can make tables difficult to understand with a screen reader, including missing or empty headers, incorrect header settings, and duplicate table names. Clear table headings help screen reader users understand which information belongs to each column or row.

  • Check forms and focus controls

    Find problems with forms and keyboard focus, including missing focus indicators and autocomplete information. A focus indicator is the visual outline or other sign that shows which link, button, or form field you're currently on when using a keyboard.

  • Check video and media accessibility

    Find videos with unverified captions and audio that starts playing automatically. Captions give people a text version of spoken audio, while unexpected sounds can be distracting or confusing. These issues can make your site harder to use for people with hearing, vision, or cognitive disabilities.

  • Check third-party content

    Check embedded videos, widgets, forms, and other content from third-party services for accessibility problems. Even when someone else provides the content, it's still part of your website experience and may still be your organization's responsibility.

  • Check accessibility best practices

    Go beyond formal WCAG violations with additional accessibility checks. These best practices can find problems that may not break a specific WCAG rule but can still make your site harder to use for people with disabilities.

  • Download and Share Actionable Reporting

    Prioritize issues by severity

    Every issue is rated Critical, Serious, Moderate, or Minor, so you can quickly see which problems need attention first.

    Get the details to fix each issue

    See the exact HTML element where an issue was found, along with the surrounding elements. Reports also include code snippets to help developers find and fix the problem in the page source.

    Identify issues needing manual review

    Automated testing can find many common accessibility problems, but it can't judge everything. BetaSweep separates clear violations from issues that need a person to review, such as whether alt text accurately describes an image or whether video captions are correct.