Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

10 PASS 6 REVIEW 8 FIX

Heading Hierarchy

Action

16 headings, 3 skip(s)

FIX

16 headings, 3 skip(s)

Multiple H1 headings (2 found)

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

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H3 Everyday Inspired Clothing
H3 Find Your Look
H6 Dianthus Henley Puff Sleeve Stripe Blouse skipped
H6 Notch Collar Blazer in Navy Peacoat
H1 Gibsonlook
H3 RECOMMENDED FOR YOU skipped
H2 REAL REVIEWS FROM CUSTOMERS
H2 Help
H2 Connect
H2 About Us
H2 Follow Us
H2 Shop the look
H2 Choose Options
H5 (empty)
H5 Edit Option
H1 Get 15% Off 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

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 ▾

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

Mobile Keyboard & Autofill

Action

4/5 eligible field(s) missing autocomplete or inputmode

FIX

4/5 eligible field(s) missing autocomplete or inputmode

4 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: search, email.

Got: <input type="search" name="q" id="boost-sd__search-widget-init-input-0">, <input type="email" name="customer[email]" id="customer_email">, <input type="search" name="q" id="boost-sd__search-widget-init-input-1">, <input type="email" name="email" id="email_01M2RA65K3PF252G80PPQHW7NW">

404 Error Page

Action

HTTP 403, custom page

FIX

HTTP 403, custom page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 403 ✗Page Title Verifying your connection... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

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 Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

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 ✗

Form Accessibility

Action

3 of 7 controls have issues

REVIEW

3 of 7 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="submit">

2 control(s) rely on placeholder only

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

Got: <input type="search" name="q" id="boost-sd__search-widget-init-input-0">; <input type="search" name="q" id="boost-sd__search-widget-init-input-1">

4 control(s) properly labeled

7 controls

4 labeled

2 placeholder only

1 unlabeled

Control	Type	Label	Method
#customer_email	email	Email Address *	for/id
#customer_password	password	Password *	for/id
#boost-sd__search-widget-init-input-2	input	When autocomplete results are available use up and down arrows to review and enter to select	aria-label
#email_01M2RA65K3PF252G80PPQHW7NW	email	Email	for/id
#boost-sd__search-widget-init-input-0	search	(Search)	placeholder only
#boost-sd__search-widget-init-input-1	search	(Search products...)	placeholder only
input	submit	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

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

Link & Button Quality

108 links, 64 buttons — all OK

REVIEW

108 links, 64 buttons — all OK

7 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="/collections/sale"]; a[href="/collections/sale"]; a[href="https://gibsonlook.com/collections/sale?pf_p_price=17%3A17"]; a[href="https://gibsonlook.com/collections/sale?pf_p_price=18%3A27"]; a[href="https://gibsonlook.com/collections/sale?pf_p_price=28%3A74.5"]; a[href="/collections/blazers"]; a[href="/collections/blazers"]

1 link(s) open in new tab without warning

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

Got: https://easyappsecom.com/?utm_source=accessibility-watermark

100 link(s) with descriptive text

108 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/collections/sale	Gibsonlook	img no alt	Add alt attribute to the image
/collections/sale	Gibsonlook	img no alt	Add alt attribute to the image
https://gibsonlook.com/collections/sale?…	Gibsonlook	img no alt	Add alt attribute to the image
https://gibsonlook.com/collections/sale?…	Gibsonlook	img no alt	Add alt attribute to the image
https://gibsonlook.com/collections/sale?…	Gibsonlook	img no alt	Add alt attribute to the image
/collections/blazers	Gibsonlook	img no alt	Add alt attribute to the image
/collections/blazers	Gibsonlook	img no alt	Add alt attribute to the image
https://easyappsecom.com/?utm_source=acc…	Accessibility Shopify App • …	new tab	Add '(opens in new tab)' to text

