Web accessibility statement

Last Revised: May 28, 2026

Propelus EverCheck® is a Propelus service. We want our platform to work for everyone who
uses it, including people who rely on assistive technology. This statement explains where we
stand on accessibility, what we’ve done, and what we still owe.

Conformance status

Web Content Accessibility Guidelines (WCAG) define three conformance levels: A, AA, and
AAA.

EverCheck (evercheck.com) is partially conformant with WCAG 2.1 Level AA. “Partially
conformant” means parts of the site meet the standard and parts do not yet.

 We build every new page and feature to WCAG 2.1 AA. We are working on updating older
parts of the platform on a planned, phased approach schedule.

What we do

  • Build new pages and features to WCAG 2.1 AA.
  • Include accessibility requirements into how we plan and release new functionality.
  • Train our product, design, and engineering teams on accessibility.
  • Test new features for accessibility before release.
  • Cover accessibility in design reviews and acceptance criteria.
  • Keep a roadmap for fixing issues in older parts of the platform.

Known limitations

We’re not done. Here is what we know is not fully conformant yet, and what we’re doing about it.
Area Issue What we’re doing
Legacy pages Some older pages have low color contrast, missing alt text on images, or partial keyboard support. Being remediated as part of our accessibility roadmap.
Older PDFs and reports Exports generated before our accessibility push may not work well with assistive technology. New reports are built with accessibility in mind. Older documents are available in accessible formats on request.
Third-party components Some embedded components from outside vendors don’t fully meet WCAG 2.1 AA. We report issues to vendors and evaluate accessibility as a factor in vendor selection.
Complex data tables Some legacy data tables lack proper header markup, which makes screen reader navigation harder. Fixed in new builds. Older views are being updated as we get to them.

Technical specifications

EverCheck’s accessibility depends on these technologies working with your browser and any
assistive tools you use:

  • HTML5
  • CSS3
  • JavaScript (ES6+)
  • Web Accessibility Initiative – Accessible Rich Internet Application (WAI-ARIA)

EverCheck is designed to work with:

  • NVDA and JAWS, on Chrome or Firefox (Windows).
  • VoiceOver, on Safari (macOS and iOS).
  • TalkBack, on Chrome (Android).
  • Keyboard-only navigation using standard browser focus.
  • Browser zoom up to 200% on all new pages, without losing content or functionality.

Tell us if something’s broken

If you hit an accessibility barrier on EverCheck, or anything is hard to use, we want to hear
about it. Contact support at evercheck.com/support.

How we assess accessibility

  • Our product and engineering teams test new work with both manual checks and
    automated tools.
  • We do keyboard and screen reader testing on new features before they ship.
  • We act on feedback from people who use assistive technology.

Standards and laws we follow

  • WCAG 2.1, Level AA — the standard we build all new work to.
  • Americans with Disabilities Act (ADA) — the U.S. law against disability discrimination.
  • Section 508 of the Rehabilitation Act — the U.S. rule that federal agencies and federally funded organizations must make their tech accessible.

New work meets WCAG 2.1 AA today. Bringing the older parts of the platform fully in line with ADA and Section 508 expectations is the work we’re doing now.

Satisfy your curiosity.

Tell us a little about yourself and we'll be in touch to schedule a personalized demo.