Accessibility Statement
AI Crawler Check (aicrawlercheck.com), run by the Horatos.ai agency, should work for everyone, including people who use a screen reader, a keyboard, voice control, screen magnification or high zoom. This page explains what we aim for, how we test it, what we know is not perfect yet, and how to tell us when something gets in your way.
The short version
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We test every release with automated checks and keyboard tests. Automated tools cannot find every problem, so we call our status partially conformant until a full manual audit with assistive technology users is done. If anything blocks you, email hello@aicrawlercheck.com and we will reply within five working days.
1. What we do
- Keyboard access. Every link, button, menu and tool works with a keyboard. A "Skip to main content" link is the first thing you reach with Tab. Focus is shown with a clear teal outline, and nothing you focus is hidden under the sticky header, the cookie banner or the help button.
- Structure. Pages use real headings in order, landmarks (header, navigation, main, footer), lists and table headers, so screen readers can move around quickly.
- Colour and contrast. Text meets the AA contrast ratio (4.5:1, or 3:1 for large text). Links in running text are underlined, so they do not rely on colour alone.
- Zoom and small screens. Pages reflow at 320 CSS pixels wide (the same as 400% zoom on a laptop) without sideways scrolling. Touch targets are at least 24 by 24 pixels.
- Motion. If your device asks for reduced motion, animations stop, including Scout, our mascot. Nothing flashes.
- Images. Informative images have text alternatives. Decorative images, including Scout, are hidden from screen readers so they do not add noise.
- Accessibility settings. The round button with the person icon, at the bottom left of every page, opens a settings panel: larger text (up to 150% on a computer, 130% on a phone), line spacing, a plainer font, high contrast, underlined links, a stronger focus outline, stopped animations and a big cursor. Drag the button to any side of the screen, as with AssistiveTouch on an iPhone, or move it with the arrow keys when it has focus. Your choices are saved on this device only and apply before the page is drawn, so there is no flash of the old style. Reset all turns everything off.
- Works without JavaScript. Articles, the bot directory and policy pages are complete in plain HTML. Interactive tools need JavaScript.
- Forms. Every input has a label, errors are described in text, and results are announced to screen readers.
2. How we test
Every release must pass these checks before it can be published:
| Test | What it covers | Pages |
|---|---|---|
| axe-core rules for WCAG 2.0, 2.1 and 2.2 A/AA | Names, roles, labels, ARIA, contrast, link purpose, language | One page of every template |
| Keyboard walk with real Tab presses | 2.4.1 Bypass Blocks, 2.4.7 Focus Visible, 2.4.11 Focus Not Obscured, 2.1.2 No Keyboard Trap | One page of every template |
| Target size and reduced motion | 2.5.8 Target Size (Minimum), 2.3.3 Animation from Interactions | One page of every template |
| Contrast in a real browser | 1.4.3 Contrast (Minimum) on rendered colours | 28 pages |
| Reflow at 320, 390 and 768 pixels | 1.4.10 Reflow, 1.4.4 Resize Text, font size floor | 24 pages |
| Structure audit | Landmarks, heading order, alt text, link names, duplicate IDs | Every page in the sitemap |
A template is a page layout we reuse, such as a bot profile or a blog article, so one page of each covers the same code as every page built from it.
3. Known limitations
We would rather tell you than have you find out the hard way:
- Downloaded reports. The PDF and spreadsheet exports from the GEO audit are generated in your browser and are not fully tagged for screen readers. The same results are on the page in accessible HTML.
- Release images. The summary images on the changelog repeat text that is already on the page. Their alt text is a summary, not a full transcript.
- Third-party content. Links to vendor documentation, Cloudflare and other sites go to pages we do not control.
- Manual testing. We have not yet completed a full audit with screen reader users (JAWS, NVDA, VoiceOver, TalkBack). Until we do, we do not claim full conformance.
4. Feedback and help
If a page or tool is hard to use, or you need information in another format, contact us:
- Email: hello@aicrawlercheck.com (subject "Accessibility feedback")
- Contact form
Please tell us the page address, what you were trying to do, and the browser and assistive technology you use if you are happy to share it. We aim to reply within five working days, and to fix confirmed barriers in the next release.
5. Technical details
The site is built with HTML, CSS and JavaScript, and relies on HTML and CSS for its accessibility. It is tested in current versions of Chrome, Edge, Firefox and Safari. The tests above run in an automated Chromium browser.
This statement was prepared on October 22, 2026 from our own testing, and is reviewed with every major release. See the changelog for what changed.
Getting around the site
Keyboard shortcuts and controls
| Key | What it does |
|---|---|
| Tab / Shift+Tab | Move forwards or backwards between links, buttons and fields. |
| Enter | Follow a link or press a button. |
| Space | Press a button, tick a checkbox or open a details section. |
| Escape | Close a menu, dialog or the help panel. |
| / | Jump to the search box on directory category pages. |
Making pages easier to read
- Zoom up to 400%: pages reflow to a single column without sideways scrolling.
- Turn on reduced motion in your operating system and animations stop, including Scout.
- Every article, directory page and policy works with JavaScript switched off.
- Expandable sections ("Test yourself", FAQs) are native HTML, so screen readers announce them as expandable.
Reporting a barrier
- Note the page address and what you were trying to do.
- Describe what got in the way and, if you can, the browser and assistive technology you use.
- Email hello@aicrawlercheck.com. The statement above explains how quickly we reply.
Accessibility features page by page
| Page type | What we do |
|---|---|
| Articles | Real headings, a table of contents, captions on figures, and FAQ answers in native expandable sections |
| Bot directory | Each bot is a list item with a heading, so screen readers can count and jump between them |
| Tables | Column and row headers, captions, and sideways scrolling on narrow screens |
| Tools | Labelled inputs, text error messages and results announced to screen readers |
| Case studies | Charts built as HTML lists with text values, not images of numbers |
Related: how AI engines choose their sources
Assistive technology we test with
- Keyboard only, in current Chrome, Firefox and Safari.
- Automated axe-core checks on every release, plus contrast and reflow checks at 320, 390 and 768 pixels.
- Zoom to 400% and reduced-motion settings.
Automated checks cannot find every problem, which is why we describe the site as partially conformant until a full manual audit is complete, as the statement above explains.
Accessibility and AI readability
Many of the practices that help people using assistive technology also help AI systems read a page: real headings in order, text alternatives for images, labelled controls, tables with headers and content that does not depend on JavaScript. When we improve one, we usually improve the other. That is one reason every article and directory page on this site is complete in plain HTML.
Keyboard shortcuts on this site
Every page starts with a skip link to the main content. The menu opens and closes with Enter and Escape, and focus returns to the menu button when it closes. Long articles have a table of contents you can reach by tabbing.
Motion and colour
Animations respect the reduced-motion setting in your operating system. Text colours are checked for contrast on every release, and information is never carried by colour alone: safety ratings, for example, always show the word as well as the colour.
Reporting a barrier
- Tell us the page address.
- Describe what you were trying to do and what happened.
- Mention the browser and any assistive technology you use.
Related: writing content AI engines can cite
Use the details on the contact page. We aim to reply within five working days and to fix confirmed barriers in the next release, which is then listed in the changelog.
Charts, tables and code on this site
Charts in our research are built as HTML lists with the values written out, so a screen reader reads the numbers rather than an image. Wide tables scroll sideways inside their own region and keep their headers. Code samples are real text in <pre> blocks, so they can be copied and read aloud.