Accessibility
Building a résumé tool more people can use
Latexy is working toward an accessible editing, compilation, and sharing experience. This statement reports what is implemented today and names the gaps that remain; it is not a claim of WCAG conformance or certification.
Current support
- Semantic page landmarks, headings, form labels, and a keyboard skip link.
- Visible keyboard focus and keyboard-operated primary application workflows.
- Text alternatives for status, validation, loading, and recovery states.
- Light, dark, and enhanced high-contrast application modes, including automatic detection of the operating-system contrast preference.
- An Atkinson Hyperlegible document-font option in the résumé design panel.
- Readable HTML text alternatives on public share links and portfolio résumés.
- No session-recording or keystroke-capture SDKs on document surfaces.
Known limitations
- Generated PDFs are not yet guaranteed to be tagged PDF/UA documents. Their text layer can be extracted, but that is not equivalent to a complete reading order and semantic structure.
- The Monaco source editor and embedded PDF viewer depend on browser and assistive- technology behavior outside our full control. Public output includes an HTML text alternative, but complex visual layout may not be represented in that text.
- Our named screen-reader test matrix is incomplete. We do not yet claim verified support for NVDA, VoiceOver, or TalkBack.
Accessibility support
If an accessibility barrier prevents you from using Latexy, email support@latexy.com with “Accessibility” in the subject. Include the page, task, browser, and assistive technology if you can. We aim to acknowledge accessibility reports within two business days and will provide a practical workaround when one is available.
Testing and updates
We combine automated accessibility checks, keyboard-only browser coverage, and manual review. We will update this page as screen-reader and output-format testing becomes reproducible. Last reviewed: September 8, 2026.