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 4 REVIEW 4 FIX

Document Language

Action

Missing <html lang> attribute (WCAG 3.1.1)

FIX

Missing <html lang> attribute (WCAG 3.1.1)

Without `<html lang="...">`, screen readers default to the user's system language even when reading content in a different one -- words get pronounced wrong (English text read with French phonetics, etc.). Add a BCP-47 language tag to the <html> root element.

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Page Title AILearnHub: Turn Any Topic into an AI-Generated Lesson ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

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

Hamburger menu detected (responsive design)

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)

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

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

1 <nav> landmark(s) found

No banner (header) landmark

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

Mobile-Readable Font Sizes

Action

85% of visible text renders at >= 12 CSS px (42 below threshold)

REVIEW

85% of visible text renders at >= 12 CSS px (42 below threshold)

42 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 ("Time Left:"); <span> 10.0px ("Get Deal Now"); <div> 11.0px ("Expert tutor + multi-discipline peers"); <div> 11.0px ("Automatic knowledge path building"); <div> 11.0px ("Whiteboard lessons + practice checks").

Favicon & Branding

7 icon(s) detected

REVIEW

7 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

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

Heading Hierarchy

52 headings, 1 skip(s)

PASS

52 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

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

H1 Turn What You Want to Learn into a Complete AI-Generated Lesson
H3 Fourier Transform (4-step intuition) skipped
H2 Turn Curiosities into Knowledge
H3 Introduction to OpenClaw
H2 AILearnHub is an AI learning tool that turns a topic into a real lesson
H3 Start from what you want to learn
H3 Generate a structured learning flow
H3 Get something closer to courseware
H2 A simple workflow from learning intent to lesson output
H3 Describe the topic or goal
H3 Let AILearnHub organize the material
H3 Review, study, or teach from it
H2 The real problem is not finding information. It is turning it into something learnable.
H3 Reduce learning friction and start sooner
H3 Give information a clearer structure
H3 Bridge the gap to understanding
H2 Built for Every Kind of Learner
H3 Students
H3 Working Professionals
H3 Self-Learners
H3 Educators & Trainers
H2 How to Learn Effectively with AI
H3 Set a Clear Goal Before You Start
H3 Use Active Recall, Not Passive Reading
H3 Space Out Your Study Sessions
H3 Teach What You Learn
H3 Review and Iterate
H2 What Users Say
H2 Simple pricing for calmer reading
H3 Free
H3 Pro
H3 Max
H2 Frequently Asked Questions
H3 Product Basics
H4 What is AILearnHub?
H4 Is AILearnHub an AI learning tool or a content platform?
H4 Can I turn any topic into a lesson with AILearnHub?
H3 How It Works
H4 How does AILearnHub generate lessons?
H4 What kind of input can I give AILearnHub?
H4 What does AILearnHub generate as output?
H3 Who It Is For
H4 Who is AILearnHub for?
H4 Can AILearnHub help with self-study?
H4 Can teachers or educators use AILearnHub?
H3 Why Use It
H4 Why use AILearnHub instead of searching for materials manually?
H4 How is AILearnHub different from a generic AI chatbot?
H4 Is AILearnHub free to try?
H2 Start Turning Topics into Lessons
H3 Product
H3 Legal

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 52 heading(s) have substantive, well-formed text

PASS

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

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

A+

Alt Text Quality

All 20 images OK

PASS

All 20 images OK

20 image(s) with good alt text

20 images 20 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 3 controls have issues

PASS

1 of 3 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="file">

2 control(s) properly labeled

3 controls

