Our commitment
This statement applies to the AlloScribe website at alloscribe.com and the AlloScribe web app at app.alloscribe.com.
We want as many people as possible to be able to use AlloScribe, including people who use a screen reader, a keyboard, voice control or magnification. We aim to meet the Web Content Accessibility Guidelines (WCAG) version 2.2 at level AA.
How accessible AlloScribe is
The website uses one main heading per page with headings in order, text alternatives for images, a skip link to the main content, and controls that work with a keyboard. Animation is turned off when your device asks for reduced motion.
In the web app you can dictate instead of typing, and see live captions of what you are saying. We know that some parts of the web app are not yet fully accessible. They are listed below.
Known issues
- Report editor with a screen reader. In the web app, the rich text editor cannot be typed into while a screen reader's accessibility mode is active. We are working on a fix. In the meantime you can dictate the report, or contact us and we will help.
- History filters at some widths. Some filter chips on the History screen clip their labels at certain screen widths.
Feedback and other formats
If you need information on this website in a different format, such as large print or plain text, or if you find a problem that is not listed on this page, email hello@alloscribe.com.
Tell us the page or screen, what you were trying to do, and the device and assistive technology you use. We will reply within 5 working days.
Technical information
AlloScribe is committed to making its website and web app accessible.
Compliance status
The website and web app are partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the issues listed below.
Content that is not accessible
- The rich text editor in the web app cannot be typed into while a screen reader's accessibility mode is active. This may fail WCAG 2.2 success criteria 2.1.1 (Keyboard) and 4.1.2 (Name, Role, Value). We plan to fix this by [target date for editor fix].
- Some filter chips on the History screen clip their labels at certain screen widths. This may fail WCAG 2.2 success criterion 1.4.10 (Reflow). We plan to fix this by [target date for filter chip fix].
How we tested
This statement is based on our own testing of the website and the web app, including use with a screen reader and at different screen widths. Independent audit: [independent accessibility audit: date and auditor, or not yet carried out].
We will update this statement when we find or fix an issue.
Preparation of this statement
This statement was prepared on 10 October 2026. It was last reviewed on 10 October 2026.