How this directory is built for accessibility, published by AIXIS, LLC. The target is WCAG 2.1 Level AA.
No accessibility overlay runs here, and every page reads without JavaScript. Where a page falls short, the route to report a barrier is the same email that handles factual corrections.
Direct answer
Accessibility statement, in one paragraph
How this directory is built for accessibility, published by AIXIS, LLC. The target is WCAG 2.1 Level AA.
No accessibility overlay runs here, and every page reads without JavaScript. Where a page falls short, the route to report a barrier is the same email that handles factual corrections.
The target is the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. In practice that means a clear heading structure on every page.
Text meets contrast requirements against its background. Contrast gets checked, not assumed.
Controls can be reached and operated with a keyboard alone. Links say what they do in their own wording, images that carry information get real alternative text, and a reduced-motion preference set in your operating system is respected.
Accessibility statement at a glance
What this site is built toward
See below
Records are real tables, not pictures of tables
See below
Keyboard and screen-reader use
See below
No accessibility overlay
See below
Known limitations
See below
What automated checking cannot tell us
See below
Reporting a barrier
See below
How this statement is maintained
See below
What this site is built toward
The target is the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. In practice that means a clear heading structure on every page.
Text meets contrast requirements against its background. Contrast gets checked, not assumed.
Controls can be reached and operated with a keyboard alone. Links say what they do in their own wording, images that carry information get real alternative text, and a reduced-motion preference set in your operating system is respected.
Call these commitments about how the site is built, not a legal guarantee that every page meets every criterion at every moment.
Records are real tables, not pictures of tables
Every company, product, integration and comparison record is marked up as an HTML table, with header cells tied to their columns. A screen reader can announce which value belongs to which field, in order, one at a time, instead of reading the whole row as one undifferentiated wall of text with no way to tell a company name from a column header.
Wide tables scroll inside their own container. No sideways scroll on the page itself.
The page itself never scrolls sideways, and no column gets cut off at a narrow width or a high zoom level.
Keyboard and screen-reader use
The navigation, the search map, the glossary, the expandable questions and the evaluation tools all work from the keyboard. Each control carries a text label, never an icon alone.
Real labels, never guesswork. Icons alone never carry the meaning here, because a screen reader has nothing to read from a picture with no accompanying text.
Browser zoom and text resizing up to 200% should not hide content or cut off controls. Each page uses one main heading with nested subheadings, so a screen reader can skim a record instead of reading it end to end.
No accessibility overlay
No overlay, toolbar or widget runs on this site. Not one, anywhere on it.
Overlays get marketed as an instant fix, yet disabled users and assistive-technology vendors widely report them interfering with the screen readers, magnifiers and browser settings people already have configured. The approach here is to build the underlying pages correctly instead.
The same reasoning is why no consent banner traps your focus: the site sets no cookies to consent to.
Known limitations
The stack assessment and the RFP builder are the most interactive parts of the site, and so the most likely to carry a defect automated checking cannot see. Ask for their output by email, in plain text, if a tool itself is unusable for you.
Records link out to company websites, press releases and source documents built by other organisations. Pages like those sit outside this site's control and may not meet the same standard.
What automated checking cannot tell us
Automated checks catch common problems. Genuine usability is a judgment no automated check can make.
A record can pass every mechanical check and still be impossible to work through with a screen reader. Feedback from real use fills that gap, and it gets treated the same way as a factual correction: read, reproduced, and either fixed or answered with a reason.
Reporting a barrier
If any page, record, table, control or tool on this site is difficult or impossible to use, use the contact form, choose the Accessibility topic, and include the page address and what happened - what you were trying to do, what your assistive technology did, and what you expected instead. Reports get acknowledged within five business days, with either a timeframe for a fix or another way to get the information. Please leave sensitive personal information out of an accessibility report.
How this statement is maintained
Accessibility gets reviewed whenever the site's shared record templates or primary interactions change, not on a fixed calendar. A template change is what moves accessibility across thousands of records at once. This page was last reviewed on September 5, 2026, and gets revised when the site's structure changes materially, or when a reported barrier changes what can be claimed here.