Accessibility statement

Based on our Voluntary Product Accessibility Template (VPAT), dated 2026-10-16.

Where we stand

We want GovConHouse to be usable by everyone, including people who use a keyboard, a screen reader or other assistive technology. We measure the product against the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, and against Section 508.

Today GovConHouse partially supports both. It does not fully conform. The gaps we know about are listed below.

What we have tested

An automated scan with axe-core covers 23 pages: 3 public pages and 20 signed-in pages. It was last re-run on 2026-10-16 and found no serious or critical violations, in light and dark mode.
A second axe-core sweep on 2026-10-16 covered every page in the signed-in navigation, 114 in all. After fixes it reports no violations at desktop width in light or dark mode, and none serious at phone width. It does not cover pages that need a record to open.
A manual review on 2026-10-08 found problems the automated scan cannot see. The ones still open are the gaps listed below.

What we have not tested yet

No testing with the NVDA, JAWS, VoiceOver or TalkBack screen readers.
No full keyboard-only walkthrough by a person.
No review by an independent accessibility professional.

Known gaps

WCAG 2.2 criteria that GovConHouse does not fully support
Criterion	Status	What it means
2.1.1 Keyboard	Partially supports	Dialogs and side sheets now keep keyboard focus inside and close on Escape, checked by automated tests. Three panels with their own handling, and the whole product by hand, have not been walked with a keyboard.
2.4.3 Focus Order	Partially supports	Dialogs return focus to the control that opened them, checked by automated tests. Reading order across complex layouts has not been checked by a person.
1.3.1 Info and Relationships	Partially supports	Some form controls have no programmatic label, for example in the pipeline add and edit dialog and in settings.
3.3.2 Labels or Instructions	Partially supports	The same unlabeled form controls, including some onboarding fields.
1.4.3 Contrast (Minimum)	Partially supports	Our automated check finds no contrast failures in light or dark mode on the pages it covers. It cannot see hover states, open menus or charts.
1.4.11 Non-text Contrast	Partially supports	Borders and focus indicators were spot-checked by hand, not checked across the whole product.
2.4.7 Focus Visible	Partially supports	Buttons and form fields show a 3 px focus ring. Custom controls have not been checked one by one.
4.1.2 Name, Role, Value	Partially supports	Dialogs are named from their titles and the icon-only buttons we found are named. Controls inside dialogs other than the pipeline one have not been scanned.
4.1.3 Status Messages	Not evaluated	Live updates are marked up for screen readers, but how they are announced has not been checked with one.

Charts provide their data as accessible markup, and the pipeline board has a keyboard alternative to drag and drop. Neither has been checked with a screen reader or a keyboard-only walkthrough.

Report a barrier

If something in GovConHouse is hard or impossible for you to use, email support@govconhouse.com. Tell us the page, what you were trying to do, and the browser and assistive technology you use. You can also ask us for the information on a page in another way.