General Accessibility Guidelines

The enterprise strives to be WCAG 2.0 AA Compliant. A detailed list of WCAG 2.0 requirements can be found on the W3 website.


  1. If you can use a native HTML element or attribute with the semantics and behavior you require already built in (like 'header' or 'nav', use that instead of re-purposing a more generic element(like 'div') and adding an ARIA role, state, or property to make it accessible
  2. Keep link underlines
  3. Add skip links at the top of the page to guide the user over areas they would like to skip
  4. Include alternative text for meaningful images
  5. All interactive elements must have an accessible name. An interactive element only has an accessible name when its accessibility API property has a value
  6. Ensure color is not the primary means of communication
  7. Alert the user when a max-width has been reached in an input

Keyboard Requirements

Anything you can do with your mouse, make sure you can do it through the keyboard.

  1. Ensure that all interactive elements are keyboard accessible
  2. Add the tabindex attribute whenever necessary
  3. Disabled controls should not be in the tab order