Accessibility Statement

Our commitment, in plain terms

ALIM LTD, trading as RankX AI, wants everyone to be able to use this website, including people who navigate by keyboard, use a screen reader, magnify the page, rely on high contrast, or need motion reduced.

We do not claim full compliance with any standard. We aim at Web Content Accessibility Guidelines 2.1 level AA, we apply some WCAG 2.2 criteria as well, and we know we are not there everywhere. This statement tells you where we are, what we have actually verified and what we have not, because a statement that claims perfection is worth nothing to someone who has just hit a barrier.

Under the Equality Act 2010 we owe a duty to make reasonable adjustments where a practice puts disabled people at a substantial disadvantage, and that duty is anticipatory: it applies before anyone asks. We treat an accessibility defect as a bug, on the same list as any other bug, not as a request for a favour.

What this statement covers

In scope: the RankX AI marketing website at rankxai.com, including the documentation, the blog and the free tools.

Not covered by this statement:

• The application at app.rankxai.com. It is a separate codebase with a different interface, and it has not been assessed to the same depth. Saying so is more useful than extending a claim to cover software this statement’s authors did not audit. If you use the application and hit a barrier, report it the same way and we will treat it the same way.
• Third-party pages we hand you over to, such as Stripe checkout and Google’s permission screen. Their accessibility is theirs.
• Content on other websites that we link to.

The standard we measure against is WCAG 2.1 level AA, with the WCAG 2.2 target-size criterion (2.5.8) applied as well. Where European accessibility rules apply to online sales to consumers, we treat the same standard as our reference point.

What has been built to the standard

These are not aspirations. Each is a property of the code as it stands, and the last four are checked automatically on every build, so a regression fails the deployment rather than reaching you.

Keyboard and focus

• A skip to content link is the first focusable element on every page, so you do not tab the whole navigation before reaching the page.
• Every page has a single main landmark that the skip link moves focus to.
• Focus is always visible. The focus indicator is a 2px outline in a colour measured at 5.98:1 against white, offset so it never sits under an adjacent element. Nothing on this site removes a focus outline without replacing it.
• Interactive components are built from native HTML controls, principally radio groups and disclosure elements, rather than scripted widgets. That means arrow key navigation, Enter and Space behave the way your browser and assistive technology already expect.
• Every call to action is a real link or button with a real destination. There are no clickable elements that only respond to a mouse.

Structure and semantics

• One h1 per page, a flat heading outline and no skipped levels. This is enforced on every build.
• Every section of every page is named, so a screen reader’s landmark and region list is navigable rather than a list of anonymous regions.
• Data tables use real table markup with a caption and row and column headers, including the tables in these legal documents.
• Every image carries alternative text, and decorative graphics are hidden from assistive technology rather than given empty descriptions to trip over. This is enforced on every build.
• The page language is declared, and the content is entirely server-rendered, so nothing depends on JavaScript to be readable.

Colour, contrast and text

• Body text is set at 16px or larger and meets or exceeds the 4.5:1 contrast minimum. Primary text on the page background measures 16.9:1.
• The brand coral is never used as text on a light background. It measures 2.68:1 there and fails, so it appears only as a background with dark text on it, and a darker variant at 5.98:1 is used wherever the brand colour has to carry words.
• Nothing is communicated by colour alone. Status and selection always carry a shape, a label or a position as well.
• Text reflows without horizontal scrolling. Wide content such as a comparison table scrolls inside its own container, so the page itself never scrolls sideways.
• Fonts are self-hosted with matched fallback metrics, so text does not jump as it loads and remains readable if a font fails.

Motion and stability

• Nothing loops. Where a section demonstrates itself, it plays through once and then rests. There is no auto-rotating carousel anywhere on this site.
• Hovering or focusing pauses a demonstration, and clicking stops it permanently.
• Every animation is disabled under prefers-reduced-motion: reduce, and the resting state is the complete state, so nothing is hidden from anyone who turns motion off.
• Pages are built to move zero pixels as they load or as state changes. Space is reserved in the resting state, and the scrollbar gutter is held open so a short page cannot shift sideways.

Targets and input

• Primary buttons are at least 56px tall, comfortably above both the 24px WCAG 2.2 AA target-size minimum and the 44px AAA figure.
• Form fields have visible, associated labels, and error messages are linked to the field they describe so a screen reader announces them.
• Nothing requires a hover, a drag, a gesture or a timed response.

Known limitations

The honest section. These are the things we know about, in rough order of how likely you are to meet one.