2 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
select	select	Select language	aria-label
input	text	Learning topic	aria-label
input	file	(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

Link & Button Quality

20 links, 14 buttons — all OK

PASS

20 links, 14 buttons — all OK

3 link(s) open in new tab without warning

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

Got: https://chromewebstore.google.com/detail/ailearnhub/dgihjimekmhphkbnnnomcbemh…; https://firstlook.tools/; https://firstlook.tools/

17 link(s) with descriptive text

20 links

0 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://chromewebstore.google.com/detail…	Start for free	new tab	Add '(opens in new tab)' to text
https://firstlook.tools/	Featured on First Look	new tab	Add '(opens in new tab)' to text
https://firstlook.tools/	Featured on First Look	new tab	Add '(opens in new tab)' to text

31 links and buttons have descriptive text

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

https://chromewebstore.google.com/detail/ailearnhub/dgihjimekmhphkbnnnomcbemh…; https://firstlook.tools/; https://firstlook.tools/

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

3 form control(s) checked, no type mismatches

PASS

3 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

3 form control(s) checked, no input-semantic issues

PASS

3 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+

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+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: AILearnHub

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name AILearnHub ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name AILearnHub Display Mode standalone Theme Color #8b5cf6 Background Color #ffffff Icons 2 icon(s)

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

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
h2 Turn Curiosities int…	19.72:1	3.0:1	#000000	#F4F8FF	Pass
h2 AILearnHub is an AI …	19.72:1	3.0:1	#000000	#F4F8FF	Pass
h2 A simple workflow fr…	19.72:1	3.0:1	#000000	#F4F8FF	Pass
h2 The real problem is …	19.72:1	3.0:1	#000000	#F4F8FF	Pass
h2 Built for Every Kind…	19.72:1	3.0:1	#000000	#F4F8FF	Pass
h2 How to Learn Effecti…	19.72:1	3.0:1	#000000	#F4F8FF	Pass
h2 What Users	19.72:1	3.0:1	#000000	#F4F8FF	Pass
h2 Simple pricing for c…	19.72:1	3.0:1	#000000	#F4F8FF	Pass
h2 Frequently Asked	19.72:1	3.0:1	#000000	#F4F8FF	Pass
h2 Start Turning Topics…	19.72:1	3.0:1	#000000	#F4F8FF	Pass
h3 Fourier Transform (4…	19.72:1	3.0:1	#000000	#F4F8FF	Pass
h3 Introduction to Open…	19.72:1	3.0:1	#000000	#F4F8FF	Pass
h3 Start from what you …	19.72:1	3.0:1	#000000	#F4F8FF	Pass
h3 Generate a structure…	19.72:1	3.0:1	#000000	#F4F8FF	Pass
h3 Get something closer…	19.72:1	3.0:1	#000000	#F4F8FF	Pass
h3 Describe the topic o…	19.72:1	3.0:1	#000000	#F4F8FF	Pass
h3 Let AILearnHub organ…	19.72:1	3.0:1	#000000	#F4F8FF	Pass
h3 Review, study, or te…	19.72:1	3.0:1	#000000	#F4F8FF	Pass
h3 Reduce learning fric…	19.72:1	3.0:1	#000000	#F4F8FF	Pass
h3 Give information a c…	19.72:1	3.0:1	#000000	#F4F8FF	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.

Lighthouse Accessibility Audits

Score 90/100 — 3 failing, 22 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
Practice `div.relative > div.relative > div.flex > span.mt-0.5`
Quiz `div.relative > div.relative > div.flex > span.mt-0.5`
Apply `div.relative > div.relative > div.flex > span.mt-0.5`
Deep interaction `div.mt-4 > div.flex > button.relative > span.pt-px`
Recommended `div.mt-4 > div.flex > button.relative > span.absolute`
01 `article.group > div.min-w-0 > div.flex > span.text-xs`
02 `article.group > div.min-w-0 > div.flex > span.text-xs`
03 `article.group > div.min-w-0 > div.flex > span.text-xs`
04 `article.group > div.min-w-0 > div.flex > span.text-xs`
05 `article.group > div.min-w-0 > div.flex > span.text-xs`

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
Fourier Transform (4-step intuition) `div.relative > div.relative > div.flex > h3.mb-6`

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

○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

●Document has a `<title>` element

●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

●Identical links have the same purpose.

●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

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has a valid value for its `[lang]` attribute

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

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

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