Skip to main content

Accessibility

Accessibility Statement

Effective June 11, 2026

Stacked Resume is committed to making our résumé-building service usable by everyone, including people with disabilities. We treat accessibility as ongoing work, not a one-time checkbox, and we welcome feedback when we fall short.

1. Our commitment

We aim to meet the spirit and the letter of the Americans with Disabilities Act (ADA) and equivalent laws, and our technical target is conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, the current best-practice standard for accessible web content.

2. Conformance status

We work toward WCAG 2.2 Level AA as we build and ship. We do not yet claim full, independently audited conformance, but we follow the guidelines as closely as we can and fix issues as they are found.

3. What we've built in

  • Semantic HTML and landmarks. Pages use standard header, navigation, main, and footer landmarks and a logical heading structure, so assistive technologies can navigate naturally.
  • Skip to content. A "skip to main content" link is the first focusable element on each page.
  • Keyboard navigation. Interactive controls are reachable and operable by keyboard. The résumé builder's drag-to-reorder lists include keyboard support, so you can move sections without a mouse.
  • Visible focus. Focused elements show a visible outline, so keyboard users can see where they are.
  • ARIA where it helps. We use ARIA roles and live regions to announce status updates (such as loading and saving states), progress indicators, and dialogs to screen readers.
  • Labelled forms. Form fields have associated labels, and validation errors are shown visually and surfaced to assistive technology.
  • Descriptive alternative text. Meaningful images include alt text; decorative graphics are hidden from assistive technology.
  • Color and contrast. Our palette was chosen with WCAG AA contrast in mind, and we avoid using color alone to convey meaning.
  • Resizable text. The interface uses relative units, so you can zoom or enlarge text in your browser without breaking the layout.

4. Compatibility

We design and test against current versions of:

  • Browsers: Chrome, Safari, Firefox, and Edge
  • Screen readers: VoiceOver (macOS, iOS), NVDA (Windows), and TalkBack (Android)
  • Mobile and desktop layouts

If you use an older or specialized assistive technology and run into a problem, please tell us (Section 6) and we'll do our best to help.

5. Known limitations

We try to be honest about where we fall short. As of the effective date above:

  • Drag-and-drop reordering. Reordering résumé sections supports the keyboard, but it may be less discoverable for screen-reader users than a simple list control. We are working to improve its announcements.
  • Rich-text editing. Some fields use a rich-text editor; its keyboard and screen-reader support depends in part on the underlying editor component and may not be perfect in every case.
  • Live preview. The live résumé preview is optimized for visual fidelity to the printed page and may not be fully described to screen readers. The underlying form fields remain the accessible source of truth for your content.
  • Exported PDFs. Exported résumés are generated for pixel-perfect print appearance and may not include a complete accessibility tag tree. If you need an accessible (tagged or plain-text) version of your résumé, contact us and we will help.
  • Third-party components. Some embedded third-party elements (such as the Cloudflare Turnstile bot-check on the contact form and Stripe checkout) are not fully under our control; we choose accessible options where they exist.

6. Feedback and getting help

If anything on Stacked Resume prevents you from completing what you came to do, we want to know, and we'll help you directly in the meantime.

To help us respond quickly, please include:

  • The page or feature where you ran into the problem (a URL helps)
  • What you were trying to do
  • What happened (or didn't)
  • Your device, browser, and any assistive technology you were using

We treat accessibility feedback as a priority and aim to acknowledge it within two business days.

7. Updates to this statement

We may update this statement as we improve the Service or learn about new issues. Material updates will be reflected by a new "Effective" date at the top of this page.

Related

This Accessibility Statement was prepared as a good-faith starting point and has not been reviewed by legal counsel or audited by an accessibility specialist. We recommend consulting an attorney or an accessibility auditor before relying on it for formal compliance.