LabRat targets WCAG 2.2 Level AA, supports keyboard and assistive-technology use where implemented, and provides a direct route to report barriers or request an accessible alternative.
Commitment and target
LabRat targets WCAG 2.2 Level AA for product-owned web and mobile interfaces and considers the European Accessibility Act requirements that apply to covered digital services. Accessibility is included in design, implementation, testing, and remediation work.
Current accessibility features
- Semantic headings, page titles, landmarks, labels, and a skip-to-content link on the public site.
- Keyboard-operable navigation and controls, visible focus treatment, and typed dialogs with focus management.
- Responsive layouts, bottom-safe-area scroll padding on mobile, and controls designed around at least 44-by-44-point targets.
- English and Simplified Chinese source copy, system text scaling support, and light/dark themes with semantic color tokens.
- Status is communicated with text in addition to color where product components expose state.
Known limitations
- AI-generated text, images, source pages, PDFs, and connected-provider interfaces may not meet LabRat’s accessibility target.
- Dense research tables and generated documents can require additional navigation or an alternative format.
- Some charts, previews, or third-party checkout surfaces may provide incomplete descriptions or keyboard behavior.
- Automated checks cannot identify every screen-reader, cognitive, motion, contrast, zoom, or voice-control barrier.
Feedback and accessible alternatives
If a LabRat screen, document, checkout route, or workflow prevents access, include the page or feature, device, browser or assistive technology, and the result you need. Do not include passwords, API keys, or unrelated personal information. LabRat will acknowledge the report and provide a reasonable alternative or remediation status where feasible.
Assessment and review
On July 11, 2026, a focused engineering audit covered representative public, legal, Web authentication, and Admin authentication surfaces using automated accessibility checks, semantic snapshots, keyboard navigation, focus behavior, and 320 CSS-pixel reflow. Detected contrast, heading-order, accessible-name, Skip Link focus, and Cookie-settings focus-return issues were corrected and the sampled routes passed the follow-up automated checks.
A formal third-party conformance audit and complete VoiceOver, TalkBack, voice-control, physical-device, generated-content, and provider-checkout audit have not been completed. This statement is reviewed after material UI, checkout, or assistive-technology changes and at least annually.