Accessibility

Accessibility Statement

Last updated: January 1, 2026

Our commitment

OmniResume aims to meet WCAG 2.2 Level AA. Accessibility is treated as a requirement, not a feature. Every interactive element is keyboard reachable, every form control has a label, every image has appropriate alternative text, and every animation respects the user's reduced motion preference.

Standards we target

• WCAG 2.2 Level AA
• Section 508 (United States)
• EN 301 549 (European Union)
• ARIA Authoring Practices for composite widgets

What we implement

• Semantic HTML landmarks: header, nav, main, section, article, aside, footer.
• Single H1 per page and logical heading hierarchy.
• Visible focus rings on every interactive element using :focus-visible.
• A skip-to-content link at the top of every page.
• Keyboard support for all controls, including modals, accordions, tabs, and the resume section list.
• Focus trapping inside modals, with Escape to close and focus returned to the opener.
• ARIA labels where native semantics are insufficient.
• ARIA live regions for autosave status, toast notifications, and form errors.
• Sufficient color contrast in both light and dark themes.
• Support for prefers-reduced-motion, which disables all non-essential animation.
• Support for prefers-color-scheme and a manual theme toggle.
• Form labels connected to inputs and error messages linked with aria-describedby.
• Touch target sizes of at least 44 × 44 pixels on mobile.
• No content that relies on color alone to convey meaning.
• Text resize support up to 200% without loss of content or function.
• Responsive layout that reflows correctly at 320 pixels wide.

Known limitations

The OmniResume design system and core flows are tested with keyboard-only navigation, screen readers (NVDA, VoiceOver, TalkBack), and automated tooling (axe, Lighthouse). Limitations we are aware of:

• PDF export depends on the browser's native print dialog. Print dialog accessibility is determined by the browser, not by OmniResume.
• Complex resume layouts with many sections may require extra keystrokes to navigate. We provide a section list with direct links to reduce this burden.
• Some third-party SVG illustrations may render differently across older screen readers. We provide text alternatives via aria-label or alt attributes.

How to report a barrier

If you encounter an accessibility barrier, please email a11y@omni-resume.pages.dev. Include the page URL, the assistive technology you are using, and a description of the issue. We aim to respond within two business days.

Assessment approach

We evaluate accessibility through a combination of automated tooling and manual testing. Automated: axe DevTools, Lighthouse, and WAVE. Manual: keyboard-only navigation, screen reader testing on NVDA (Windows), VoiceOver (macOS and iOS), and TalkBack (Android), plus visual review of contrast ratios and focus indicators.