Dichiarazione di Accessibilità
Il nostro impegno e dove siamo ancora carenti.
Ultimo aggiornamento:
Il nostro impegno
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, Livello AA and use the specific practices below.
Cosa facciamo
·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.
Lacune conosciute
Siamo onesti su dove non siamo ancora completamente conformi ai livelli AA:
·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.
Come testiamo
·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.
Formati alternativi
Se hai bisogno di contenuti di Prism in un formato alternativo (stampa grande, Braille, testo semplice), scrivici via email e lo organizzeremo.
Contenuti e servizi di terze parti
Prism include contenuti forniti dai nostri subprocessori (checkout Stripe, email Resend, hosting Vercel). Quelle pagine di terze parti sono soggette agli standard di accessibilità di ogni fornitore. Se riscontri un problema su una tale pagina, comunicacelo e lo escaleremo.
Feedback e supporto
Se riscontri una barriera di accessibilità in Prism, comunicacelo — la trattiamo come un bug, non come una richiesta di funzionalità.
·accessibility@prismlens.net (preferred)
Miriamo a rispondere entro 5 giorni lavorativi.