Skip to content
https://nicepage.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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.

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ 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
No dark mode signals
FIX
No dark mode signals
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 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.

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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Heading Hierarchy
Action
20 headings, 3 skip(s)
REVIEW
20 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Ultimate Freehand. Web Design 3.0
  • H1 Create stunningwebsites and themes
  • H2 30
  • H5 Web design skipped
  • H2 Absolute Creativity WithNo Coding
  • H2 What IsWeb Design 3.0?
  • H2 All You Need And More
  • H4 10,000+ of Website & Block Templates skipped
  • H4 Easy Drag-n-Drop
  • H4 No Coding
  • H4 Mobile-Friendly
  • H2 Start With Beautiful Website Templates
  • H2 Perfect Results On Any Device
  • H4 Alan Hollander skipped
  • H2 More happy customers
  • H2 Companies That Use Our Products:
  • H3 Free Website Builder Download
  • H2 Best Free Website Builder Templates
  • H3 Free Download Website Builder Software
  • H3 This site was made in

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

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

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
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 18 fail WCAG AA
REVIEW

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

2 pass 18 fail WCAG AA
h1 Create stunning
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
32px · bottom of viewport · over background image/gradient
h1 websites and themes
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
32px · bottom of viewport · over background image/gradient
h2 Absolute Creativity With
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
24px · bottom of viewport
h2 No Coding
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What Is
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Web Design 3.0?
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
24px · bottom of viewport
h2 All You Need And More
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Start With Beautiful Website Templates
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Perfect Results On Any Device
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
24px · bottom of viewport
h2 More happy customers
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Companies That Use Our Products:
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Best Free Website Builder Templates
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Ultimate Freehand. Web Design 3.0
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient
h3 Free Website Builder Download
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Free Download Website Builder Software
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport
h3 This site was made in
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport
a Download
1.23:1
#000000
on
#191B2A
needs 4.5:1 (normal text)
16px · top of page (header area)
a 400+ Features
1.23:1
#000000
on
#191B2A
needs 4.5:1 (normal text)
16px · top of page (header area)

3 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)
ElementRatioRequiredFGBGResult
h1 Create stunning1.29:13.0:1
#000000
#202022
Fail
h1 websites and themes1.29:13.0:1
#000000
#202022
Fail
h2 Absolute Creativity …1.29:13.0:1
#000000
#202022
Fail
h2 No Coding1.29:13.0:1
#000000
#202022
Fail
h2 What Is1.29:13.0:1
#000000
#202022
Fail
h2 Web Design 3.0?1.29:13.0:1
#000000
#202022
Fail
h2 All You Need And Mor…1.29:13.0:1
#000000
#202022
Fail
h2 Start With Beautiful…1.29:13.0:1
#000000
#202022
Fail
h2 Perfect Results On A…1.29:13.0:1
#000000
#202022
Fail
h2 More happy customers1.29:13.0:1
#000000
#202022
Fail
h2 Companies That Use O…1.29:13.0:1
#000000
#202022
Fail
h2 Best Free Website Bu…1.29:13.0:1
#000000
#202022
Fail
h3 Ultimate Freehand. W…1.29:13.0:1
#000000
#202022
Fail
h3 Free Website Builder…1.29:13.0:1
#000000
#202022
Fail
h3 Free Download Websi…1.29:13.0:1
#000000
#202022
Fail
h3 This site was made i…1.29:13.0:1
#000000
#202022
Fail
title Free Website Builder…20.12:14.5:1
#000000
#FAFAFA
Pass
span Toggle navigation20.12:14.5:1
#000000
#FAFAFA
Pass
a Download1.23:14.5:1
#000000
#191B2A
Fail
a 400+ Features1.23:14.5:1
#000000
#191B2A
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 85/100 — 5 failing, 17 passed
REVIEW
85

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
DISCOVER THE SECRET div.u-layout-row > div.u-align-left > div.u-container-layout > a.u-btn
DOWNLOAD NOW div.u-clearfix > div.u-align-center > div.u-container-layout > a.u-btn
DOWNLOAD ul.thumbnails > li.thumbnail-item > div.download-block > a.btn
DOWNLOAD ul.thumbnails > li.thumbnail-item > div.download-block > a.btn
DOWNLOAD ul.thumbnails > li.thumbnail-item > div.download-block > a.btn
DOWNLOAD ul.thumbnails > li.thumbnail-item > div.download-block > a.btn
DOWNLOAD NOW div.u-clearfix > div.u-align-center > div.u-container-layout > a.u-btn
Accept body > div#np-cookie-consent > div.cookieButton > button

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
10,000+ of Website & Block Templates div.u-container-layout > div.u-container-style > div.u-container-layout > h4.u-align-center
Alan Hollander div.u-layout-row > div.u-container-style > div.u-container-layout > h4.u-text

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.u-responsive-xs html.u-responsive-xs

These items highlight common accessibility best practices.

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
DOWNLOAD NOW div.u-clearfix > div.custom-expanded > div.u-container-layout > a.u-btn
○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
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●ARIA attributes are used as specified for the element's role
●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 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
●Touch targets have sufficient size and spacing.
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[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-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
○`[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
○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
○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.
A+
Alt Text Quality
All 75 images OK
PASS
All 75 images OK
Info::
14 decorative image(s) correctly marked
Info::
61 image(s) with good alt text
75 images 61 good alt text 14 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback