An accountability artifact, not a public relations gesture. This page details WCAG conformance, known issues, assistive technology coverage, and how to request alternative formats or report barriers.
These govern how accessibility is built, tested and supported —
and how it is talked about.
Core content, controls, support and reporting are usable without a mouse and without relying on colour, motion, sound or vision alone.
Conformance language is status-qualified and tied to scope, test date, method, exceptions and a named owner.
Accessibility of the product and public site is not a premium-plan feature. Procurement artifacts may be sales-assisted; access itself is never gated.
Semantic HTML before ARIA. Custom widgets require complete keyboard and assistive-technology behaviour.
Accessibility applies to full workflows, not isolated components or hero sections.
Reporting an accessibility issue never requires a sales conversation, marketing consent or an account upgrade.
Accessibility has owners, a test cadence, regression gates, issue severity, remediation targets and evidence.
WCAG is a technical standard, not a certification programme.
Conformance claims are the responsibility of the content provider,
so each scope carries its own evaluated status.
Each pattern carries its own status. This page follows every one of
them, so you can verify the claims on the page you are reading.
Every interactive control reachable and operable by keyboard across complete workflows, not isolated components.
A persistent, high-contrast focus outline on every focusable element. Focus is never suppressed for aesthetics.
DOM order matches visual order. Focus moves predictably and returns sensibly when a dialog closes.
A skip-to-content link is the first focusable element on every page, visible on focus.
Focus can always leave a component. Modal focus is contained deliberately and released on close.
Semantic HTML before ARIA. Headings, landmarks, lists and tables carry real structure rather than styled substitutes.
Every control has a programmatic name matching its visible label, including icon-only actions.
Status changes, filter results and async panels announce through live regions with appropriate politeness.
Icons and separators that carry no meaning are hidden from assistive technology rather than announced.
Body text meets 4.5:1 against its background. Measured programmatically rather than assumed from a palette.
Every status carries a text label. Colour reinforces but never carries the meaning by itself.
Content reflows to a single column without horizontal scrolling at 320 CSS pixels equivalent.
Content remains readable when line height, letter and word spacing are increased by user stylesheet.
Timeouts, validation errors and dense tables are the three places
accessible design most often breaks in governance software.
Automated checks alone catch a minority of barriers. The
combinations below are what we test against, with their coverage
status.
Two high, five medium, nine low. The high-severity items are listed
in full below; the remainder are available in an accessibility review.
Affects: dense analytics views in the web app
Screen reader and keyboard users cannot access the underlying values for several chart types.
Workaround: the same data is available in the adjacent registry table for most views.
Owner: Design system lead
No completion date published until the fix is approved for release.
Affects: evidence and detail drawers in three workflows
Keyboard focus moves to the document start, forcing users to re-traverse the page.
Workaround: none currently available.
Owner: Web app engineering
Regression gate added so the fix cannot silently revert.
Affects: one embedded surface in the web app
Some controls within the embedded component are not keyboard reachable.
Mitigation: an equivalent non-embedded path is provided for the same task.
Owner: Vendor management — raised with supplier
Vendor accessibility evidence requested; response pending.
We want to understand the task you were trying to complete and the barrier you encountered. You do not need to be a customer or provide marketing consent to report an issue.
Enterprise diligence without overclaiming. Where an artifact does
not exist, that is stated rather than promised.
An ACR following the VPAT format, covering the evaluated scope with criterion-level findings and remarks.
Method, cadence, AT combinations covered, and the current issue register by severity.
Full list with severity, user impact, workaround, owner and status — including items not listed publicly.
Prioritisation approach and current work in progress. No committed dates for unapproved fixes.
Vendor accessibility statements for embedded components, where the vendor has supplied them.
A third-party assessment naming assessor, scope, date, method and artifact.
Everything claimed here applies to this page. Tab through it without a mouse. Zoom to 400%. Turn colour off and check that every status still reads. If something fails, the reporting form above needs no account, no consent and no contact details.
No conformance is claimed for a scope that has not been fully evaluated and approved, and no independent accessibility certification exists.
Every section of this page was readable without it.
Direct first sentences, then qualified detail. Every answer is
present in the page source.
WCAG 2.2 Level AA is the design and testing target. Conformance is published only for scopes fully evaluated and approved — and most scopes currently read "verified — partial".
Visual, contrast and reflow conforms. Keyboard, screen reader and forms are partial. Data tables and charts are in remediation. Documents, media and mobile are in testing. See the statuses