Accessibility statement
Last updated November 3, 2026
Our commitment
ALIS should work for everyone, including people who use a keyboard, a screen reader, magnification or a switch device, and people who are sensitive to motion. We treat accessibility as a requirement for every release, not an extra.
This statement covers alisassessment.org, including the assessment, the chat, the dashboard and the pages around them.
The standard we follow
We build to the Web Content Accessibility Guidelines (WCAG) 2.2, level AA, on every page and component. WCAG 2.2 AA includes the 2.1 AA requirements that US courts and the Department of Justice point to under the Americans with Disabilities Act.
Conformance status
ALIS is partially conformant with WCAG 2.2 level AA. That means we meet most of the requirements, and some parts do not yet meet them or have not yet been verified.
We do not claim full conformance. Automated checks and our own review are not proof of compliance. We will not change this status until an outside accessibility expert has audited the site and we have fixed what the audit finds.
What we have done
- Automated checks on every change. Every page is tested in both themes with two accessibility rule engines, axe and IBM Equal Access. The checks also cover reflow at 320 pixels wide (400% zoom), text spacing, target size, focus that is never hidden, forced colors modes, and names for images, links and buttons.
- Keyboard testing. An automated check tabs through every page and presses every control. It fails on keyboard traps, lost focus, invisible focus and controls the keyboard cannot reach.
- Our own review. Alongside the automated checks, we test for compliance by hand on an ongoing basis. Our most recent full review of every page against WCAG 2.2 AA was on October 27, 2026.
- Animations you can pause. Pause animations stops every moving picture across the site. Signed in, it's in your account menu (off until you turn it on); otherwise it's the button beside the Light and Dark switch in the header and in the menu on phones. This device remembers your choice. If your device asks for reduced motion, animations don't play at all. The loading picture moves until the page is ready.
- Light and dark themes. Choose either with the theme button in the header. Both are checked for contrast.
Known limitations
These are the areas still in progress, and what happens next.
- Screen-reader testing is ongoing. We have a written test script for VoiceOver (macOS and iOS) and NVDA, and we are working through it now. We will publish the results here.
- PDF report accessibility is still under testing. The PDF does not yet have the tags, reading order and image descriptions that screen readers need. Each PDF is printed from your report's page in your dashboard, so with a screen reader, read the report there: it has the same content.
- Third party service restrictions. Payment checkout (Dodo Payments) and sign-in with Google or Discord are run by other companies, and how they are built is up to them. We test each one as it is connected to ALIS. The sign-in page also offers a link sent to your email, which works without either.
- Independent audit. An audit by an outside accessibility expert and a formal conformance report (VPAT) are planned before launch.
Compatibility
ALIS is designed for the current versions of Safari, Chrome, Firefox and Edge, on computers, phones and tablets.
The screen readers we are testing with are VoiceOver on macOS and iOS (with Safari) and NVDA on Windows (with Chrome or Firefox). Other systems are not supported at this time.
Tell us about a problem
If something on ALIS is hard or impossible to use, please tell us. Email support@alisassessment.org. Say which page you were on, what you tried to do, and what got in the way. Tell us which browser and assistive technology you use if you can. You do not need to explain your disability.
We aim to reply within 2 business days, and to tell you when we expect to fix the problem. If email and the contact page both get in your way, tell us how you would like us to reach you.
About this statement
This statement was written on October 28, 2026. We will update it after each audit, after screen-reader testing is recorded, and whenever a known limitation is fixed or a new one is found.
