Skip to main content

Accessibility Statement

Last updated: 10 October 2026 · Target: WCAG 2.2 Level AA

1. Commitment

Advoke CV is built with accessibility as a design constraint, not an afterthought. Every interactive element is operable by keyboard, focus indicators are visible on light and dark backgrounds, motion respects user preference, and colour contrast targets WCAG 2.2 AA minimums.

2. What is implemented

Keyboard

  • A "Skip to main content" link is the first focusable element on every page.
  • Modals and drawers trap focus while open and restore focus when closed.
  • Tabs, accordions, dropdowns, and pagination respond to arrow keys, Home, End, Enter, Space, and Escape according to the WAI-ARIA Authoring Practices.
  • Section reordering is available through move-up and move-down buttons in addition to drag-and-drop, so drag is never the only way to reorder.
  • Global keyboard shortcuts in the editor (undo, redo, save) are mirrored by visible buttons.

Focus

  • A consistent 2px outline is drawn on every focused element via :focus-visible.
  • Focus ring colour is chosen to remain visible against light and dark backgrounds.

Colour and contrast

  • Body text meets a contrast ratio of at least 4.5:1 against its background.
  • Large text and non-text UI elements meet 3:1.
  • Colour alone is never used to convey information. Status indicators pair a coloured dot with descriptive text.
  • prefers-contrast: more and forced-colors: active are handled with explicit style overrides.

Motion and transparency

  • prefers-reduced-motion: reduce disables animations and transitions.
  • prefers-reduced-transparency: reduce removes backdrop blur from sticky headers.

Screen readers

  • Semantic HTML uses header, main, nav, footer, aside, section, and article landmarks.
  • Live regions announce toasts and status changes without moving focus.
  • ARIA attributes are limited to cases where native semantics fall short.
  • Form errors are associated with their fields and summarised at the top of the editor.

Forms

  • Every input has a visible or programmatically associated label.
  • Required fields are indicated in the label text, not only by colour.
  • Errors are announced via a polite live region and linked to their fields.

Touch

  • Interactive controls are at least 44 × 44 CSS pixels on mobile.
  • No critical editor function is available only on hover.

3. Known limitations

  • Right-to-left mirrored layouts are not supported in version 1.0. Unicode RTL text renders correctly inside fields, but the interface and templates remain left-to-right.
  • The resume preview is a visual representation. Users who cannot consume a visual layout can export a plain-text version of the resume from the Export dialog.
  • No third-party accessibility audit has been performed yet. Full conformance is not claimed until testing is complete.
  • Screen reader testing against NVDA, JAWS, VoiceOver, and TalkBack is pending.

4. Testing status

The design and code implement the target. Automated and manual testing has not yet been performed on a live deployment. Testing status is tracked in /reports/ACCESSIBILITY-AUDIT.md, where unperformed tests are marked NOT TESTED.

5. Reporting a barrier

If you encounter an accessibility barrier, please open an issue in the Advoke CV repository. Include the page URL or file path, the browser and assistive technology you used, and a description of the problem. Do not include personal resume content in the report.

6. Feedback loop

Accessibility reports are reviewed on the same cadence as other issues. When a barrier is confirmed, a fix is prioritised over new feature work.