Skip to content
https://nrf.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
7
REVIEW
2
PASS
4
INFO
0
Checks
13
4 PASS 2 REVIEW 7 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✓ 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
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
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 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
Heading Hierarchy
Action
52 headings, 1 skip(s)
REVIEW
52 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H5 Events
  • H5 Resources
  • H5 About Us
  • H5 Membership
  • H5 Retail Advocacy
  • H5 Policy Issues
  • H5 Retail Events
  • H5 Global Events
  • H5 Sponsor and Exhibit
  • H5 Research & Insights
  • H5 Topics
  • H5 Resource Centers
  • H5 Careers & Employment
  • H5 NRF News
  • H5 Media Center
  • H5 About
  • H5 Advocacy
  • H5 Events
  • H5 Research & Insights
  • H5 Resources
  • H5 News & Media
  • H2 Mother's Day Spending
  • H2 The National Retail Federation is the world’s largest retail trade association.
  • H2 Retail’s outlook for 2026
  • H2 Retail sales grow for sixth consecutive month
  • H2 CNBC/NRF Retail Monitor coverage
  • H2 2026 Top 50 Global Retailers
  • H2 Latest from NRF
  • H2 Digital shelf labels
  • H2 Retail Advocacy
  • H3 6 retail policy priorities for 2026
  • H3 Permanent Tax Relief
  • H3 Digital Pricing and Retail
  • H3 Tariffs
  • H3 Policy Spotlight
  • H3 Action Center
  • H2 NRF Events
  • H2 NRF Foundation Honors Raises $2.7 Million to Support Retail Careers
  • H2 NRF Business of Retail Initiative at Georgetown University
  • H2 Retail Gets Real Podcast
  • H2 SmartBrief newsletters
  • H5 About Us skipped
  • H5 Advocacy
  • H5 Events
  • H5 Top Resources
  • H5 News and Media
  • H5 About Us
  • H5 Advocacy
  • H5 Events
  • H5 Top Resources
  • H5 News and Media
  • H5 Also of interest

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA
h3 Policy Spotlight
1.00:1
#FFFFFF
on
#FFFFFF
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient
h3 Action Center
1.00:1
#FFFFFF
on
#FFFFFF
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient

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)
ElementRatioRequiredFGBGResult
h2 The National Retail …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Retail’s outlook f…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Retail sales grow fo…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 CNBC/NRF Retail Moni…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 2026 Top 50 Global R…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Latest from NRF21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Digital shelf labels21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Retail Advocacy21.00:13.0:1
#000000
#FFFFFF
Pass
h2 NRF Events21.00:13.0:1
#000000
#FFFFFF
Pass
h2 NRF Foundation Honor…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 NRF Business of Reta…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Retail Gets Real Pod…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 SmartBrief newslette…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 6 retail policy prio…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Permanent Tax Relief21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Digital Pricing and …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Tariffs21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Policy Spotlight1.00:13.0:1
#FFFFFF
#FFFFFF
Fail
h3 Action Center1.00:13.0:1
#FFFFFF
#FFFFFF
Fail
title National Retail Fede…18.76:14.5:1
#000000
#F2F2F2
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
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 CONTENTINFO footer

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

A+
Alt Text Quality
1 of 31 images have issues
PASS
1 of 31 images have issues
Warning::
1 image(s) with generic alt text
Info::
1 decorative image(s) correctly marked
Info::
29 image(s) with good alt text
31 images 29 good alt text 1 decorative 1 generic
IssueCount
generic1 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A
Lighthouse Accessibility Audits
Score 94/100 — 2 failing, 22 passed
PASS
94

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.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#block3fc90185-0d02-456d-8f2c-ee1212a8de21 > div.Block6633_block6633_side66__CG1MB > div.Block6633_block6633_html__xkr1A > iframe div#block3fc90185-0d02-456d-8f2c-ee1212a8de21 > div.Block6633_block6633_side66__CG1MB > div.Block6633_block6633_html__xkr1A > iframe

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.

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
About Us div.Footer_footerAccordions__VQcBW > div.Footer_accordion_item_container__xMa70 > div.Footer_accordion_item_question__ewnY0 > h5.Footer_footerColor__Z_I8E

These are opportunities to improve keyboard navigation in your application.

○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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●Touch targets have sufficient size and spacing.
●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
○`<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
○Form elements have associated labels
○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.
○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>`.
○All heading elements contain content.
○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