Skip to content
https://parceltheory.ca

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
6
REVIEW
4
PASS
14
INFO
0
Checks
24
14 PASS 4 REVIEW 6 FIX
D
Mobile Keyboard & Autofill
Action
6/6 eligible field(s) missing autocomplete or inputmode
FIX
6/6 eligible field(s) missing autocomplete or inputmode
Warning::
2 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email, tel.
Got: <input type="email" id="email-input-50600621-5e16-4d4f-8782-60f597989957">, <input type="tel" id="phone-input-50600621-5e16-4d4f-8782-60f597989957">
Warning::
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: email, search, tel.
Got: <input type="email" name="contact[email]" id="EmailInput-ANi93Wi93MzlJYnNmd__email_signup_crihX7">, <input type="search" name="q" id="cmdk-input">, <input type="email" id="email-input-50600621-5e16-4d4f-8782-60f597989957">, <input type="tel" id="phone-input-50600621-5e16-4d4f-8782-60f597989957">
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
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 Missing
✓ 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
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: rgb(255 255 255)
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 ModePartial Dark Mode
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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Form Accessibility
2 of 7 controls have issues
REVIEW
2 of 7 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" id="email-input-50600621-5e16-4d4f-8782-60f597989957">; <input type="tel" id="phone-input-50600621-5e16-4d4f-8782-60f597989957">
Info::
5 control(s) properly labeled
7 controls
5 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#drawerSelectselectLanguagearia-label
#dropdownSelectselectLanguagearia-label
#EmailInput-ANi93Wi93MzlJYnNmd__email_signup_crihX7emailEmailfor/id
#cmdk-inputsearchSearchfor/id
#optIn-50600621-5e16-4d4f-8782-60f597989957checkboxOpt-in to Our Email List for More Discounts and Products!for/id
#phone-input-50600621-5e16-4d4f-8782-60f597989957tel(Enter your phone number)placeholder only
#email-input-50600621-5e16-4d4f-8782-60f597989957email(Enter your email)placeholder only

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

<input type="email" id="email-input-50600621-5e16-4d4f-8782-60f597989957">; <input type="tel" id="phone-input-50600621-5e16-4d4f-8782-60f597989957">

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
404 Error Page
Action
HTTP 404, custom page
REVIEW
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 ✓Page Title 404 Not Found – Parcel Theory Canada ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Lighthouse Accessibility Audits
Score 89/100 — 3 failing, 21 passed
REVIEW
89

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.

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
New Finds div.group-block > div.group-block-content > div.spacing-style > h3

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.hero__container > div.hero__media-grid > div.hero__media-wrapper > img.hero__media div.hero__container > div.hero__media-grid > div.hero__media-wrapper > img.hero__media

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
section#shopify-section-template--27317845328175__hero_jVaWmY > div#Hero-template--27317845328175__hero_jVaWmY > div.hero__container > a.hero__link section#shopify-section-template--27317845328175__hero_jVaWmY > div#Hero-template--27317845328175__hero_jVaWmY > div.hero__container > a.hero__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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[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
○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
○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.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
○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+
Landmark Structure
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary" SEARCH MAIN ASIDE CONTENTINFO footer
A
Heading Hierarchy
16 headings, 1 skip(s)
PASS
16 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Parcel Theory Canada
  • H2 Language
  • H2 Language
  • H3 New Finds
  • H3 Chunky Oversized Cable Knit Sweater Canada | Fall Cozy Essential
  • H3 Black Ankle Boots Canada | Fall Essential
  • H3 Metallic Blazer Dress Canada | Gold & Silver
  • H3 Cape Turtleneck Pleated Skirt Set Canada
  • H3 Cream Jacket & Trouser Suit Set Canada
  • H3 Structured Carrier Handbag Canada
  • H2 Join our email list
  • H2 Your cart is empty
  • H2 Your cart is empty
  • H2 Search
  • H4 Products skipped
  • H2 Join the Parcel Theory Canada Insider List

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

A+
Heading Text Quality
All 16 heading(s) have substantive, well-formed text
PASS
All 16 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A
Alt Text Quality
2 of 57 images have issues
PASS
2 of 57 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
1 image(s) with generic alt text
Info::
1 image(s) with alt text over 125 characters
Info::
25 decorative image(s) correctly marked
Info::
29 image(s) with good alt text
57 images 29 good alt text 25 decorative 1 generic 1 missing
IssueCount
missing1 image(s)
generic1 image(s)
too long1 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

A+
Form Input Types
7 form control(s) checked, no type mismatches
PASS
7 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
7 form control(s) checked, no input-semantic issues
PASS
7 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
14 explicit tabindex attribute(s) checked, no anti-patterns
PASS
14 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://parceltheory.ca/web-pixels@05c62d7ewbe538af9pdeb4fec1me339d55a/custom/w…")
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.
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 10 visible text node(s) render at >= 12 CSS pixels
PASS
All 10 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
2 mobile-depth signal(s) detected
PASS
2 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
Info::
Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices
The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.
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 Parcel Theory Canada21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Language18.10:13.0:1
#000000
#F3EDE9
Pass
h2 Language18.10:13.0:1
#000000
#F3EDE9
Pass
h2 Join our email list18.10:13.0:1
#000000
#F3EDE9
Pass
h2 Your cart is empty18.10:13.0:1
#000000
#F3EDE9
Pass
h2 Search18.10:13.0:1
#000000
#F3EDE9
Pass
h2 Join the Parcel Theo…13.77:13.0:1
#202223
#F3EDE9
Pass
h3 New Finds18.10:13.0:1
#000000
#F3EDE9
Pass
h3 Chunky Oversized Cab…18.10:13.0:1
#000000
#F3EDE9
Pass
h3 Black Ankle Boots Ca…18.10:13.0:1
#000000
#F3EDE9
Pass
h3 Metallic Blazer Dres…18.10:13.0:1
#000000
#F3EDE9
Pass
h3 Cape Turtleneck Plea…18.10:13.0:1
#000000
#F3EDE9
Pass
h3 Cream Jacket & Trous…18.10:13.0:1
#000000
#F3EDE9
Pass
h3 Structured Carrier H…18.10:13.0:1
#000000
#F3EDE9
Pass
title Parcel Theory Canada…18.51:14.5:1
#000000
#F5F0E8
Pass
div Free shipping for or…18.51:14.5:1
#000000
#F5F0E8
Pass
span $150.0018.51:14.5:1
#000000
#F5F0E8
Pass
a Skip to content19.98:14.5:1
#000000
#FBF9F6
Pass
p 🌸🌸SIGN UP FOR …21.00:14.5:1
#000000
#FFFFFF
Pass
span Home11.29:14.5:1
#000000
#C3BDB8
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.

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

Send Feedback