Accessibility
CapitolMath's accessibility conformance report, based on the VPAT® 2.5 template (WCAG edition). It reports how the product meets WCAG 2.2 Levels A and AA, and covers WCAG 2.0 and 2.1 too. Report date: October 8, 2026.
Product and scope
CapitolMath is a legislative intelligence service: people search and track bills, votes, legislators and hearings; build dashboards, maps, scorecards and saved lists; ask an assistant; and reach the same data through a REST API, an MCP server and embeddable widgets.
This report covers the interfaces CapitolMath builds and serves:
- The public site: home, pricing, the trust and legal pages, the Help center, the API and MCP documentation, and the visitor assistant.
- The application: browse and search, bill and official panels, dashboards, maps, scorecards, saved lists, the calendar, the assistant, support requests, profile and organization settings, API keys and the API playground, and the staff console.
- Embeddable widgets that customers place on their own sites.
It doesn't cover sign-in, sign-up and multi-factor pages hosted by our identity provider; checkout and the billing portal hosted by our payment processor; the REST API and MCP server themselves, which return data rather than a user interface; or email.
How it was evaluated
- Automated scans with axe-core (WCAG 2.2 A and AA rules) of the public pages and key application views.
- Review of the source code of every interface against each success criterion, assisted by AI code review.
- Keyboard-only checks of overlays, menus, comboboxes, forms and focus return, and layout checks at 320 CSS pixels.
- Contrast ratios computed for the design tokens, chart palettes and widget themes.
Not yet done: testing with screen readers (VoiceOver, NVDA, JAWS), speech input or screen magnification, and testing by people with disabilities, or an independent audit. Ratings reflect code review and automated checks; we will revise them as that testing is completed.
Standards and terms
| Standard | Included |
|---|---|
| WCAG 2.0 | Level A and AA: yes. Level AAA: no. |
| WCAG 2.1 | Level A and AA: yes. Level AAA: no. |
| WCAG 2.2 | Level A and AA: yes. Level AAA: no. |
| Revised Section 508, EN 301 549 | Not covered by this edition; available on request. |
| Term | Meaning |
|---|---|
| Supports | The functionality has at least one method that meets the criterion without known defects, or meets it with equivalent facilitation. |
| Partially Supports | Some functionality does not meet the criterion. |
| Does Not Support | The majority of functionality does not meet the criterion. |
| Not Applicable | The criterion is not relevant to the product. |
| Not Evaluated | Not evaluated against the criterion. Used only for Level AAA. |
Level A
| Criterion | Name | Conformance | Remarks |
|---|---|---|---|
| 1.1.1 | Non-text Content | Supports | Icons and icon-only controls have text names; decorative symbols are hidden from assistive technology. Dashboard charts, district and score maps, and widget charts offer a "Show data" table with the same values. |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | Not Applicable | The product has no audio or video content. |
| 1.2.2 | Captions (Prerecorded) | Not Applicable | No video content. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | Not Applicable | No video content. |
| 1.3.1 | Info and Relationships | Supports | Pages use landmarks, headings, lists, data tables with headers, and labeled form fields. Calendar week and month views are tables with day headers; dialogs are labeled by their headings. |
| 1.3.2 | Meaningful Sequence | Supports | Reading order follows the visual order; overlays receive focus when they open. |
| 1.3.3 | Sensory Characteristics | Supports | Instructions name controls by their text, not by shape, position or color. |
| 1.4.1 | Use of Color | Supports | Status, vote outcomes, party, alerts and the current page in navigation are conveyed by text, a mark or weight as well as color. Links inside text are underlined. |
| 1.4.2 | Audio Control | Not Applicable | The product plays no audio. |
| 2.1.1 | Keyboard | Supports | Menus, comboboxes, sliders, dialogs, drawers, tables, chart data, map panning and list reordering work from the keyboard. Scrolling code samples and tables take focus. |
| 2.1.2 | No Keyboard Trap | Supports | Modal layers hold Tab inside while open and release it when closed; Escape closes the top layer. |
| 2.1.4 | Character Key Shortcuts | Supports | The only keyboard shortcut (⌘K or Ctrl+K, search) uses a modifier key. |
| 2.2.1 | Timing Adjustable | Supports | CapitolMath sets no time limits. Session length is managed by the identity provider (out of scope). |
| 2.2.2 | Pause, Stop, Hide | Supports | Home-page motion is a short entrance animation, removed for people who prefer reduced motion. The one auto-refreshing staff page has a pause button. |
| 2.3.1 | Three Flashes or Below Threshold | Supports | No content flashes. |
| 2.4.1 | Bypass Blocks | Supports | A "Skip to main content" link is the first focusable element on every page, and every page has header, navigation and main landmarks. |
| 2.4.2 | Page Titled | Supports | Every page has a unique, descriptive title. |
| 2.4.3 | Focus Order | Supports | Focus moves into panels, dialogs and menus when they open and returns to the control that opened them. When a control disappears (a removed item, a revealed list, an edit form), focus moves to the next sensible element. |
| 2.4.4 | Link Purpose (In Context) | Supports | Link text, or its sentence, says where the link goes. |
| 2.5.1 | Pointer Gestures | Supports | Map panning and sliders have single-pointer buttons; reordering has Move up and Move down buttons. |
| 2.5.2 | Pointer Cancellation | Supports | Actions run on release, using standard controls. |
| 2.5.3 | Label in Name | Supports | Controls' accessible names begin with their visible text. |
| 2.5.4 | Motion Actuation | Not Applicable | No function is operated by moving the device. |
| 3.1.1 | Language of Page | Supports | Every page declares its language as English. |
| 3.2.1 | On Focus | Supports | Focusing a control does not change context. |
| 3.2.2 | On Input | Supports | Changing a filter updates results in place and announces the new count, without moving focus or opening a new page. |
| 3.2.6 | Consistent Help | Supports | The help button, with the assistant and a way to message a person, is in the same place on every page. |
| 3.3.1 | Error Identification | Supports | Errors are shown in text by the field, the field is marked invalid, and the error is announced. |
| 3.3.2 | Labels or Instructions | Supports | Fields have visible labels. Where an action is unavailable, the reason is shown as text or linked to the control. |
| 3.3.7 | Redundant Entry | Supports | Information entered earlier in a flow is carried forward, including the email address from registration to sign-in. |
| 4.1.1 | Parsing | Not Applicable | Obsolete and removed in WCAG 2.2; under WCAG 2.0 and 2.1 it is treated as always supported for HTML. |
| 4.1.2 | Name, Role, Value | Supports | Custom controls use standard roles and states: comboboxes, listboxes, sliders, disclosures, dialogs, toggle buttons and tabs with arrow-key navigation. |
Level AA
| Criterion | Name | Conformance | Remarks |
|---|---|---|---|
| 1.2.4 | Captions (Live) | Not Applicable | No live audio or video. |
| 1.2.5 | Audio Description (Prerecorded) | Not Applicable | No video content. |
| 1.3.4 | Orientation | Supports | Layouts work in portrait and landscape. |
| 1.3.5 | Identify Input Purpose | Supports | Fields that collect the user's own name, email, organization and address declare their purpose with autocomplete. |
| 1.4.3 | Contrast (Minimum) | Supports | Text, placeholders, chart labels and status colors meet 4.5:1 (3:1 for large text). Widgets compute readable text colors from each customer's chosen accent and warn when a choice falls short. |
| 1.4.4 | Resize Text | Supports | Text scales to 200% with browser zoom without loss of content or function. |
| 1.4.5 | Images of Text | Supports | Text is rendered as text; the logo is the only image of text. |
| 1.4.10 | Reflow | Supports | Pages reflow to 320 CSS pixels without horizontal scrolling; wide data tables and code samples scroll within their own region. |
| 1.4.11 | Non-text Contrast | Supports | Form field borders, focus outlines, chart segments and heatmap cells meet 3:1, by color or by outline. |
| 1.4.12 | Text Spacing | Supports | Content adapts to increased line, paragraph, letter and word spacing; calendar event labels wrap instead of truncating. |
| 1.4.13 | Content on Hover or Focus | Supports | Tooltips, info pop-ups and map hover cards can be dismissed with Escape, stay open while pointed at, and persist until dismissed. |
| 2.4.5 | Multiple Ways | Supports | Pages are reached from navigation, search (⌘K), saved lists and links between related records. |
| 2.4.6 | Headings and Labels | Supports | Every page has one main heading, and section headings and labels describe their content. |
| 2.4.7 | Focus Visible | Supports | A 2-pixel outline marks keyboard focus everywhere, including on dark surfaces. |
| 2.4.11 | Focus Not Obscured (Minimum) | Supports | Pages reserve scroll padding for the sticky header, so a focused element is not hidden beneath it. |
| 2.5.7 | Dragging Movements | Supports | Every drag has a single-pointer alternative. |
| 2.5.8 | Target Size (Minimum) | Supports | Targets are at least 24 by 24 CSS pixels, or spaced so that a 24-pixel circle on each does not overlap another. |
| 3.1.2 | Language of Parts | Supports | All content is in English. |
| 3.2.3 | Consistent Navigation | Supports | Navigation appears in the same order on every page of each site. |
| 3.2.4 | Consistent Identification | Supports | Components with the same function have the same names throughout. |
| 3.3.3 | Error Suggestion | Supports | Error messages say what to change, such as the required format or the allowed range. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | Supports | Purchases are confirmed at checkout; deleting saved lists, scorecards, conversations, API keys, webhooks, widgets, members or the organization asks for confirmation. |
| 3.3.8 | Accessible Authentication (Minimum) | Supports | CapitolMath's own forms require no cognitive test and allow pasting. Sign-in itself is hosted by the identity provider (out of scope); it supports password managers and single sign-on. |
| 4.1.3 | Status Messages | Supports | Result counts, confirmations, errors and the assistant's answers are announced without moving focus. |
Level AAA
Not evaluated. CapitolMath targets WCAG 2.2 Level AA. Some Level AAA behavior is present — help is available in context on every page, and nothing has a time limit — but it hasn't been assessed criterion by criterion.
Third-party components
Sign-in, sign-up and multi-factor authentication are provided by our identity provider, and checkout and billing by our payment processor (both listed on subprocessors). Their accessibility is theirs to report. Embeddable widgets take on the accessibility of the page they're placed on, and their accent color is the customer's choice; the widget builder warns when a choice would make text hard to read.
This report describes the product as of the date above and is provided for information; it is not a warranty. CapitolMath changes often, and this page is updated when a rating changes.
Report a barrier
If something in CapitolMath doesn't work for you, email support@capitolmath.ai or use the help button at the lower right of any page and choose to message a person. Tell us the page, what you were trying to do, and the assistive technology you use, if any. A copy of this report as a document is available from the same address.