Skip to content
https://prettysites.io

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
79
GRADE
C
FIX
5
REVIEW
5
PASS
14
INFO
0
Checks
24
14 PASS 5 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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: #080808
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

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 ✗
D
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
6 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 6 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Landmark Structure
13 landmarks
REVIEW
13 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
1 of 6 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Main navigation" SEARCH MAIN ASIDE "Two-prompt pack" CONTENTINFO footer

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

B
Heading Hierarchy
58 headings, 1 skip(s)
REVIEW
58 headings, 1 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Choose a siteCopy designMake it yours
  • H3 OFFGRID skipped
  • H3 Try this site with your product
  • H3 MILO FACES
  • H3 Jenga Games
  • H3 OVAL Atelier
  • H3 Cell Studio
  • H3 Aerolume
  • H3 Bee2Bee SaaS
  • H3 HabitFlow
  • H3 AUREN
  • H3 SynapseX
  • H3 VOID CHILD
  • H3 Fastshot
  • H3 Silverline
  • H3 Forme
  • H3 N/FORM
  • H3 SkyLiner
  • H3 Afterimage
  • H3 TEINTE
  • H3 Barwell Strength Club
  • H3 Every design. One membership.
  • H3 Loop Dept
  • H3 Product Stage
  • H3 Rain Atlas
  • H3 Orbita
  • H3 Jelly
  • H3 SAC
  • H3 OUTPOST
  • H3 Thera
  • H3 Formplay
  • H3 Afterhours
  • H3 Aether 3D
  • H3 OFFFORM
  • H3 Vesper
  • H3 Soft Hours
  • H3 PrettySites Dispatch
  • H3 Donmigos Pizza
  • H3 Summit
  • H3 Anatomy Atelier
  • H3 ODDROOM
  • H3 Motion Form
  • H3 3D Codebase City
  • H3 Earth Jumping
  • H3 Pelagia
  • H3 Liberty Walk F40
  • H3 STRIDE
  • H3 Knight Feast
  • H3 Floret
  • H3 SIDEQUEST
  • H3 ORVA
  • H3 Surface Film
  • H3 AZAKA
  • H3 M7
  • H3 Offroute
  • H1 Website prompts for AI coding tools duplicate H1
  • H2 Website designs
  • H2 How it works

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

B
Mobile-Readable Font Sizes
94% of visible text renders at >= 12 CSS px (9 below threshold)
REVIEW
94% of visible text renders at >= 12 CSS px (9 below threshold)
Info::
9 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 ("2026"); <p> 11.0px ("PrettySites."); <p> 11.0px ("All rights reserved."); <p> 11.0px ("PrettySites is a product of LLC Mahaon A..."); <a> 11.0px ("Terms of Use").
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | PrettySites ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 Website prompts for AI coding tools
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Website designs
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How it works
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
24px · bottom of viewport
h3 OFFGRID
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Try this site with your product
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
19px · bottom of viewport
h3 MILO FACES
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Jenga Games
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
19px · bottom of viewport
h3 OVAL Atelier
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Cell Studio
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Aerolume
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Bee2Bee SaaS
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
19px · bottom of viewport
h3 HabitFlow
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
19px · bottom of viewport
h3 AUREN
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
19px · bottom of viewport
h3 SynapseX
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
19px · bottom of viewport
h3 VOID CHILD
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Fastshot
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Silverline
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Forme
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
19px · bottom of viewport
h3 N/FORM
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
19px · bottom of viewport
h3 SkyLiner
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Website prompts for …1.12:13.0:1
#000000
#121212
Fail
h2 Website designs1.12:13.0:1
#000000
#121212
Fail
h2 How it works1.12:13.0:1
#000000
#121212
Fail
h3 OFFGRID1.12:13.0:1
#000000
#121212
Fail
h3 Try this site with y…1.12:13.0:1
#000000
#121212
Fail
h3 MILO FACES1.12:13.0:1
#000000
#121212
Fail
h3 Jenga Games1.12:13.0:1
#000000
#121212
Fail
h3 OVAL Atelier1.12:13.0:1
#000000
#121212
Fail
h3 Cell Studio1.12:13.0:1
#000000
#121212
Fail
h3 Aerolume1.12:13.0:1
#000000
#121212
Fail
h3 Bee2Bee SaaS1.12:13.0:1
#000000
#121212
Fail
h3 HabitFlow1.12:13.0:1
#000000
#121212
Fail
h3 AUREN1.12:13.0:1
#000000
#121212
Fail
h3 SynapseX1.12:13.0:1
#000000
#121212
Fail
h3 VOID CHILD1.12:13.0:1
#000000
#121212
Fail
h3 Fastshot1.12:13.0:1
#000000
#121212
Fail
h3 Silverline1.12:13.0:1
#000000
#121212
Fail
h3 Forme1.12:13.0:1
#000000
#121212
Fail
h3 N/FORM1.12:13.0:1
#000000
#121212
Fail
h3 SkyLiner1.12:13.0:1
#000000
#121212
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.

A
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Info::
1 heading(s) are too short (≤2 characters) to convey meaning
Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H3: "M7"
Got: 1 ≤2-char heading(s)
Info::
13 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 13 all-caps heading(s)
A+
Alt Text Quality
All 54 images OK
PASS
All 54 images OK
Info::
54 decorative image(s) correctly marked
54 images 54 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputinputnone
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
Info::
Input "Search designs" should use type="search" (currently type="text")
Field name "Search designs" 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
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
2 explicit tabindex attribute(s) checked, no anti-patterns
PASS
2 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 iframe(s) missing title; 0 placeholder(s)
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.
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
2 mobile-depth signal(s) detected
PASS
2 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
Info::
Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices
The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.
A+
Lighthouse Accessibility Audits
Score 98/100 — 2 failing, 22 passed
PASS
98

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
OFFGRID article.card > div.meta > div.card-labels > h3

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Free & Premium div.toolbar > div.catalog-tools > div.select-menu > button.select-trigger
2 div.slot > article.card > div.card-visual-wrap > button.save-card
2 div.slot > article.card > div.card-visual-wrap > button.save-card
○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
●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 have a discernible name
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[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 an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Image elements have `[alt]` attributes
○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.
○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
○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.

Send Feedback