One standard: this site, the app, and Studio.
WCAG 2.2 level AA is the bar, and the rules live in the design system rather than in whoever builds a screen. A build fails when a color pair, a spacing value or a type size breaks one.
Accessibility work in a martial arts school is not hypothetical. A parent signs a waiver on a phone in a parking lot. An instructor checks students in one-handed under bad lighting. A student in their fifties reads the curriculum at 200% text size. Those are the people these rules are for.
Checked before it ships, not after
Contrast is computed, not judged by eye
Every text color is checked against every surface it is allowed to sit on before it ships. On this site body text is 14.73 to 1 against the page and muted text is 4.76 to 1, against a required 4.5 to 1.
Controls are sized for a thumb
Buttons, menu items and form controls on the public pages are at least 44 by 44 pixels, with space between them so two neighboring controls are not one mistake. A link inside a sentence takes the size of the text around it, which the standard allows.
System fonts, and your zoom works
Body copy is set in the font your device already uses, at 15 to 16 pixels. When you zoom the browser the layout reflows, instead of clipping or scrolling sideways.
Reduced motion is respected here
If your system asks for less motion, transitions on this site stop. Nothing on these pages moves, flashes or plays on its own in the first place.
A visible focus ring, in a sensible order
Every control can be reached by keyboard, and shows a two-pixel ring when it has focus. On the dark blocks the ring flips color to stay visible. A skip link is the first thing in the tab order.
Real headings, real landmarks, real tables
One page heading, then levels in order. One main region, one navigation region. Comparison tables are real tables with row and column headers, and a wide one scrolls inside its own region that a keyboard can reach.
Color is never the only signal
A yes, a no and a partial in a comparison table each carry a mark and a written label, not just a color. Images carry alt text that says what they show, and decoration is hidden from screen readers instead of being announced.
Everything you read is a readable size
The 11-pixel size is reserved for short section labels of a few words, and 12 pixels for a status tag. Everything you actually read is 13 pixels or larger, and most of it is 15 or 16.
What we have not finished
These are the things we would tell you on a call, so they are on the page instead.
No independent audit yet
Konjo has not been through a third-party accessibility audit and does not publish a VPAT. What is on this page is our own testing against WCAG 2.2 AA, and it is written by the person who built the software.
The mobile app has had no audited screen-reader pass
Almost every control in the app is labeled for a screen reader. But nobody has walked the app end to end with VoiceOver or TalkBack and signed it off. Where a label alone would not explain a button, the extra hint is still missing.
Large text sizes are not fully tested
The app scales text with your system setting and never turns scaling off. Not every screen has been checked at the largest sizes, where 15-point body text becomes about 46 points. Fixing that is a known piece of work.
Reduced motion is partial in the app
Most screens in the app still animate even when your system asks for less motion. Nothing flashes, and no animation lasts longer than a moment, but the setting is not yet respected everywhere.
Charts in Studio owe a table view
The design system requires every chart to offer the same numbers as text, so a chart is never the only way to get a fact. That rule is not yet met by every chart that has shipped.
If something blocks you, tell us
An accessibility problem is a bug, and it goes to the front of the queue with the others that stop someone using the product. Email galen@getkonjo.com and say what you were trying to do, the page or screen you were on, and the assistive technology, browser or device you were using. A person reads it — the one who writes the code — and you will hear what happened to it.
If you need something on this site in another format — large print, or plain text a screen reader handles better — ask, and it will be sent to you.
Last reviewed Sep 5, 2026.
Ask what this means for your school.
If a student, a parent or an instructor at your school needs something this page does not promise yet, say so on the call. The person answering is the one who writes the code, so you get a date or a no rather than a maybe.
The terms the product runs under are in the privacy policy and the terms of service.