Skip to content
https://improvingliteracy.org

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
82
GRADE
B
FIX
4
REVIEW
5
PASS
15
INFO
0
Checks
24
15 PASS 5 REVIEW 4 FIX
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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <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.
B
Heading Hierarchy
29 headings, 2 skip(s)
REVIEW
29 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
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.
  • H6 National Center on Improving Literacy
  • H4 Search site
  • H4 Topics
  • H4 Content Types
  • H4 Tools
  • H1 Free Evidence-Based Resources for Literacy Success
  • H3 Why Does Fluent Reading Matter? skipped
  • H3 Understanding the New IDA Dyslexia Definition
  • H3 Key Roles for Children’s Literacy Success
  • H2 Explore by Topic
  • H2 For Families
  • H3 Is Your Child Having Trouble Reading? Warning Signs and a Checklist
  • H3 How Families Can Partner With Schools on Literacy Development
  • H3 Screening for Emergent Literacy During Well Visits
  • H2 For Educators
  • H3 Understanding Screening: Statistical Bias
  • H3 Instructional Coaching: Understanding the Role with Ready-to-Use Resources
  • H3 Succeeding in School: Essential Features of Literacy Development
  • H2 Decision-Support Tools
  • H5 Multi-Tiered System of Support in Reading Guide skipped
  • H5 Adolescent Assessment of Literacy Tool
  • H5 State of Dyslexia Legislation Map
  • H5 Benchmark Effectiveness & Actionable Core Outcomes Navigator
  • H5 Pre-K Reading Assessment
  • H2 Want Support?
  • H2 About Us
  • H2 In Partnership With
  • H3 Contact Us
  • H3 Stay In Touch

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

B
Mobile-Readable Font Sizes
96% of visible text renders at >= 12 CSS px (3 below threshold)
REVIEW
96% of visible text renders at >= 12 CSS px (3 below threshold)
Info::
3 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <p> 11.0px ("By submitting this form, you are consent..."); <a> 11.0px ("Emails are serviced by Constant Contact."); <a> 11.0px ("Our Privacy Policy.").
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 7 fail WCAG AA
REVIEW

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

13 pass 7 fail WCAG AA 3 pass AA only
title National Center on Improving Literacy
3.82:1
#000000
on
#007481
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
3.82:1
#000000
on
#007481
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to footer
3.82:1
#000000
on
#007481
needs 4.5:1 (normal text)
16px · top of page (header area)
a National Center on
3.82:1
#000000
on
#007481
needs 4.5:1 (normal text)
16px · top of page (header area)
a Improving Literacy
3.82:1
#000000
on
#007481
needs 4.5:1 (normal text)
16px · above the fold
span Resources
3.82:1
#000000
on
#007481
needs 4.5:1 (normal text)
16px · above the fold
a Alphabetic Principle & Phonics
3.82:1
#000000
on
#007481
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Free Evidence-Based …5.60:13.0:1
#000000
#33909A
Pass
h2 Explore by Topic5.60:13.0:1
#000000
#33909A
Pass
h2 For Families5.60:13.0:1
#000000
#33909A
Pass
h2 For Educators5.60:13.0:1
#000000
#33909A
Pass
h2 Decision-Support Too…5.60:13.0:1
#000000
#33909A
Pass
h2 Want Support?5.60:13.0:1
#000000
#33909A
Pass
h2 About Us5.60:13.0:1
#000000
#33909A
Pass
h2 In Partnership With5.60:13.0:1
#000000
#33909A
Pass
h3 Contact Us5.60:13.0:1
#000000
#33909A
Pass
h3 Stay In Touch5.60:13.0:1
#000000
#33909A
Pass
title National Center on I…3.82:14.5:1
#000000
#007481
Fail
a Skip to main content3.82:14.5:1
#000000
#007481
Fail
a Skip to footer3.82:14.5:1
#000000
#007481
Fail
a National Center on3.82:14.5:1
#000000
#007481
Fail
a Improving Literacy3.82:14.5:1
#000000
#007481
Fail
h4 Search site3.82:13.0:1
#000000
#007481
Pass
span Search4.88:14.5:1
#000000
#208691
Pass
span Resources3.82:14.5:1
#000000
#007481
Fail
h4 Topics3.82:13.0:1
#000000
#007481
Pass
a Alphabetic Principle…3.82:14.5:1
#000000
#007481
Fail

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
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Menu" MAIN CONTENTINFO footer
A+
Heading Text Quality
All 29 heading(s) have substantive, well-formed text
PASS
All 29 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
1 of 16 images have issues
PASS
1 of 16 images have issues
Warning::
1 image(s) with filename as alt text
Info::
15 image(s) with good alt text
16 images 15 good alt text 1 generic
IssueCount
filename1 image(s)
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
#search-input-hdfnavsearchSearchfor/id
A+
Form Input Types
1 form control(s) checked, no type mismatches
PASS
1 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
1 form control(s) checked, no input-semantic issues
PASS
1 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found – National Center on Improving Literacy ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
A
Lighthouse Accessibility Audits
Score 94/100 — 2 failing, 22 passed
PASS
94

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.

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
Why Does Fluent Reading Matter? div.brxe-tyiinw > div.brxe-kbwsif > div.brxe-svpiga > h3.brxe-yufles
Multi-Tiered System of Support in Reading Guide div#brxe-a93740 > div#brxe-9bc943 > div#brxe-fef12d > h5#brxe-000914

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#brxe-yirjjm > ul.brxe-ylmdvp > li.repeater-item > a div#brxe-yirjjm > ul.brxe-ylmdvp > li.repeater-item > a
div#brxe-yirjjm > ul.brxe-ylmdvp > li.repeater-item > a div#brxe-yirjjm > ul.brxe-ylmdvp > li.repeater-item > a
div#brxe-yirjjm > ul.brxe-ylmdvp > li.repeater-item > a div#brxe-yirjjm > ul.brxe-ylmdvp > li.repeater-item > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

○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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●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
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●ARIA IDs are unique
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[role]`s have all required `[aria-*]` attributes
○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
○`[role]` values are valid
○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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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.
○Elements with visible text labels have matching accessible names.
○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