Skip to content
https://workable.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
3
REVIEW
2
PASS
8
INFO
0
Checks
13
8 PASS 2 REVIEW 3 FIX
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #004038
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 ModePartial Dark Mode
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::
1 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 1 <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.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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

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
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Workable | All-in-one HR software ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
A+
Heading Hierarchy
48 headings
PASS
48 headings
Info::
Single H1 present
  • H1 The future-ready HR platform
  • H2 A complete talent sourcing solution
  • H3 Post to 200+ job boards
  • H3 Great results on LinkedIn & Indeed
  • H3 Passive candidate sourcing tools
  • H3 Employee referral program
  • H3 Careers page builder
  • H2 A comprehensive recruiting platform
  • H3 Talent CRM database
  • H3 Evaluation tools
  • H3 AI-assisted applicant screening
  • H3 Self-service interview scheduling
  • H3 Candidate experience
  • H3 Flexible workflows
  • H3 Offer management
  • H2 A flexible employee management system
  • H3 New hire onboarding
  • H3 Self-service employee portal
  • H3 360° performance review tools
  • H3 System of record for all HR data
  • H3 Digital document and e-signature management
  • H2 An easy way to track time and make payroll
  • H3 Time off and PTO management
  • H3 Time and attendance tracking
  • H3 One-click payroll reporting
  • H2 AI that works for you
  • H3 Creating content
  • H3 Automating tasks
  • H3 Sourcing and matching candidates
  • H2 Built for demanding businesses
  • H3 Powerful reporting tools
  • H3 270+ integrations
  • H3 Mobile-first HR
  • H3 Enterprise-grade security & compliance
  • H3 Outstanding support & training
  • H2 Our take on HR software
  • H3 No smoke and mirrors
  • H3 Simplicity isn't simple
  • H3 Software shouldn't be a second job
  • H3 AI isn't the future, it's now
  • H3 We solve real problems
  • H2 Trusted by thousands of businesses like yours
  • H2 30,000+
  • H2 400M
  • H2 2.1M
  • H2 100+
  • H2 98%
  • H2 Try out Workable
A+
Alt Text Quality
All 36 images OK
PASS
All 36 images OK
Info::
36 image(s) with good alt text
36 images 36 good alt text
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A
Favicon & Branding
20 icon(s) detected
PASS
20 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Workable
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: minimal-ui
PWA Install Criteria ✓ Installable
Name Workable ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode minimal-ui ✓
Name Workable Display Mode minimal-ui Theme Color #00756a Background Color #00756a Icons 10 icon(s)
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 The future-ready HR …19.55:13.0:1
#000000
#FFF5EE
Pass
h2 A complete talent19.55:13.0:1
#000000
#FFF5EE
Pass
h2 sourcing solution19.55:13.0:1
#000000
#FFF5EE
Pass
h2 A comprehensive21.00:13.0:1
#000000
#FFFFFF
Pass
h2 recruiting platform21.00:13.0:1
#000000
#FFFFFF
Pass
h2 A flexible employee21.00:13.0:1
#000000
#FFFFFF
Pass
h2 management system21.00:13.0:1
#000000
#FFFFFF
Pass
h2 An easy way to track…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 and make payroll21.00:13.0:1
#000000
#FFFFFF
Pass
h2 AI that works for yo…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Built for demanding21.00:13.0:1
#000000
#FFFFFF
Pass
h2 businesses21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our take on HR softw…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trusted by thousands21.00:13.0:1
#000000
#FFFFFF
Pass
h2 of businesses like y…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 30,000+21.00:13.0:1
#000000
#FFFFFF
Pass
h2 400M21.00:13.0:1
#000000
#FFFFFF
Pass
h2 2.1M21.00:13.0:1
#000000
#FFFFFF
Pass
h2 100+21.00:13.0:1
#000000
#FFFFFF
Pass
h2 98%21.00:13.0:1
#000000
#FFFFFF
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 98/100 — 1 failing, 24 passed
PASS
98

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.

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 html

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
●`[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.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●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
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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
○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
○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.
○`[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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback