Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 6 REVIEW 4 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.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ff4c00

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModePartial Dark Mode

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

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

No navigation patterns

FIX

No navigation patterns

3 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 3 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

6 landmarks

REVIEW

6 landmarks

<main> landmark present

3 <nav> landmark(s) found

2 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

Heading Hierarchy

Action

35 headings, 1 skip(s)

REVIEW

35 headings, 1 skip(s)

No H1 heading found

Every page should have one H1 that describes the page content.

Heading level skipped: H3 → H5 (missing H4)

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

H3 6 Ways to Implement Integrated Studies as a Music Teacher
H3 How to Help Students Develop a Personal Moral Compass for School
H3 How to Create Highly Effective, Discussion-Worthy Multiple-Choice Questions
H2 A Friendly Reminder!
H3 Building Empathy Through Mixed-Media Art
H3 How Do I Carve Out Time for What I Need to Do as a Leader?
H3 Low-Lift Elementary Classroom Routines That Get Students Ready to Learn
H3 A Simple Game to Teach Effective Storytelling
H3 Igniting Student Curiosity in Math and Science Lessons
H3 How Number Lines Can Boost Mathematical Understanding
H3 How to Avoid Rushing—a Pitfall for Even the Most Experienced Teachers
H3 Classroom Routines That Support Mathematical Thinking
H3 Streaming Toward Reading Fluency
H3 Writing Notes by Hand for Better Processing
H3 Why Students Give Up on a Task—and What Teachers Can Do About It
H3 60-Second Strategy: Whisper It in Your Hand
H3 Unlocking Effortful Thinking by Asking the Right Questions
H3 Nature-Based Activities for Preschool
H3 Building Students’ Confidence and Resilience by Shifting Your Attention
H3 5 Ways to Build Respect in Early Childhood Classrooms
H3 Building Empathy Through Haiku
H3 Lesson Starters That Work for You and Your Students
H3 60-Second Strategy: Whisper It in Your Hand
H3 Bouncing Back After a Class Is Interrupted
H3 Using Fun Songs to Transition Between Activities in Preschool
H3 Research-Backed Strategies to Keep Students on Task
H3 13 Books Featuring Characters With Disabilities and Physical Differences
H3 10 Books With Neurodivergent Characters
H3 A Principal’s 4 Steps for Reducing Chronic Absenteeism
H3 For Elementary Counselors, Big Caseloads Require Getting Creative
H3 Helping Students Return From a Long Absence
H5 Popular Topics skipped
H5 Grade Levels
H5 About Us
H3 Follow Edutopia

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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

Link & Button Quality

Action

30 issue(s) across 174 links and 37 buttons

REVIEW

30 issue(s) across 174 links and 37 buttons

6 link(s) open in new tab without warning

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

Got: https://www.facebook.com/edutopia; https://bsky.app/profile/edutopia.org; https://www.pinterest.com/edutopia/; https://www.instagram.com/edutopia/; https://www.youtube.com/edutopia; https://glef.org/

