Skip to content
https://100wears.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
81
GRADE
B
FIX
4
REVIEW
3
PASS
17
INFO
0
Checks
24
17 PASS 3 REVIEW 4 FIX
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <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.
C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A
Landmark Structure
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Warning::
Skip link target(s) don't exist on page: #content
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN ASIDE CONTENTINFO footer

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

A+
Heading Hierarchy
21 headings
PASS
21 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)
  • H2 Adidas Flat Earther Review: A Flop That Actually Works
  • H2 Alden Unlined LHS in Shell: Simply the Best?
  • H2 Jordan 1 Union x Fragment Review: Sizing, Comfort, and Value
  • H2 Amberjack The Original: Built for a Purpose
  • H2 Allen Edmonds Park Ave: 12 Years Later (2026)
  • H2 Adidas UltraBoost 1 vs. UltraBoost 5x: Comparison and Review
  • H2 Grant Stone Tassel Loafer: Still in Love
  • H2 Amberjack The Atlas Review: A Comfort-First Take on GAT Sneakers
  • H2 What’s the Best Oxford for Your Budget? (2026)
  • H2 Amberjack The Low Top: Does it Deliver on Comfort?
  • H2 Shopping Guides
  • H2 Reviews
  • H2 Comparisons
  • H2 Construction
  • H2 Contact
  • H2 Reviews
  • H2 Shopping Guides
  • H2 Contact
  • H2 Find on Site
  • H2 Privacy Policy & Disclosure

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

A+
Heading Text Quality
All 21 heading(s) have substantive, well-formed text
PASS
All 21 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 11 images OK
PASS
All 11 images OK
Info::
1 decorative image(s) correctly marked
Info::
10 image(s) with good alt text
11 images 10 good alt text 1 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">
Info::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
ssearchSearch for:none
inputsubmit(none)none

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

<input type="submit">

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

A+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
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 187 visible text node(s) render at >= 12 CSS pixels
PASS
All 187 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
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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+
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
h2 Shopping Guides20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Reviews20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Comparisons20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Construction20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Contact20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Reviews20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Shopping Guides20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Contact20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Find on Site20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Privacy Policy & Dis…20.12:13.0:1
#000000
#FAFAFA
Pass
title - Out of the Box Onl…21.00:14.5:1
#000000
#FFFFFF
Pass
title Your Page Title21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to content21.00:14.5:1
#000000
#FFFFFF
Pass
a Privacy Policy21.00:14.5:1
#000000
#FFFFFF
Pass
a Sizing Guide21.00:14.5:1
#000000
#FFFFFF
Pass
a What does 100 wears …21.00:14.5:1
#000000
#FFFFFF
Pass
p Out of the Box Only …21.00:14.5:1
#000000
#FFFFFF
Pass
span Menu21.00:14.5:1
#000000
#FFFFFF
Pass
a Stitched Footwear21.00:14.5:1
#000000
#FFFFFF
Pass
a Amberjack21.00:14.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 90/100 — 3 failing, 26 passed
PASS
90

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Adidas Flat Earther Review: A Flop That Actually Works article#post-6804 > div.post-wrap > div.post-media > a.post-thumbnail
Alden Unlined LHS in Shell: Simply the Best? article#post-375 > div.post-wrap > div.post-media > a.post-thumbnail
Jordan 1 Union x Fragment Review: Sizing, Comfort, and Value article#post-6770 > div.post-wrap > div.post-media > a.post-thumbnail
Amberjack The Original: Built for a Purpose article#post-5031 > div.post-wrap > div.post-media > a.post-thumbnail
Allen Edmonds Park Ave: 12 Years Later (2026) article#post-81 > div.post-wrap > div.post-media > a.post-thumbnail
Adidas UltraBoost 1 vs. UltraBoost 5x: Comparison and Review article#post-6293 > div.post-wrap > div.post-media > a.post-thumbnail
Grant Stone Tassel Loafer: Still in Love article#post-3623 > div.post-wrap > div.post-media > a.post-thumbnail
Amberjack The Atlas Review: A Comfort-First Take on GAT Sneakers article#post-6749 > div.post-wrap > div.post-media > a.post-thumbnail
What’s the Best Oxford for Your Budget? (2026) article#post-1698 > div.post-wrap > div.post-media > a.post-thumbnail
Amberjack The Low Top: Does it Deliver on Comfort? article#post-6730 > div.post-wrap > div.post-media > a.post-thumbnail

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.

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
May 10, 2026 div.entry-meta > span.posted-on > a > time.entry-date
6 Min Reading div.post-meta > div.post-date > div.entry-meta > span.min-read
April 26, 2026 div.entry-meta > span.posted-on > a > time.entry-date
12 Min Reading div.post-meta > div.post-date > div.entry-meta > span.min-read
April 19, 2026 div.entry-meta > span.posted-on > a > time.entry-date
9 Min Reading div.post-meta > div.post-date > div.entry-meta > span.min-read
April 11, 2026 div.entry-meta > span.posted-on > a > time.entry-date
13 Min Reading div.post-meta > div.post-date > div.entry-meta > span.min-read
April 11, 2026 div.entry-meta > span.posted-on > a > time.entry-date
9 Min Reading div.post-meta > div.post-date > div.entry-meta > span.min-read
April 4, 2026 div.entry-meta > span.posted-on > a > time.entry-date
6 Min Reading div.post-meta > div.post-date > div.entry-meta > span.min-read
April 3, 2026 div.entry-meta > span.posted-on > a > time.entry-date
10 Min Reading div.post-meta > div.post-date > div.entry-meta > span.min-read
March 22, 2026 div.entry-meta > span.posted-on > a > time.entry-date
7 Min Reading div.post-meta > div.post-date > div.entry-meta > span.min-read
March 8, 2026 div.entry-meta > span.posted-on > a > time.entry-date
8 Min Reading div.post-meta > div.post-date > div.entry-meta > span.min-read
March 1, 2026 div.entry-meta > span.posted-on > a > time.entry-date
8 Min Reading div.post-meta > div.post-date > div.entry-meta > span.min-read
div.footer-top-box > section#search-5 > form.search-form > input.search-submit div.footer-top-box > section#search-5 > form.search-form > input.search-submit

These are opportunities to improve the legibility of your content.

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.head_one > div.container > div.logo > a.custom-logo-link div.head_one > div.container > div.logo > a.custom-logo-link
div.container > div.logo > h1.site-title > a div.container > div.logo > h1.site-title > a
div#primary > main#main > div.pagination > a.next div#primary > main#main > div.pagination > a.next

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
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●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 use only permitted ARIA attributes
●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.
●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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Identical links have the same purpose.
○`[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 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.
○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>`.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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.

Send Feedback