Skip to content
https://payscale.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
D
Landmark Structure
Action
11 landmarks
FIX
11 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
8 <nav> landmark(s) found
Warning::
2 of 8 <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!) 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
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::
8 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 8 <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.
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
Info::
Homepage link present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title PayScale - Error 404 (Not Found) Custom Styling Navigation Homepage Link Search Form
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Present
Multiple Sizes Missing
B
Web Manifest
PWA-ready
REVIEW
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: PayScale
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria Installable
Name PayScale 192×192 icon 512×512 icon Start URL / Display Mode standalone
Name PayScale Display Mode standalone Icons 1 icon(s)
A+
Heading Hierarchy
40 headings
PASS
40 headings
Info::
Single H1 present
Info::
1 hidden heading(s) (aria-hidden)
  • H1 Confident pay decisions. Real business impact.
  • H2 Today’s pay playbook can’t keep up with tomorrow’s business challenges
  • H2 The shift isn’t luck – it’s a system
  • H2 Built for every role that touches a pay decision
  • H3 You own the strategy. We give you the system.
  • H3 Compensation touches every HR workflow.
  • H3 Every business decision has a comp consequence.
  • H3 Bridge the gap between strategy and managers.
  • H3 Your team's pay affects everything.
  • H3 Compete for skilled talent in a tight labor market.
  • H3 Smart compensation for high-volume retail.
  • H3 Attract and retain talent in a high-turnover industry.
  • H3 Attract top faculty and staff on limited budgets.
  • H3 Keep projects on track with the right pay strategy.
  • H3 Attract and retain top technical talent in a competitive market.
  • H2 Real outcomes. Real customers.
  • H2 For decades, Payscale has set the standard for how organizations pay
  • H3 Pay Pioneers
  • H3 Data Coverage & Confidence
  • H3 Proven Solutions
  • H3 Continuous Innovation
  • H2 Insights from the industry's pay pioneers
  • H3 2026 Compensation Best Practices Report
  • H3 Q1 2026 Labor Market and Wage Trends Report
  • H2 Ready to make every pay decision count?
  • H2 Cookie Preferences
  • H2 Cookie Preferences hidden
  • H3 Your Privacy
  • H3 Social Media Cookies
  • H3 Targeting Cookies
  • H3 Functional Cookies
  • H3 Performance Cookies
  • H3 Strictly Necessary Cookies
  • H4 Your Privacy
  • H4 Social Media Cookies
  • H4 Targeting Cookies
  • H4 Functional Cookies
  • H4 Performance Cookies
  • H4 Strictly Necessary Cookies
  • H3 Cookie List
A
Alt Text Quality
1 of 88 images have issues
PASS
1 of 88 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
54 decorative image(s) correctly marked
Info::
33 image(s) with good alt text
88 images 33 good alt text 54 decorative 1 missing
IssueCount
missing1 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