1. No independent audit has been carried out. Everything above was verified by us, using automated checks in the build pipeline, manual keyboard testing and contrast measurement. No external accessibility auditor has reviewed this site, and no formal accessibility conformance report exists. An independent audit is planned; until it happens, treat this statement as a good-faith self-assessment.
2. Screen reader testing has not covered every combination. Testing has focused on keyboard operation and semantic structure rather than on exhaustive testing across NVDA, JAWS, VoiceOver and TalkBack. Behaviour that is correct in one may be awkward in another, and we will not know until someone tells us.
3. The simulated product interfaces are illustrations, and their screen reader experience is not equivalent to the visual one. Several pages show a mock dashboard or a mock AI answer to demonstrate what the product does. They are built from real markup, they are labelled as illustrative in visible text, and their meaning is also stated in the surrounding prose, which is the mitigation. But a complex simulated data display read linearly is not as useful as seeing it, and we do not claim otherwise. Nothing in them is information you can only get there.
4. The documentation section loads a second, third-party stylesheet. Our documentation runs on Fumadocs, which ships its own complete styling that loads after ours and overrides parts of it. We have corrected the specific problems this caused, but the underlying situation means the documentation section is not fully under our own design system’s control, and contrast or spacing there may differ from the rest of the site.
5. Tabbed sections use automatic activation and no manual mode. Our interactive sections are native radio groups rather than scripted tab widgets, which is a deliberate choice that makes them work without JavaScript. The accepted cost is that arrowing through options changes the panel immediately, and there is no focus-then-Enter alternative. This is a complete native pattern rather than a broken tab pattern, but if automatic activation causes you difficulty we would like to know.
6. A demonstration that plays once can finish before you reach it. The single-pass animations start when the page loads, so a section far down the page may already be at rest by the time you scroll to it. Nothing is lost, because the resting state is complete and every claim is always-visible text, but the demonstration itself may not be seen. The browser feature that would fix this properly is not implemented in any browser yet.
7. The bot protection widget is third-party. The free tools and the audit form are protected by Cloudflare Turnstile. It is invisible in normal use and is designed to be more accessible than an image puzzle, but if it presents you with a challenge you cannot complete, email us and we will run the check for you.
8. Some very long tables need horizontal scrolling on a narrow screen. They scroll inside their own container rather than moving the page, and every one has a caption and proper headers, but reading a five-column table on a phone is work.
9. The content management interface has not been assessed. It is a third-party administration panel used only by our own staff and is not reachable by visitors.

There is no audio or video content on this site, so there are no captions or transcripts to provide, and no PDFs, so there are no untagged documents.

How we test

Accessibility is checked at three points, and the first one is the reason the claims in section 3 can be stated as facts:

1. On every build, automatically. The deployment pipeline fails if a page has no h1 or more than one, if a heading level is skipped, if an image has no alternative text, if the page language is missing, or if a page renders without server-side content. A build that breaks any of those does not ship.
2. By hand, on every new page and section. Keyboard traversal, focus visibility, contrast measurement against the tokens, behaviour at 390px, 768px, 1024px, 1280px and 1440px, and a pass with reduced motion enabled.
3. In design. The design system itself carries the constraints: a fixed seven-state matrix for every interactive element, a rule that selection is never signalled by weight alone, a rule that nothing may change size when state changes, and recorded contrast measurements for every colour pairing.

Testing is done in current versions of Chrome, Firefox, Safari and Edge, on desktop and on iOS and Android.

Tell us when something does not work

If any part of this website is not accessible to you, please tell us. You do not need to explain why, quote a guideline, or use any particular words.

Email

[email protected]

What helps, if you can

The page address, what you were trying to do, what happened, and the browser and assistive technology you were using. Any one of those is better than none, and a one-line message is welcome.

What we commit to. We acknowledge within 2 business days. Within 10 business days we will tell you either that it is fixed, or what we are going to do and roughly when. If we cannot fix something quickly, we will offer another way to get what you needed, which may be as simple as a member of staff doing it with you.

If you need information from this site in a different format, ask. We will provide it in a format that works for you at no charge.

If you are not satisfied with our response

Tell us first, and give us the chance to put it right. If you are still not satisfied, you can get free, confidential advice from the Equality Advisory and Support Service, which is the body that handles discrimination enquiries in England, Scotland and Wales:

Equality Advisory and Support Service

equalityadvisoryservice.com

Telephone

0808 800 0082

In Northern Ireland, the Equality Commission for Northern Ireland performs the equivalent role. If you are in the European Union, your national enforcement body for the European Accessibility Act can also take a complaint about an online service sold to consumers.

This statement does not affect your rights under the Equality Act 2010 or any other law, and nothing in it, or in the Terms of Service, limits them.

Preparation and review of this statement

This statement was prepared on 18 August 2026. It was written by the team that builds the site, based on our own testing as described in section 5, and has not been externally reviewed.

We review it whenever a significant part of the site changes, and at least once a year. When the independent audit in section 4 happens, this statement will be rewritten around its findings, including anything it finds that we missed.

The website was designed and built by RankX AI with accessibility considered from the start rather than retrofitted, which is why the constraints in section 5 sit inside the design system rather than in a checklist at the end.