Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Salesforce QA / Tester
medium

How do you do accessibility testing?

Accessibility = software usable by people with disabilities. Often legally required (Section 508 US, EAA EU).

Standards:

  • WCAG 2.1 AA (most common).
  • WCAG 2.2 AAA (highest).
  • Section 508 (US federal).

Test areas:

  • Keyboard navigation: all features accessible without mouse.
  • Screen reader: VoiceOver, NVDA, JAWS announce content correctly.
  • Color contrast: text legible.
  • Focus indicators: visible when tabbing.
  • Alt text: images described.
  • ARIA labels: dynamic content labeled.
  • Form labels: every input labeled.

Tools:

  • axe DevTools — browser extension.
  • WAVE — accessibility checker.
  • Lighthouse — Chrome built-in.
  • Cypress + axe-core — automated.
  • Manual: real users with assistive tech.

Salesforce specific:

  • Lightning components built on accessible primitives.
  • Custom components must follow WCAG.
  • Lightning Design System components are accessible by default.

Common pitfalls:

  • Skipping accessibility — legal risk.
  • Custom components inaccessible.
  • Color-only conveying information.
  • No keyboard support.

Senior insight: accessibility is good design. Helps everyone, mandatory for some.

Why this answer works

Modern. The standards / tools / patterns and "good design" framing are mature.

Follow-ups to expect

Related dictionary terms