Accessibility Product Conformance Report - WCAG 2.1 AA VPAT

Criteria

Conformance Level

Remarks and Explanations

1.1.1 Non-text Content

Partially Supports

Substantial remediation has been documented for alt text, decorative image handling, charts, cards, dashboards, simulation tables, HUD components, and repeated simulation UI patterns. Remaining manual follow-up is still required for some components to confirm that all meaningful images, charts, and other non-text content are correctly exposed.

1.2.1 Audio-only and Video-only (Prerecorded)

Not Applicable

No prerecorded audio-only or video-only content was identified in the evaluated Startup Wars application scope.

1.2.2 Captions (Prerecorded)

Not Applicable

No prerecorded synchronized media requiring captions was identified in the evaluated Startup Wars application scope. 

1.2.3 Audio Description or Media Alternative (Prerecorded)

Not Applicable

No prerecorded synchronized media requiring audio description or a media alternative was identified in the evaluated Startup Wars application scope.

1.2.4 Captions (Live)

Not Applicable

No live synchronized media requiring captions was identified in the evaluated Startup Wars application scope

1.2.5 Audio Description (Prerecorded)

Not Applicable

No prerecorded synchronized media requiring audio description was identified in the evaluated Startup Wars application scope

1.3.1 Info and Relationships

Partially Supports

Accessibility work has been documented for headings, landmarks, lists, tables, tablists, dialogs, radio groups, form labels, and labeled regions across the portals and simulation support UI. Full manual confirmation is still needed across all views and states.

1.3.2 Meaningful Sequence

Partially Supports

Multiple flows have been updated to improve document structure, step flow, reading order, focus order, and modal sequencing. Complete verification across all dynamic application states is not yet substantiated.

1.3.3 Sensory Characteristics

Partially Supports

Labels, instructions, hidden guidance, and explicit status text have been added across many selection, setup, modal, and simulation flows. Broader confirmation is still required to ensure all instructions avoid depending only on shape, location, or visual positioning.

1.4.1 Use of Color

Partially Supports

The reviewed evidence shows improvements to status text, pressed states, focus indicators, and other non-color cues. A full product-wide manual review for color-only meaning is not yet substantiated.

1.4.2 Audio Control

Not Applicable

No autoplaying audio content requiring an independent audio control was identified in the evaluated application scope.

2.1.1 Keyboard

Partially Supports

Many pointer-only interactions have been converted to native buttons, links, tabs, radios, or other keyboard-operable patterns. The application still requires broader end-to-end keyboard validation across all routes and live simulation interactions before a full Supports claim is justified.

2.1.2 No Keyboard Trap

Partially Supports

Documented improvements include dialog controls, close behavior, step-flow handling, escape handling, and overlay behavior. Remaining manual follow-up is still needed for some dialogs and dynamic interfaces to verify that keyboard users are never trapped.

2.1.4 Character Key Shortcuts

Not Applicable

No single-character keyboard shortcuts were identified in the evaluated web application interfaces.

2.2.1 Timing Adjustable

Partially Supports

Many portal and setup flows are user-paced, but the simulations include time-based and session-based behavior. The reviewed evidence does not yet substantiate full conformance across all timing-related scenarios.

2.2.2 Pause, Stop, Hide

Partially Supports

The reviewed application evidence does not show problematic autoplay media, and several status and loading behaviors have been improved. A complete review of all moving, blinking, scrolling, or auto-updating content across the simulation experience is not yet substantiated.

2.3.1 Three Flashes or Below Threshold

Supports

No content flashing more than three times per second was identified in the evaluated evidence.

2.4.1 Bypass Blocks

Partially Supports

Main regions and landmarks are present in key application areas, including important portal pages. A complete and consistent bypass-block strategy across all routes and simulation states has not yet been fully substantiated.

2.4.2 Page Titled

Partially Supports

The application includes document titles and route-level headings, but complete verification that each page and state exposes an accurate and useful title has not yet been substantiated across the full product.

2.4.3 Focus Order

Partially Supports

The reviewed remediation includes improvements to focus order in dialogs, billing flows, cards, dashboards, selection flows, and other simulation interfaces. Complete validation across all routes and dynamic states is not yet substantiated.

2.4.4 Link Purpose (In Context)

Partially Supports

Meaningful action names and context-aware labels have been added to many controls, including repeated cards, row actions, resource links, and simulation-related actions. Further manual verification is still needed to confirm consistent clarity across the full product.

2.5.1 Pointer Gestures

Supports

No multipoint or path-based pointer gestures were identified as required for the evaluated web application scope.

2.5.2 Pointer Cancellation

Partially Supports

The reviewed evidence shows movement toward more standard controls and safer interaction patterns. Full validation of pointer cancellation behavior across the complete live simulation experience is not yet substantiated.

2.5.3 Label in Name

Partially Supports

Accessible names have been improved across many dynamic controls and card-based interfaces. Full confirmation that visible labels consistently match programmatic names across all views is still pending.

2.5.4 Motion Actuation

Not Applicable

No motion-actuated features were identified in the evaluated desktop web application scope.

3.1.1 Language of Page

Supports

The evaluated application entry documents specify English as the page language.

3.2.1 On Focus

Partially Supports

The reviewed evidence shows reduced reliance on nonstandard focus behavior and stronger keyboard-safe interactions. Full validation across all focusable elements, dialogs, overlays, and simulation states is not yet substantiated.

3.2.2 On Input

Partially Supports

Forms, selectors, and stateful controls have been improved in many areas. Additional validation is still needed to confirm that changes of context occur only when expected across all workflows.

3.3.1 Error Identification

Partially Supports

The reviewed remediation includes improvements to validation messaging, invalid-field handling, and state-aware form behavior. Broader confirmation is still required across all forms and data-entry flows.

3.3.2 Labels or Instructions

Partially Supports

Labels and instructions have been added across forms, setup flows, dialogs, selectors, and simulation support interfaces. The remaining issue is incomplete verification across all product areas rather than a lack of documented remediation.

4.1.1 Parsing

Supports

The current accessibility inventory reports no remaining automated parsing-related issues in the inventoried templates reviewed by the accessibility program. 

4.1.2 Name, Role, Value

Partially Supports

Extensive remediation has been documented for accessible naming, roles, states, and values across portals, shared controls, and simulation support UI. The full application still requires broader validation before a complete Supports claim is justified.

4.1.2 Name, Role, Value

Partially Supports

Extensive remediation has been documented for accessible naming, roles, states, and values across portals, shared controls, and simulation support UI. The full application still requires broader validation before a complete Supports claim is justified.