Salesforce
Accessibility Testing for Salesforce and Experience Cloud

Rishabh Kumar
Published On

Table of contents
Lorem ipsum
Lorem ipsum
Lorem ipsum
Lorem ipsum
Lorem ipsum
How Do You Test Salesforce Accessibility?
Test it where customers and employees actually meet it, which means Experience Cloud portals, screen flows and OmniScripts, custom Lightning Web Components and the service console. Combine automated checks against WCAG success criteria with keyboard-only and screen-reader walkthroughs of the journeys that matter most, and repeat them on every Salesforce release and every site publish.
Both releases and publishes can change accessibility without anyone touching your configuration. Salesforce builds accessibility into its standard components, but custom components, custom styling and configuration choices are yours, and so is responsibility for the journeys built from them.
Why Accessibility is Now a Release Criterion
Three things have moved accessibility from a nice-to-have to something Salesforce teams test every release.
The European Accessibility Act
Directive (EU) 2019/882 has applied since 28 June 2025 to a defined set of consumer products and services in the EU, including consumer banking and e-commerce, wherever the provider is based. Its technical benchmark is the harmonised standard EN 301 549, which references WCAG 2.1 Level AA for web content. Salesforce sites and portals delivering in-scope services to EU consumers fall within it, and your legal team should confirm which of your services are in scope.
More of Salesforce Faces Customers
Experience Cloud portals, self-service, web chat and AI agents put more Salesforce screens directly in front of customers, including customers with disabilities.
Releases Change Accessibility
Winter ‘27, for example, enforced changes to how page components behave at 200% browser zoom. A release can improve accessibility in standard components while breaking assumptions your custom components relied on.
Changes like these arrive as release updates, so you can catch them before Salesforce enforces them. Find out how in testing Salesforce release updates.
Start with Salesforce's Own Conformance Reports
Salesforce publishes Accessibility Conformance Reports for its products, release by release, including Experience Cloud, Lightning base components and individual clouds. They're written against WCAG and Section 508, and they're candid. Where a standard component only partially supports a success criterion, the report says so, and names the pages and patterns affected.
Read the reports for the products your journeys use before you plan testing. Any known gap in a standard component you rely on is a gap in your journey too, and those are the first places to look, and the first issues to raise with Salesforce.
What to Cover
Area | What to check | Why Salesforce changes it |
|---|---|---|
Keyboard access | Every critical journey can be completed with the keyboard alone, with visible focus and a logical order | Component and layout changes can move focus order |
Screen readers | Fields, buttons, errors and dynamic updates are announced meaningfully | Custom components often lack the labels and roles standard components have |
Zoom and reflow | Pages stay usable at 200% zoom and on narrow screens | Winter ‘27 enforced zoom changes, and themes such as SLDS 2 alter layout |
Contrast and colour | Text and controls meet contrast requirements, and colour is never the only signal | Branding and theme changes, especially on Experience Cloud sites |
Forms and errors | Labels, instructions and error messages are clear and properly linked to their fields | Screen flows and OmniScripts render forms differently from record pages |
Time limits | Sessions and multi-step forms give enough time, or let users extend it | Session policy changes |
Authentication | Login, MFA and self-registration are accessible | Login flow and identity provider changes |
AI agents | Chat can be used with a keyboard and screen reader, and new messages are announced | Messaging and agent channel updates |
Automated checkers find a useful share of issues, such as missing labels and contrast failures, but nowhere near all of them. Pair them with manual walkthroughs.
Custom components are where most Salesforce accessibility issues start. Salesforce LWC testing explains how to test what Salesforce doesn't build for you, and accessibility testing covers what automated scanners can and can't catch.
A 15-minute Walkthrough for Every Release
Pick your three most important journeys, such as a customer logging in and updating their details, a case being raised, and a screen flow being completed. For each one, run through these checks in the preview sandbox.
Unplug the mouse: Complete the journey with Tab, Shift+Tab, Enter, Space and the arrow keys. Can you see where focus is at every step?
Zoom to 200%: Complete it again. Does anything overlap, disappear or need sideways scrolling?
Switch on a screen reader: Listen to the first form and the first error message. Do the labels make sense on their own? Is the error announced when it appears?
Trigger every error state: Submit the form with gaps. Is each error linked to its field, and does focus move somewhere sensible?
Open the chat, if there is one: Can you send a message and hear the reply without touching the mouse?
Anything that fails goes into the release’s defect list, with the same priority as a functional failure. Then run your automated checker across the same pages.
Error handling is where forms most often fail, accessible or not. Work through it field by field with form testing.
Where Virtuoso QA Fits
Virtuoso QA covers the functional side of accessibility work. It proves that the portal and console journeys your accessibility checks depend on still work after every release and publish, so audits and walkthroughs always start from journeys that function.
The same plain English journeys double as the list of pages and steps your accessibility reviews should cover.
Accessibility conformance itself needs dedicated accessibility checkers, keyboard and screen-reader walkthroughs, and expert review. No platform can certify conformance on its own, and Virtuoso QA doesn't claim to.
Virtuoso QA's Salesforce test automation reruns your portal and console journeys on every preview sandbox and site publish, so accessibility checks never start from a broken page.
Related Reads
Frequently Asked Questions
Is Salesforce Accessible?
Does the European Accessibility Act Apply to Salesforce Portals?
What Standard Should Salesforce Sites Meet?
How Often Should Salesforce Sites Be Tested for Accessibility?
Written by

Rishabh Kumar
AI Testing & Quality Engineering Contributor
Rishabh leads business development and marketing at Virtuoso QA. He writes about AI-powered test automation, end-to-end testing, self-healing tests, and quality engineering, exploring how these capabilities can improve test coverage, reduce test maintenance, and support reliable software releases.










