Digital Accessibility Statement

A highway overpass at night with the lights of cars blurred from moving quickly.

Vertex, Inc. is committed to providing an equal and quality experience for everyone. We're constantly working to improve the accessibility of our website to ensure equal access for individuals with disabilities, including those with visual, hearing, cognitive, and motor impairments.

Wherever possible, we strive to conform to level AA of the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines (WCAG) 2.2. These guidelines provide a foundation for how to make web content more accessible for people with various disabilities. We believe not only in conformance with these guidelines but that optimisation around them will help make the web more user-friendly for everyone.

Known Exceptions

While we strive to meet the success criteria outlined in the WCAG 2.2 AA guidelines, we recognise that, at this time, some regions of our site are not accessible or may be difficult to navigate, particularly for screen reader users (such as those using NVDA with the Firefox web browser).

The pages/sections listed below may contain accessibility issues that may present issues for some users:

Within the sitewide Search Flyout (accessed from the top “utility” navigation), the menu is structured in a way where a screen reader user may not be clearly informed of its expanded/collapsed state. This fails WCAG 2.2 A success criterion 4.1.2 (Name, Role, Value).
On pages using components such as the “Icon List,” “Leadership Cards,” or “Content Panels,” heading levels may be out of order, disrupting the page outline. This fails WCAG 2.2 A success criterion 1.3.1 (Info and Relationships).
On pages where the “Quote Panel” component is used, the quote text has insufficient color contrast for normal-size text, making it difficult to read for many users. This fails WCAG 2.2 AA success criterion 1.4.3 (Contrast - Minimum).
On the Partner Listing page, some interactive buttons (e.g., the Chevron icon) lack accessible names, and buttons are improperly nested within each other. This fails WCAG 2.2 A success criterion 4.1.2 (Name, Role, Value) and 1.3.1 (Info and Relationships).
On the Partner Listing page, elements that are not triggers indicate that they are interactive, confusing the behavior for assistive technologies. This fails WCAG 2.2 A success criterion 4.1.2 (Name, Role, Value).
On the Partner Listing page, some category and filter tabs use improper roles, making it unclear how they should be interacted with and what the result of that interaction is, breaking semantic expectations. This fails WCAG 2.2 A success criterion 1.3.1 (Info and Relationships) and 4.1.2 (Name, Role, Value).
On pages where the “Tabs” component is used, the content panels use improper roles, making it unclear how they should be interacted with and what the result of that interaction is, breaking semantic expectations. This fails WCAG 2.2 A success criterion 1.3.1 (Info and Relationships) and 4.1.2 (Name, Role, Value).
On pagination elements across several pages (e.g., News and Resource Library), the nav element includes a redundant role and may introduce confusion for some assistive technologies. This fails WCAG 2.2 A success criterion 4.1.2 (Name, Role, Value).
On certain pages, images are either missing alternative text or use generic descriptions, making it difficult for screen reader users to understand the image’s content or context. This fails WCAG 2.2 A success criterion 1.1.1 (Non-text Content).
On certain pages, empty heading tags may be present, which can cause confusion for users navigating by headings. This fails WCAG 2.2 A success criterion 1.3.1 (Info and Relationships).
On certain pages, text links use non-descriptive phrases such as “Click Here” or “Learn More” without additional context, making it unclear to screen reader users what the link does. This fails WCAG 2.2 A success criterion 2.4.4 (Link Purpose - In Context).
In some instances where data tables are used, column and row headers are not properly identified, which can make data navigation difficult for screen reader users. This fails WCAG 2.2 A success criterion 1.3.1 (Info and Relationships).

Note: Some of these regions may be powered by third-party plugins, which we recognise do not provide the level of accessibility for which we strive.

We are actively working on improving the experience in these and other impacted areas by working directly with vendors or seeking more accessible alternatives. Please be aware that our efforts to remediate any issues with these sections are ongoing.

Have Feedback or Need Help?

We continue to strive not only to meet a high level of accessibility support but also to provide a polished experience for all visitors. In the meantime, we welcome your questions and comments on how to improve our website’s accessibility. If you need assistance or are assisting somebody with a disability and having an issue using specific features, please contact us by email at legal@vertexinc.com.

Preparation of this accessibility statement This statement was prepared on July 01, 2025. It was last updated on August 21, 2025.