Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 4 REVIEW 7 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

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

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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

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-02hnru

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://jigsy.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://jigsy.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 ✗

Alt Text Quality

Action

5 of 7 images have issues

REVIEW

5 of 7 images have issues

5 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image(s) with good alt text

7 images 2 good alt text 5 missing

Issue	Count
missing	5 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

Link & Button Quality

Action

4 issue(s) across 32 links and 2 buttons

REVIEW

4 issue(s) across 32 links and 2 buttons

3 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a#fancybox-close; javascript:;; javascript:;

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.close (#272 on page)

29 link(s) with descriptive text

32 links

3 empty

0 generic text

0 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
javascript:;	(empty)	empty	Add link text or aria-label
javascript:;	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label

30 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a#fancybox-close; javascript:;; javascript:;

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Icon-only buttons need an aria-label so screen readers can announce them.

button.close (#272 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Color Contrast (Screenshot)

Action

20 text elements analyzed, 6 fail WCAG AA

REVIEW

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

14 pass 6 fail WCAG AA

title The Easy Website Builder, it's free! Jig…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

div Menu

1.28:1

#000000

#2E1B05

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a Home

2.60:1

#000000

#74450E

needs 4.5:1 (normal text)

16px · top of page (header area)

a Blog

1.36:1

#000000

#2F220D

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a Features

1.05:1

#000000

#000A0C

needs 4.5:1 (normal text)

16px · above the fold

a Pricing

1.26:1

#000000

#142023

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

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)

Element	Ratio	Required	FG	BG	Result
h1 The Easy Website Bui…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Save Time. Create a …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 No installation nece…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Your website is secu…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 World Class Customer…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Our Plans & Pricing	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Starter	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Basic	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Premium	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Create your own webs…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Build now, pay later	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 $3.99	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 $7.99	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 $10.99	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title The Easy Website Bui…	1.00:1	4.5:1	#000000	#000000	Fail
div Menu	1.28:1	4.5:1	#000000	#2E1B05	Fail
a Home	2.60:1	4.5:1	#000000	#74450E	Fail
a Blog	1.36:1	4.5:1	#000000	#2F220D	Fail
a Features	1.05:1	4.5:1	#000000	#000A0C	Fail
a Pricing	1.26:1	4.5:1	#000000	#142023	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.

Lighthouse Accessibility Audits

Action

Score 72/100 — 5 failing, 15 passed

REVIEW

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.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
We use cookies Cookies help us deliver the best experience on our website. By … `body#welcome_index > div#cookie-consent-dialog`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
body#welcome_index > div#cookie-consent-dialog > div.container > button.close `body#welcome_index > div#cookie-consent-dialog > div.container > button.close`

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.row > div.col-sm-6 > img.center_image `div.container > div.row > div.col-sm-6 > img.center_image`

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.container > div#copyright > div.social_links > a.social_twitter `div.container > div#copyright > div.social_links > a.social_twitter`
div.container > div#copyright > div.social_links > a.social_facebook `div.container > div#copyright > div.social_links > a.social_facebook`

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
SIGN UP `div.row > div.col-md-4 > div.package_2428 > a.signup`
SIGN UP `div.row > div.col-md-4 > div.package_2429 > a.signup`
SIGN UP `div.row > div.col-md-4 > div.package_2430 > a.signup`

These are opportunities to improve the legibility of your content.

○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-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

●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

●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

○`[aria-*]` attributes match their roles

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted 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

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○The page contains a heading, skip link, or landmark region

○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

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

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

Heading Hierarchy

18 headings

PASS

18 headings

Multiple H1 headings (2 found)

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

H1 The Easy Website Builder
H2 Save Time. Create a Website in Minutes
H2 No installation necessary
H2 Your website is secure with us
H2 World Class Customer Service
H2 Our Plans & Pricing
H3 Build now, pay later
H2 Starter
H3 $3.99
H4 Regular Price $7.99
H2 Basic
H3 $7.99
H4 Regular Price $14.99
H2 Premium
H3 $10.99
H4 Regular Price $19.99
H2 Create your own website today
H1 We use cookies duplicate H1

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

A+

Form Accessibility

No form controls

PASS

No form controls

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.