Skip to content
ZenTheme Lab

Guide · Accessibility

Zendesk Help Center accessibility: what WCAG 2.1 AA means for your theme

Zendesk's default Copenhagen theme is built to WCAG 2.1 AA. The moment you customize it, keeping it accessible becomes your job. Here is what that covers and how to check it.

Updated

This guide is for admins who own a Help Center and want to know where the responsibility sits and what to test. It is not legal advice. If a regulation applies to you, ask someone qualified.

What Zendesk says it covers

In Making your help center accessible (opens in a new tab), Zendesk describes the Copenhagen theme as developed to comply with the WCAG 2.1 AA standard, and says it strives to meet or exceed it. That applies to the theme as Zendesk ships it.

What changes when you customize

The same article is direct about custom themes. When you create one, you take ownership of it. Custom themes are not supported by Zendesk and are not updated automatically when new theme features are released, and you are responsible for the accessibility of the theme.

Zendesk also asks you to consult WCAG 2.1 AA when you change colors, fonts, the logo or images in the theme settings. So even without touching code, a low-contrast brand color is your doing, not the theme's.

Five checks that catch most problems

  1. Text contrast: body text needs a ratio of at least 4.5:1 against its background, large text 3:1, per WCAG 1.4.3 (opens in a new tab). Test your brand color on buttons, your link color on the page background, and muted helper text.
  2. Non-text contrast: input borders, focus outlines and icons that carry meaning need 3:1, per WCAG 1.4.11 (opens in a new tab). Pale grey borders on a white form are the usual failure.
  3. Links: Zendesk's content guidance (opens in a new tab) says links need contrast and a cue other than color, such as an underline.
  4. Keyboard: tab through the home page, search, an article and the request form. Every control should be reachable and show where focus is.
  5. Your own content: headings in order with one h1, alt text on images that matter, and link text that makes sense out of context. The theme cannot fix these for you.

Keeping a custom theme current

Zendesk's advice is to start from the latest Copenhagen version and add your changes to it. The Copenhagen repository (opens in a new tab) has a changelog (opens in a new tab) where you can see which fixes you are missing. The article also says accessibility improvements for advanced helpers are generally not released to older Templating API versions, so a theme still on v1 to v3 is stuck without them. The v4 migration guide covers the move.

Where a theme can help

If you would rather not track Copenhagen releases yourself, pick a theme that stays on the current version and lets you set colors without code. ZenTheme Pro is built on Copenhagen, and its default light and dark palettes are set to meet WCAG AA contrast. Your own colors and content still need the checks above.

Not affiliated with Zendesk.