Skip to content
https://shrm.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
F
Heading Hierarchy
Action
31 headings
FIX
31 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
9 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 Already have an account?
  • H5 (empty)
  • H5 Join SHRM for Exclusive Access to Professional Content
  • H5 Free Article
  • H5 Limit Reached
  • H5 Free Article
  • H5 Limit Reached
  • H5 (empty)
  • H5 Unlock Your Career with SHRM Membership
  • H5 (empty)
  • H5 Join SHRM for Exclusive Access to Professional Premium Content
  • H5 (empty)
  • H5 Join SHRM for Exclusive Access to Student Content
  • H5 (empty)
  • H5 Join SHRM for Exclusive Access to Executive Network Content
  • H6 Our Brands
  • H6 Overview
  • H6 Advocacy
  • H6 Brand Partnership
  • H6 Member Resources
  • H2 Your Privacy Choices
  • H3 Manage Consent Preferences
  • H4 Strictly Necessary Cookies
  • H4 Targeting Cookies
  • H4 Functional Cookies
  • H4 Performance Cookies
  • H3 Cookie List

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

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

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::
8 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 8 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Alt Text Quality
Action
5 of 29 images have issues
REVIEW
5 of 29 images have issues
Critical::
5 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
7 decorative image(s) correctly marked
Info::
17 image(s) with good alt text
29 images 17 good alt text 7 decorative 5 missing
IssueCount
missing5 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

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

14 pass 6 fail WCAG AA 14 pass AA only
h2 Your Privacy Choices
1.87:1
#000000
on
#1A3B67
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Manage Consent Preferences
1.87:1
#000000
on
#1A3B67
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Cookie List
1.87:1
#000000
on
#1A3B67
needs 3.0:1 (large text)
19px · bottom of viewport
a Personal
2.75:1
#000000
on
#41556F
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a Business
1.87:1
#000000
on
#1A3B67
needs 4.5:1 (normal text)
16px · mid-page
a Foundation
1.87:1
#000000
on
#1A3B67
needs 4.5:1 (normal text)
16px · mid-page

1 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 Your Privacy Choices1.87:13.0:1
#000000
#1A3B67
Fail
h3 Manage Consent Prefe…1.87:13.0:1
#000000
#1A3B67
Fail
h3 Cookie List1.87:13.0:1
#000000
#1A3B67
Fail
title Welcome to SHRM | Th…5.24:14.5:1
#000000
#7F7F7F
Pass
a Skip to main content5.24:14.5:1
#000000
#7F7F7F
Pass
p Your membership is …5.24:14.5:1
#000000
#7F7F7F
Pass
span Renew now5.24:14.5:1
#000000
#7F7F7F
Pass
span opens in a new tab5.24:14.5:1
#000000
#7F7F7F
Pass
p Your membership has …5.24:14.5:1
#000000
#7F7F7F
Pass
span Renew Now5.24:14.5:1
#000000
#7F7F7F
Pass
span opens in a new tab5.24:14.5:1
#000000
#7F7F7F
Pass
p Your Executive Netwo…5.24:14.5:1
#000000
#7F7F7F
Pass
span Renew Now5.24:14.5:1
#000000
#7F7F7F
Pass
span opens in a new tab5.24:14.5:1
#000000
#7F7F7F
Pass
p Your membership has …5.24:14.5:1
#000000
#7F7F7F
Pass
span Renew Now5.24:14.5:1
#000000
#7F7F7F
Pass
span opens in a new tab5.24:14.5:1
#000000
#7F7F7F
Pass
a Personal2.75:14.5:1
#000000
#41556F
Fail
a Business1.87:14.5:1
#000000
#1A3B67
Fail
a Foundation1.87:14.5:1
#000000
#1A3B67
Fail

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 87/100 — 3 failing, 27 passed
REVIEW
87

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#uuid_s778022_a2581994-8af3-4254-b595-7fa26eac37d6_2 > div#uuid_s778022_af9824ca-2ee8-4828-a921-f580a1714935_2 > div#uuid_s778022_ac17a68f-2f39-4c2f-acbb-64dd247df958_2 > maglr-counter.hydrated div#uuid_s778022_a2581994-8af3-4254-b595-7fa26eac37d6_2 > div#uuid_s778022_af9824ca-2ee8-4828-a921-f580a1714935_2 > div#uuid_s778022_ac17a68f-2f39-4c2f-acbb-64dd247df958_2 > maglr-counter.hydrated
div#uuid_s778022_a2581994-8af3-4254-b595-7fa26eac37d6_2 > div#uuid_s778022_accf81b1-56eb-40ad-8127-2a8cbe937dd5_2 > div#uuid_s778022_a69cebf8-1e89-4232-ab9e-82661a33740b_2 > maglr-counter.hydrated div#uuid_s778022_a2581994-8af3-4254-b595-7fa26eac37d6_2 > div#uuid_s778022_accf81b1-56eb-40ad-8127-2a8cbe937dd5_2 > div#uuid_s778022_a69cebf8-1e89-4232-ab9e-82661a33740b_2 > maglr-counter.hydrated
div#uuid_s778022_a2581994-8af3-4254-b595-7fa26eac37d6_2 > div#uuid_s778022_ae433383-ed19-4317-9d00-056dbe1763bd_2 > div#uuid_s778022_aa9b9c20-55c9-4cd0-8872-8b07a28e7f41_2 > maglr-counter.hydrated div#uuid_s778022_a2581994-8af3-4254-b595-7fa26eac37d6_2 > div#uuid_s778022_ae433383-ed19-4317-9d00-056dbe1763bd_2 > div#uuid_s778022_aa9b9c20-55c9-4cd0-8872-8b07a28e7f41_2 > maglr-counter.hydrated

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#uuid_s778022_a4225c21-04cb-49ed-b24b-83df360a118b_2 > div#uuid_s778022_add25f62-13b4-49ec-9720-9d1f45834517_2 > div#uuid_s778022_a342c02e-3f9b-44fa-a7c8-f645cf256e21_2 > div#uuid_s778022_ae5be3b2-95f2-40b1-a83e-85143a6536a5_2 div#uuid_s778022_a4225c21-04cb-49ed-b24b-83df360a118b_2 > div#uuid_s778022_add25f62-13b4-49ec-9720-9d1f45834517_2 > div#uuid_s778022_a342c02e-3f9b-44fa-a7c8-f645cf256e21_2 > div#uuid_s778022_ae5be3b2-95f2-40b1-a83e-85143a6536a5_2

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.

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
Member Login section#scene_s778022_a4225c21-04cb-49ed-b24b-83df360a118b_2 > div#uuid_s778022_a4225c21-04cb-49ed-b24b-83df360a118b_2 > div#uuid_s778022_a2e0c423-405a-4743-a58e-85b80bd517ca_2 > div#uuid_s778022_a8306ab7-cb82-4826-ba2f-74fc00be5352_2

These items highlight common accessibility best practices.

○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-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
●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
●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
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●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 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
○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.
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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.
A
Landmark Structure
13 landmarks
PASS
13 landmarks
Info::
<main> landmark present
Info::
8 <nav> landmark(s) found
Warning::
6 of 8 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

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

A+
Form Accessibility
All 8 controls labeled
PASS
All 8 controls labeled
Info::
8 control(s) properly labeled
8 controls
8 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback