Skip to content
https://loremipsum.io

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
4
REVIEW
8
PASS
12
INFO
0
Checks
24
12 PASS 8 REVIEW 4 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
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 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
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.
B
Heading Text Quality
1 heading-text-quality issue(s) detected
REVIEW
1 heading-text-quality issue(s) detected
Warning::
3 heading(s) contain placeholder / generic text
Some headings contain placeholder or generic text patterns that often leak through from CMS templates / WYSIWYG defaults / unfinished drafts. Affected (first 3): - H1: "Lorem Ipsum" - H2: "Lorem Ipsum Generator" - H2: "Lorem Ipsum All the Things" Replace with descriptive text that summarizes the section's content. Search engines use heading text to understand page structure; placeholder text contributes nothing to relevance signals.
Got: 3 placeholder heading(s)
C
Form Accessibility
Action
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input name="n">; <select name="t">; <input type="submit">
3 controls
0 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
ninput(none)none
tselect(none)none
inputsubmit(none)none

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

<input name="n">; <select name="t">; <input type="submit">

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

B
Iframe Accessibility
3/4 iframe(s) missing title; 0 placeholder(s)
REVIEW
3/4 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="about:blank")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
C
Tap Target Adequacy
Action
4 tap target(s) too small or too close together
REVIEW
4 tap target(s) too small or too close together
Warning::
4 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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'>.
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✗ 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, 19 fail WCAG AA
REVIEW

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

1 pass 19 fail WCAG AA
h2 What is Lorem Ipsum?
1.09:1
#000000
on
#0B0F0F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Origins and Discovery
1.09:1
#000000
on
#0B0F0F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Fuzzy Beginnings
1.09:1
#000000
on
#0B0F0F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Meaning of Lorem Ipsum
1.09:1
#000000
on
#0B0F0F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Usage and Examples
1.09:1
#000000
on
#0B0F0F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Controversy in the Design World
1.09:1
#000000
on
#0B0F0F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 When to Use Lorem Ipsum
1.09:1
#000000
on
#0B0F0F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Lorem Ipsum All the Things
1.09:1
#000000
on
#0B0F0F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Original Source Text
1.09:1
#000000
on
#0B0F0F
needs 3.0:1 (large text)
24px · bottom of viewport
h3 History, Purpose and Usage
1.09:1
#000000
on
#0B0F0F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Hedonist Roots
1.09:1
#000000
on
#0B0F0F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Remixing a Classic
1.09:1
#000000
on
#0B0F0F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Interpreting Nonsense
1.09:1
#000000
on
#0B0F0F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Digital Ipsum
1.09:1
#000000
on
#0B0F0F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Design or (Dis)content
1.09:1
#000000
on
#0B0F0F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Form Over Function
1.09:1
#000000
on
#0B0F0F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Because it’s the Internet
1.09:1
#000000
on
#0B0F0F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Section 1.10.32 of Cicero’s “De fini…
1.09:1
#000000
on
#0B0F0F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Section 1.10.33 of Cicero’s “De fini…
1.09:1
#000000
on
#0B0F0F
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Lorem Ipsum21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What is Lorem Ipsum?1.09:13.0:1
#000000
#0B0F0F
Fail
h2 Origins and Discover…1.09:13.0:1
#000000
#0B0F0F
Fail
h2 Fuzzy Beginnings1.09:13.0:1
#000000
#0B0F0F
Fail
h2 Meaning of Lorem Ips…1.09:13.0:1
#000000
#0B0F0F
Fail
h2 Usage and Examples1.09:13.0:1
#000000
#0B0F0F
Fail
h2 Controversy in the D…1.09:13.0:1
#000000
#0B0F0F
Fail
h2 When to Use Lorem Ip…1.09:13.0:1
#000000
#0B0F0F
Fail
h2 Lorem Ipsum All the …1.09:13.0:1
#000000
#0B0F0F
Fail
h2 Original Source Text1.09:13.0:1
#000000
#0B0F0F
Fail
h3 History, Purpose and…1.09:13.0:1
#000000
#0B0F0F
Fail
h3 Hedonist Roots1.09:13.0:1
#000000
#0B0F0F
Fail
h3 Remixing a Classic1.09:13.0:1
#000000
#0B0F0F
Fail
h3 Interpreting Nonsens…1.09:13.0:1
#000000
#0B0F0F
Fail
h3 Digital Ipsum1.09:13.0:1
#000000
#0B0F0F
Fail
h3 Design or (Dis)conte…1.09:13.0:1
#000000
#0B0F0F
Fail
h3 Form Over Function1.09:13.0:1
#000000
#0B0F0F
Fail
h3 Because it’s the I…1.09:13.0:1
#000000
#0B0F0F
Fail
h3 Section 1.10.32 of C…1.09:13.0:1
#000000
#0B0F0F
Fail
h3 Section 1.10.33 of C…1.09:13.0:1
#000000
#0B0F0F
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.

B
Lighthouse Accessibility Audits
Score 80/100 — 5 failing, 23 passed
REVIEW
80

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.md:col-span-8 > div.w-full > div.flex > button.flex div.md:col-span-8 > div.w-full > div.flex > button.flex

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.w-full > div.flex > form.flex > input.sm:w-16 div.w-full > div.flex > form.flex > input.sm:w-16

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Paragraphs Sentences Words div.w-full > div.flex > form.flex > select.sm:w-36

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
© 2015–2026 body.__variable_59b718 > footer.grid > div.flex > span.md:text-base
Sitemap body.__variable_59b718 > footer.grid > div.flex > span.md:text-base

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Font Generator div.flex > ul.sm:col-span-3 > li > a.md:text-base
Name Generator div.flex > ul.sm:col-span-3 > li > a.md:text-base
Placeholders div.flex > ul.sm:col-span-3 > li > a.md:text-base
Generators div.flex > ul.sm:col-span-3 > li > a.md:text-base

These items highlight common accessibility best practices.

○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
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●`[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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Warning::
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
BANNER header NAV MAIN CONTENTINFO footer

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

A
Heading Hierarchy
22 headings, 1 skip(s)
PASS
22 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Lorem Ipsum
  • H2 Lorem Ipsum Generator
  • H4 Discover More skipped
  • H2 What is Lorem Ipsum?
  • H3 History, Purpose and Usage
  • H2 Origins and Discovery
  • H3 Hedonist Roots
  • H2 Fuzzy Beginnings
  • H3 Remixing a Classic
  • H2 Meaning of Lorem Ipsum
  • H3 Interpreting Nonsense
  • H2 Usage and Examples
  • H3 Digital Ipsum
  • H2 Controversy in the Design World
  • H3 Design or (Dis)content
  • H2 When to Use Lorem Ipsum
  • H3 Form Over Function
  • H2 Lorem Ipsum All the Things
  • H3 Because it’s the Internet
  • H2 Original Source Text
  • H3 Section 1.10.32 of Cicero’s “De finibus bonorum et malorum”
  • H3 Section 1.10.33 of Cicero’s “De finibus bonorum et malorum”

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+
Alt Text Quality
All 9 images OK
PASS
All 9 images OK
Info::
9 image(s) with good alt text
9 images 9 good alt text
All images have appropriate alt text.
A+
Form Input Types
3 form control(s) checked, no type mismatches
PASS
3 form control(s) checked, no type mismatches
Info::
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
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"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Mobile-Readable Font Sizes
All 211 visible text node(s) render at >= 12 CSS pixels
PASS
All 211 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback