Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 1 REVIEW 6 FIX

Link & Button Quality

Action

10 issue(s) across 140 links and 8 buttons

FIX

10 issue(s) across 140 links and 8 buttons

5 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://www.facebook.com/greenhouse.io/; https://www.linkedin.com/company/greenhouse-inc-/; https://www.youtube.com/channel/UCwLlhrx5lFssgTwKCHEuC8g; https://www.instagram.com/greenhousesoftware/; https://www.tiktok.com/@greenhouse_software

5 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /blog/g2-2026-awards-best-software-spring ("Learn more"); /events/open-for-ops-save-the-date-2026 ("Learn more"); /ai-recruiting ("Learn more"); /real-talent-candidate-matching ("Learn more"); https://my.greenhouse.com ("Learn more")

7 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://my.greenhouse.com/; https://my.greenhouse.com/; https://www.facebook.com/greenhouse.io/; https://www.linkedin.com/company/greenhouse-inc-/; https://www.youtube.com/channel/UCwLlhrx5lFssgTwKCHEuC8g; https://www.instagram.com/greenhousesoftware/; https://www.tiktok.com/@greenhouse_software

123 link(s) with descriptive text

140 links

5 empty

5 generic text

7 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://my.greenhouse.com/	Job seekers	new tab	Add '(opens in new tab)' to text
/blog/g2-2026-awards-best-software-sprin…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: G2 2026 Awards Best Software Spring
/events/open-for-ops-save-the-date-2026	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Open For Ops Save The Date 2026
https://www.facebook.com/greenhouse.io/	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/greenho…	(empty)	empty	Add link text or aria-label
https://www.youtube.com/channel/UCwLlhrx…	(empty)	empty	Add link text or aria-label
https://www.instagram.com/greenhousesoft…	(empty)	empty	Add link text or aria-label
https://www.tiktok.com/@greenhouse_softw…	(empty)	empty	Add link text or aria-label
/ai-recruiting	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Ai Recruiting
/real-talent-candidate-matching	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Real Talent Candidate Matching
https://my.greenhouse.com	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: My.Greenhouse.Com
https://my.greenhouse.com/	Job seekers	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/greenhouse.io/	facebook	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/greenho…	linkedin	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UCwLlhrx…	youtube	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/greenhousesoft…	instagram	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@greenhouse_softw…	tiktok	new tab	Add '(opens in new tab)' to text

131 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://www.facebook.com/greenhouse.io/; https://www.linkedin.com/company/greenhouse-inc-/; https://www.youtube.com/channel/UCwLlhrx5lFssgTwKCHEuC8g; https://www.instagram.com/greenhousesoftware/; https://www.tiktok.com/@greenhouse_software

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

/blog/g2-2026-awards-best-software-spring ("Learn more"); /events/open-for-ops-save-the-date-2026 ("Learn more"); /ai-recruiting ("Learn more"); /real-talent-candidate-matching ("Learn more"); https://my.greenhouse.com ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

https://my.greenhouse.com/; https://my.greenhouse.com/; https://www.facebook.com/greenhouse.io/; https://www.linkedin.com/company/greenhouse-inc-/; https://www.youtube.com/channel/UCwLlhrx5lFssgTwKCHEuC8g; https://www.instagram.com/greenhousesoftware/; https://www.tiktok.com/@greenhouse_software

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://greenhouse.io/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://greenhouse.io/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Heading Hierarchy

12 headings, 1 skip(s)

REVIEW

12 headings, 1 skip(s)

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 The only hiring platform you’ll
H1 ever need duplicate H1
H3 Real Talent skipped
H2 See who’s hiring with Greenhouse
H2 Hire faster and smarter with Greenhouse AI
H2 Great companies hire with Greenhouse
H2 Greenhouse has made a real difference to how we hire at Ocado Group. It’s helped us simplify our recruitment processes, cutting our time-to-hire by nearly 30%.
H2 The best teams start with hiring – and the best hiring starts with Greenhouse
H3 Flex and scale with ease
H3 Future-proof your hiring
H2 Everything you need to get better at hiring
H2 Check out upcoming events and webinars

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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+

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

No banner (header) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Alt Text Quality

All 45 images OK

PASS

All 45 images OK

2 image(s) with alt text over 125 characters

15 decorative image(s) correctly marked

28 image(s) with good alt text

45 images 28 good alt text 15 decorative

Issue	Count
too long	2 image(s)

Form Accessibility

1 of 3 controls have issues

PASS

1 of 3 controls have issues

1 control(s) without accessible label

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

Got: <input type="submit">

2 control(s) properly labeled

3 controls

2 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#search-3	search	Search the site	for/id
#Email	email	*Email address	for/id
input	submit	(none)	none

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

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

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form 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 ✓

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)

Element	Ratio	Required	FG	BG	Result
h1 The	17.09:1	3.0:1	#000000	#C9F0E6	Pass
h1 hiring platform you�…	17.09:1	3.0:1	#000000	#C9F0E6	Pass
h1 ever need	17.09:1	3.0:1	#000000	#C9F0E6	Pass
h2 See who’s hiring w…	17.09:1	3.0:1	#000000	#C9F0E6	Pass
h2 Hire faster and smar…	17.09:1	3.0:1	#000000	#C9F0E6	Pass
h2 Great companies hire…	17.09:1	3.0:1	#000000	#C9F0E6	Pass
h2 Greenhouse has made …	17.09:1	3.0:1	#000000	#C9F0E6	Pass
h2 The best teams start…	17.09:1	3.0:1	#000000	#C9F0E6	Pass
h2 Everything you need …	17.09:1	3.0:1	#000000	#C9F0E6	Pass
h2 Check out upcoming e…	17.09:1	3.0:1	#000000	#C9F0E6	Pass
h3 Flex and scale with …	17.09:1	3.0:1	#000000	#C9F0E6	Pass
h3 Future-proof your hi…	17.09:1	3.0:1	#000000	#C9F0E6	Pass
title Greenhouse \| Applica…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to Content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Close mobile sub-nav…	16.62:1	4.5:1	#000000	#C6EDE3	Pass
a Greenhouse Home Link	17.09:1	4.5:1	#000000	#C9F0E6	Pass
button Platform	17.09:1	4.5:1	#000000	#C9F0E6	Pass
span Open menu for	17.09:1	4.5:1	#000000	#C9F0E6	Pass
div Platform	17.09:1	4.5:1	#000000	#C9F0E6	Pass
a Only in Greenhouse	17.09:1	4.5:1	#000000	#C9F0E6	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 97/100 — 2 failing, 27 passed

PASS

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.

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
Real Talent `div#w-node-a24719bc-8506-a42c-bf29-1dcf62c6e58d-ba6594cf > div.content-gallery-item > div.content-gallery-item-heading > h3`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Including a skip link can help users skip to the main content to save time. Learn more about skip links.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Skip to Content `body > div.page-header > a.link-11-2-2`

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.

○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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

●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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●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 have a discernible name

●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

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○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

○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 type="image">` elements have `[alt]` text

○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.

○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.