A+
Form Accessibility
All 23 controls labeled
PASS
All 23 controls labeled
Info::
23 control(s) properly labeled
23 controls
23 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#FirstNametext*for/id
#LastNametext*for/id
#Emailemail*for/id
#Companytext*for/id
#Phonetel*for/id
#Titletext*for/id
#mktoCheckbox_148420_0checkboxBy submitting this form, you agree to Payscale's Terms of Use and Privacy Policy.for/id
#FirstNametext*for/id
#LastNametext*for/id
#Emailemail*for/id
#Companytext*for/id
#Phonetel*for/id
#Titletext*for/id
#mktoCheckbox_148378_0checkboxBy submitting this form, you agree to Payscale's Terms of Use and Privacy Policy.for/id
#ot-group-id-C0005checkboxSocial Media Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#chkbox-idcheckboxcheckbox labelfor/id
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)
ElementRatioRequiredFGBGResult
h1 Confident pay decis…18.74:13.0:1
#000000
#F4F2EA
Pass
h1 Real business18.74:13.0:1
#000000
#F4F2EA
Pass
h2 Today’s pay18.74:13.0:1
#000000
#F4F2EA
Pass
h2 can’t keep up with…18.74:13.0:1
#000000
#F4F2EA
Pass
h2 The shift isn’t lu…18.74:13.0:1
#000000
#F4F2EA
Pass
h2 Built for every role…18.74:13.0:1
#000000
#F4F2EA
Pass
h2 Real outcomes.18.74:13.0:1
#000000
#F4F2EA
Pass
h2 For decades, Payscal…18.74:13.0:1
#000000
#F4F2EA
Pass
h2 Insights from the in…18.74:13.0:1
#000000
#F4F2EA
Pass
h2 Ready to make every …18.74:13.0:1
#000000
#F4F2EA
Pass
h2 Cookie Preferences18.74:13.0:1
#000000
#F4F2EA
Pass
h2 Cookie Preferences18.74:13.0:1
#000000
#F4F2EA
Pass
h3 You own the strategy…18.74:13.0:1
#000000
#F4F2EA
Pass
h3 Compensation touches…18.74:13.0:1
#000000
#F4F2EA
Pass
h3 Every business decis…18.74:13.0:1
#000000
#F4F2EA
Pass
h3 Bridge the gap betwe…18.74:13.0:1
#000000
#F4F2EA
Pass
h3 Your team's pay affe…18.74:13.0:1
#000000
#F4F2EA
Pass
h3 Compete for skilled …18.74:13.0:1
#000000
#F4F2EA
Pass
h3 Smart compensation f…18.74:13.0:1
#000000
#F4F2EA
Pass
h3 Attract and retain t…18.74:13.0:1
#000000
#F4F2EA
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 91/100 — 3 failing, 24 passed
PASS
91

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.

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
Get a Demo div.header-wrapper > div.button-group > a.btn-modal-form-simple > div
THE NEW REALITY div.container-global > div.header-wrapper > div.label-tag > div
TODAY'S REALITY div.comparison-card > div.comparison-card-title-wrapper > div.label-tag > div.comparison-label
THE INTELLIGENCE FUTURE div.comparison-card > div.comparison-card-title-wrapper > div.comparison-label > div
INTRODUCING PAYSCALE INTELLIGENCE CLOUD div.container-global > div.header-wrapper > div.label-tag > div
Explore Solutions div.header-wrapper > div.button-group > a.btn > div
WHO IT'S FOR div.container-global > div.w-layout-vflex > div.label-tag > div
Get a Demo div.who-subtabs_content > div.button-group > a.btn > div
Contact Sales div.who-subtabs_content > div.button-group > a.btn > div
WHY PAYSCALE div.container-global > div.w-layout-vflex > div.label-tag > div
Get a Demo div.container-global > div.w-layout-vflex > a.btn > div
RESOURCES div.container-global > div.header-wrapper > div.label-tag > div
Read the report a.resources-card > div.resources-content > div.arrow-link > div
Read the report a.resources-card > div.resources-content > div.arrow-link > div
Payscale products div.footer_group > div.footer_link-group > a.footer_link > div
Marketpay div.footer_group > div.footer_link-group > a.footer_link > div
Payfactors div.footer_group > div.footer_link-group > a.footer_link > div
Paycycle div.footer_group > div.footer_link-group > a.footer_link > div
Partners & integrations div.footer_group > div.footer_link-group > a.footer_link > div
Contact us div.footer_group > div.footer_link-group > a.footer_link > div
Customer success & services div.footer_group > div.footer_link-group > a.footer_link > div
Customer stories div.footer_group > div.footer_link-group > a.footer_link > div
Why Payscale div.footer_group > div.footer_link-group > a.footer_link > div
Leadership div.footer_group > div.footer_link-group > a.footer_link > div
Careers div.footer_group > div.footer_link-group > a.footer_link > div
Newsroom div.footer_group > div.footer_link-group > a.footer_link > div
Press releases div.footer_group > div.footer_link-group > a.footer_link > div
Corporate responsibility div.footer_group > div.footer_link-group > a.footer_link > div
For individuals div.footer_group > div.footer_link-group > a.footer_link > div
Salary research div.footer_group > div.footer_link-group > a.footer_link > div
Find a job div.footer_group > div.footer_link-group > a.footer_link > div
Cost of living calculator div.footer_group > div.footer_link-group > a.footer_link > div
Career path planner div.footer_group > div.footer_link-group > a.footer_link > div
Salary survey div.footer_group > div.footer_link-group > a.footer_link > div

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.padding-global > div.container-global > div.footer_top-group > a.footer-logo div.padding-global > div.container-global > div.footer_top-group > a.footer-logo
div.footer_link-group > div.footer_sc-wr > div.footer_soc-links > a.w-inline-block div.footer_link-group > div.footer_sc-wr > div.footer_soc-links > a.w-inline-block
div.footer_link-group > div.footer_sc-wr > div.footer_soc-links > a.w-inline-block div.footer_link-group > div.footer_sc-wr > div.footer_soc-links > a.w-inline-block
div.footer_link-group > div.footer_sc-wr > div.footer_soc-links > a.w-inline-block div.footer_link-group > div.footer_sc-wr > div.footer_soc-links > a.w-inline-block
div.footer_link-group > div.footer_sc-wr > div.footer_soc-links > a.w-inline-block div.footer_link-group > div.footer_sc-wr > div.footer_soc-links > a.w-inline-block
div.footer_link-group > div.footer_sc-wr > div.footer_soc-links > a.w-inline-block div.footer_link-group > div.footer_sc-wr > div.footer_soc-links > a.w-inline-block

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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.w-mod-js html.w-mod-js

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-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
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
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
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.
`button`, `link`, and `menuitem` elements have accessible names
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
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
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
Deprecated ARIA roles were not used
ARIA IDs are unique
Identical links have the same purpose.
`[accesskey]` values are unique
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 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
Buttons have an accessible name
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
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
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.
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