Last updated: April 2026
Code.org is committed to making our platform accessible to all learners, including those with disabilities. We conduct annual third-party accessibility evaluations against WCAG 2.1 Level AA guidelines and publish the results here. Our current conformance status, detailed findings, and progress over time are documented below.
For districts navigating ADA Title II
The ADA Title II enforcement deadline for digital accessibility is April 24, 2026 (see the ADA website for more details). While Code.org is not itself bound by Title II, we understand that our school and district customers are. If you need to document the accessibility status of tools in your curriculum, our 2026 VPAT provides the third-party verified evidence most compliance reviews require.
2026 at a glance
- 20% increase in fully supported criteria since our 2024 assessment
- Of 50 WCAG criteria, 24 fully supported, 20 partially supported, 4 not applicable — only 2 criteria not yet supported
- Third-party verified by Deque, an industry-leading accessibility evaluator
- Annual assessments published every year so you always have current documentation
Is Code.org conformant with WCAG 2.1 Level AA?
Code.org continues to make significant and active progress toward WCAG 2.1 Level A and AA conformance. These gains are spread across our learning experiences, but highlights from the past year include expanding support for keyboard navigation, increasing alt text coverage, and ensuring correct language attributes across the platform.
While we do not yet fully conform to all success criteria across all experiences, we are actively addressing identified gaps and are making steady progress towards full conformance.
What’s challenging about accessibility in computer science tools?
Some areas of computer science education are especially hard to make accessible, such as interactive visuals, animation, games, and block-based coding environments. These rely heavily on visual-only outputs (e.g., sprites, characters, app screens) that don't yet have widely adopted solutions for blind or low-vision learners.
Many interactive coding platforms face similar challenges in meeting WCAG 2.1 AA requirements for highly visual programming environments. We believe in being honest and transparent, and we’re pushing the field forward through research, partnerships, and innovation.
Our pace of improvement reflects the nature of accessibility work over time. Early gains often come from systematic fixes like language attributes, page titles, and alt text that can be addressed at scale across the platform. The criteria we're still working toward tend to involve more complex, interactive experiences like block-based coding environments and visual programming outputs, where solutions require deeper engineering investment and, in some cases, new approaches that don't yet have industry-wide precedent.
What are we doing next?
In 2026, we’re prioritizing:
- Ensuring our newest and upcoming courses (AI Foundations for high school and AI Discoveries for middle school) meet WCAG 2.1 A and AA standards
- Expanding screen reader compatibility within our Blockly-based coding labs
- Improving color contrast across interactive components
- Continuing annual third-party accessibility assessments and publishing updated VPAT reports
Current VPAT
In Spring 2026, we conducted our annual accessibility assessment with independent third-party evaluator Deque, using the Voluntary Product Accessibility Template (VPAT). This assessment measures our conformance to WCAG 2.1 Level A and AA standards, the current federal benchmark for digital accessibility under the ADA. Our evaluation is based on representative sample pages and may not reflect every individual page or configuration.
Each criterion in the table below is rated using one of these categories:
- Supports: Product functionality contains at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some product functionality meets the criterion.
- Not Yet Supported: The majority of product functionality currently does not meet the criterion, but improvement work is planned or underway.
- N/A: Not Applicable - the criterion is not relevant to the product.
[View the full 2026 VPAT/ACR Report here]
| Criteria | Conformance Level |
| Success Criteria, Level A | |
| 1.1.1 Non-text Content (Level A) | Partially Supports |
| 1.2.1 Audio Only and Video-only (Prerecorded) (Level A) | Partially Supports |
| 1.2.2 Captions (Prerecorded) (Level A) | N/A |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | N/A |
| 1.3.1 Info and Relationships (Level A) | Not Yet Supported |
| 1.3.2 Meaningful Sequence (Level A) | Partially Supports |
| 1.3.3 Sensory Characteristics (Level A) | Supports |
| 1.4.1 Use of Color (Level A) | Partially Supports |
| 1.4.2 Audio Control (Level A) | Supports |
| 2.1.1 Keyboard (Level A) | Partially Supports |
| 2.1.2 No Keyboard Trap (Level A) | Supports |
| 2.1.4 Character Key Shortcuts (Level A 2.1 only) | Supports |
| 2.2.1 Timing Adjustable (Level A) | Partially Supports |
| 2.2.2 Pause, Stop, Hide (Level A) | Supports |
| 2.3.1 Three Flashes Below Threshold (Level A) | N/A |
| 2.4.1 Bypass Blocks (Level A) | Supports |
| 2.4.2 Page Titled (Level A) | Supports |
| 2.4.3 Focus Order (Level A) | Partially Supports |
| 2.4.4 Link Purpose (In Context) (Level A) | Partially Supports |
| 2.5.1 Pointer Gestures (Level A 2.1 only) | Supports |
| 2.5.2 Pointer Cancellation (Level A 2.1 only) | Supports |
| 2.5.3 Label in Name (Level A 2.1 only) | Supports |
| 2.5.4 Motion Actuation (Level 2.1 Only) | Supports |
| 3.1.1 Language of Page (Level A) | Supports |
| 3.2.1 On Focus (Level A) | Supports |
| 3.2.2 On Input (Level A) | Supports |
| 3.3.1 Error Identification (Level A) | Supports |
| 3.3.2 Labels or Instructions (Level A) | Partially Supports |
| 4.1.1 Parsing (Level A) | Supports |
| 4.1.2 Name, Role, Value (Level A) | Not Yet Supported |
| Success Criteria, Level AA | |
| 1.2.4 Captions Live (Prerecorded) (Level AA) | N/A |
| 1.2.5 Audio Description (Prerecorded) (Level AA) | Partially Supports |
| 1.3.4 Orientation (Level AA 2.1 only) | Supports |
| 1.3.5 Identify Input Purpose (Level AA 2.1 only) | Supports |
| 1.4.3 Contrast (Minimum) (Level AA) | Partially Supports |
| 1.4.4 Resize text (Level AA) | Partially Supports |
| 1.4.5 Images of Text (Level AA) | Partially Supports |
| 1.4.10 Reflow (Level AA 2.1 only) | Partially Supports |
| 1.4.11 Non-text Contrast (Level AA 2.1 only) | Partially Supports |
| 1.4.12 Text Spacing (Level AA 2.1 only) | Partially Supports |
| 1.4.13 Content on Hover or Focus (Level AA 2.1 only) | Partially Supports |
| 2.4.5 Multiple Ways (Level AA) | Supports |
| 2.4.6 Headings and Labels (Level AA) | Partially Supports |
| 2.4.7 Focus Visible (Level AA) | Partially Supports |
| 3.1.2 Language of Parts (Level AA) | Supports |
| 3.2.3 Consistent Navigation (Level AA) | Supports |
| 3.2.4 Consistent Identification (Level AA) | Supports |
| 3.3.3 Error Suggestion (Level AA) | Supports |
| 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) | Supports |
| 4.1.3 Status Messages (Level AA 2.1 only) | Partially Supports |
You can see our past VPAT/ACR reports here:
Need more information?
Do you have a question that wasn't answered here? Email us at accessibility@code.org