Skip to content
https://salary.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
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'>.
Info::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✗ 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::
4 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 4 <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.
B
Landmark Structure
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
1 of 4 <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 navigation" 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

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

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 Page Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 Pay decisions
2.08:1
#000000
on
#722257
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Everything you need to manage compensati…
2.08:1
#000000
on
#722257
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Explore salaries
2.08:1
#000000
on
#722257
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What customers are saying
2.08:1
#000000
on
#722257
needs 3.0:1 (large text)
24px · bottom of viewport
h2 One platform, every stakeholder
2.08:1
#000000
on
#722257
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Salary.com connects to the systems you a…
2.08:1
#000000
on
#722257
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ready to get pay right?
2.08:1
#000000
on
#722257
needs 3.0:1 (large text)
24px · bottom of viewport
h3 CompAnalyst
2.08:1
#000000
on
#722257
needs 3.0:1 (large text)
19px · bottom of viewport
h3 CompXL
2.08:1
#000000
on
#722257
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Data
2.08:1
#000000
on
#722257
needs 3.0:1 (large text)
19px · bottom of viewport
h3 “Comprehensive compensation data and o…
2.08:1
#000000
on
#722257
needs 3.0:1 (large text)
19px · bottom of viewport
h3 “CompAnalyst AI Suite is proving to be…
2.08:1
#000000
on
#722257
needs 3.0:1 (large text)
19px · bottom of viewport
h3 “The Salary.com AI platform is easy to…
2.08:1
#000000
on
#722257
needs 3.0:1 (large text)
19px · bottom of viewport
h3 “Salary.com has greatly improved our c…
2.08:1
#000000
on
#722257
needs 3.0:1 (large text)
19px · bottom of viewport
h3 “Amazing experience with Salary.com. I…
2.08:1
#000000
on
#722257
needs 3.0:1 (large text)
19px · bottom of viewport
h3 “Comprehensive compensation data and o…
2.08:1
#000000
on
#722257
needs 3.0:1 (large text)
19px · bottom of viewport
h3 “CompAnalyst AI Suite is proving to be…
2.08:1
#000000
on
#722257
needs 3.0:1 (large text)
19px · bottom of viewport
h3 From spreadsheet chaos to compensation c…
2.08:1
#000000
on
#722257
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Compensation strategy that keeps you com…
2.08:1
#000000
on
#722257
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Compensation answers without the learnin…
2.08:1
#000000
on
#722257
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Pay decisions2.08:13.0:1
#000000
#722257
Fail
h2 Everything you need …2.08:13.0:1
#000000
#722257
Fail
h2 Explore salaries2.08:13.0:1
#000000
#722257
Fail
h2 What customers are s…2.08:13.0:1
#000000
#722257
Fail
h2 One platform, every …2.08:13.0:1
#000000
#722257
Fail
h2 Salary.com connects …2.08:13.0:1
#000000
#722257
Fail
h2 Ready to get pay rig…2.08:13.0:1
#000000
#722257
Fail
h3 CompAnalyst2.08:13.0:1
#000000
#722257
Fail
h3 CompXL2.08:13.0:1
#000000
#722257
Fail
h3 Data2.08:13.0:1
#000000
#722257
Fail
h3 “Comprehensive com…2.08:13.0:1
#000000
#722257
Fail
h3 “CompAnalyst AI Su…2.08:13.0:1
#000000
#722257
Fail
h3 “The Salary.com AI…2.08:13.0:1
#000000
#722257
Fail
h3 “Salary.com has gr…2.08:13.0:1
#000000
#722257
Fail
h3 “Amazing experienc…2.08:13.0:1
#000000
#722257
Fail
h3 “Comprehensive com…2.08:13.0:1
#000000
#722257
Fail
h3 “CompAnalyst AI Su…2.08:13.0:1
#000000
#722257
Fail
h3 From spreadsheet cha…2.08:13.0:1
#000000
#722257
Fail
h3 Compensation strateg…2.08:13.0:1
#000000
#722257
Fail
h3 Compensation answers…2.08:13.0:1
#000000
#722257
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 86/100 — 4 failing, 24 passed
REVIEW
86

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

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Compensation Teams div.tabbed-content-wrapper > div.tab-nav > div.tab-scroll > button.tab-button
HR Leaders div.tabbed-content-wrapper > div.tab-nav > div.tab-scroll > button.tab-button
HR Generalists div.tabbed-content-wrapper > div.tab-nav > div.tab-scroll > button.tab-button

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.testimonial-container > div#sliderTestimonial > div.custom-pagination > button.active div.testimonial-container > div#sliderTestimonial > div.custom-pagination > button.active
div.testimonial-container > div#sliderTestimonial > div.custom-pagination > button div.testimonial-container > div#sliderTestimonial > div.custom-pagination > button
div.testimonial-container > div#sliderTestimonial > div.custom-pagination > button div.testimonial-container > div#sliderTestimonial > div.custom-pagination > button
div.testimonial-container > div#sliderTestimonial > div.custom-pagination > button div.testimonial-container > div#sliderTestimonial > div.custom-pagination > button
div.testimonial-container > div#sliderTestimonial > div.custom-pagination > button div.testimonial-container > div#sliderTestimonial > div.custom-pagination > button
div.testimonial-container > div#sliderTestimonial > div.custom-navigation > button.btn-sal div.testimonial-container > div#sliderTestimonial > div.custom-navigation > button.btn-sal
div.testimonial-container > div#sliderTestimonial > div.custom-navigation > button.btn-sal div.testimonial-container > div#sliderTestimonial > div.custom-navigation > button.btn-sal

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.

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
Yes body > div > div#pi_tracking_opt_in_div > a#pi_tracking_opt_in_yes
No body > div > div#pi_tracking_opt_in_div > a#pi_tracking_opt_in_no

