ClearPoint's VPAT is written against WCAG 2.2. Here is what it covers, how we tested it, and how to request a copy.
- Check a VPAT's date, edition and WCAG version first. ClearPoint's current report is VPAT 2.5Rev, WCAG 2.2 edition, dated September 23, 2026.
- Read the tallies, not the adjective. ClearPoint Next rates Supports on all 44 applicable WCAG 2.2 A and AA criteria; the other 11 are Not Applicable.
- Accept a WCAG 2.2 report where 2.1 is required. W3C says content conforming to 2.2 also conforms to 2.1, which ADA Title II names.
- Read the criteria new in WCAG 2.2 closely. Hidden focus, drag-only controls, small targets and CAPTCHA sign-in are gaps a 2.1 report never tested.
- Get the VPAT from the ClearPoint Trust Center. It covers ClearPoint Next; Classic customers gain this accessibility work by moving to Next.
ClearPoint documents its accessibility the way procurement teams expect it: a VPAT written against WCAG 2.2. The current report, dated September 23, 2026, rates ClearPoint Next against all 55 Level A and AA success criteria. It reports 44 as Supports and 11 as Not Applicable, with none at Partially Supports or Does Not Support.
ClearPoint builds this into the product itself rather than adding an overlay, and the 2026 report gives no overlay credit toward any result. The rest of this page covers what the report includes, how we tested, and how to get a copy for your procurement file.
What a VPAT is, and what it is not
A VPAT (Voluntary Product Accessibility Template) is a free template from the Information Technology Industry Council (ITI). Once a vendor fills it in with test results, it becomes an Accessibility Conformance Report, or ACR. ITI is plain about the limits: there is no VPAT certification and no pass/fail scale. The report is the vendor's documented evidence, criterion by criterion, and it is only as good as the testing behind it.
ITI publishes several editions. The 508 edition incorporates WCAG 2.0, the EU edition WCAG 2.1, and the WCAG and INT editions WCAG 2.2. ClearPoint's report uses VPAT 2.5Rev, WCAG edition, so every row is written against WCAG 2.2.
Why test against WCAG 2.2 when the rule names 2.1
The Department of Justice's ADA Title II rule sets WCAG 2.1 Level AA as the technical standard for state and local government web content and mobile apps. An Interim Final Rule published April 20, 2026 moved the compliance dates to April 26, 2027 for public entities with a population of 50,000 or more, and to April 26, 2028 for smaller entities and special district governments. If you publish dashboards for residents, our public dashboard best practices cover that side.
WCAG 2.2 adds to 2.1 rather than replacing it. The W3C states that sites which conform to WCAG 2.2 also conform to WCAG 2.1, and 2.2 removed one criterion, 4.1.1 Parsing. The criteria worth reading closely in any 2.2 report are the new A and AA ones, because a 2.1 report never asked about them:
- 2.4.11 Focus Not Obscured (Minimum). Keyboard focus is never hidden behind other on-screen content.
- 2.5.7 Dragging Movements. Every drag-and-drop interaction in ClearPoint has a working non-drag alternative.
- 2.5.8 Target Size (Minimum). Controls meet the minimum target size or sit far enough from their neighbors.
- 3.2.6 Consistent Help. Help is in the same place across the product.
- 3.3.7 Redundant Entry. Not Applicable: ClearPoint's data-entry flows are single-step, so nothing asks you to re-enter what you already provided.
- 3.3.8 Accessible Authentication (Minimum). You can sign in with single sign-on or a password manager, and there is no CAPTCHA or other cognitive test.
What the report covers
The report covers ClearPoint Next, the current generation of the ClearPoint application. The audit worked through the screens people use every reporting cycle:
- Getting around. Login, the main dashboard, breadcrumbs and the toolbar menus.
- Scorecards and elements. Scorecard lists and details, measure and objective pages in view and edit mode, initiative details and the Milestones grid.
- Reports and plans. The Alignment Matrix report on desktop and mobile, Briefing Book generation, the Strategy Map editor, Portfolio, Mission and Values, and the Strategic Plan table.
- Settings and fields. My Settings and the Collaborators and Tags fields.
If you are on ClearPoint Classic
The VPAT covers ClearPoint Next only. It does not cover ClearPoint Classic. The accessibility work behind this report was done in Next, and Next is where that work continues. If accessibility is part of your organization's obligations, it is a reason to plan your move from Classic to Next.
How we tested
The original audit ran in August 2026 and the retest in September 2026, on production with follow-up testing on our staging environment.
- Automated scans. Two rounds of axe DevTools in Chrome, the second across seven page types.
- Manual tests of 19 components. Keyboard only, the accessibility tree, contrast measured from computed styles and rendered pixels, reflow at a 320px viewport, and a multi-hour idle test of the session timeout.
- Screen readers. NVDA, JAWS and Narrator on status messages. VoiceOver was not tested in this cycle.
- Language. A Spanish-locale pass for language of parts.
A scanner finds candidates. It does not prove conformance, so no verdict in the report rests on a scan alone: each one needs dated evidence from that cycle.
What it means day to day
- Keyboard. You can run the whole product from the keyboard, nothing traps focus, every focused control shows a visible indicator, and panels and dialogs put focus back where it belongs when they close.
- Screen readers. Charts, icons and images carry text that describes their content, headings and table headers are exposed, and status messages are announced without moving focus.
- Color. Status never relies on color alone; a label or icon always goes with it, and text and meaningful icons meet the contrast ratios.
- Zoom and spacing. Text resizes to 200%, content reflows on narrow screens without sideways scrolling, and pages stay usable with wider line, letter and word spacing.
- Session timeout. You are warned before an idle session ends and can choose to keep working.
- Language. Interface text declares its language, including under non-English locales.
How we keep it true
A VPAT describes one release on one date. We keep ours as data, one record per WCAG 2.2 criterion, so the next cycle retests what changed instead of starting from zero, and a fix counts only once it ships in the release that cycle tests. Every cycle also reruns the whole-product automated pass, because a criterion nobody touched can still regress through a shared component.
Our engineering standard holds customer-facing screens to WCAG 2.2 AA: 4.5:1 contrast for body text in both light and dark themes, no meaning carried by color alone, an accessible name on every control, a keyboard path in reading order, a non-drag path for every drag interaction, and no animation when your system asks for reduced motion. An accessibility lint rule set checks part of that in the code.
Getting the report
The current VPAT is in the ClearPoint Trust Center, alongside our SOC 2 and TX-RAMP documentation. When you read any vendor's report, check three things first: its date, its edition and WCAG version, and the list of screens it tested. For the security half of the same review, see our security page.
Common questions
Is ClearPoint WCAG 2.2 AA compliant?
There is no official WCAG or VPAT certification, so the evidence is the report. ClearPoint Next's VPAT, dated September 23, 2026, rates Supports on all 44 applicable WCAG 2.2 Level A and AA criteria. The other 11 are Not Applicable; six of those cover audio and video, which the product does not contain.
Does a WCAG 2.2 report meet a WCAG 2.1 AA requirement such as ADA Title II?
The W3C states that content conforming to WCAG 2.2 also conforms to WCAG 2.1, because 2.2 adds criteria and removes only 4.1.1 Parsing. The DOJ's Title II rule names WCAG 2.1 Level AA, with compliance dates of April 26, 2027 or April 26, 2028 depending on the government's size.
How do I get ClearPoint's VPAT?
It is in the ClearPoint Trust Center at trust.clearpointstrategy.com, with ClearPoint's SOC 2 and TX-RAMP documentation. The current report is VPAT 2.5Rev, WCAG 2.2 edition, and covers ClearPoint Next, not ClearPoint Classic.








%2520Strategy%2520vs%2520Tactics%2520Differences%252C%2520Examples%2520%2526%2520How%2520to%2520Track%2520Both.jpg)



















.png)




.png)


















.webp)















%2520OKRs%2520vs%2520KPIs%2520Breaking%2520Down%2520the%2520Difference.jpg)