Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

8 PASS 5 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

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

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 ✗

A+

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

25 headings

PASS

25 headings

Single H1 present

H3 Live Online
H3 Self-Paced
H1 Research-based, results-driven UX guidance and training.
H2 Recent Articles & Videos
H3 Less Chat, More Answer: Site AI Chatbots Need to Get to the Point
H3 Boost Design Autonomy with an Information Pipeline
H3 Use AI Responsibly in Analysis
H3 Field Guide to Explaining UX Strategy
H2 Live Online Courses
H2 Self-Paced Courses
H2 Earn UX Certification
H3 Take 5 live courses, pass 5 online exams
H2 Learn with Your Team
H2 Partner with Our Experts
H2 Why NNGroup
H3 Research-backed, 28+ years strong.
H3 Deep topics, digestible guidance.
H3 Evidence over opinions.
H2 Leading Organizations Learn from NNGroup
H2 Never miss an update
H3 Courses
H3 Consulting
H3 Help
H3 Company
H2 Follow Us

A+

Alt Text Quality

All 11 images OK

PASS

All 11 images OK

4 decorative image(s) correctly marked

7 image(s) with good alt text

11 images 7 good alt text 4 decorative

All images have appropriate alt text.

Form Accessibility

1 of 2 controls have issues

PASS

1 of 2 controls have issues

1 control(s) without accessible label

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

Got: <input type="email" name="email">

1 control(s) properly labeled

2 controls

1 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#search	text	Search	for/id
email	email	(none)	none

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

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

Link & Button Quality

1 issue(s) across 71 links and 13 buttons

PASS

1 issue(s) across 71 links and 13 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /cart/

1 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://podcasters.spotify.com/pod/show/nngroup

69 link(s) with descriptive text

71 links

1 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://podcasters.spotify.com/pod/show/…	The NN/G UX Podcast	new tab	Add '(opens in new tab)' to text
/cart/	(empty)	empty	Add link text or aria-label

82 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/cart/

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://podcasters.spotify.com/pod/show/nngroup

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

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 Nielsen Norman Group ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

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)

Element	Ratio	Required	FG	BG	Result
h1 Research-based, resu…	20.57:1	3.0:1	#000000	#FEFCFE	Pass
h2 Recent Articles & Vi…	20.57:1	3.0:1	#000000	#FEFCFE	Pass
h2 Live Online Courses	20.57:1	3.0:1	#000000	#FEFCFE	Pass
h2 Self-Paced Courses	20.57:1	3.0:1	#000000	#FEFCFE	Pass
h2 Earn UX Certificatio…	20.57:1	3.0:1	#000000	#FEFCFE	Pass
h2 Learn with Your Team	20.57:1	3.0:1	#000000	#FEFCFE	Pass
h2 Partner with Our Exp…	20.57:1	3.0:1	#000000	#FEFCFE	Pass
h2 Why NNGroup	20.57:1	3.0:1	#000000	#FEFCFE	Pass
h2 Leading Organization…	20.57:1	3.0:1	#000000	#FEFCFE	Pass
h2 Never miss an update	20.57:1	3.0:1	#000000	#FEFCFE	Pass
h2 Follow Us	20.57:1	3.0:1	#000000	#FEFCFE	Pass
h3 Live Online	18.52:1	3.0:1	#000000	#F9EDFA	Pass
h3 Self-Paced	19.16:1	3.0:1	#000000	#FAF2FB	Pass
h3 Take 5 live courses,…	20.57:1	3.0:1	#000000	#FEFCFE	Pass
h3 Research-backed, 28+…	20.57:1	3.0:1	#000000	#FEFCFE	Pass
h3 Deep topics, digesti…	20.57:1	3.0:1	#000000	#FEFCFE	Pass
h3 Evidence over opinio…	20.57:1	3.0:1	#000000	#FEFCFE	Pass
h3 Courses	20.57:1	3.0:1	#000000	#FEFCFE	Pass
h3 Consulting	20.57:1	3.0:1	#000000	#FEFCFE	Pass
h3 Help	20.57:1	3.0:1	#000000	#FEFCFE	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 95/100 — 1 failing, 27 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.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.newsletter > form.form-field > div.subscribe-wrap > input.newsletter-email `div.newsletter > form.form-field > div.subscribe-wrap > input.newsletter-email`

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

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

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●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

○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

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

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