Skip to main content

Make your careers site accessible

Understand who is responsible for your careers site's accessibility, what we build in, and the steps you can take in the editor.

An accessible careers site is one that everyone can use — including candidates who navigate by keyboard, use a screen reader, zoom in, or turn off motion. We build the sections and components of the CareersHub to support that, but the content you put into them is yours. This article explains the split: what we take care of, what's left to you, and exactly where in the editor to do it.

Important: You are solely responsible for the compliance of your careers site. Accessibility requirements differ by country, state, and region, and we can't advise on which ones apply to you. Consult your legal team about your obligations.


Who's responsible for what

Accessibility is a shared job, and it helps to be precise about where the line falls.

We're responsible for the building blocks. The sections, blocks, forms, and navigation in the CareersHub are built to be usable with a keyboard and a screen reader, and we test them on every release.

You're responsible for what you put in them. A perfectly accessible image section still fails a screen reader user if the image has no description. A well-built text block still fails if you use bold text where a heading belongs.

Because of that split, we recommend talking to:

  • Your legal team about the requirements that apply in the regions you hire in

  • Your recruiting team about accessible job descriptions, since those come from your job, not from the site builder

  • Your content team about images, headings, and link text on your pages

Note: There's no single global accessibility standard, and no site is ever "100% accessible" for everyone. Treat it as something you improve continuously, not a box you tick once.


What we build in

Here's what the careers site does for you, without any setup on your side.

Standards we work to

We follow the Web Content Accessibility Guidelines (WCAG) 2.1, aiming to meet or exceed Level AA.

Every component in the site builder is checked automatically against those guidelines on each release, and we run performance and accessibility audits on published pages for both desktop and mobile.

Keyboard and screen reader support

  • Skip to content — a keyboard user pressing Tab on a careers page gets a Skip to content link as the very first stop, so they can jump past the navigation straight to the page body. It's hidden until it's focused, and it's translated into your site's languages.

  • Visible focus indicator — every interactive element shows a clear focus outline when you reach it by keyboard. The outline doesn't appear for mouse clicks, which keeps the design clean without taking the cue away from keyboard users.

  • Page landmarks — navigation, main content, and footer are marked up as distinct regions, so a screen reader user can jump between them.

  • Page language — each page declares its language, which is what tells a screen reader how to pronounce the text. On a multilingual site, this follows the language the visitor is viewing.

Application form

The application form is the most important thing on your careers site, so it gets extra attention:

  • Every field has a proper label, not just placeholder text

  • Errors are announced to screen readers and tied to the field that caused them

  • When a candidate submits an incomplete form, the page scrolls to the first problem field and puts the cursor in it

Motion

If a visitor has Reduce motion turned on in their operating system, a section with a video background shows a still image from the video instead of playing it. You don't need to configure anything for this.

Cookie consent

The cookie consent dialog is announced as a dialog, with its title and description read out, and the checkboxes inside it are properly labelled.

Responsive layout and languages

Sites adapt to different screen sizes, and the site builder supports multiple languages — including a language switcher in the navigation and separate content per language.

Important: None of this guarantees an accessible site. Accessible components can still be used in inaccessible ways. The rest of this article covers the part that's up to you.


Make your content accessible

These are the changes you can make yourself, in the editor, in rough order of impact.

Add alt text to your images

Alt text is a short description that's read aloud by screen readers, shown if the image fails to load, and used by search engines.

Open the upload window from the image you want to describe.

Select the image thumbnail.

Type your description in the Image details panel.

Alt text is available for logos, images in an Image section, Gallery images, card images, and quote author photos. If your site has more than one language, you can set a different description per language.

Note: Background images don't have an alt text field. They're treated as decoration and skipped by screen readers — which is correct, as long as you don't put information only into a background image. If a background image carries meaning, repeat that meaning in the text of the section.

Tip: Describe what the image shows, not that it's an image. Three colleagues at a standing desk is useful; photo1.jpg isn't. If an image is purely decorative, leaving the alt text empty is the right answer — a screen reader will then skip it instead of announcing a filename.

Note: If you leave a logo's alt text empty, we fall back to your company name followed by "logo".

Use a logical heading structure

Screen reader users navigate a page by jumping from heading to heading. If you make text look like a heading by bolding it, it won't appear in that list at all.

In a text block, select your text and pick a level from the block menu in the toolbar: Paragraph, Heading 1, Heading 2, Heading 3, or Heading 4.

Keep the order logical and don't skip levels — a Heading 3 should sit under a Heading 2, not directly under a Heading 1.

Tip: This matters just as much in your job descriptions. Sections like What you'll be doing and What we offer should be real headings, not bold paragraphs. Job descriptions are edited in your job, not in the CareersHub.

