Skip to content
https://workday.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
49
GRADE
F
FIX
6
REVIEW
6
PASS
1
INFO
0
Checks
13
1 PASS 6 REVIEW 6 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Missing
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::
3 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 3 <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
12 landmarks
REVIEW
12 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
1 of 3 <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 ASIDE "Open Cookie Preferences Modal" 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

C
Alt Text Quality
Action
8 of 29 images have issues
REVIEW
8 of 29 images have issues
Critical::
8 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
3 decorative image(s) correctly marked
Info::
18 image(s) with good alt text
29 images 18 good alt text 3 decorative 8 missing
IssueCount
missing8 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

C
Form Accessibility
Action
9 of 27 controls have issues
REVIEW
9 of 27 controls have issues
Critical::
9 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select id="vjs_select_732">; <select id="vjs_select_751">; <select id="vjs_select_766">; <select id="vjs_select_1639">; <select id="vjs_select_1658">; <select id="vjs_select_1673">; <select id="vjs_select_2541">; <select id="vjs_select_2560">; <select id="vjs_select_2575">
Info::
18 control(s) properly labeled
27 controls
18 labeled
0 placeholder only
9 unlabeled
ControlTypeLabelMethod
#vjs_select_682selectColorfor/id
#vjs_select_687selectOpacityfor/id
#vjs_select_697selectColorfor/id
#vjs_select_702selectOpacityfor/id
#vjs_select_712selectColorfor/id
#vjs_select_717selectOpacityfor/id
#vjs_select_1589selectColorfor/id
#vjs_select_1594selectOpacityfor/id
#vjs_select_1604selectColorfor/id
#vjs_select_1609selectOpacityfor/id
#vjs_select_1619selectColorfor/id
#vjs_select_1624selectOpacityfor/id
#vjs_select_2491selectColorfor/id
#vjs_select_2496selectOpacityfor/id
#vjs_select_2506selectColorfor/id
#vjs_select_2511selectOpacityfor/id
#vjs_select_2521selectColorfor/id
#vjs_select_2526selectOpacityfor/id
#vjs_select_732select(none)none
#vjs_select_751select(none)none
#vjs_select_766select(none)none
#vjs_select_1639select(none)none
#vjs_select_1658select(none)none
#vjs_select_1673select(none)none
#vjs_select_2541select(none)none
#vjs_select_2560select(none)none
#vjs_select_2575select(none)none

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

<select id="vjs_select_732">; <select id="vjs_select_751">; <select id="vjs_select_766">; <select id="vjs_select_1639">; <select id="vjs_select_1658">; <select id="vjs_select_1673">; <select id="vjs_select_2541">; <select id="vjs_select_2560">; <select id="vjs_select_2575">

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

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

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

2 pass 18 fail WCAG AA
h2 Welcome,
1.13:1
#000000
on
#011328
needs 3.0:1 (large text)
24px · bottom of viewport
a Skip to main content
2.48:1
#000000
on
#434D62
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
button Products
1.24:1
#000000
on
#091B3D
needs 4.5:1 (normal text)
16px · top of page (header area)
p Discover superintelligence for the new w…
1.24:1
#000000
on
#091B3D
needs 4.5:1 (normal text)
16px · above the fold
a Artificial Intelligence
1.16:1
#000000
on
#041630
needs 4.5:1 (normal text)
16px · above the fold
a Sana from Workday
1.13:1
#000000
on
#011328
needs 4.5:1 (normal text)
16px · above the fold
a Agent System of Record
1.13:1
#000000
on
#011328
needs 4.5:1 (normal text)
16px · above the fold
a Agents
1.13:1
#000000
on
#011328
needs 4.5:1 (normal text)
16px · above the fold
a Responsible AI
1.13:1
#000000
on
#011328
needs 4.5:1 (normal text)
16px · above the fold
a AI Masterclass
1.13:1
#000000
on
#011328
needs 4.5:1 (normal text)
16px · above the fold
p Empower your people and adapt your workf…
1.13:1
#000000
on
#011328
needs 4.5:1 (normal text)
16px · above the fold
a HR Solutions
1.13:1
#000000
on
#011328
needs 4.5:1 (normal text)
16px · above the fold
h4 PRODUCTS
1.13:1
#000000
on
#011328
needs 3.0:1 (large text)
16px · mid-page
a Human Capital Management
1.13:1
#000000
on
#011328
needs 4.5:1 (normal text)
16px · mid-page
a Human Resource Management
1.13:1
#000000
on
#011328
needs 4.5:1 (normal text)
16px · mid-page
a Workday Paradox
1.13:1
#000000
on
#011328
needs 4.5:1 (normal text)
16px · mid-page
a Talent Management
1.13:1
#000000
on
#011328
needs 4.5:1 (normal text)
16px · mid-page
a Workforce Management
1.13:1
#000000
on
#011328
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 Welcome,1.13:13.0:1
#000000
#011328
Fail
title The Enterprise AI Pl…7.37:14.5:1
#000000
#999999
Pass
button Continue7.37:14.5:1
#000000
#999999
Pass
a Skip to main content2.48:14.5:1
#000000
#434D62
Fail
button Products1.24:14.5:1
#000000
#091B3D
Fail
p Discover superintell…1.24:14.5:1
#000000
#091B3D
Fail
a Artificial Intellige…1.16:14.5:1
#000000
#041630
Fail
a Sana from Workday1.13:14.5:1
#000000
#011328
Fail
a Agent System of Reco…1.13:14.5:1
#000000
#011328
Fail
a Agents1.13:14.5:1
#000000
#011328
Fail
a Responsible AI1.13:14.5:1
#000000
#011328
Fail
a AI Masterclass1.13:14.5:1
#000000
#011328
Fail
p Empower your people …1.13:14.5:1
#000000
#011328
Fail
a HR Solutions1.13:14.5:1
#000000
#011328
Fail
h4 PRODUCTS1.13:13.0:1
#000000
#011328
Fail
a Human Capital Manage…1.13:14.5:1
#000000
#011328
Fail
a Human Resource Manag…1.13:14.5:1
#000000
#011328
Fail
a Workday Paradox1.13:14.5:1
#000000
#011328
Fail
a Talent Management1.13:14.5:1
#000000
#011328
Fail
a Workforce Management1.13:14.5:1
#000000
#011328
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.

