Our commitment

Accessibility Statement

AI Tool Hub is committed to ensuring digital accessibility for people with disabilities. We continually improve the user experience for everyone and apply the relevant accessibility standards.

Conformance status

AI Tool Hub aims to conform to WCAG 2.1 Level AA. These guidelines explain how to make web content more accessible for people with disabilities, and user-friendly for everyone.

The site was last audited for accessibility on July 24, 2026. We test with:

  • axe DevTools browser extension
  • WAVE Web Accessibility Evaluation Tool
  • Lighthouse Accessibility audit in Chrome DevTools
  • Manual keyboard navigation testing
  • Manual screen reader testing (NVDA on Windows, VoiceOver on Mac)

Current Lighthouse Accessibility score: 96/100. Last full audit: July 24, 2026.

Accessibility features

The site includes the following accessibility features:

Keyboard navigation

  • All interactive elements are keyboard accessible (Tab, Enter, Space, Arrow keys)
  • Visible focus indicators on all focusable elements
  • Skip-to-content link at the top of every page (visible on focus)
  • No keyboard traps

Screen reader support

  • Semantic HTML (header, nav, main, article, footer)
  • ARIA labels on all interactive elements without visible text
  • ARIA landmarks for major page sections
  • Form labels properly associated with inputs
  • Live regions for dynamic content (theme toggle, language switcher)
  • Alt text on all meaningful images (descriptive, not keyword-stuffed)
  • Decorative images marked with empty alt attributes

Visual accessibility

  • Color contrast ratios meet WCAG AA (4.5:1 for normal text, 3:1 for large text)
  • Dark mode and light mode both meet contrast requirements
  • Text resizes properly up to 200% without breaking layout
  • No information conveyed by color alone (icons + labels)
  • Focus indicators visible in both themes

Content structure

  • Proper heading hierarchy (single H1 per page, H2s for sections)
  • Lists use proper ul/ol markup
  • Tables have proper header rows and captions
  • Forms have associated labels and error messages
  • Landmarks (header, nav, main, footer) properly identified

Language support

  • Bilingual (English + Simplified Chinese) with proper lang attributes
  • hreflang tags for search engines
  • x-default for language negotiation

Motion and animation

  • Respects prefers-reduced-motion CSS media query
  • No essential content conveyed through animation alone
  • No flashing content that could trigger seizures

Known limitations

We are aware of the following accessibility issues and are working to fix them:

  • Some SVG icons may not be perfectly announced by all screen readers. We are adding aria-label and aria-hidden attributes as needed. (Target: Q3 2026)
  • The dark mode toggle currently does not announce the new state to screen readers. We are adding aria-live announcements. (Target: Q3 2026)
  • Some interactive elements in the homepage hero are keyboard-trapped in older versions of Safari. We are fixing the focus management. (Target: Q3 2026)

We track all known issues in our internal accessibility backlog. Issues are prioritized by severity (blocker, serious, moderate, minor) and fixed in order of priority.

Compatibility with assistive technology

AI Tool Hub is designed to be compatible with the following assistive technologies:

  • Screen readers: NVDA 2024+, JAWS 2024+, VoiceOver (macOS 13+, iOS 16+), TalkBack (Android 12+)
  • Voice control: Dragon NaturallySpeaking 15+, Apple Voice Control, Windows Voice Access
  • Screen magnification: ZoomText 2024, Windows Magnifier, macOS Zoom, browser zoom (up to 400%)
  • Switch control: iOS Switch Control, Android Switch Access
  • Eye tracking: Tobii Dynavox, EyeGaze

We test with the latest versions of these tools quarterly. If you find a compatibility issue, please email us.

How to report accessibility issues

If you encounter an accessibility barrier on AI Tool Hub, please let us know. We take all reports seriously and respond within 2 business days.

To report an issue, email accessibility@ai-tool-hub.example with:

  • The URL of the page where you encountered the issue
  • A description of the issue (what you were trying to do, what went wrong)
  • The assistive technology you were using (screen reader, voice control, etc.)
  • Your browser and operating system
  • Your contact information (optional, if you want a follow-up)

We aim to fix all reported issues within 30 days, depending on severity. We will follow up with you if you provide contact information.

How to request content in alternative formats

If you need any content on this site in an alternative format (large print, plain text, audio), email accessibility@ai-tool-hub.example with the URL and the format you need. We will provide it within 5 business days, free of charge.

Our accessibility team

AI Tool Hub accessibility is overseen by:

  • Lin Chen (Lead Reviewer) - accessibility@ai-tool-hub.example
  • External accessibility consultant: WebAIM (for quarterly audits)

The team is responsible for the accessibility roadmap, the quarterly audits, and the response to user reports.

Our accessibility roadmap

What we are working on in 2026:

  • Q3 2026: Fix the 3 known issues listed above, add skip-to-content link, improve color contrast on the homepage hero
  • Q4 2026: Add a high-contrast theme option, add a dyslexia-friendly font option, expand the screen reader testing
  • Q1 2027: Add full keyboard shortcuts for navigation (j/k for next/prev article, / for search, ? for help), add a text-only view of the homepage
  • Q2 2027: WCAG 2.2 Level AAA compliance for the top 20 pages

Formal accessibility policy

AI Tool Hub is committed to:

  1. Maintaining WCAG 2.1 Level AA conformance as a minimum, with the goal of Level AAA for critical pages
  2. Quarterly accessibility audits by an external firm (WebAIM)
  3. Fixing all reported accessibility issues within 30 days, with priority on blocker and serious issues
  4. Including accessibility in our editorial process - every new page is tested before publication
  5. Training all new team members on accessibility basics
  6. Reporting our accessibility metrics in our public changelog

Frequently asked questions about accessibility

Do you support screen readers?

Yes. We test with NVDA, JAWS, VoiceOver, and TalkBack. The site is fully usable with a screen reader. See the Known limitations section above for the 3 issues we are still working on.

Do you support keyboard-only navigation?

Yes. All interactive elements are keyboard accessible. The Tab key moves focus, Enter and Space activate buttons and links, Arrow keys navigate within components, Escape closes modals and menus. A visible focus indicator is shown on the currently focused element.

Do you have a high-contrast mode?

Not yet. We have a dark mode and a light mode, both of which meet WCAG AA contrast requirements. A dedicated high-contrast mode is on the Q4 2026 roadmap.

Can I use a screen reader to navigate the reviews?

Yes. The review pages are structured with semantic HTML (article, section, h2, h3) and ARIA landmarks, so screen readers can navigate by heading, by landmark, or by link. The FAQ sections are properly marked with summary/details elements.

Do you have captions for audio/video content?

We do not currently have audio or video content. If we add it in the future, we will provide captions and transcripts. This is a hard requirement for us.

More about our commitments

For our editorial process, see our editorial guidelines. For our scoring methodology, see our methodology. For the team, see our team page. For our monetization, see our advertise page.