GEP Accessibility Statement

GEP Accessibility Statement

GEP Accessibility Statement

Our Commitment

GEP is committed to ensuring that our platforms are accessible to all users, including those who rely on assistive technology. We believe that accessible software is better software — and that inclusion is a design requirement, not an afterthought.

We are actively working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA across our platforms, and we evaluate our products against these standards on an ongoing basis.

Applicable Standards and Regulations

Our accessibility program is designed with reference to the following standards and regulatory frameworks:

WCAG 2.2 Level AA

The international standard for web and application accessibility, published by the W3C Web Accessibility Initiative

Section 508

Section 508 of the Rehabilitation Act of 1973 (United States)

EN 301 549

EN 301 549 — European standard for ICT product and service accessibility

How We Test

GEP uses a combination of automated and manual testing methods to evaluate accessibility across our platforms:

  • Automated scanning using Axe DevTools and WAVE to identify and track issues across the codebase
  • Manual testing with JAWS and NVDA screen readers on Windows, across Chrome, Edge, and Firefox
  • Keyboard-only navigation testing across all core workflows
  • Design-phase review — accessibility requirements are evaluated from the design stage through to final code, not solely as a post-development audit

Accessibility Conformance Reports

GEP publishes Accessibility Conformance Reports (ACRs) completed using the VPAT® template for key modules across GEP SMART and GEP Quantum Intelligence. These reports document how each area of the platform performs against WCAG 2.2 AA criteria, including areas where full conformance has not yet been achieved. ACRs can be provided upon request. 

Feedback and Contact

If you experience a barrier while using any GEP platform, we want to hear from you. Your feedback directly informs our remediation priorities.

When reaching out, it helps to include:

  • The platform and module where you encountered the issue
  • The browser and operating system you were using
  • Any assistive technology you were using at the time (e.g., JAWS, NVDA, VoiceOver)
  • A description of what you were trying to do and what happened

User Recommendations

To get the best experience using GEP's platforms with assistive technology, we recommend:

  • Keeping your browser updated to the latest version
  • Using built-in browser accessibility features such as text zoom and high contrast mode
  • For screen reader users, GEP platforms are tested with JAWS and NVDA on Windows
  • Product documentation is available in accessible PDF format upon request — contact accessibility@gep.com