This page summarizes the current Startup Wars Accessibility Conformance Report. It is intended to help educators, accessibility teams, and procurement reviewers understand the evaluated scope, methods, and limits.
Product and report details
- Product: Startup Wars
- Report date: April 15, 2026
- Product type: A web-based educational application with an instructor portal, student portal, and interactive entrepreneurship simulations
- Standard reviewed: WCAG 2.1 Level A and Level AA
Current conformance statement
Startup Wars Partially Supports WCAG 2.1 Level A and Level AA.
This is the strongest conformance statement supported by the current evaluation. Startup Wars does not claim full WCAG 2.1 AA conformance across every route, dialog, simulation state, or assistive technology scenario.
“Partially Supports” means that significant areas appear to meet a success criterion, while gaps, incomplete validation, or unverified states remain.
How to read the status terms
The terms have set meanings in this report.
- Supports means the proof reviewed for this scope shows that the product meets the rule.
- Partially Supports means that much of the product may meet the rule, but gaps or test work remain.
- Does Not Support means that the proof shows the product does not meet the rule.
- Not Applicable means that the rule does not apply to the scope that was checked.
- Not Evaluated means there is not enough proof to rate the rule.
A status applies only to the scope and date of the report. It is not a promise about each task, browser, device, or access tool. Schools should test the tasks that matter to their own users.
Evaluated scope
The report covers:
- the instructor portal;
- the student portal; and
- the simulation-related web interface, including the shell UI, heads-up displays, dialogs, overlays, setup flows, reports, and shared support components.
The evaluation reviewed documented accessibility remediation, component inventory coverage, and automated smoke tests for selected login, instructor, student, and simulation-launch flows.
The April 2026 evaluation used Google Chrome on a 2019 MacBook Pro. Assistive technology checks included NVDA, Apple VoiceOver, and keyboard-only navigation.
Product-area summary
Instructor portal: Partially Supports
Accessibility work has addressed dashboards, class and assignment flows, tables, billing and publishing flows, navigation, and dialogs. Current evidence does not establish complete WCAG 2.1 AA conformance across all instructor routes and states.
Student portal: Partially Supports
Accessibility work has addressed dashboards, classes, assignment selection, simulation launch paths, dialogs, and accessible names. Key flows have automated smoke coverage, but complete assistive technology validation across all student states has not been substantiated.
Simulations: Partially Supports
Accessibility work has addressed setup, tutorials, overlays, heads-up displays, reports, store flows, goals, and shared simulation UI. Current evidence is not sufficient to claim full conformance for every live simulation state and gameplay interaction.
Areas of documented progress
The report identifies work in these areas:
- headings, landmarks, lists, tables, and labeled regions;
- native buttons, links, tabs, and other keyboard-operable controls;
- dialog focus, close, escape, and overlay behavior;
- accessible names, roles, states, and values;
- contrast and visible focus styling;
- status messages and live-region announcements; and
- form labels, instructions, validation, and error handling.
Many WCAG 2.1 A and AA criteria remain rated Partially Supports because complete manual verification across all product states is not finished. The current report rates a smaller set as Supports or Not Applicable within the evaluated scope. These include specific criteria for flashing content, page language, language of parts, and certain gestures or media that were not present.
Reflow and the simulation surface
For WCAG 2.1 success criterion 1.4.10, the essential two-dimensional Phaser gameplay surface is treated as an exception where two-dimensional interaction is fundamental to the activity. This exception does not apply to the surrounding web interface, such as menus, dialogs, overlays, heads-up display text, controls, and support flows.
The report rates reflow as Partially Supports because surrounding interface work is documented, while full product-wide verification remains in progress.
What schools should verify
Accessibility needs differ by learner and course. Before adoption, schools should test the workflows their students and instructors will use. A review may include:
- signing in and finding an assignment;
- navigating with a keyboard only;
- using NVDA, VoiceOver, or the institution’s required screen reader;
- opening and closing dialogs;
- reviewing visible focus and contrast;
- zooming and resizing surrounding web content;
- completing a simulation launch and a representative activity; and
- reviewing errors, status messages, and reports.
Ask Startup Wars about known limits, current remediation, and an appropriate alternative if a required workflow presents a barrier.
A short test plan
Pick a task that a student must do in class. Write down each step. Then try the same task with a keyboard. Check that focus is easy to see. Make sure each control has a clear name. Open and close each dialog. Check that an error tells the user what went wrong and how to fix it.
Next, repeat the task with the screen reader used by your school. Listen for the page title, headings, labels, and status updates. Zoom the page and check the web controls around the game. Keep notes on each barrier and the exact step where it took place.
Share the notes with Startup Wars before the lesson. Ask what fix, support, or other path is available. Test that path as well. This gives the school and the learner a clear plan.
Accessibility support and feedback
If you experience an accessibility barrier or need assistance:
- Email support@startupwars.com with the subject Accessibility Support.
- Call (215) 821-8673.
- Report a web accessibility issue.
For a plain-language overview of the work, read how Startup Wars is building toward WCAG 2.1 AA. Schools can also contact the Startup Wars team to discuss a specific workflow or procurement review.