164 links and buttons have descriptive text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="/collections/sale"]; a[href="/collections/sale"]; a[href="https://gibsonlook.com/collections/sale?pf_p_price=17%3A17"]; a[href="https://gibsonlook.com/collections/sale?pf_p_price=18%3A27"]; a[href="https://gibsonlook.com/collections/sale?pf_p_price=28%3A74.5"]; a[href="/collections/blazers"]; a[href="/collections/blazers"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

https://easyappsecom.com/?utm_source=accessibility-watermark

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

Form Input Quality

2 input-semantic issue(s) across 7 form control(s)

REVIEW

2 input-semantic issue(s) across 7 form control(s)

1 password field(s) missing or with invalid `autocomplete`

Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" name="customer[password]">.

1 login form field(s) missing `autocomplete=username` (or `email`)

On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input type="email" name="customer[email]">.

Iframe Accessibility

3/3 iframe(s) missing title; 0 placeholder(s)

REVIEW

3/3 iframe(s) missing title; 0 placeholder(s)

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.

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.

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.

Mobile-Readable Font Sizes

98% of visible text renders at >= 12 CSS px (1 below threshold)

REVIEW

98% of visible text renders at >= 12 CSS px (1 below threshold)

1 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: <span> 0.0px ("Cart").

Color Contrast (Screenshot)

Action

20 text elements analyzed, 11 fail WCAG AA

REVIEW

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

9 pass 11 fail WCAG AA 9 pass AA only

title Gibsonlook - Elevated Knit Blazers, Dres…

2.38:1

#000000

#723A3B

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

3.40:1

#000000

#725C5C

needs 4.5:1 (normal text)

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

span Shop

4.37:1

#000000

#727272

needs 4.5:1 (normal text)

16px · top of page (header area)

div Shop

4.37:1

#000000

#727272

needs 4.5:1 (normal text)

16px · above the fold

a SHOP BEST SELLERS

4.37:1

#000000

#727272

needs 4.5:1 (normal text)

16px · above the fold

a SHOP ALL

4.37:1

#000000

#727272

needs 4.5:1 (normal text)

16px · above the fold

strong Clothing

2.60:1

#000000

#505050

needs 3.0:1 (large text)

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

a New Arrivals

1.79:1

#000000

#383838

needs 4.5:1 (normal text)

16px · above the fold

a Tops

1.76:1

#000000

#373737

needs 4.5:1 (normal text)

16px · above the fold

a Blazers

1.76:1

#000000

#373737

needs 4.5:1 (normal text)

16px · above the fold

a Dresses & Jumpsuits

1.76:1

#000000

#373737

needs 4.5:1 (normal text)

16px · above the fold

2 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 Gibsonlook	4.37:1	3.0:1	#000000	#727272	Pass
h2 REAL REVIEWS FROM CU…	4.37:1	3.0:1	#000000	#727272	Pass
h2 Help	4.37:1	3.0:1	#000000	#727272	Pass
h2 Connect	4.37:1	3.0:1	#000000	#727272	Pass
h2 About Us	4.37:1	3.0:1	#000000	#727272	Pass
h2 Follow Us	4.37:1	3.0:1	#000000	#727272	Pass
h3 Everyday Inspired Cl…	4.37:1	3.0:1	#000000	#727272	Pass
h3 Find Your Look	4.37:1	3.0:1	#000000	#727272	Pass
title Gibsonlook - Elevate…	2.38:1	4.5:1	#000000	#723A3B	Fail
a Skip to content	3.40:1	4.5:1	#000000	#725C5C	Fail
b FALL WAREHOUSE SALE:…	4.37:1	3.0:1	#000000	#727272	Pass
span Shop	4.37:1	4.5:1	#000000	#727272	Fail
div Shop	4.37:1	4.5:1	#000000	#727272	Fail
a SHOP BEST SELLERS	4.37:1	4.5:1	#000000	#727272	Fail
a SHOP ALL	4.37:1	4.5:1	#000000	#727272	Fail
strong Clothing	2.60:1	3.0:1	#000000	#505050	Fail
a New Arrivals	1.79:1	4.5:1	#000000	#383838	Fail
a Tops	1.76:1	4.5:1	#000000	#373737	Fail
a Blazers	1.76:1	4.5:1	#000000	#373737	Fail
a Dresses & Jumpsuits	1.76:1	4.5:1	#000000	#373737	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+

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

1 <nav> landmark(s) found

No banner (header) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

2 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: 2 all-caps heading(s)

A+

Alt Text Quality

All 22 images OK

PASS

All 22 images OK

7 decorative image(s) correctly marked

15 image(s) with good alt text

22 images 15 good alt text 7 decorative

All images have appropriate alt text.

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

Input "q" should use type="search" (currently type="text")

Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

0 positive, 1 -1-on-focusable

PASS

0 positive, 1 -1-on-focusable

tabindex="-1" on naturally-focusable <input>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

A+

Lighthouse Accessibility Audits

Score 97/100 — 1 failing, 31 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.

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
FALL WAREHOUSE SALE: Styles from $17. Shop Now `div#sections--15655269073035__c976ea60-9448-46f5-b560-dadbefa9728a-announcement-1 > a > u > b`

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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

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

●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

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

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

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