Skip to content
https://icims.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
5
REVIEW
7
PASS
1
INFO
0
Checks
13
1 PASS 7 REVIEW 5 FIX
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::
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

B
Heading Hierarchy
46 headings
REVIEW
46 headings
Info::
Single H1 present
Warning::
4 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 ICIMS Hire
  • H3 ICIMS Engage
  • H3 ICIMS Employer Branding
  • H3 Retail
  • H3 Healthcare & hospitals
  • H3 Manufacturing
  • H3 Finance
  • H3 CHROs & HR leaders
  • H3 Talent acquisition leaders
  • H3 IT leaders
  • H3 HR operations leaders
  • H3 Created with ICIMS
  • H3 The Cheesecake Factory
  • H3 Resource center
  • H3 Editor's Pick
  • H3 Corporate newsroom
  • H3 About ICIMS
  • H3 ADP
  • H3 Infor
  • H3 Microsoft
  • H3 UKG
  • H1 Power exceptional hiring
  • H2 Meet ICIMS Coalesce AI
  • H2 All-in-one recruitment software
  • H2 Customer transformations
  • H2 (empty)
  • H3 How The Cheesecake Factory hires 30,000+ annually with a great candidate experience, powered by ICIMS Applicant Tracking System.
  • H2 (empty)
  • H3 How a global services provider uses ICIMS to streamline hiring worldwide and improve overall productivity.
  • H2 (empty)
  • H3 How Xanterra increased both applicants per opening and quality of hire for unique hospitality workers.
  • H2 (empty)
  • H3 How NorthStar Anesthesia hires highly specialized, in-demand talent.
  • H3 Ready to learn more?Let's talk.
  • H3 Thank you for your interest in iCIMS. A Sales representative will be in touch with you shortly.
  • H2 FAQ
  • H3 What is ICIMS responsible AI program?
  • H3 How do you use AI to hire?
  • H3 What is ICIMS?
  • H3 How does ICIMS improve the hiring process?
  • H3 Can ICIMS integrate with other platforms and job boards?
  • H3 Does ICIMS support high-volume hiring?
  • H3 How does ICIMS enhance candidate engagement?
  • H3 How does ICIMS protect candidate and company data?
  • H3 Does ICIMS support global and multilingual recruiting?
  • H3 What kind of training and support does ICIMS provide?

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

C
Alt Text Quality
Action
9 of 59 images have issues
REVIEW
9 of 59 images have issues
Critical::
9 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
18 decorative image(s) correctly marked
Info::
32 image(s) with good alt text
59 images 32 good alt text 18 decorative 9 missing
IssueCount
missing9 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
Form Accessibility
2 of 12 controls have issues
REVIEW
2 of 12 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" id="searchsubmit">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s" id="s">
Info::
10 control(s) properly labeled
12 controls
10 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#FirstNametext*for/id
#LastNametext*for/id
#Emailemail*for/id
#Phonetel*for/id
#Function__cselect*for/id
#ResponsibilityLevel__cselect*for/id
#Companytext*for/id
#NumberOfEmployeesselect*for/id
#Number_of_New_Hires_Annually__cselect*for/id
#Countryselect*for/id
#stext(Search)placeholder only
#searchsubmitsubmit(none)none

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

<input type="submit" id="searchsubmit">

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

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="s" id="s">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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 Page not found | ICIMS | The Leading Cloud Recruiting Software ✓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
B
Lighthouse Accessibility Audits
Score 84/100 — 6 failing, 30 passed
REVIEW
84

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

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
+1 div.mktoFieldWrap > div.iti > div.iti__flag-container > div.iti__selected-flag

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
AI assistant body.home > q-focus-sentinel > div
After AI assistant body.home > q-focus-sentinel > div
AI assistant, start div#qualified-multimodal-host > div
AI assistant, end div#qualified-multimodal-host > div

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

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.card > div.card-body > p.card-text > img div.card > div.card-body > p.card-text > img
div.content-container > div.slide-copy > p > img.rotator-logo div.content-container > div.slide-copy > p > img.rotator-logo
div.content-container > div.slide-copy > p > img.rotator-logo div.content-container > div.slide-copy > p > img.rotator-logo
div.content-container > div.slide-copy > p > img.rotator-logo div.content-container > div.slide-copy > p > img.rotator-logo
div.content-container > div.slide-copy > p > img.rotator-logo div.content-container > div.slide-copy > p > img.rotator-logo
body.home > div.module-rotator > div.controls > img.chevron body.home > div.module-rotator > div.controls > img.chevron
body.home > div.module-rotator > div.controls > img.chevron body.home > div.module-rotator > div.controls > img.chevron

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.module-rotator > div.slide > div.image-container > a div.module-rotator > div.slide > div.image-container > a
div.module-rotator > div.slide > div.image-container > a div.module-rotator > div.slide > div.image-container > a
div.module-rotator > div.slide > div.image-container > a div.module-rotator > div.slide > div.image-container > a
div.module-rotator > div.slide > div.image-container > a div.module-rotator > div.slide > div.image-container > a
div.container > div > div.social-icons > a div.container > div > div.social-icons > a
div.container > div > div.social-icons > a div.container > div > div.social-icons > a
div.container > div > div.social-icons > a div.container > div > div.social-icons > a
div.container > div > div.social-icons > a div.container > div > div.social-icons > a
div.container > div > div.social-icons > a div.container > div > div.social-icons > 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
Privacy notice |  Terms of use |  Cookie Settings |  Modern Slavery Statement |… div.footer-lower-section > div.container > div.footer-links > ul

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

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
Privacy Notice. div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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 are valid and not misspelled
●Buttons have an accessible name
●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.
●Select elements have associated label elements.
●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
●ARIA input fields have accessible names
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●All heading elements contain content.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○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
○`<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
○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
○Tables have different content in the summary attribute and `<caption>`.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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+
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
h2 Meet ICIMS Coalesce …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 All-in-one recruitme…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Customer transformat…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 FAQ21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ICIMS Hire21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ICIMS Engage21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ICIMS Employer Brand…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Retail21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Healthcare & hospita…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Manufacturing21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Finance21.00:13.0:1
#000000
#FFFFFF
Pass
h3 CHROs & HR leaders21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Talent acquisition l…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 IT leaders21.00:13.0:1
#000000
#FFFFFF
Pass
h3 HR operations leader…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Created with ICIMS21.00:13.0:1
#000000
#FFFFFF
Pass
h3 The Cheesecake Facto…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Resource center21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Editor's Pick21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Corporate newsroom21.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.

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

Send Feedback