Accessibility
Accessibility statement.
This statement explains how elan1.ai is built to be accessible: the standard it aims for, the checks it runs, such as keyboard operation, visible focus, reduced motion and real tables, any known limits, and how to report a barrier so a person can fix it.
elan1.ai targets WCAG 2.2 Level AA. Here is what we built in, what we test, what we know is not yet right, and how to tell us.
01Our target
We want everyone to be able to read, operate and understand elan1.ai. The site is designed and built to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA.
Status: target, not yet independently audited. We test the site ourselves as described below. When an independent audit is completed, its result is summarised here.
02What we built in
- One heading 1 per page, landmarks, a skip link and breadcrumbs on every page except the home page.
- Every control works by keyboard, with a visible focus outline. Menus, tabs and accordions open instantly; nothing autoplays.
- Status is never shown by colour alone: every badge and marker carries a word.
- Text and controls meet AA contrast on every surface; links on ink use ember, at 7.2:1.
- Buttons, form controls and stand-alone links are at least 44 by 44 pixels, above the 24-pixel minimum in WCAG 2.2. Links inside a sentence follow the size of the text, as WCAG 2.2 allows.
- Forms have visible labels, errors beside the field and in a linked summary at the top, and no time limits.
- Motion runs once and stops. It respects your system’s reduced-motion setting, and the footer has a “reduce motion” switch of its own.
- Tables are real tables, and every diagram and console screenshot has a text alternative.
- Layouts reflow to 320 pixels wide and to 400% zoom without horizontal scrolling, except data tables, which scroll inside their frame.
03What we test, and how
| Test | How |
|---|---|
| Keyboard only | Every page, every interactive feature, without a mouse |
| Screen readers | NVDA with Firefox on Windows; VoiceOver with Safari on macOS and iOS; TalkBack with Chrome on Android |
| Zoom and reflow | 200% and 400% zoom; 320-pixel viewport |
| Contrast | Every token pair in the design system, on paper, bone and ink |
| Reduced motion | System setting and the site’s own switch; every motion has a static end state |
| Automated checks | axe-core on each template, as a first pass only — automated tools find a minority of issues |
04Known limits
We know of these limits today, and list them so you are not surprised:
- Console screenshots are images. Each has a caption and numbered notes in text, but small interface text inside the image is not readable by a screen reader.
- Some interactive specimens, such as the proof-record inspector, present dense monospaced data. Every field has a name and tooltip in text; we are still improving how they read aloud.
- PDFs in the library may not be fully tagged. If one does not work for you, ask and we send the content in a format that does.
- Docs and the status page are separate sites and may not meet this statement.
- The site has not yet been independently audited.
05Tell us about a barrier
If something on elan1.ai does not work for you, tell us through the contact form or write to elango@elan1.ai. Say which page and what happened; we reply within 2 working days and, where we can, send the information in a format that works for you.
06Standards and law
This statement refers to WCAG 2.2 (W3C Recommendation). In India, the Rights of Persons with Disabilities Act, 2016 and the Guidelines for Indian Government Websites point to the same standard family. elan1 does not claim certification against any of them.
// A BARRIER?
Tell us what didn't work.
Name the page and what happened. A person reads it and replies.