Help

UsingGetting startedConcept

Accessibility

How CapitolMath meets WCAG 2.2 AA, what the conformance report (VPAT) covers and how it was tested, widgets on an accessible site, and how to report a barrier.

CapitolMath is built to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA — the public site, the app, Help, the API docs and the widgets you embed on your own site. How well it does is set out criterion by criterion in our accessibility conformance report.

The conformance report (VPAT)#

The conformance report follows the VPAT® 2.5 template (WCAG edition), the format public agencies and procurement teams ask for. It lists every WCAG 2.2 Level A and AA success criterion with a rating — Supports, Partially Supports, Does Not Support or Not Applicable — and remarks saying how CapitolMath meets it. Because WCAG 2.2 contains 2.0 and 2.1, it covers those versions too. Level AAA isn't evaluated.

The revised Section 508 standards adopt WCAG 2.0 Level A and AA for web content, so the report covers what a Section 508 review checks. It isn't a separate Section 508 or EN 301 549 edition of the VPAT; ask support if you need one.

It doesn't cover pages run by other companies: sign-in, sign-up and two-step verification are hosted by our identity provider, and checkout and billing by our payment processor. It doesn't cover the REST API or MCP server either, which return data rather than pages.

If you need the report as a document for a procurement file, ask support and we'll send it.

How it was tested#

The report is self-assessed. CapitolMath was checked with automated accessibility scans, a review of the code of every page and panel against each criterion, keyboard-only use of every menu, panel and form, layout checks at phone width and 200% zoom, and contrast measurements of every color in the product and the widgets.

It hasn't yet been tested with screen readers (VoiceOver, NVDA, JAWS) or by people with disabilities, and no third-party audit has been done. The report says so, and it will be updated when that testing is done.

What that means in use#

  • Keyboard. Everything works without a mouse. Panels, menus and dialogs take focus when they open, Esc closes the one on top, and focus goes back where it was. Skip to main content is the first thing Tab reaches on every page.
  • Screen readers. Result counts, confirmations, errors and the assistant's answers are announced. Charts, maps and the calendar have a Show data table or a table structure with the same values.
  • Zoom and phones. Pages fit a phone's width and zoom to 200% without scrolling sideways.
  • Color. Text and controls meet WCAG's contrast minimums, and nothing is shown by color alone.

Widgets on an accessible site#

Widgets meet WCAG 2.2 AA on their own, so they can go on a site that has to — a government agency's or a public university's, say. The one thing you choose that affects it is the accent color: the widget builder works out readable text colors from it and warns you if a choice would fail contrast. See About widgets.

Report a barrier#

If something in CapitolMath doesn't work for you, tell us: use the help button at the bottom right of any page and choose Message support, or email support@capitolmath.ai. Say which page, what you were trying to do and, if you use one, which assistive technology. See Getting help.