Accessibility

This page reports what we have measured about TranscriptAI’s accessibility, including the parts that fall short. The figures below are produced by an automated check that runs on every build, so this page cannot describe a version of the product that no longer exists.

What is in place

Keyboard and focus behaviour: Dialogs, menus, tabs and comboboxes are built on Radix primitives, which manage focus trapping, focus return and the ARIA roles and states those patterns require.
Reduced motion: If your system asks for reduced motion, animations and transitions are switched off rather than shortened.
Increased contrast: If your system asks for higher contrast, borders are strengthened so component edges remain visible.
Text scaling and zoom: Layouts are built with relative units, so browser zoom and larger default text sizes reflow the page rather than clipping it.

What we measure, and what it currently says

Every screen in the application is scanned for interactive controls without an accessible name: the text a screen reader announces when you reach a field or button. A control without one is announced only as “edit text” or “button”, which tells you nothing about what it does.

748

screens and components scanned

578

form controls that do have a name, of 578 found

controls that still have no accessible name

How those break down

3Carries an id whose label we cannot resolve automatically (often correct)

What this page does not claim

This is not a statement of conformance to WCAG 2.1 or any other standard. We have not carried out a full audit against those success criteria, and we would rather say so than imply a level we have not measured.

The check behind the figures above has real limits, and they are worth stating plainly. It can tell whether a control has a name; it cannot tell whether that name is the right one: a label wired to the wrong field reads as correct to it. It does not assess colour contrast, focus order, reading order, error handling, or how any of this behaves with a real screen reader. Those need a person, and where a number here is zero, that means the automated check found nothing, not that nothing is there.

If something blocks you, tell us

If any part of TranscriptAI is unusable with the tools you rely on, we want the specific details: the screen, what you were trying to do, and the assistive technology and browser you were using. That is far more useful to us than a general report, and it is what turns a number on this page into a fix.

If you study or work somewhere that funds assistive technology and needs written information about this product’s accessibility, point them here and get in touch. We would rather answer directly than have anyone rely on a claim we have not measured.