Digital Design System

Overview

At WTW, we adhere to WCAG 2.1 Level AA standards. This guidance is for everyone creating digital (web-based) properties, given Section 508 / ADA guidelines as well as more stringent European standards.

Adhering to WCAG 2.1 Level AA can be complicated; fortunately, accessibility is fairly well-documented. When building and testing for WTW, we refer to Google’s Web Fundamentals > Accessibility and Mozilla’s Accessibility documentation.

Accessibility is key to communicating with all users, regardless of ability.
  • Global legal compliance is necessary. Websites that aren’t in compliance are at risk of legal action.
  • Accessible content supports all of our users/client base.
  • Accessibility supports the real goal of the web – access for all.
  • While work is needed on the back-end of a website to support accessibility guidelines, much of accessibility is the responsibility of the content editor. Any time you add a link or image to a page, you’re encountering a possible accessibility problem. Content editors, just like front-end and back-end developers, must always champion accessibility as they add content to a page.
  • If you are working with a vendor, you should place WCAG 2.1 Level AA requirements into your SOW. They and you are responsible for eventual compliance.

Accessibility compliance can be particularly tricky in these areas:

Basic Terminology

<code>aria-label</code> and <code>aria-hidden</code>

  • technique of helping a screen reader connect information or establish a relationship on a page
  • can exist on any HTML element
  • provides detailed information depending on ARIA technique used alt="" attribute
  • associated with an <img> tag
  • detailed attribute mandatory for imagery that conveys information
  • left blank (<code>alt=""</code>) for imagery that is decorative

title="" attribute

  • deprecated
  • similar in functionality to the <code>aria-label</code>

role="presentation" attribute

  • depending on the screen reader, this may be used by the backend/front-end development teams to indicate to the screen reader that an element is not significant to read
  • not useful for content editors

WCAG References