Skip to main content
Accessibility

Accessibility Statement

Last reviewed September 10, 2026

Automated rule testing

axe-core runs against the public pages, an RTL locale, the mobile navigation, the signed-in application screens, and all 23 résumé templates rendered against every accent colour.

Scripted keyboard and focus testing

Every focusable control is checked for a visible focus indicator, no keyboard traps, modal focus containment and release, and that focus is never hidden behind sticky page furniture.

Structure testing

Landmarks, heading order, form-label association, unique element identifiers, and accessible names are asserted on every build.

EliteResume is committed to making our service usable by everyone, including people who navigate with a keyboard, a screen reader, screen magnification, or speech input. This statement explains the standard we hold ourselves to, how we test against it, what we know is not yet fixed, and how to reach us if something blocks you.

Conformance status

EliteResume aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Based on our own assessment, the service is conformant with WCAG 2.2 level AA, with the exceptions listed under “Known limitations” below. “Conformant” means the content meets the standard; the exceptions describe the parts where we cannot yet make that claim.

Standards this covers

WCAG 2.2 AA is the common denominator for the regimes that apply to us, so meeting it addresses all of them:

  • EN 301 549 / European Accessibility Act (Directive (EU) 2019/882)
  • Americans with Disabilities Act (ADA) Titles II and III
  • Section 508 of the US Rehabilitation Act
  • AODA Integrated Accessibility Standards Regulation (Ontario)
  • Accessible Canada Act (ACA)

What this statement covers

This statement applies to the EliteResume web application at eliteresume.net, including the marketing pages, the sign-in and account flows, the résumé and cover-letter editors, the job tracker, and every résumé template we ship.

  • Content you create. The text, images and profile photos you put into your own résumé are yours; we cannot guarantee that they meet the standard. Our editor and exported documents will not degrade what you provide.
  • Third-party services. Payment pages hosted by our payment provider and sign-in screens hosted by identity providers are outside our control; we monitor their published conformance.
  • Reference-request flow. Pages sent to a referee are published in English only and are marked as such in the page markup so assistive technology pronounces them correctly.

How we test

Accessibility is checked automatically on every change, not once a year. Our continuous integration pipeline fails the build when any of the following regress:

  • Automated rule testing. axe-core runs against the public pages, an RTL locale, the mobile navigation, the signed-in application screens, and all 23 résumé templates rendered against every accent colour.
  • Scripted keyboard and focus testing. Every focusable control is checked for a visible focus indicator, no keyboard traps, modal focus containment and release, and that focus is never hidden behind sticky page furniture.
  • Layout and text testing. Pages are verified to reflow at 320 CSS pixels, to survive 200% zoom without horizontal scrolling, and to lose no content under the WCAG text-spacing overrides.
  • Structure testing. Landmarks, heading order, form-label association, unique element identifiers, and accessible names are asserted on every build.

We test with recent versions of Chrome, Safari (WebKit) and their mobile equivalents.

This is a self-assessment. It has not been audited by an independent third party.

Known limitations

We would rather name these than leave you to discover them:

  • No published screen-reader test report. Our checks verify what is exposed to the accessibility tree — roles, names, states and announcements — but we have not yet completed and published a manual test pass with NVDA, JAWS and VoiceOver. That work is scheduled.
  • Judgement-based criteria. Automated checks cannot decide whether alternative text, headings or error messages are meaningful. We review these by hand during design review, but they are not machine-verified.
  • Administrative console. Our internal admin tools meet the same structural requirements but are not covered by the full test suite and are available in English only.
  • Editor-uploaded media. Video uploaded to our blog by editors may lack captions until the editor supplies them.

We do not claim a disproportionate-burden exemption for any part of the service.

Tell us about a barrier

If any part of EliteResume blocks you, please tell us — including the page address, what you were trying to do, and the browser and assistive technology you were using. We treat these reports as defects, not feature requests.

Email: accessibility@eliteresume.net

Our commitment

We acknowledge every report within 5 business days and give you a fix or a timeline within 20 business days. If you need information that is currently inaccessible, we will provide it in an alternative format at no cost.

Contact support

If we do not resolve it

If our response does not satisfy you, you can escalate:

  • European Union — contact the national enforcement body for the European Accessibility Act in your country of residence.
  • United Kingdom — the Equality Advisory and Support Service (EASS).
  • United States — the Civil Rights Division of the US Department of Justice under the ADA, or the relevant federal agency under Section 508.
  • Canada — the Accessibility Commissioner (federal) or the Ontario Ministry responsible for AODA compliance.

About this statement

Prepared using a self-assessment of the service against WCAG 2.2 level AA, supported by the automated and scripted test suite described above.

This statement was first published on 6 August 2026.

It is reviewed whenever the test suite changes materially, and at least once every 12 months.