Skip to content
https://code.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
7
REVIEW
1
PASS
5
INFO
0
Checks
13
5 PASS 1 REVIEW 7 FIX
D
Heading Hierarchy
Action
55 headings, 3 skip(s)
FIX
55 headings, 3 skip(s)
Warning::
Multiple H1 headings (13 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 AI is reshaping the world
  • H2 Education must lead what comes next
  • H5 The Hour of Code sparked a generation. This fall, the Hour of AI will define the next. skipped
  • H1 It’s here: the newest Hour of AI activity duplicate H1
  • H2 We are the experts in preparing students for an AI-driven world.
  • H3 AI is built on CS. We teach both.
  • H1 107M duplicate H1
  • H1 1.94B duplicate H1
  • H1 3M duplicate H1
  • H1 190 duplicate H1
  • H1 190 duplicate H1
  • H1 50 U.S. states duplicate H1
  • H1 190 duplicate H1
  • H2 Join the group shaping what comes next.
  • H2 Why Now
  • H2 Join the group shaping what comes next.
  • H2 Why now?
  • H2 From puzzles to software engineering
  • H2 The new Web Lab is live! Jump right in.
  • H2 Celebrate National AI Literacy Day, March 27
  • H2 Why now?
  • H2 Why Now
  • H1 Professional learning built for educators. duplicate H1
  • H2 Our work
  • H4 Curriculum for the AI era skipped
  • H4 Setting the standard
  • H4 System-level change
  • H1 102M duplicate H1
  • H1 3M duplicate H1
  • H2 AI + CS Education is for every student, everywhere
  • H2 Every student deserves to thrive in an AI-driven world.
  • H2 Bring artificial intelligence to your classroom
  • H2 For computer science classes
  • H3 How AI Makes Decisions
  • H3 Coding with AI
  • H3 Artificial Intelligence Foundations
  • H2 For all subjects
  • H3 AI for Oceans
  • H3 Generative AI for Humanities
  • H3 Societal Impact of Generative AI
  • H2 The most widely used AI+CS curriculum in the U.S.
  • H2 Want to understand AI? Start here.
  • H2 Exploring Generative AI
  • H2 Professional learning for teachers at all levels
  • H2 Help expand access to AI education
  • H3 Help students
  • H3 District support
  • H3 Advocacy Coalition
  • H2 Backed by global leaders
  • H1 Join millions teaching and learning duplicate H1
  • H2 Start your AI education journey
  • H5 Students skipped
  • H5 Educators
  • H5 Parents
  • H5 Districts

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

D
404 Error Page
Action
HTTP 404, custom page
FIX
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

18 pass 2 fail WCAG AA
h1 AI is reshaping the world
1.10:1
#000000
on
#081018
needs 3.0:1 (large text)
32px · above the fold
h2 Education must lead what comes next
1.09:1
#000000
on
#070F17
needs 3.0:1 (large text)
24px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 AI is reshaping the …1.10:13.0:1
#000000
#081018
Fail
h1 It’s here: the new…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 107M21.00:13.0:1
#000000
#FFFFFF
Pass
h1 1.94B21.00:13.0:1
#000000
#FFFFFF
Pass
h1 19021.00:13.0:1
#000000
#FFFFFF
Pass
h1 19021.00:13.0:1
#000000
#FFFFFF
Pass
h1 50 U.S. states21.00:13.0:1
#000000
#FFFFFF
Pass
h1 19021.00:13.0:1
#000000
#FFFFFF
Pass
h1 Professional learnin…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 102M21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Join millions teachi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Education must lead …1.09:13.0:1
#000000
#070F17
Fail
h2 We are the experts i…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Join the group shapi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Why Now21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Join the group shapi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Why now?21.00:13.0:1
#000000
#FFFFFF
Pass
h2 From puzzles to soft…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The new Web Lab is l…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Celebrate National A…21.00:13.0:1
#000000
#FFFFFF
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A
Landmark Structure
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV "Main navigation" MAIN CONTENTINFO footer

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

A+
Alt Text Quality
All 57 images OK
PASS
All 57 images OK
Info::
53 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
57 images 4 good alt text 53 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
language-selectselectLanguage selection dropdownaria-label
A+
Lighthouse Accessibility Audits
Score 95/100 — 3 failing, 23 passed
PASS
95

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
WHO WE ARE div.cf-4c41f6a4d0f6d9764d017cb615a0857c > div.cf-97f92044dc40a2f5f0093c31861b9841 > div.cf-c3206da2b9ad45bfcd0bb3b3549acb47 > p.MuiTypography-root
FLAGSHIP WORK section.section-background-secondary > div.MuiContainer-root > div.cf-ad95f457ade13bd9c8fd2226396dce62 > p.MuiTypography-root
OUR SUPPORTERS div.cf-8b4434df2a9778b5ef0b45338ad7044d > div.cf-98672fd7b4fe05d51c848acf6d8959b1 > div.cf-d6e4617d602895b466c7440880251b1f > p.MuiTypography-root

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Curriculum for the AI era div.cf-a7c8dbcf2b8e47039ae8d687b4f06d99 > div.cf-63e35c8243004acac65b04828fdd9a47 > div.cf-f6a86e00f23d5ad8f796977a686bc25c > h4.MuiTypography-root

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Learn about Code.org div.cf-97f92044dc40a2f5f0093c31861b9841 > div.cf-5171f0cd3bd370039acfda30d9bd4c01 > div.cf-19fa17c745ec096b6396c78685291e49 > a.genericButton-module__button___-ZvEw
Explore more stats div.cf-97f92044dc40a2f5f0093c31861b9841 > div.cf-5171f0cd3bd370039acfda30d9bd4c01 > div.cf-793ea3ccffb5860a2e85fc3fc0a1a02e > a.genericButton-module__button___-ZvEw
Partner with us div.cf-c75c47033e830504de35b5df5840ea5f > div.cf-1664d88001345c4955b130e4604c0a1d > div.cf-d63c92cb905caad3d90b4c391c27ebc8 > a.genericButton-module__button___-ZvEw
Explore curriculum catalog div.cf-503a38a75061122bc5d2aa1222d3213a > div.cf-a318afa9f3a81b1b7a0bb62e50593924 > div.cf-8fef7fbb8527341d663afedbed841ef3 > a.genericButton-module__button___-ZvEw
Get started now div.cf-6d9929e522f0aa34377f6efce0f8c247 > div.cf-25973a64a5784700b2a80e055ebfcfb5 > div.cf-883b8fa4bbcfcecabbee156469550e16 > a.genericButton-module__button___-ZvEw
Read the Framework div.cf-81eb36cf5c15490dae991c5d843279a1 > div.cf-670a77c1bf4aec010c56b582328319f6 > div.cf-4a29891aecab19aa62b4e710ca426272 > a.genericButton-module__button___-ZvEw
Meet our supporters div.cf-8b4434df2a9778b5ef0b45338ad7044d > div.cf-98672fd7b4fe05d51c848acf6d8959b1 > div.cf-ae51a5a9e52d3cdce5283a41fb9a6798 > a.genericButton-module__button___-ZvEw
Sign up for free section.section-background-patternPrimary > div.MuiContainer-root > div.cf-3c6501cbcaeb07b42da6b85d8ed7c835 > a.genericButton-module__button___-ZvEw
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Select elements have associated label elements.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback