Loading

Salesforce Product Accessibility Resource Library

Udgivelsesdato: May 1, 2026
Beskrivelse

Our accessibility efforts extend to how we think about our products, events, and experiences, with the goal of becoming a top employer for people with disabilities. Our goal is that you and your customers Shift Left with accessibility: Shifting Left means integrating accessibility reviews, testing, and remediation at every stage of the development cycle, from design through to release, rather than treating it as a final quality check. This approach ensures that accessibility is built in from the start rather than retrofitted at the end.

Løsning

​​​​​​Salesforce's commitment to Accessibility

These resources provide an overview of Salesforce's accessibility programme, published conformance reports, and design system guidance. Administrators and developers evaluating Salesforce's WCAG (Web Content Accessibility Guidelines) conformance posture -- for example when completing a VPAT (Voluntary Product Accessibility Template) -- should start here.


Testing for Accessibility

Salesforce recommends a combination of manual and automated testing to achieve thorough accessibility coverage. For manual testing, use the three most widely adopted screen readers: NVDA (NonVisual Desktop Access) on Windows, JAWS (Job Access With Speech) on Windows, and VoiceOver on macOS and iOS. For automated testing, Salesforce provides the sa11y library described below.

Salesforce's sa11y

sa11y (Salesforce Accessibility) is a set of JavaScript libraries, created by Salesforce, to help you write automated accessibility tests. sa11y helps you detect machine-knowable static DOM accessibility issues. It is based on axe-core, an accessibility testing JavaScript engine. sa11y provides support for Jest, WebdriverIO, and generic JavaScript tests. Developers building custom components or LWC-based apps should use sa11y as part of their CI/CD pipeline to catch accessibility regressions automatically.


Using Salesforce with Assistive Technology

These articles help end users and administrators configure and navigate Salesforce using screen readers and keyboards. If a customer or internal user reports difficulty using a specific part of Lightning Experience with assistive technology, the articles below cover the most common scenarios.


Reporting accessibility issues with Salesforce Accessibility Support

If you or your customers encounter an accessibility issue not covered by the Known Issues list, use the steps below to submit a formal product accessibility case. Before submitting, check the Known Issues list to avoid duplicating an existing report.

 

Yderligere ressourcer

The following authoritative references support the guidance in this article:

  • W3C WCAG 2.2 -- The full Web Content Accessibility Guidelines specification. Use this when evaluating whether a specific Salesforce behaviour meets a particular success criterion. It is important to note that when reporting a case to Salesforce accessibility, using one of these criterions will help your case get solved faster.
  • Salesforce Accessibility -- Salesforce's main accessibility landing page, including links to the latest VPATs and conformance reports. 
  • sa11y on GitHub -- Source code, documentation, and contribution guide for Salesforce's automated accessibility testing library.
Vidensartikelnummer

000393483

 
Indlæser
Salesforce Help | Article