30 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.lite (#232 on page); button.lite (#254 on page); button.lite (#282 on page); button.lite (#329 on page); button.lite (#353 on page); button.lite (#377 on page); button.lite (#405 on page); button.lite (#430 on page); button.lite (#454 on page); button.lite (#482 on page) (+20 more)

168 link(s) with descriptive text

174 links

0 empty

0 generic text

6 new tab

30 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/edutopia	facebook icon	new tab	Add '(opens in new tab)' to text
https://bsky.app/profile/edutopia.org	bluesky icon	new tab	Add '(opens in new tab)' to text
https://www.pinterest.com/edutopia/	pinterest icon	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/edutopia/	instagram icon	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/edutopia	youtube icon	new tab	Add '(opens in new tab)' to text
https://glef.org/	George Lucas Educational Found…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

175 links and buttons have descriptive text

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

https://www.facebook.com/edutopia; https://bsky.app/profile/edutopia.org; https://www.pinterest.com/edutopia/; https://www.instagram.com/edutopia/; https://www.youtube.com/edutopia; https://glef.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

Icon-only buttons need an aria-label so screen readers can announce them.

button.lite (#232 on page); button.lite (#254 on page); button.lite (#282 on page); button.lite (#329 on page); button.lite (#353 on page); button.lite (#377 on page); button.lite (#405 on page); button.lite (#430 on page); button.lite (#454 on page); button.lite (#482 on page) (+20 more)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

404 Error Page

HTTP 404, custom page

REVIEW

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Edutopia ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Lighthouse Accessibility Audits

Score 87/100 — 3 failing, 18 passed

REVIEW

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite `div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite`

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.

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
INTEGRATED STUDIES `div.css-124ae9w > div.hero-card-bottom-wrap-bottom > div.css-1seknyz > div.eyebrow`
Bill Manchester `div.hero-card-bottom-wrap-bottom > div.css-1seknyz > div.css-rs4cum > a.css-1s343gm`
CRITICAL THINKING `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
Maurice J. Elias `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
FORMATIVE ASSESSMENT `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
Katie R. Medill `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
Hear from peers! `div.css-pfq62c > div.skeleton-container > div > a.css-1tz00mm`
SOCIAL & EMOTIONAL LEARNING (SEL) `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
ADMINISTRATION & LEADERSHIP `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
Andrew Miller `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
CLASSROOM MANAGEMENT `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
Wendy Turner `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
LITERACY `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
Andrew Paull `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
STUDENT ENGAGEMENT `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
Kathryn Lemerich `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
Jessica Holloway `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
RESEARCH `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
Andrea Tamayo `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
CURRICULUM PLANNING `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
Miriam Plotinsky `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
POPULAR `div.css-1f07lbu > div.css-jxc7g8 > div.css-q1v2j2 > span.css-1td86i2`
COMMUNICATION SKILLS `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
Christina Grassi `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
Meghan Lowe `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
TECHNOLOGY INTEGRATION `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
BRAIN-BASED LEARNING `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
STUDENT ENGAGEMENT `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
Cathleen Beachboard `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
TEACHING STRATEGIES `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
SOCIAL & EMOTIONAL LEARNING (SEL) `div.css-jxc7g8 > div.css-q1v2j2 > span.css-1td86i2 > a`
TEACHING STRATEGIES `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
SOCIAL & EMOTIONAL LEARNING (SEL) `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
Connie Morris `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
SOCIAL & EMOTIONAL LEARNING (SEL) `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
Donna Paul `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
SOCIAL & EMOTIONAL LEARNING (SEL) `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
Cara Zelas `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
SOCIAL & EMOTIONAL LEARNING (SEL) `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
Matthew James Friday `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
CLASSROOM MANAGEMENT `div.css-jxc7g8 > div.css-q1v2j2 > span.css-1td86i2 > a`
CLASSROOM MANAGEMENT `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
Rachel Lawton `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
TEACHING STRATEGIES `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
CLASSROOM MANAGEMENT `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
Crystal Frommert `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
CLASSROOM MANAGEMENT `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
Corrie Littlejohn-Pope `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
CLASSROOM MANAGEMENT `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
Todd Finley `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
STUDENT WELLNESS `div.css-jxc7g8 > div.css-q1v2j2 > span.css-1td86i2 > a`
STUDENT WELLNESS `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
Amy Brownlee `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
STUDENT WELLNESS `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
Amy Brownlee `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
ADMINISTRATION & LEADERSHIP `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
Jerald McNair `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
STUDENT WELLNESS `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
Sheila Garth `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
STUDENT WELLNESS `div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow`
Ella Miesner `div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm`
Privacy Policy `section > ul.css-p2bolw > li.css-11rkab1 > a.css-14vv2hs`
Terms of Use `section > ul.css-p2bolw > li.css-11rkab1 > a.css-14vv2hs`

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
POPULAR TOPICS `section.topic-links > nav.css-13gb0g9 > div.css-1swx3yj > h5.css-13tn2mc`

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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

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

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●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

○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

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

A+

Alt Text Quality

All 37 images OK

PASS

All 37 images OK

37 image(s) with good alt text

37 images 37 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 2 controls have issues

PASS

1 of 2 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="submit" name="op">

1 control(s) properly labeled

2 controls

1 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#headerSearch	text	Search	for/id
op	submit	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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
h2 A Friendly Reminder!	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Follow Edutopia	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Edutopia - What Work…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Close	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Edutopia	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Menu	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Topics	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Assessment	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Integrated Studies	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Project-Based Learni…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Social and Emotional…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Professional Learnin…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Technology Integrati…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a ALL TOPICS	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Videos	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Ask & Answer	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span POWER UP!	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Search	21.00:1	4.5:1	#000000	#FFFFFF	Pass
label Search	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Integrated Studies	21.00:1	4.5: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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.