Write link text that makes sense on its own

Screen reader users often pull up a list of every link on a page, with no surrounding text. "Click here" and "Read more" tell them nothing.

Instead of

Write

Want to meet the team? Click here to see team photos

Meet our Engineering team in photos

For application instructions, read more

Read our step-by-step application guide

Check your colour contrast

Text needs enough contrast against what's behind it. This is the single most common accessibility failure on careers sites, and it's usually introduced by brand colours.

The CareersHub doesn't check contrast for you, so use an external tool — WebAIM's contrast checker is free and takes seconds.

Pay particular attention to:

  • Text over a background image or video, where contrast changes across the image

  • Light grey body text on a white background

  • Button text against your brand colour

Tip: If text sits over a photo, add a colour or gradient background layer over the image and lower its opacity. You get a consistent, readable backdrop without losing the photo.

Don't rely on colour alone

If colour is the only thing distinguishing two things — a "new" job from an old one, an error from a hint — that distinction disappears for colour blind visitors. Add a word, an icon, or a shape as well.

Keep text big enough to read

Aim for at least 16 pixels for body text. You can adjust this in two places:

  • Across the site — set Font size for your text styles in the theme menu

  • Per section — use Text size in the section's settings

Leave space between clickable things

Links and buttons sitting right on top of each other are hard to hit accurately, especially on a phone or for anyone with a motor impairment. Use the spacing and padding settings in a section rather than cramming elements together.

Be careful with video and motion

  • Avoid anything that flashes more than three times a second — it can trigger seizures.

  • Captions and subtitles are set on YouTube or Vimeo, not in the CareersHub. If a video carries information a candidate needs, make sure it's captioned on the platform hosting it, or repeat the information in text on the page.

Be careful with custom code

Custom HTML, CSS, and JavaScript bypass everything we build in. A custom widget can introduce a keyboard trap or remove focus outlines across your whole site, and our automated tests won't catch it.

Important: If you add custom code to your careers site, its accessibility is entirely yours to test.


Check your site

Work through this list on your live careers site — not in the editor preview.

Tab through a page from the top. The first thing you reach should be Skip to content. Keep going and check you can see where you are at every step, and that you never get stuck.

Complete an application using only the keyboard. Submit it with a required field empty and check that the error is clear and that the cursor lands on the field.

Review your alt text. Open each image section and gallery and check every image that carries meaning has a description.

Check your heading order. Read the page and note where levels skip or where bold text is standing in for a heading.

Read your links out of context. Any link that reads "click here" or "read more" needs rewriting.

Run a contrast check on your body text, your buttons, and any text sitting over a photo.

Zoom to 200% in your browser and check nothing overlaps or disappears.

Tip: Do this once properly, then re-check after any change to your theme colours or fonts — those changes affect every page at once.


Learn more

These are independent resources, not ours, and they're the ones we'd point you to first:

Note: These cover general web accessibility. For an audit of your specific site, or for advice on the law where you hire, work with an accessibility specialist and your legal team.


Tell us about accessibility problems

We'd rather hear about a problem than not.

Report an issue

Contact your customer success manager or our Support team via chat. To help us reproduce it quickly, include:

  • The exact URL where it happens

  • What you did, step by step

  • A screenshot or screen recording

  • Which assistive technology you were using, if any

  • Your browser and device

For example: "A screen reader can't reach the search box in the jobs list on example.recruitee.com/careers."

Suggest an improvement

Post it on our Canny board for the careers site, where you can also see and vote on what others have asked for. You can read about how we prioritize our roadmap to see what happens next.

Share an audit

If you've had your careers site audited, send us the report through your customer success manager or Support. It's genuinely useful to us.

Note: Audits of a careers site usually find a mix of issues. Some will be ours to fix in the components, and a significant share will be content on your side — missing alt text, heading order, contrast, and link text.


Frequently asked questions

Is my careers site WCAG compliant?

We build and test our components against WCAG 2.1 Level AA, but compliance is a property of your finished site, not of the builder. Your content, your colours, and any custom code all affect the result.

Are my job descriptions covered?

The page around them is. The text of the job description comes from your job, so its heading structure, link text, and formatting are yours to get right.

Can the CareersHub tell me if my colours have enough contrast?

No. Use an external contrast checker such as WebAIM's.

Do I need to add captions to a background video?

A background video is decoration and has no audio track playing, so captions don't apply. But don't put information only in a video — if it matters, put it in the text too.

Does accessibility affect SEO?

Yes, substantially. Alt text, heading structure, and descriptive link text are all things search engines use to understand your pages.


Did this answer your question?