Our commitment, and where we’re still short.

Prism aims to be usable by everyone, including people with visual, auditory, motor, or cognitive disabilities. We design and build against the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, and use the specific practices below.

·Semantic HTML. Appropriate headings, landmarks, and ARIA roles. Interactive elements are keyboard-operable.

·Keyboard navigation. Prism is usable without a mouse. Focus states are visible. Tab order follows reading order.

·Screen-reader support. Primary workflows (writing an entry, reading a Mirror, managing settings) are tested with VoiceOver (macOS/iOS) and NVDA (Windows).

·Contrast. Body text is at least 4.5:1 against its background; large headings are at least 3:1. Our accent orange is used only for non-essential accents and links; links carry additional non-colour indicators.

·Zoom and reflow. Content reflows correctly at 200% zoom. Text is not clipped.

·Form labels. All form fields have associated labels; error messages are associated with their fields and announced to screen readers.

·Motion. Animation is minimal and respects prefers-reduced-motion. No autoplay, no parallax scrolling.

·Audio transcription. Voice input is transcribed by OpenAI Whisper and shown as editable text; you can always read and correct the transcript.

·Colour as meaning. We do not rely on colour alone to convey information.

We are honest about where we are not yet fully AA-compliant:

·The rich-text editor (Tiptap-based). Some formatting toolbar actions do not yet have full keyboard shortcuts or ARIA labels. Entries can still be created with plain text without using the toolbar.

·Weekly Mirror animations. Entry-list animations use subtle motion; we respect prefers-reduced-motion, but some browsers don’t honour that token correctly.

·Error recovery on unreliable networks. We are improving error messaging for offline/slow-network conditions, including better announcements to screen readers.

·Automated checks (axe-core, Lighthouse) run on every production build.

·Manual keyboard-only navigation is part of our release checklist.

·Manual screen-reader checks are done before major UI changes.

If you need any Prism content in an alternative format (large print, Braille, plain text), email us and we’ll arrange it.

Prism includes content delivered by our subprocessors (Stripe checkout, Resend email, Vercel hosting). Those third-party pages are subject to each provider’s accessibility standards. If you encounter an issue on such a page, please tell us and we’ll escalate.

If you encounter an accessibility barrier in Prism, please tell us — we treat it as a bug, not a feature request.

·accessibility@prismlens.net (preferred)

·support@prismlens.net

We aim to respond within 5 business days.