C
Lighthouse Accessibility Audits
Action
Score 70/100 — 9 failing, 23 passed
REVIEW
70

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
Change Cookie Preferences » div.mainContent > div > div.pdynamicbutton > a.shp
Privacy Statement div > div.footer > div.left > a#privacyPolicyAnchor
Cookie Notice div > div.footer > div.left > a.inline-bwxxkt
Powered by: div.wrapper > div > div.footer > div.right

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.persona-cards > div.persona-grid > div.persona-card > img#a4fbfe234db29473d89a6ae2b73a40ad42a4c39aaeabbfa3f4418f14458994d6-0 div.persona-cards > div.persona-grid > div.persona-card > img#a4fbfe234db29473d89a6ae2b73a40ad42a4c39aaeabbfa3f4418f14458994d6-0
div#dcce5556079fd7db824c09e19a45f30f5df4997a462bede31872cd72ea822ab2 > div.lottie__wrapper > div.fallback > img.fallback__img div#dcce5556079fd7db824c09e19a45f30f5df4997a462bede31872cd72ea822ab2 > div.lottie__wrapper > div.fallback > img.fallback__img

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.carousel-slides-wrapper > div.carousel-slide > div.video-play-overlay > a.play-video-btn div.carousel-slides-wrapper > div.carousel-slide > div.video-play-overlay > a.play-video-btn
nav > ul.footer-container__wrapper--legal-links > li.footer-container__wrapper--legal-items > a nav > ul.footer-container__wrapper--legal-links > li.footer-container__wrapper--legal-items > a

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Legal Privacy Accessibility Subscriptions Your Privacy Choices Cookie Preferenc… div.row > div.col > nav > ul.footer-container__wrapper--legal-links

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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
Go to slide 2 div#c19ce4f7bb0e41a1966f2210c4c988dbfd4400028560ebededbc582070b20ec9 > div.carousel-section-container > div.carousel-pagination > button.pagination-dot
Go to slide 3 div#c19ce4f7bb0e41a1966f2210c4c988dbfd4400028560ebededbc582070b20ec9 > div.carousel-section-container > div.carousel-pagination > button.pagination-dot
Go to slide 4 div#c19ce4f7bb0e41a1966f2210c4c988dbfd4400028560ebededbc582070b20ec9 > div.carousel-section-container > div.carousel-pagination > button.pagination-dot
Go to slide 5 div#c19ce4f7bb0e41a1966f2210c4c988dbfd4400028560ebededbc582070b20ec9 > div.carousel-section-container > div.carousel-pagination > button.pagination-dot
Go to slide 6 div#c19ce4f7bb0e41a1966f2210c4c988dbfd4400028560ebededbc582070b20ec9 > div.carousel-section-container > div.carousel-pagination > button.pagination-dot

These items highlight common accessibility best practices.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#pop-outerdiv08440674501816143 > div#pop-div206779166990352654 > div#pop-div309661101445641218 > div#pop-frame08534654904411774 div#pop-outerdiv08440674501816143 > div#pop-div206779166990352654 > div#pop-div309661101445641218 > div#pop-frame08534654904411774

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
About Cookies on This Site We use cookies on this site to make our site work. … div.wrapper > div

