AudityxeAudityxe

Audit module

Website Accessibility Audit

What accessibility issues does Audityxe detect?

Audityxe's automated accessibility audit checks document language, form labels, button and link names, descriptive link text, image alt text, landmark regions, skip-to-content links, iframe titles, ARIA misuse, and keyboard-focus visibility — plus mobile viewport and zoom settings.

Automated checks catch only a portion of accessibility problems. A passing score does not mean a site conforms to WCAG; manual testing with assistive technology is still required.

What is checked

Accessibility

HTML-level accessibility signals.

  • Document language
  • Form labels
  • Button names and link names
  • Descriptive link text
  • Skip-to-content link
  • Image alt text
  • tabindex usage
  • aria-hidden misuse
  • Landmark regions
  • iframe titles
  • Keyboard focus visibility

Mobile Responsiveness

Viewport and touch readiness.

  • Viewport meta tag
  • Pinch-to-zoom not disabled
  • Responsive CSS
  • Apple touch icon
  • Theme color

UX / UI

Clarity and structure.

  • Above-the-fold CTA
  • Primary heading clarity
  • Heading nesting
  • Markup semantics
  • Form length
  • Placeholder text

How to run it

Web app: Paste a URL and open the Accessibility category.

Command line (see the CLI guide):

npx audityxe-cli https://example.com

Frequently asked questions

Does Audityxe certify WCAG compliance?

No. Audityxe runs automated accessibility checks and reports findings, but it cannot certify WCAG conformance. Manual review and assistive-technology testing are still required.

Does Audityxe test color contrast?

Real-browser contrast measurement comes from the Lighthouse accessibility category when the PageSpeed pass is enabled (Pro plan, or --psi-key in the CLI). The default HTML-level checks listed above do not compute rendered contrast.

Last reviewed against the Audityxe source code. Product names mentioned are trademarks of their respective owners; Audityxe is not affiliated with them.