Accessibility statement
RQAI wants Scribble to be usable with different devices, input methods and assistive technologies. The product aims towards WCAG 2.2 AA principles, but this launch statement is not a claim that every screen or user-created item already conforms.
What is supported
- Semantic headings, labels and native form controls across core flows;
- keyboard-operable navigation and controls, with touch targets designed for mobile use;
- light/dark/system themes and reduced-motion support in key animation surfaces;
- text alternatives for many interface icons and image alt-text editing;
- visible AI notices that do not rely on colour alone.
Known limitations
- Complex drawing, timeline, diagram, sticker and drag/reorder tools may not yet offer an equivalent experience for every keyboard or screen-reader user.
- User-created colours, media, interactives and exported content can fail contrast, caption or alternative-text requirements.
- Browser speech recognition and third-party provider interfaces vary by platform.
- Very small screens or high zoom may require additional scrolling in dense creative controls.
Help and feedback
If a barrier prevents access, email hello@rqai.co.uk with “Scribble accessibility” in the subject. Describe the screen, device/browser, assistive technology and the format or adjustment needed. Do not include passwords or provider keys. We will acknowledge the report and seek a reasonable alternative while investigating.
Ongoing work
Release checks include automated accessibility checks and targeted keyboard and responsive-layout testing. This does not replace a full independent WCAG audit. Drawing/timeline alternatives, focus management and screen-reader announcements remain priority areas for manual testing and improvement.