Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 1 REVIEW 6 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

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

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 ✗

Heading Hierarchy

No headings

REVIEW

No headings

No headings found

Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

No links or buttons

PASS

No links or buttons

No links or buttons on this page

0 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Nordstrom Online & In Store: Shoes, Jewelry, Clothing, Makeup, Dresses ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Lighthouse Accessibility Audits

Score 96/100 — 2 failing, 26 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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
BLACK/CHARCOAL/GREY `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK/ BLACK `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK `div.UOItI > div > div.OO7SP > ul.J0R8B`
PERFECT BLACK / PERFECT BLACK `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK/ SILVER/ WARM APRICOT `div.UOItI > div > div.OO7SP > ul.J0R8B`
SILVER `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK `div.UOItI > div > div.OO7SP > ul.J0R8B`
PALE GREY HEATHER `div.UOItI > div > div.OO7SP > ul.J0R8B`
Black `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK/ BLACK/ ASPHALT `div.UOItI > div > div.OO7SP > ul.J0R8B`
GREY MATTER/ TRUFFLE SALT `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK / SILVER `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK `div.UOItI > div > div.OO7SP > ul.J0R8B`
POIGNANT POPPYS `div.UOItI > div > div.OO7SP > ul.J0R8B`
Mint `div.UOItI > div > div.OO7SP > ul.J0R8B`
CBLACK/FTW `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK/ ECLIPSE `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK `div.UOItI > div > div.OO7SP > ul.J0R8B`
GREY `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK SUEDE `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK PETAL WHISPER `div.UOItI > div > div.OO7SP > ul.J0R8B`
CBLACK/WON `div.UOItI > div > div.OO7SP > ul.J0R8B`
CORE BLACK/ FTWR WHITE/ GUM5 `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK `div.UOItI > div > div.OO7SP > ul.J0R8B`
WOLF/ GHOST `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK LEATHER `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK `div.UOItI > div > div.OO7SP > ul.J0R8B`
Black `div.UOItI > div > div.OO7SP > ul.J0R8B`
LIGHT HEATHER GREY `div.UOItI > div > div.OO7SP > ul.J0R8B`
CBLACK/CWH `div.UOItI > div > div.OO7SP > ul.J0R8B`
QUARRY `div.UOItI > div > div.OO7SP > ul.J0R8B`
WHITE `div.UOItI > div > div.OO7SP > ul.J0R8B`
CBLACK/FTW `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK LEATHER `div.UOItI > div > div.OO7SP > ul.J0R8B`
WILD BROWN `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK JET `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK/ BETTER SCARLET/ GUM `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK `div.UOItI > div > div.OO7SP > ul.J0R8B`
Black `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK `div.UOItI > div > div.OO7SP > ul.J0R8B`
BLACK LEAT `div.UOItI > div > div.OO7SP > ul.J0R8B`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`
Popular `li.Hd2rY > div.Irf18 > div.r5rUT > a.yQhJC`

○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

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

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●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

●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●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

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

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

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