These are opportunities to improve the legibility of your content.

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
Trusted by 10,000+ organizations worldwide section.logo-scroll > div.logo-scroll-container > div.logo-scroll-text-col > h4.logo-scroll-title

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
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[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
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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.
○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
○`<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.
○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
Heading Hierarchy
31 headings, 1 skip(s)
PASS
31 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H4 Software + AI
  • H4 Data
  • H4 Expertise
  • H4 Partners
  • H4 Company
  • H1 Pay decisionsbuilt to last.
  • H4 Trusted by 10,000+ organizations worldwide skipped
  • H2 Everything you need to manage compensation – unified
  • H3 CompAnalyst
  • H3 CompXL
  • H3 Data
  • H2 Explore salaries
  • H2 What customers are saying
  • H3 “Comprehensive compensation data and outstanding support make Salary.com a standout tool.”
  • H3 “CompAnalyst AI Suite is proving to be a valuable planning resource. It enables the team to efficiently analyze large volumes of job descriptions that would otherwise take months to sort through man
  • H3 “The Salary.com AI platform is easy to use and intuitive. The pre-baked prompts and insights into competitor pay strategies set it apart from generic AI tools and make it especially valuable for com
  • H3 “Salary.com has greatly improved our compensation strategy, enhancing pay equity & HR decision-making.”
  • H3 “Amazing experience with Salary.com. I will always recommend to other HR professionals.”
  • H3 “Comprehensive compensation data and outstanding support make Salary.com a standout tool.”
  • H3 “CompAnalyst AI Suite is proving to be a valuable planning resource. It enables the team to efficiently analyze large volumes of job descriptions that would otherwise take months to sort through man
  • H2 One platform, every stakeholder
  • H3 From spreadsheet chaos to compensation clarity
  • H3 Compensation strategy that keeps you competitive
  • H3 Compensation answers without the learning curve
  • H2 Salary.com connects to the systems you already use
  • H2 Ready to get pay right?
  • H3 New to Salary.com?
  • H3 About Salary.com
  • H3 Popular Links
  • H4 Ready to see it work?
  • H4 Let's talk

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

A+
Alt Text Quality
All 117 images OK
PASS
All 117 images OK
Info::
5 decorative image(s) correctly marked
Info::
112 image(s) with good alt text
117 images 112 good alt text 5 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#heroEmailInputemailWork emailaria-label
#jobTitletextJob titlefor/id
#locationtextLocationfor/id
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback