Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 6 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-scv0b7

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://webs.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://webs.com/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

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 ✗

A+

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

No contentinfo (footer) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

10 headings

PASS

10 headings

Single H1 present

H1 Create a website your way – for free!
H2 Benefits that help you grow
H3 Tailored to small businesses
H3 Expert help & guidance
H3 Grow with trusted services
H3 An all-in-one experience
H3 Tailored to small businesses
H3 Expert help & guidance
H3 Grow with trusted services
H3 An all-in-one experience

A+

Alt Text Quality

All 27 images OK

PASS

All 27 images OK

1 image(s) with alt text over 125 characters

19 decorative image(s) correctly marked

7 image(s) with good alt text

27 images 7 good alt text 19 decorative

Issue	Count
too long	1 image(s)

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#digital-search-component-text-input	search	Search	aria-label

Link & Button Quality

8 links, 5 buttons — all OK

PASS

8 links, 5 buttons — all OK

2 link(s) open in new tab without warning

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

Got: https://www.wix.com/about/terms-of-use/onepager; https://www.wix.com/about/privacy-onepager

6 link(s) with descriptive text

8 links

0 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.wix.com/about/terms-of-use/o…	Terms of Use	new tab	Add '(opens in new tab)' to text
https://www.wix.com/about/privacy-onepag…	Privacy Policy	new tab	Add '(opens in new tab)' to text

11 links and buttons have descriptive text

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

https://www.wix.com/about/terms-of-use/onepager; https://www.wix.com/about/privacy-onepager

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+

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
h1 Create a website you…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Benefits that help y…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Tailored to small bu…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Expert help & guidan…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Grow with trusted se…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 An all-in-one experi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Tailored to small bu…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Expert help & guidan…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Grow with trusted se…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 An all-in-one experi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Webs.com has been sh…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Accessibility	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to main content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Help is here	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Important Update	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Webs is retired	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div We’re excited to s…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div We’ve got you cove…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Create a Free Websit…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p We’ve partnered wi…	21.00:1	4.5:1	#000000	#FFFFFF	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 97/100 — 1 failing, 25 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.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.swan-bounded-content > div.site-header-main > nav.site-header-links > a.site-header-link `div.swan-bounded-content > div.site-header-main > nav.site-header-links > a.site-header-link`

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.

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

●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

●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

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

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

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

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.