https://improvingliteracy.org/resource/understanding-the-new-ida-dyslexia-definition/

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

17 PASS 4 REVIEW 3 FIX

Web Manifest

Action

Not found

FIX

Not found

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

2 navigation pattern(s)

FIX

2 navigation pattern(s)

Breadcrumb navigation detected

Got: aria-label

Skip navigation link detected

2 navigation landmark(s) detected

Breadcrumbs aria-label navigation

Skip Link Skip link detected

Labeled Navigation 2 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

Link & Button Quality

Action

3 issue(s) across 64 links and 6 buttons

REVIEW

3 issue(s) across 64 links and 6 buttons

3 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://www.facebook.com/improvingliteracy; https://www.linkedin.com/company/national-center-on-improving-literacy; https://www.youtube.com/@improvingliteracy

2 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.stateofdyslexia.org/; https://www.stateofdyslexia.org/

59 link(s) with descriptive text

64 links

3 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.stateofdyslexia.org/	Dyslexia Policy & Legislation	new tab	Add '(opens in new tab)' to text
https://www.stateofdyslexia.org/	State of Dyslexia Legislation …	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/improvinglitera…	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/nationa…	(empty)	empty	Add link text or aria-label
https://www.youtube.com/@improvinglitera…	(empty)	empty	Add link text or aria-label

65 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://www.facebook.com/improvingliteracy; https://www.linkedin.com/company/national-center-on-improving-literacy; https://www.youtube.com/@improvingliteracy

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://www.stateofdyslexia.org/; https://www.stateofdyslexia.org/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Mobile-Readable Font Sizes

97% of visible text renders at >= 12 CSS px (3 below threshold)

REVIEW

97% of visible text renders at >= 12 CSS px (3 below threshold)

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.").

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

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.

A+

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

14 headings, 1 skip(s)

PASS

14 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H5 (missing H2)

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 Understanding the New IDA Dyslexia Definition
H5 What the Highlights Mean skipped
H4 New Definition of Dyslexia (2025)
H4 Key Updates
H3 How Schools Identify Dyslexia and Other Learning Disabilities
H3 4 Questions to Ask After Universal Screening for Dyslexia
H3 Understanding Dyslexia: Signs to Watch for by Age
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

A+

Heading Text Quality

All 14 heading(s) have substantive, well-formed text

PASS

All 14 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 9 images OK

PASS

All 9 images OK

9 image(s) with good alt text

9 images 9 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#search-input-hdfnav	search	Search	for/id

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

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

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

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"

<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

A+

Iframe Accessibility

No iframes on this page

PASS

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

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

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Understanding the Ne…	19.79:1	3.0:1	#000000	#F9F8F6	Pass
h3 Contact Us	19.79:1	3.0:1	#000000	#F9F8F6	Pass
h3 Stay In Touch	19.79:1	3.0:1	#000000	#F9F8F6	Pass
title Understanding the Ne…	14.48:1	4.5:1	#000000	#C7DADB	Pass
a Skip to main content	14.48:1	4.5:1	#000000	#C7DADB	Pass
a Skip to footer	19.79:1	4.5:1	#000000	#F9F8F6	Pass
p Free Evidence-Based …	19.79:1	4.5:1	#000000	#F9F8F6	Pass
a National Center on	19.79:1	4.5:1	#000000	#F9F8F6	Pass
a Improving Literacy	19.79:1	4.5:1	#000000	#F9F8F6	Pass
h4 Search site	19.79:1	3.0:1	#000000	#F9F8F6	Pass
span Search	19.79:1	4.5:1	#000000	#F9F8F6	Pass
span Resources	19.79:1	4.5:1	#000000	#F9F8F6	Pass
h4 Topics	19.79:1	3.0:1	#000000	#F9F8F6	Pass
a Alphabetic Principle…	19.79:1	4.5:1	#000000	#F9F8F6	Pass
a Comics	19.79:1	4.5:1	#000000	#F9F8F6	Pass
a Dyslexia	19.79:1	4.5:1	#000000	#F9F8F6	Pass
a Dyslexia Policy & Le…	19.79:1	4.5:1	#000000	#F9F8F6	Pass
a Fluency & Comprehens…	19.79:1	4.5:1	#000000	#F9F8F6	Pass
a Instruction & Interv…	19.79:1	4.5:1	#000000	#F9F8F6	Pass
a Learning to Read & W…	19.79:1	4.5:1	#000000	#F9F8F6	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+

Lighthouse Accessibility Audits

Score 98/100 — 1 failing, 26 passed

PASS

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
What the Highlights Mean `div#brxe-lhkfiq > div#brxe-oxafde > div#brxe-frrezu > h5.wp-block-heading`

These are opportunities to improve keyboard navigation in your application.

○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

●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.

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Elements with visible text labels have matching accessible names.

○`[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

○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.

○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.