Accessibility
What works, what has not been tested, and how to tell us.
An honest status page for accessibility: the features that exist today, the gaps we know about, and a direct route to report a barrier.
Last reviewed: August 15, 2026 · Next scheduled review: September 14, 2026
Where this stands
This is a progress statement, not a conformance claim. We have not completed an accessibility audit of the site, so we do not say Keiko meets WCAG or any other standard, and we make no claim about compatibility with a particular screen reader or assistive technology.
What follows is what the interface actually does today, what we know has not been checked, and how to tell us when something blocks you.
What is in place today
- Keyboard skip link and main landmark
- The first focusable element on every page is a Skip to content link that moves focus to the main content region, so keyboard users can pass the navigation.
- Visible focus indicator
- Interactive elements draw a two-pixel offset focus ring when reached by keyboard, using the same outline token across the site.
- Reduced motion
- Animated transitions are disabled when your system asks for reduced motion, and the navigation progress bar switches itself off entirely rather than animating.
- Document language
- The page declares English as its language so assistive technology selects the right pronunciation rules. Individual passages in other languages are not separately marked.
- Shared colour tokens with a contrast check
- Interface colours come from one shared set of semantic tokens rather than ad-hoc palette values, and an automated test computes contrast ratios for the core text and surface pairings in both themes.
- Named controls and larger touch targets
- Shared components such as the exam hub carousel carry explicit names and roles for assistive technology, announce changes politely, and use touch targets of at least 44 by 44 pixels.
What has not been done yet
There is no completed keyboard, zoom, reflow, contrast, or screen-reader baseline across the full set of routes — public pages, sign-in, account, practice, mock exams, the tutor, writing, the notebook, billing, consent, and error states. Until that baseline exists, individual features may work well while a specific flow does not.
We have not selected a formal conformance target, a supported browser and assistive-technology matrix, or published severity and response targets. No independent accessibility reviewer has assessed the site, and nothing here has been checked against the accessibility duties of any particular jurisdiction.
Two known limits are worth stating plainly: mathematical notation is rendered visually and we have not verified how it is spoken by assistive technology, and mock exams run to a fixed time limit that cannot currently be extended for an individual learner.
Reporting a barrier
If something stops you from studying, tell us — it is the fastest route to a fix and it is how the remediation list gets built. Use the contact form or write to support@keiko.study.
Helpful details, if you have them: the page address, what you were trying to do, what happened instead, and the browser, device, or assistive technology you were using. Please do not include health or disability information you would rather not share; we do not need a diagnosis to fix a barrier.
We cannot promise a response time or a fix date, and we will not tell you an issue is resolved until it has actually been changed and retested.
Review and corrections
This page is reviewed on the schedule above, and again after a material interface release, after a shared component change, and whenever an accessibility report comes in. If a statement here does not match what you experience, that mismatch is itself a correction we want.
Something on this page looks wrong, out of date, or does not match what you experience? Tell us and we will recheck it. You can also email support@keiko.study. Please leave passwords, payment details, and other people's personal information out of the message.