Accessibility Conformance Report
Impact Suite — VPAT® 2.x, WCAG Edition
A web-based platform used by AmeriCorps and other national service programs to capture member activity, measure impact, and report outcomes to funders and state commissions.
- Standard evaluated
- WCAG 2.1 Level AA
- Report date
- July 29, 2026
- Vendor
- America Learns, LLC
Vendor and product information
| Vendor name | America Learns, LLC |
|---|---|
| Product name | Impact Suite |
| Product version | Continuously released — new features ship every 1–6 weeks; no fixed version number. |
| Report date | July 29, 2026 |
| Standard / guidelines applied | WCAG 2.1 Level AA (VPAT® 2.x, WCAG Edition) |
| Report author | Gary Kosman, Chief Executive Officer, America Learns |
| Accessibility contact | support@americalearns.net · 310-689-0542 |
| Responsible for accessibility policy and compliance | Gary Kosman, CEO (leads the UI/UX team) |
Conformance summary
44
Supports
0
Partially Supports
0
Does Not Support
6
Not Applicable
44 of the 50 WCAG 2.1 Level A and AA success criteria are fully supported. The remaining 6 are not applicable because the Impact Suite contains no audio or video media.
Terms used in this report
- Supports — the functionality of the product meets the criterion without known defects or 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.
Evaluation methods used
- Human factors testing with participants drawn from our live user base, which ranges in age from 16 to 90+.
- Testing with participants who navigate without the use of their hands, including foot-driven input and mouth stylus users.
- Testing with participants who have low vision or light sensitivity.
- Screen reader verification with NVDA (Windows) and VoiceOver (macOS / iOS).
- One-on-one and small-group feedback sessions on every new module prior to release.
- Image- and video-driven surveys distributed to broad segments of the user base.
- Manual keyboard-only traversal and browser zoom testing up to 200%.
Accessibility commitment and governance
Our user base includes people from the ages of 16 through 90 and above. When we build new modules, we conduct human factors tests with people who represent that base — people of different ages, people with a range of physical abilities including those who navigate with their feet or a mouth stylus rather than their hands, and people with vision-specific needs including low vision and light sensitivity.
The Impact Suite works with both the NVDA and VoiceOver screen reading platforms. Our development practice is to design each feature in collaboration with a wide group of our users before it ships, and to revise the interface when that feedback shows a barrier.
Responsibility. Gary Kosman, CEO (leads the UI/UX team) owns accessibility policy and compliance and leads the UI/UX team that designs each feature in collaboration with users.
Keeping current. We track changing legal requirements and accessibility best practices, solicit structured feedback on every new module from broad segments of our user base, and act on client-reported needs as they arise.
Demonstrations. America Learns can provide live or pre-recorded demonstrations of the accessibility of the Impact Suite on request.
Reporting an issue. Email support@americalearns.net or call 310-689-0542. Reports are acknowledged, reproduced, and prioritized according to the impact on affected users, and the reporter is kept informed through resolution.
WCAG 2.1 Level A and AA success criteria
Showing 50 of 50 success criteria.
Perceivable
| Criterion | Level | Conformance | Remarks and explanations |
|---|---|---|---|
| 1.1.1 Non-text ContentAll non-text content presented to the user has a text alternative that serves the equivalent purpose. | A | Supports | Icons, charts, and graphical controls carry text alternatives or accessible names. Decorative imagery is marked so that assistive technology skips it. |
| 1.2.1 Audio-only and Video-only (Prerecorded)An alternative is provided for prerecorded audio-only content, and an alternative or audio track is provided for prerecorded video-only content. | A | Not Applicable | Not applicable. The Impact Suite contains no prerecorded or live audio or video media. If media is introduced in a future release, this criterion will be re-evaluated and this report updated. |
| 1.2.2 Captions (Prerecorded)Captions are provided for all prerecorded audio content in synchronized media. | A | Not Applicable | Not applicable. The Impact Suite contains no prerecorded or live audio or video media. If media is introduced in a future release, this criterion will be re-evaluated and this report updated. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded)An alternative for time-based media or audio description of prerecorded video content is provided for synchronized media. | A | Not Applicable | Not applicable. The Impact Suite contains no prerecorded or live audio or video media. If media is introduced in a future release, this criterion will be re-evaluated and this report updated. |
| 1.2.4 Captions (Live)Captions are provided for all live audio content in synchronized media. | AA | Not Applicable | Not applicable. The Impact Suite contains no prerecorded or live audio or video media. If media is introduced in a future release, this criterion will be re-evaluated and this report updated. |
| 1.2.5 Audio Description (Prerecorded)Audio description is provided for all prerecorded video content in synchronized media. | AA | Not Applicable | Not applicable. The Impact Suite contains no prerecorded or live audio or video media. If media is introduced in a future release, this criterion will be re-evaluated and this report updated. |
| 1.3.1 Info and RelationshipsInformation, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. | A | Supports | Pages use semantic headings, lists, landmarks, and data tables with header associations. Form controls are programmatically associated with their labels. |
| 1.3.2 Meaningful SequenceA correct reading sequence can be programmatically determined. | A | Supports | DOM order matches visual reading order across all modules, including multi-column reporting layouts. |
| 1.3.3 Sensory CharacteristicsInstructions do not rely solely on sensory characteristics such as shape, size, visual location, orientation, or sound. | A | Supports | Instructional text names controls by their visible label rather than by position, shape, or color alone. |
| 1.3.4 OrientationContent does not restrict its view and operation to a single display orientation unless essential. | AA | Supports | The responsive interface operates in both portrait and landscape on phones and tablets; orientation is never locked. |
| 1.3.5 Identify Input PurposeThe purpose of each input field collecting information about the user can be programmatically determined. | AA | Supports | Fields collecting user identity and contact information use standard autocomplete tokens and appropriate input types. |
| 1.4.1 Use of ColorColor is not used as the only visual means of conveying information. | A | Supports | Status, validation, and chart series are conveyed with text labels, icons, or patterns in addition to color. |
| 1.4.2 Audio ControlA mechanism is available to pause, stop, or control the volume of audio that plays automatically for more than three seconds. | A | Not Applicable | Not applicable. The Impact Suite contains no prerecorded or live audio or video media. If media is introduced in a future release, this criterion will be re-evaluated and this report updated. |
| 1.4.3 Contrast (Minimum)Text and images of text have a contrast ratio of at least 4.5:1 (3:1 for large text). | AA | Supports | The interface palette was revised following our 2026 accessibility review; body and large text meet or exceed the required ratios. |
| 1.4.4 Resize TextText can be resized without assistive technology up to 200 percent without loss of content or functionality. | AA | Supports | Verified via browser zoom to 200% in Chrome, Safari, Firefox, and Edge. Layouts reflow without clipping or loss of function. |
| 1.4.5 Images of TextText is used to convey information rather than images of text, except where customizable or essential. | AA | Supports | All interface text, including headings, buttons, labels, and report output, is rendered as live text. Images of text are not used. |
| 1.4.10 ReflowContent can be presented without loss of information or functionality and without two-dimensional scrolling at 320 CSS pixels wide. | AA | Supports | The responsive layout reflows to a single column on narrow viewports. Wide data tables scroll horizontally within their own region, which is a permitted exception. |
| 1.4.11 Non-text ContrastUser interface components and graphical objects have a contrast ratio of at least 3:1 against adjacent colors. | AA | Supports | Control borders, focus indicators, and chart elements meet the 3:1 minimum following the 2026 palette revision. |
| 1.4.12 Text SpacingNo loss of content or functionality occurs when users override line height, paragraph spacing, letter spacing, and word spacing. | AA | Supports | Text containers expand with content; no fixed-height text boxes clip content when spacing overrides are applied. |
| 1.4.13 Content on Hover or FocusAdditional content triggered by hover or focus is dismissible, hoverable, and persistent. | AA | Supports | Tooltips and popovers can be dismissed with the Escape key, remain visible while hovered, and persist until dismissed or focus moves. |
Operable
| Criterion | Level | Conformance | Remarks and explanations |
|---|---|---|---|
| 2.1.1 KeyboardAll functionality is operable through a keyboard interface. | A | Supports | Every workflow, including data entry, reporting, and administration, is completable with the keyboard alone. Verified during human factors testing with participants who do not use a mouse. |
| 2.1.2 No Keyboard TrapKeyboard focus can be moved away from any component using only the keyboard. | A | Supports | Dialogs and menus trap focus only while open and release it on Escape or close, returning focus to the triggering control. |
| 2.1.4 Character Key ShortcutsSingle-character key shortcuts can be turned off, remapped, or are active only on focus. | A | Supports | The Impact Suite implements no single-character key shortcuts. |
| 2.2.1 Timing AdjustableUsers can turn off, adjust, or extend time limits set by the content. | A | Supports | The platform imposes no task time limits. Session expiry warnings are presented in advance and can be extended with a single action. |
| 2.2.2 Pause, Stop, HideMoving, blinking, scrolling, or auto-updating information can be paused, stopped, or hidden. | A | Supports | The interface contains no auto-scrolling, blinking, or auto-advancing content. Loading indicators are the only motion and are brief and non-essential. |
| 2.3.1 Three Flashes or Below ThresholdContent does not flash more than three times per second. | A | Supports | No flashing content exists anywhere in the platform. |
| 2.4.1 Bypass BlocksA mechanism is available to bypass blocks of content repeated on multiple pages. | A | Supports | A skip-to-main-content link is the first focusable element on each page, and ARIA landmarks allow screen reader users to jump between regions. |
| 2.4.2 Page TitledPages have titles that describe their topic or purpose. | A | Supports | Each screen sets a unique, descriptive document title reflecting the module and record in view. |
| 2.4.3 Focus OrderFocusable components receive focus in an order that preserves meaning and operability. | A | Supports | Tab order follows the visual and logical reading order. Opening a dialog moves focus into it; closing returns focus to the trigger. |
| 2.4.4 Link Purpose (In Context)The purpose of each link can be determined from the link text alone or with its programmatically determined context. | A | Supports | Links are written descriptively. Ambiguous phrasing such as "click here" is avoided; icon-only links carry accessible names. |
| 2.4.5 Multiple WaysMore than one way is available to locate a page within a set of pages, except where the page is a step in a process. | AA | Supports | Users can reach any screen via persistent primary navigation, in-app search, dashboard shortcuts, and direct links. Steps within a guided submission flow are the permitted exception. |
| 2.4.6 Headings and LabelsHeadings and labels describe topic or purpose. | AA | Supports | Headings follow a logical hierarchy without skipped levels, and every form control has a descriptive visible label. |
| 2.4.7 Focus VisibleAny keyboard-operable interface has a visible focus indicator. | AA | Supports | A high-contrast focus ring is applied to all interactive elements and is never suppressed. |
| 2.5.1 Pointer GesturesFunctionality using multipoint or path-based gestures can be operated with a single pointer without those gestures. | A | Supports | No multipoint or path-based gestures are required; all actions have single-pointer and keyboard equivalents. |
| 2.5.2 Pointer CancellationFunctions triggered by a single pointer can be aborted or undone. | A | Supports | Actions activate on pointer-up, so a user can move off a control before releasing to cancel. |
| 2.5.3 Label in NameFor components with visible text labels, the accessible name contains the visible text. | A | Supports | Accessible names match visible labels so that speech-input users can activate controls by saying what they see. |
| 2.5.4 Motion ActuationFunctionality operated by device or user motion can also be operated by user interface components. | A | Supports | No functionality is triggered by device motion or gestures. |
Understandable
| Criterion | Level | Conformance | Remarks and explanations |
|---|---|---|---|
| 3.1.1 Language of PageThe default human language of each page can be programmatically determined. | A | Supports | Each page declares its language on the root HTML element. |
| 3.1.2 Language of PartsThe human language of each passage or phrase can be programmatically determined. | AA | Supports | Passages that differ from the page language are marked with the appropriate language attribute. |
| 3.2.1 On FocusReceiving focus does not initiate a change of context. | A | Supports | No component triggers navigation, submission, or a context change on focus alone. |
| 3.2.2 On InputChanging the setting of a component does not automatically change context unless the user has been advised. | A | Supports | Selections require explicit confirmation before navigation or submission. Where a change updates the view, the behavior is described in advance. |
| 3.2.3 Consistent NavigationRepeated navigational mechanisms occur in the same relative order on each page. | AA | Supports | Global navigation, utility controls, and footer links are consistent across modules. |
| 3.2.4 Consistent IdentificationComponents with the same functionality are identified consistently. | AA | Supports | Shared actions such as save, export, and delete use the same label and icon throughout the platform. |
| 3.3.1 Error IdentificationInput errors that are automatically detected are identified and described to the user in text. | A | Supports | Errors are described in text next to the field in error, associated programmatically, and announced to screen readers. |
| 3.3.2 Labels or InstructionsLabels or instructions are provided when content requires user input. | A | Supports | Every field has a persistent visible label, with format guidance and required-field indication provided in text. |
| 3.3.3 Error SuggestionIf an input error is detected and corrections are known, suggestions are provided to the user. | AA | Supports | Validation messages state the expected format or value range rather than reporting a generic failure. |
| 3.3.4 Error Prevention (Legal, Financial, Data)Submissions that create legal or financial commitments, modify user data, or submit test responses are reversible, checked, or confirmed. | AA | Supports | Reversible. Submitted records can be reopened and corrected, and destructive actions require explicit confirmation. |
Robust
| Criterion | Level | Conformance | Remarks and explanations |
|---|---|---|---|
| 4.1.1 ParsingElements have complete start and end tags, are nested correctly, avoid duplicate attributes, and use unique IDs. | A | Supports | Markup is generated by a component framework that produces well-formed output with unique element identifiers. |
| 4.1.2 Name, Role, ValueFor all user interface components, name and role can be programmatically determined, and states, properties, and values can be programmatically set. | A | Supports | Native HTML elements are used wherever possible; custom widgets expose correct roles, names, states, and values and were verified with NVDA and VoiceOver. |
| 4.1.3 Status MessagesStatus messages can be programmatically determined through role or properties without receiving focus. | AA | Supports | Save confirmations, validation summaries, and background progress updates are announced through live regions without moving focus. |
Legal disclaimer
This Accessibility Conformance Report is a self-assessment prepared by America Learns, LLC and reflects the state of the Impact Suite as of July 29, 2026. It is not a third-party certification or audit. The Impact Suite is under continuous development, and America Learns makes no warranty that the product is free of accessibility defects. To confirm you are referencing the current version of this report, or to request a signed copy or a live accessibility demonstration, contact support@americalearns.net. VPAT® is a registered service mark of the Information Technology Industry Council (ITI).