Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 2 REVIEW 6 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-knrx1t

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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 Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://esl-go.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://esl-go.com/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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

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

Mobile-Readable Font Sizes

Action

73% of visible text renders at >= 12 CSS px (24 below threshold)

REVIEW

73% of visible text renders at >= 12 CSS px (24 below threshold)

24 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: <span> 10.0px ("By Elevate ESL Lessons"); <span> 10.0px ("Tenses & Structure"); <span> 11.0px ("lessons"); <p> 11.0px ("Targeted listening for present, past, fu..."); <span> 10.0px ("Idiomatic English").

Color Contrast (Screenshot)

Action

20 text elements analyzed, 3 fail WCAG AA

REVIEW

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

17 pass 3 fail WCAG AA

title Elevate Listening Lessons — Free Gramm…

1.44:1

#000000

#1E293B

needs 4.5:1 (normal text)

16px · top of page (header area)

span ELEVATE

1.44:1

#000000

#1E293B

needs 4.5:1 (normal text)

16px · top of page (header area)

span Listening Lessons

3.22:1

#000000

#6B5D26

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Free Listening Tests…	10.95:1	3.0:1	#000000	#EAB308	Pass
h2 Curated Practice Cat…	19.17:1	3.0:1	#000000	#F1F5F9	Pass
h2 Elevate ESL Lessons …	20.82:1	3.0:1	#000000	#FEFEFE	Pass
h2 How Our Grammar-Base…	20.82:1	3.0:1	#000000	#FEFEFE	Pass
h3 Present Simple Liste…	20.82:1	3.0:1	#000000	#FEFEFE	Pass
h3 Past Simple Listenin…	20.82:1	3.0:1	#000000	#FEFEFE	Pass
title Elevate Listening Le…	1.44:1	4.5:1	#000000	#1E293B	Fail
span ELEVATE	1.44:1	4.5:1	#000000	#1E293B	Fail
span Listening Lessons	3.22:1	4.5:1	#000000	#6B5D26	Fail
span By Elevate ESL Lesso…	10.95:1	4.5:1	#000000	#EAB308	Pass
button Home	10.95:1	4.5:1	#000000	#EAB308	Pass
span Listening Tests	10.95:1	4.5:1	#000000	#EAB308	Pass
span Tests	10.95:1	4.5:1	#000000	#EAB308	Pass
button About	10.95:1	4.5:1	#000000	#EAB308	Pass
button Contact	10.95:1	4.5:1	#000000	#EAB308	Pass
span English Listening Pr…	10.95:1	4.5:1	#000000	#EAB308	Pass
p Listen to recorded a…	19.17:1	4.5:1	#000000	#F1F5F9	Pass
span Full Directory (2)	19.17:1	4.5:1	#000000	#F1F5F9	Pass
p Choose a specific la…	19.17:1	4.5:1	#000000	#F1F5F9	Pass
span Tenses & Structure	19.17:1	4.5:1	#000000	#F1F5F9	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.

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

14 headings, 1 skip(s)

PASS

14 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

H1 Free Listening Tests Organized by Grammar
H2 Curated Practice Categories
H3 Grammar Structures
H3 Phrasal Verbs in Action
H3 Idioms & Real Expressions
H3 Everyday Dialogues
H2 Listening Practice Tests
H3 Present Simple Listening Practice: Daily Routines & Schedules
H3 Past Simple Listening Practice: Weekend Stories & Memorable Events
H2 Elevate ESL Lessons on Teachers Pay Teachers
H2 How Our Grammar-Based Listening Works
H4 Authentic Audio Dialogues skipped
H4 Grammar-Targeted Questions
H4 Instant Self-Grading

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 8 images OK

PASS

All 8 images OK

8 image(s) with good alt text

8 images 8 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
input	text	(Search grammar or topic...)	placeholder only

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Link & Button Quality

3 links, 17 buttons — all OK

PASS

3 links, 17 buttons — all OK

2 link(s) open in new tab without warning

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

Got: https://www.teacherspayteachers.com/store/elevate-esl-lessons; https://www.teacherspayteachers.com/store/elevate-esl-lessons

1 link(s) with descriptive text

3 links

0 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.teacherspayteachers.com/stor…	Visit Elevate Store on TPT	new tab	Add '(opens in new tab)' to text
https://www.teacherspayteachers.com/stor…	TPT StorePrintables & PPT	new tab	Add '(opens in new tab)' to text

18 links and buttons have descriptive text

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

https://www.teacherspayteachers.com/store/elevate-esl-lessons; https://www.teacherspayteachers.com/store/elevate-esl-lessons

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

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "Search grammar or topic..." should use type="search" (currently type="text")

Field name "Search grammar or topic..." suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

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"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

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

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.

Lighthouse Accessibility Audits

Score 90/100 — 2 failing, 12 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.

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
Choose a specific language focus to view corresponding listening practice tests. `div.mb-10 > div.flex > div > p.text-xs`
Click on any test to open the self-contained listening audio and interactive qu… `div.max-w-6xl > div.flex > div > p.text-xs`
Showing 2 tests `div > div.max-w-6xl > div.flex > span.text-xs`
Start test `div.p-5 > div.pt-3 > span.inline-flex > span`
Start test `div.p-5 > div.pt-3 > span.inline-flex > span`
Visit Elevate Store on TPT `div.max-w-6xl > section.bg-gradient-to-r > a.inline-flex > span`
01 `div.max-w-6xl > div.grid > div.bg-white > span.text-amber-600`
02 `div.max-w-6xl > div.grid > div.bg-white > span.text-amber-600`
03 `div.max-w-6xl > div.grid > div.bg-white > span.text-amber-600`
Listening Lessons `div.flex > div.flex > div.font-extrabold > span.text-amber-600`
TPT Store `div.max-w-6xl > div.flex > a.text-[#00897b] > span`
© 2026 Elevate Listening Lessons. All rights reserved. Free audio practice, gra… `div.min-h-screen > footer.border-t > div.border-t > p`

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
Authentic Audio Dialogues `div.max-w-6xl > div.grid > div.bg-white > h4.font-bold`

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-hidden="true"]` is not present on the document `<body>`

●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-hidden="true"]` elements do not contain focusable descendents

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○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

○Elements use only permitted ARIA attributes

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

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

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

○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

○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

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

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