Accessibility Conformance Report
GSBKit ACR for the widget, dashboard, and trust pages.
This VPAT-style report documents current support levels for GSBKit-owned web surfaces. It is a procurement aid, not a legal guarantee or certification.
- Product
- GSBKit web widget and dashboard
- Report date
- June 11, 2026
- Standards reviewed
- WCAG 2.2 A/AA and Revised 508
Scope
Included: the production widget panel, dashboard home, sites, billing, profile, settings, alt-text tool, public trust pages, and government readiness pages. Excluded: customer websites where the widget is installed, customer-uploaded content, browser extensions, mobile apps, and non-GSBKit surfaces in this mixed repository.
Evaluation methods
- Automated axe-core checks covering dashboard pages, public trust pages, the government readiness pages, and the opened widget panel.
- Manual keyboard path checks, Escape handling, zoom-equivalent overflow checks, interactive control names, and Chrome accessibility-tree smoke checks.
- Code review for widget fail-silent behavior, focus handling, semantic controls, color contrast, and dashboard empty/error states.
WCAG 2.2 A/AA support table
Support levels are intentionally conservative. Items marked partially supported have known limits or need broader assistive-technology coverage before being raised.
| Criterion | Level | Support | Remarks |
|---|---|---|---|
| 1.1.1 Non-text Content | A | Partially Supports | Core GSBKit pages use alt text or decorative-hidden images. Customer content and legacy non-GSBKit marketing surfaces are outside this report. |
| 1.2.1 Audio-only and Video-only | A | Not Applicable | The evaluated widget and dashboard surfaces do not publish prerecorded audio-only or video-only content. |
| 1.2.2 Captions (Prerecorded) | A | Not Applicable | The evaluated surfaces do not publish prerecorded video content. |
| 1.2.3 Audio Description or Media Alternative | A | Not Applicable | The evaluated surfaces do not publish prerecorded video content. |
| 1.2.4 Captions (Live) | AA | Not Applicable | The evaluated surfaces do not publish live synchronized media. |
| 1.2.5 Audio Description (Prerecorded) | AA | Not Applicable | The evaluated surfaces do not publish prerecorded video content. |
| 1.3.1 Info and Relationships | A | Supports | Pages use headings, landmarks, lists, labels, tables, and semantic controls in the audited surfaces. |
| 1.3.2 Meaningful Sequence | A | Supports | Audited pages and the widget expose content in a logical DOM order. |
| 1.3.3 Sensory Characteristics | A | Supports | Instructions do not rely only on shape, color, size, or location. |
| 1.3.4 Orientation | AA | Supports | Audited pages and widget controls are responsive without locking a single orientation. |
| 1.3.5 Identify Input Purpose | AA | Partially Supports | Dashboard forms use visible labels; autocomplete coverage is still limited on some account and billing flows. |
| 1.4.1 Use of Color | A | Supports | Status and action labels use text in addition to color on audited surfaces. |
| 1.4.2 Audio Control | A | Not Applicable | Audited surfaces do not autoplay audio. |
| 1.4.3 Contrast (Minimum) | AA | Supports | The current axe audit reports zero contrast violations on audited GSBKit surfaces. |
| 1.4.4 Resize Text | AA | Supports | Manual zoom-equivalent checks pass without blocking horizontal overflow on audited pages. |
| 1.4.5 Images of Text | AA | Supports | Audited GSBKit UI text is rendered as text, not images of text. |
| 1.4.10 Reflow | AA | Supports | Manual viewport checks pass for audited dashboard, public, government, and widget surfaces. |
| 1.4.11 Non-text Contrast | AA | Supports | Audited focus indicators, controls, and status borders meet automated and manual checks. |
| 1.4.12 Text Spacing | AA | Partially Supports | Core layouts use normal text flow; dedicated text-spacing override testing is still a follow-up. |
| 1.4.13 Content on Hover or Focus | AA | Partially Supports | Primary audited flows do not depend on hover-only content; full tooltip behavior coverage remains limited. |
| 2.1.1 Keyboard | A | Supports | Manual checks confirm keyboard paths through audited pages and the opened widget panel. |
| 2.1.2 No Keyboard Trap | A | Supports | Manual checks confirm focus can move through audited surfaces and Escape closes the widget panel. |
| 2.1.4 Character Key Shortcuts | A | Not Applicable | Audited GSBKit surfaces do not define single-character keyboard shortcuts. |
| 2.2.1 Timing Adjustable | A | Not Applicable | Audited surfaces do not impose user-facing time limits. |
| 2.2.2 Pause, Stop, Hide | A | Supports | The evaluated widget and pages do not include blocking auto-moving content. |
| 2.3.1 Three Flashes or Below Threshold | A | Supports | Audited surfaces do not include flashing content. |
| 2.4.1 Bypass Blocks | A | Partially Supports | Pages use main landmarks; a visible skip link is still a follow-up for some public pages. |
| 2.4.2 Page Titled | A | Supports | Audited routes define meaningful page titles. |
| 2.4.3 Focus Order | A | Supports | Manual keyboard reviews found logical focus paths on audited pages. |
| 2.4.4 Link Purpose (In Context) | A | Supports | Audited links use descriptive text or clear surrounding context. |
| 2.4.5 Multiple Ways | AA | Partially Supports | Footer and navigation links expose core pages; full sitemap/navigation coverage remains mixed because the repo includes non-GSBKit surfaces. |
| 2.4.6 Headings and Labels | AA | Supports | Audited pages use visible headings and labels. |
| 2.4.7 Focus Visible | AA | Supports | Keyboard focus visibility is included in manual review. |
| 2.4.11 Focus Not Obscured (Minimum) | AA | Supports | Manual review did not find obscured focus targets on audited surfaces. |
| 2.5.1 Pointer Gestures | A | Supports | Audited controls do not require path-based or multipoint gestures. |
| 2.5.2 Pointer Cancellation | A | Supports | Buttons and links use standard activation behavior. |
| 2.5.3 Label in Name | A | Supports | Manual checks verify interactive controls expose usable names. |
| 2.5.4 Motion Actuation | A | Not Applicable | Audited surfaces do not require device motion or user motion. |
| 2.5.7 Dragging Movements | AA | Not Applicable | Audited GSBKit surfaces do not require dragging. |
| 2.5.8 Target Size (Minimum) | AA | Partially Supports | Primary controls are sized for use; full target-size measurement across all dashboard controls remains a follow-up. |
| 3.1.1 Language of Page | A | Supports | The root document declares English; widget translation states are client-side features. |
| 3.1.2 Language of Parts | AA | Partially Supports | The language picker stores language metadata; translated page fragments need broader language-tag verification. |
| 3.2.1 On Focus | A | Supports | Audited controls do not trigger unexpected context changes on focus. |
| 3.2.2 On Input | A | Supports | Audited inputs do not trigger unexpected context changes without user action. |
| 3.2.3 Consistent Navigation | AA | Supports | Dashboard and public trust navigation are consistent within their respective areas. |
| 3.2.4 Consistent Identification | AA | Supports | Repeated controls use consistent labels on audited surfaces. |
| 3.2.6 Consistent Help | A | Partially Supports | Footer and support paths are consistent on public pages; in-widget help patterns remain basic. |
| 3.3.1 Error Identification | A | Partially Supports | Dashboard forms show clear error states where implemented; several future setup flows are still empty-state based. |
| 3.3.2 Labels or Instructions | A | Supports | Audited forms and controls use visible labels or contextual instructions. |
| 3.3.3 Error Suggestion | AA | Partially Supports | Some forms provide recovery guidance; deeper validation-specific suggestions remain a follow-up. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | AA | Partially Supports | Billing actions rely on Stripe-hosted flows; destructive account/site actions use confirmation, but broader review workflows are still limited. |
| 3.3.7 Redundant Entry | A | Partially Supports | Dashboard data is reused where available; onboarding and account flows still need broader redundant-entry review. |
| 3.3.8 Accessible Authentication (Minimum) | AA | Partially Supports | Email-based auth is supported; third-party provider and password-reset details depend on Supabase configuration. |
| 4.1.1 Parsing | A | Not Applicable | This criterion is obsolete in WCAG 2.2 and is not used for the current evaluation. |
| 4.1.2 Name, Role, Value | A | Supports | Manual accessibility-tree checks verify named controls and the widget dialog semantics. |
| 4.1.3 Status Messages | AA | Partially Supports | Some dashboard states are visible text; not every async status has live-region behavior yet. |
Revised Section 508 notes
These rows summarize applicable software, support documentation, and support service areas for procurement review.
| Criterion | Level | Support | Remarks |
|---|---|---|---|
| 302 Functional Performance Criteria | Revised 508 | Partially Supports | Keyboard and visual checks pass for audited surfaces; screen-reader testing across multiple AT/browser combinations remains a deeper follow-up. |
| 501 General | Revised 508 | Partially Supports | GSBKit is web software with an audited widget and dashboard; coverage is limited to GSBKit-owned surfaces listed in this report. |
| 502 Interoperability with Assistive Technology | Revised 508 | Partially Supports | Semantic roles and names are present in audited Chrome accessibility-tree checks; full AT interoperability testing is not complete. |
| 503 Applications | Revised 508 | Partially Supports | The dashboard and widget use standard web controls and dialogs; some advanced workflows remain under development. |
| 504 Authoring Tools | Revised 508 | Partially Supports | The alt text tool helps create image alt text, but GSBKit is not yet a full content-authoring system. |
| 602 Support Documentation | Revised 508 | Supports | Public docs, transparency notes, accessibility statement, and this ACR are available online. |
| 603 Support Services | Revised 508 | Partially Supports | Support paths exist, but dedicated accessibility support SLAs and staffed government support procedures are not yet published. |
Known follow-ups
Deeper live screen-reader testing, full target-size measurement, tagged-PDF workflow coverage, map navigation coverage, and support-service procedures remain open product work. This report should be updated after those tickets ship.