These are opportunities to improve the interpretation of your content by users in different locales.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Explore Sana div.aem-Grid > div.button > div.cmp-button > a.wd-btn
All HR div.aem-Grid > div.button > div.cmp-button > a.wd-btn
Explore Our Agents div.aem-Grid > div.button > div.cmp-button > a.wd-btn
Read Story div.standardcard__container-content--button > div.button > div.cmp-button > a.wd-btn
Read Story div.standardcard__container-content--button > div.button > div.cmp-button > a.wd-btn
Read Story div.standardcard__container-content--button > div.button > div.cmp-button > a.wd-btn
Read Story div.standardcard__container-content--button > div.button > div.cmp-button > a.wd-btn
Read Story div.standardcard__container-content--button > div.button > div.cmp-button > a.wd-btn
Read Story div.standardcard__container-content--button > div.button > div.cmp-button > a.wd-btn
Contact Sales div > div.button > div.cmp-button > a.wd-btn
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
`button`, `link`, and `menuitem` elements have accessible names
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.
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Heading elements appear in a sequentially-descending order
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
`[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
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.
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.
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.
A
Heading Hierarchy
162 headings, 1 skip(s)
PASS
162 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Products
  • H3 AI
  • H4 Artificial Intelligence
  • H4 Sana from Workday
  • H4 Agent System of Record
  • H4 Agents
  • H4 Responsible AI
  • H4 AI Masterclass
  • H3 HR
  • H4 HR Solutions
  • H4 PRODUCTS
  • H4 Human Capital Management
  • H4 Human Resource Management
  • H4 Workday Paradox
  • H4 Talent Management
  • H4 Workforce Management
  • H4 Employee Experience
  • H4 HR Service Delivery
  • H4 Employee Voice
  • H4 Workforce Planning
  • H4 Analytics & Reporting
  • H4 Vendor Management System
  • H4 Local & Global Payroll
  • H3 Finance
  • H4 Finance Solutions
  • H4 PRODUCTS
  • H4 Financial Management
  • H4 Spend Management
  • H4 Financial Planning
  • H4 Analytics & Reporting
  • H4 Payroll
  • H3 Planning
  • H4 Planning
  • H4 PRODUCTS
  • H4 Financial Planning
  • H4 Close & Consolidation
  • H4 Workforce Planning
  • H4 Operational Planning
  • H3 Legal
  • H4 Legal Overview
  • H4 Products
  • H4 Contract Intelligence
  • H4 Contract Lifecycle Management
  • H3 Industry Operations
  • H4 All Industries
  • H4 PRODUCTS
  • H4 Frontline Workforce Solutions
  • H4 Professional Services Automation
  • H4 Supply Chain Management for Healthcare
  • H4 Student Management
  • H3 Platform
  • H4 IT Solutions
  • H4 PRODUCTS
  • H4 Our Technology
  • H4 Extensions
  • H4 Orchestrate & Integrations
  • H4 Data Cloud
  • H4 Workday Extend
  • H3 Workday ERP
  • H3 Marketplace
  • H3 Midsize Business Solutions
  • H3 Workday Build
  • H3 Why Workday
  • H2 Industries
  • H3 Financial Services
  • H4 Banking & Capital Markets
  • H4 Financial Services
  • H4 Insurance
  • H4 Investment Management
  • H3 Healthcare
  • H3 Hospitality
  • H3 Manufacturing
  • H4 Energy and Resources
  • H4 Life Sciences
  • H4 Manufacturing
  • H3 Professional & Business Services
  • H3 Public Services
  • H4 Higher Education
  • H4 Nonprofit
  • H4 Public Sector
  • H4 Special Districts
  • H4 State & Local Government
  • H4 U.S. Federal Government
  • H3 Retail
  • H3 Technology, Media & Communications
  • H4 Communications
  • H4 Media & Entertainment
  • H4 Technology
  • H3 Transportation
  • H3 All Industries
  • H2 Customers
  • H3 Customer Stories
  • H3 Services
  • H4 Overview
  • H4 Deployment
  • H4 Training & Certifications
  • H4 Success Plans
  • H3 Support
  • H4 Overview
  • H4 Community
  • H4 Login Help
  • H2 Learn
  • H3 Demos
  • H3 Events
  • H3 Webinars
  • H3 Resources
  • H4 All Resources
  • H4 For Finance
  • H4 For HR
  • H4 For IT
  • H4 For Planning
  • H4 For Legal
  • H3 Training & Certifications
  • H3 Topics Hub
  • H3 Blog
  • H2 Partners
  • H3 Overview
  • H3 Find a Partner
  • H4 Advisory
  • H4 Innovation
  • H4 Managed Service Provider
  • H4 Services
  • H3 Partner Program
  • H3 Marketplace
  • H2 Company
  • H3 About Workday
  • H4 Our Story
  • H4 Our Values
  • H4 Leadership
  • H4 Inclusion & Belonging
  • H4 Public Policy
  • H4 Sponsorships
  • H4 Contact Us
  • H4 Workday Ventures
  • H3 Careers
  • H4 Overview
  • H4 Life at Workday
  • H4 Early Career
  • H4 Job Search
  • H3 Corporate Responsibility
  • H4 Overview
  • H4 Foundation
  • H4 Sustainability
  • H4 Workforce Development
  • H3 Trust
  • H3 Investor Relations
  • H3 Newsroom
  • H3 Perspectives
  • H2 Sign in
  • H2 Welcome,
  • H1 Superintelligence for work. Meet Sana.
  • H2 Empower your entire organization to reimagine work.
  • H3 HR
  • H3 Finance
  • H3 IT
  • H3 Legal
  • H3 Operations
  • H2 Products Products
  • H2 Industries Industries
  • H2 Learn Learn
  • H2 Company Company
  • H5 Please accept cookies to continue. skipped

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

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

Send Feedback