Skip to content
https://wix.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
D
404 Error Page
Action
HTTP 404, custom page
FIX
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 ✓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
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::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 2 <nav> element(s)
Back to Top
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.
B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="email" id="input_comp-m1dgpu8i">; <input type="text" name="type-the domain you want" id="input_comp-m0jalyp3_r_comp-lybpx1vp">
2 controls
0 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#input_comp-m1dgpu8iemail(Enter your email address)placeholder only
#input_comp-m0jalyp3_r_comp-lybpx1vptext(Type the domain you want)placeholder only

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

<input type="email" name="email" id="input_comp-m1dgpu8i">; <input type="text" name="type-the domain you want" id="input_comp-m0jalyp3_r_comp-lybpx1vp">

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

C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
A
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 menu" 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
57 headings
PASS
57 headings
Info::
Single H1 present
  • H1 The new way to create a website
  • H2 Flow between instant generation and hand-crafted design
  • H2 Website templates are another way in
  • H2 Prompt, ask, bounce ideas. We can do it all together. I’m your personal web design and business expert tuned in to your site.
  • H2 Extreme customization. Absolute control.
  • H3 Drag and drop freedom
  • H3 Create with Aria
  • H3 A library of possibilities
  • H3 Define your brand
  • H2 Add anything you need for your business as you go
  • H3 eCommerce
  • H3 Scheduling
  • H3 Portfolio
  • H3 Blog
  • H3 Online courses
  • H3 Events
  • H2 Make your website official with your own domain name
  • H2 Market your site from launch to scale
  • H3 SEO tools and AI visibility
  • H3 Google, Facebook and Instagram ads
  • H3 Social media marketing
  • H3 AI-generated email marketing
  • H2 Run your business from one dashboard
  • H3 Payments
  • H3 CRM solution
  • H3 Custom automations
  • H3 Data & analytics
  • H3 Mobile app
  • H2 Grow your website on a rock-solid foundation
  • H3 Engineered for top speed
  • H3 Designed for accessibility
  • H3 Secured by industry experts
  • H3 Built with reliability in mind
  • H2 How to create a website for free
  • H2 Thriving with Wix
  • H2 Get inspired, gain new skills and see what’s trending
  • H2 Made on Wix
  • H2 We’re here for you 24/7
  • H3 Get answers
  • H3 Chat with us
  • H3 Hire a pro
  • H2 Website builder FAQ
  • H3 Is it easy to build a website?
  • H3 How do I create a website?
  • H3 How do I choose the best website builder?
  • H3 What types of websites can you build on Wix?
  • H3 What makes a good website?
  • H3 Can I create a website for free?
  • H3 How much does it cost to build a website?
  • H3 Can I create a website without knowing how to code?
  • H3 Should I use a website builder or hire a developer?
  • H3 Does my free website come with hosting?
  • H3 How can I connect a domain to my website?
  • H3 How can I optimize my site for SEO on Wix?
  • H3 Can I use 3rd party apps with my website?
  • H3 How can I design a logo for my website?
  • H2 Your vision. Your goals. Your website.
A+
Alt Text Quality
1 of 69 images have issues
PASS
1 of 69 images have issues
Warning::
1 image(s) with filename as alt text
Info::
6 decorative image(s) correctly marked
Info::
62 image(s) with good alt text
69 images 62 good alt text 6 decorative 1 generic
IssueCount
filename1 image(s)
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)
ElementRatioRequiredFGBGResult
h1 The new way to creat…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Flow between instant…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Website templates ar…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Extreme customizatio…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Run your business fr…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Made on Wix21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Your vision. Your go…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Drag and drop freedo…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Create with Aria21.00:13.0:1
#000000
#FFFFFF
Pass
h3 A library of possibi…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Define your brand21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Built with reliabili…21.00:13.0:1
#000000
#FFFFFF
Pass
title Website Builder - Cr…21.00:14.5:1
#000000
#FFFFFF
Pass
button Skip to Main Content21.00:14.5:1
#000000
#FFFFFF
Pass
span Product20.62:14.5:1
#000000
#FCFDFE
Pass
span CREATION20.12:14.5:1
#000000
#F9FAFD
Pass
span Website design19.63:14.5:1
#000000
#F6F7FC
Pass
p Create your site wit…19.28:14.5:1
#000000
#F3F5FC
Pass
span Website templates18.80:14.5:1
#000000
#F0F2FB
Pass
p Choose from 900+ web…18.33:14.5:1
#000000
#EDEFFA
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.

A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 32 passed
PASS
100

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.

○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
●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
●`[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.
●`button`, `link`, and `menuitem` elements have accessible names
●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 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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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 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
○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.
○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