Accessibility Statement

Last updated: August 1, 2026

same3le is being designed toward WCAG 2.2 Level AA accessibility. This is a continuing engineering goal, not a claim that every browser, device, and feature is fully conformant today.

Current accessibility features

• Semantic headings, labels, buttons, fieldsets, and status regions
• Keyboard-accessible controls and visible focus indicators
• A skip-to-content link
• Single-letter shortcuts replaced with modifier-key combinations
• Support for browser zoom and responsive layouts
• Reduced-motion handling when the device requests it
• Text alternatives for meaningful non-text interface elements
• Passive review that does not require microphone input

Known limitations

• Speech recognition support varies by browser and operating system.
• Lock-screen review is experimental and may not work consistently with assistive technology or background-audio restrictions.
• Browser-generated voice lists may contain unclear or duplicate voice names.
• Some dynamically announced study-state changes may behave differently across screen readers.
• The installed PWA experience may differ from the browser experience.

Testing approach

Before production subscription launch, the app should be tested with keyboard-only navigation, iPhone VoiceOver, Android TalkBack, at least one desktop screen reader, browser zoom at 200% and 400%, high-contrast settings, reduced motion, and automated accessibility tools. Automated tests do not replace manual testing.

Feedback

An active accessibility email and response process will be published before production launch. Reports should include the page, feature, device, browser, assistive technology, and a description of the barrier. Paid subscriptions should not launch until this contact channel is monitored.