Skip to content
https://highsnobiety.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
D
Landmark Structure
Action
42 landmarks
FIX
42 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
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.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) ASIDE CONTENTINFO footer

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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

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: #ffffff
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
4 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
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 Highsnobiety ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
125 icon(s) detected
REVIEW
125 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 Present
✓ Multiple Sizes Present
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 6 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The latest from our …4.71:13.0:1
#000000
#DD3932
Pass
h2 HIGHSNOBIETY’S SPR…4.71:13.0:1
#000000
#DD3932
Pass
h2 Get Highsnobiety str…4.71:13.0:1
#000000
#DD3932
Pass
h2 Frontpage4.71:13.0:1
#000000
#DD3932
Pass
h3 Download our free iO…4.71:13.0:1
#000000
#DD3932
Pass
h3 Web Accessibility St…4.71:13.0:1
#000000
#DD3932
Pass
h3 Disclaimer4.71:13.0:1
#000000
#DD3932
Pass
h3 Contact Us4.71:13.0:1
#000000
#DD3932
Pass
title Discover and Shop Wh…21.00:14.5:1
#000000
#FFFFFF
Pass
span Want to stay in the …21.00:14.5:1
#000000
#FFFFFF
Pass
span We've got you covere…18.43:14.5:1
#000000
#F0F0F0
Pass
span Download the Highsno…18.43:14.5:1
#000000
#F0F0F0
Pass
span menu18.43:14.5:1
#000000
#F0F0F0
Pass
span Highsnobiety18.43:14.5:1
#000000
#F0F0F0
Pass
a Latest4.71:14.5:1
#000000
#DD3932
Pass
a Shopping4.71:14.5:1
#000000
#DD3932
Pass
a Style4.71:14.5:1
#000000
#DD3932
Pass
a Sneakers4.71:14.5:1
#000000
#DD3932
Pass
a Culture4.71:14.5:1
#000000
#DD3932
Pass
a Beauty4.71:14.5:1
#000000
#DD3932
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.

B
Lighthouse Accessibility Audits
Score 88/100 — 5 failing, 31 passed
REVIEW
88

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Highsnobiety Magazine Teaser Video div > aside.drawerMenu___DAflD > nav.nav___iLV_l > div.tileSlideshow___UkpPw

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
CULTURE div.contentSection___s6xm3 > footer.footer___lyeFj > ul.categoryList___dNv2e > li.categoryItem___gUdai
ROSS SCARANO div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w
label.label___Ap4iz > div.wrapper > div.container___eA4W5 > span.label___Ap4iz label.label___Ap4iz > div.wrapper > div.container___eA4W5 > span.label___Ap4iz

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.contentSectionWrapper___TizIy > div.heroDense___HZYas > article.primaryTeaser___A10XK > a.link___rADBZ div.contentSectionWrapper___TizIy > div.heroDense___HZYas > article.primaryTeaser___A10XK > a.link___rADBZ
div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ
div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ
div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ
div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ
div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ
div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
PAUL THOMPSON div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w
ANNA SILMAN div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w
IVA DIXIT div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w
(SHOP NOW) div.contentSection___s6xm3 > footer.footer___lyeFj > span.cta___ujsTk > a.ctaLink___oDDv4
(SHOP NOW) div.contentSection___s6xm3 > footer.footer___lyeFj > span.cta___ujsTk > a.ctaLink___oDDv4
HENRY LEVINSON div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w
TREY DICKENSON div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w
CHRIS ERIK THOMAS div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w
TOM BARKER div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w
HIGHSNOBIETY div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w
CHRIS ERIK THOMAS div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w
YOHANA DESTA div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w
JORDAN COLEY div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w
CLAIRE LANDSBAUM div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w
TOM BARKER div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w
PAUL CHAUMIEN div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w
TOM BARKER div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w
ROSS SCARANO div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SUBSCRIBE div.contentSectionWrapper___TizIy > div.section___xVV4I > form.sectionForm___vvAPL > button.subscribeButton___uGjM7
○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]`s are contained by their required parent element
●`[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.
●Select elements have associated label elements.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<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
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○No form fields have multiple labels
○`<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
○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.
○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.
○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+
Heading Hierarchy
37 headings
PASS
37 headings
Info::
Single H1 present
  • H2 Kaytranada Goes Underground
  • H2 Talia Ryder Is Bigger Than Hollywood
  • H2 How Sage Elsesser Grew Up
  • H2 HIGHSNOBIETY’S SPRING ‘26 ISSUE
  • H2 KAYTRANADA
  • H2 TALIA RYDER
  • H2 SAGE ELSESSER
  • H2 Google Pixel x HS Launch the Google Pixel Institute of Fashion & Technology
  • H2 Watchmaking Maximalism Is So Back
  • H3 This 10-Person Brand Gets “Good” Clothing Right
  • H3 You Don't Have to Care About Clothes to Love Arpenteur
  • H3 What's New at the Most Important Store In Menswear? Everything
  • H3 Why Usyk Wearing Stone Island Is Bigger Than Usyk
  • H3 “Some Call It Boring but It’s What People Want”
  • H3 Thanks to A24, Movies Are Brands Now
  • H2 Get Highsnobiety straight to your inbox
  • H2 The "Polo Godfather" Who Made His Own Ralph
  • H2 Tom Holland Is an Autumn. So Is Vuori
  • H2 This NYC Couple Does It All. So Do Their Rain Jackets
  • H1 The latest from our world
  • H2 When Did Tabi Sneakers Get so Normal?
  • H2 Striking Gold + Steel with BVLGARI
  • H2 He Helped Design the iPhone. Now, He Designed Pharrell's Travel Kit
  • H2 Frontpage
  • H2 Don Cheadle Is Really That Guy
  • H2 Jazz Chisholm Jr. Needs Just One More Piece
  • H2 Lykke Li Sees God
  • H2 Jamie Demetriou's Moment
  • H2 Everyone Watches Natasha Cloud
  • H2 When Did Tabi Sneakers Get so Normal?
  • H2 From Nike to Crocs, the Seven Best Sneakers to Cop Right Now
  • H2 How to Make ASICS' Dad Shoe Daddier? Make It a BBQ Sandal
  • H2 Everything Is Streetwear: 20 Years of Stories From the Underground That Went Global
  • H3 Download our free iOS and Android App
  • H3 Web Accessibility Statement
  • H3 Disclaimer
  • H3 Contact Us
A+
Alt Text Quality
All 49 images OK
PASS
All 49 images OK
Info::
49 image(s) with good alt text
49 images 49 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
emailemailEnter Your Emailaria-label
shipping.countryselectnone
A
Web Manifest
Valid manifest
PASS
Valid manifest
Info::
Name present: Highsnobiety
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Highsnobiety ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name Highsnobiety Display Mode standalone Theme Color #fff Background Color #fff Icons 112 icon(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback