Accessibility Conformance Report
Based on VPAT® Version 2.5 - WCAG Edition
Conforms to WCAG 2.1 Level AAVPAT Score builds software that evaluates other vendors' accessibility, so we hold our own product to the same standard. This report documents the conformance of the VPAT Score web application with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA.
Product and Report Information
- Name of Product / Version
- VPAT Score (web application, vpatscore.com)
- Report Date
- June 4, 2026
- Product Description
- VPAT Score is a web-based SaaS application that parses Voluntary Product Accessibility Template (VPAT) and Accessibility Conformance Report (ACR) documents and generates conformance scores, letter grades, and risk ratings to assist procurement teams in evaluating vendor accessibility claims against WCAG 2.1 and 2.2 success criteria.
- Contact Information
- accessibility@vpatscore.com - Sterling Software LLC (operating VPAT Score), 2105 Vista Oeste NW, Suite E #3216, Albuquerque, NM 87120
- Notes
- This report covers the full VPAT Score web application, including all authenticated and unauthenticated pages, in both the default (light) and dark display themes.
- Evaluation Methods Used
- Conformance was determined through a combination of (a) automated testing with the WAVE Web Accessibility Evaluation Tool and axe-core, (b) manual code review of all page templates, (c) full keyboard-only operation testing, (d) computed color-contrast analysis of every text and user-interface color in both light and dark themes, and (e) screen-reader spot checks of landmarks, labels, headings, and dynamic status messages.
Applicable Standards and Guidelines
| Standard / Guideline | Included In Report |
|---|---|
| WCAG 2.1, Level A | Yes |
| WCAG 2.1, Level AA | Yes |
| WCAG 2.1, Level AAA | No (not evaluated) |
Conformance Terms
- Supports: The functionality of the product has at least one method that meets the criterion without known defects, or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
WCAG 2.1 Report: Success Criteria, Level A
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text ContentLevel A | Supports | All non-text content has a text alternative. Decorative icons are marked aria-hidden="true"; the analytics chart is exposed with role="img" and a descriptive aria-label, accompanied by an equivalent visually-hidden data table. The product uses no informational images (icon fonts and inline SVG only). |
| 1.2.1 Audio-only and Video-only (Prerecorded)Level A | Not Applicable | The product contains no prerecorded audio-only or video-only content. |
| 1.2.2 Captions (Prerecorded)Level A | Not Applicable | The product contains no prerecorded synchronized media. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded)Level A | Not Applicable | The product contains no prerecorded synchronized media. |
| 1.3.1 Info and RelationshipsLevel A | Supports | Structure and relationships are conveyed programmatically: HTML5 landmarks (nav, main, footer), associated form labels, fieldset/legend for grouped controls, a correct heading hierarchy, and data tables with caption and th scope. |
| 1.3.2 Meaningful SequenceLevel A | Supports | The DOM reading and navigation order matches the visual presentation; no CSS reordering disrupts the intended sequence. |
| 1.3.3 Sensory CharacteristicsLevel A | Supports | Instructions do not rely solely on shape, size, visual location, or sound; every control has a programmatic name. |
| 1.4.1 Use of ColorLevel A | Supports | Color is never the only means of conveying information. Conformance levels, letter grades, risk ratings, and statuses carry text labels and/or icons; in-text links are underlined in addition to color. |
| 1.4.2 Audio ControlLevel A | Not Applicable | The product plays no automatically-starting audio. |
| 2.1.1 KeyboardLevel A | Supports | All functionality is operable from the keyboard, including the drag-and-drop upload zone (a keyboard-focusable control that opens the file picker) and all inline-edit widgets (Enter saves, Escape cancels). |
| 2.1.2 No Keyboard TrapLevel A | Supports | Keyboard focus can always be moved away from a component using standard navigation; dialogs are dismissible by keyboard. |
| 2.1.4 Character Key ShortcutsLevel A | Supports | The product implements no single-character key shortcuts. |
| 2.2.1 Timing AdjustableLevel A | Supports | No time limits are imposed on task completion. The only time limit is an authentication session inactivity timeout retained for security, which falls under the essential exception of this success criterion. |
| 2.2.2 Pause, Stop, HideLevel A | Supports | The product contains no moving, blinking, scrolling, or auto-updating content lasting more than five seconds. The brief chart entry animation is non-essential and is disabled during export. |
| 2.3.1 Three Flashes or Below ThresholdLevel A | Supports | No content flashes more than three times in any one-second period. |
| 2.4.1 Bypass BlocksLevel A | Supports | A "Skip to main content" link is the first focusable element on every page, and ARIA landmark regions are provided. |
| 2.4.2 Page TitledLevel A | Supports | Every page has a unique, descriptive title element. |
| 2.4.3 Focus OrderLevel A | Supports | Focus moves in a logical, meaningful order consistent with the visual layout; no positive tabindex values are used. |
| 2.4.4 Link Purpose (In Context)Level A | Supports | Link text describes its destination or action; icon-only links carry descriptive aria-labels, and links that open a new tab are identified. |
| 2.5.1 Pointer GesturesLevel A | Supports | All functionality uses single-point activation; no path-based or multipoint gestures are required. |
| 2.5.2 Pointer CancellationLevel A | Supports | Activation occurs on the up-event, allowing actions to be aborted before completion. |
| 2.5.3 Label in NameLevel A | Supports | The accessible name of every control contains its visible label text. |
| 2.5.4 Motion ActuationLevel A | Supports | No functionality is operated by device or user motion. |
| 3.1.1 Language of PageLevel A | Supports | The lang="en" attribute is set on the html element of every page. |
| 3.2.1 On FocusLevel A | Supports | Moving focus to a component does not initiate a change of context. |
| 3.2.2 On InputLevel A | Supports | Changing a form control does not cause an unexpected change of context; where selecting a value submits a form, the outcome is predictable and consistent with the visible control. |
| 3.3.1 Error IdentificationLevel A | Supports | Input errors are described in text and programmatically associated with their fields via aria-describedby and aria-invalid; error regions are announced with aria-live. |
| 3.3.2 Labels or InstructionsLevel A | Supports | Every form control has a visible label or instruction; required fields and expected input formats are indicated. |
| 4.1.1 ParsingLevel A | Supports | Markup is well-formed: elements have complete start/end tags, are nested per specification, and contain no duplicate IDs. |
| 4.1.2 Name, Role, ValueLevel A | Supports | All user-interface components expose a correct name, role, and value through native HTML semantics and ARIA where needed (aria-expanded on disclosures, aria-label on icon-only controls, aria-live on status regions). |
WCAG 2.1 Report: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live)Level AA | Not Applicable | The product contains no live synchronized media. |
| 1.2.5 Audio Description (Prerecorded)Level AA | Not Applicable | The product contains no prerecorded video content. |
| 1.3.4 OrientationLevel AA | Supports | Content is not restricted to a single display orientation; the responsive layout functions in both portrait and landscape. |
| 1.3.5 Identify Input PurposeLevel AA | Supports | Fields that collect information about the user use the appropriate autocomplete tokens (email, name, given-name, family-name, current-password, new-password, organization). |
| 1.4.3 Contrast (Minimum)Level AA | Supports | All text meets at least 4.5:1 (3:1 for large text) against its background in both the light and dark themes, verified by computed contrast ratios across the entire color palette. |
| 1.4.4 Resize TextLevel AA | Supports | Text can be resized to 200% using browser zoom with no loss of content or functionality; relative font units are used. |
| 1.4.5 Images of TextLevel AA | Supports | All text is rendered as real text; the product uses no images of text. |
| 1.4.10 ReflowLevel AA | Supports | Content reflows to a single column at 320 CSS pixels of width without requiring two-dimensional scrolling; the layout is fully responsive. |
| 1.4.11 Non-text ContrastLevel AA | Supports | User-interface components, keyboard focus indicators, and meaningful graphical objects meet at least 3:1 contrast against adjacent colors in both themes. |
| 1.4.12 Text SpacingLevel AA | Supports | No loss of content or functionality occurs when users override line height, paragraph spacing, letter spacing, and word spacing. |
| 1.4.13 Content on Hover or FocusLevel AA | Supports | Additional content revealed on hover or focus (tooltips, dropdown menus) is dismissible, hoverable, and remains visible until dismissed. |
| 2.4.5 Multiple WaysLevel AA | Supports | More than one way is provided to locate content: persistent global navigation, the searchable review history, and direct links. |
| 2.4.6 Headings and LabelsLevel AA | Supports | Headings and labels are descriptive; each page has exactly one h1 and a logical, gap-free heading hierarchy. |
| 2.4.7 Focus VisibleLevel AA | Supports | A high-contrast (at least 3:1) focus-visible indicator is displayed for every keyboard-focusable element in both light and dark themes. |
| 3.1.2 Language of PartsLevel AA | Supports | All content is presented in English; no passages require a different lang value. |
| 3.2.3 Consistent NavigationLevel AA | Supports | Navigation appears in the same relative order on every page through the shared application layout. |
| 3.2.4 Consistent IdentificationLevel AA | Supports | Components with the same functionality are labeled and identified consistently throughout the product. |
| 3.3.3 Error SuggestionLevel AA | Supports | When an input error is detected and a correction is known, a suggestion is provided in text (password requirements and field format hints). |
| 3.3.4 Error Prevention (Legal, Financial, Data)Level AA | Supports | Actions with significant consequences are reversible or confirmable: destructive actions such as account deletion require explicit confirmation, and payment is processed by Stripe with an opportunity to review before submission. |
| 4.1.3 Status MessagesLevel AA | Supports | Status messages (inline saves, validation results, upload progress, filter result counts, bulk-action status) are programmatically exposed with role="status"/aria-live and do not move focus. |
Download This Report
Have an accessibility question or want to report a barrier? Contact accessibility@vpatscore.com.
Legal Disclaimer
This Accessibility Conformance Report is provided by Sterling Software LLC for informational purposes and represents the product's conformance with the referenced standards as of the report date. Accessibility is maintained as an ongoing commitment, and this report will be updated as the product evolves.
VPAT® is a registered trademark of the Information Technology Industry Council (ITI).