Loading

Unresponsive Pages in Chrome and Microsoft Edge when Accessibility Mode is enabled.

Дата публикации: Jul 10, 2026
Описание

Update (March 2022): Google has confirmed they have included the first set of accessibility performance regression fixes in version 99.04844.74. Web accessibility in Chromium-based browsers will still add some performance overhead. Google is working on longer-term changes via the bug linked below. We will continue to update this article as new information becomes available. 

As of the v89 release, utilizing Chromium-based browsers (the current most updated version of Chrome and MS Edge) Salesforce users may notice unresponsive clicks, page unresponsive errors, and other unexplained latency. This behavior is caused by the enablement of Accessibility Mode.

Accessibility Mode is prompted by applications, websites, or system-requested enablement. When Accessibility mode is triggered, the code continually updates and reviews all browser processes. This is an expensive, synchronous operation that consumes browser and machine resources, and can cause symptoms similar to a memory leak. 

Even if accessibility mode is not enabled by default, it can be triggered by a variety of factors external to Salesforce. 

We understand the impact this has on your users and business, and are collaborating with Chrome to resolve this issue. In the interim, we have the following workarounds. We will continue to update this article as more information becomes available. 

To follow up with Chrome directly regarding this impact, please see this bug

UPDATE (January 2022): 

Chrome is targeting an M99 launch for the auto-disable accessibility feature, which is expected to help minimize the impact of the issue here. You can try out the feature now by going to chrome://flags/#enable-auto-disable-accessibility and selecting Enabled from the dropdown. What it does is turn off accessibility when there isn't a tool/utility actively using it for 30 seconds. 

Chrome is asking for feedback on how this improves performance via the bug.

Chrome hopes to resolve this issue in the first half of 2022. Salesforce continues to recommend the installation and usage of an alternate browser (Non-Chromium). Please see the resolution steps below for instructions on transferring bookmarks and passwords for Safari and Firefox. 

Salesforce support utilizes multiple Browsers to remain agile, quickly troubleshoot, and minimize downtime. We are considering updates to our documentation to recommend the same as a best practice for all Salesforce users. 

Решение

Use the steps below to disable Accessibility Mode in Chrome or Edge and restore Salesforce performance. Option 1 is the most effective long-term fix. Options 2 and 3 are interim workarounds.

Option 1 — Switch to a Non-Chromium Browser (Recommended)

The most effective resolution is to use a non-Chromium browser such as Mozilla Firefox or Apple Safari, which are not affected by this Accessibility Mode issue. To preserve bookmarks and passwords when switching:

  • Switching to Firefox: See Import bookmarks from Chrome to Firefox.
  • Switching to Safari: See Import bookmarks from Chrome to Safari.

Salesforce Support recommends maintaining multiple supported browsers to remain agile and minimize downtime. See also: Import bookmarks from Chrome to Firefox and Import bookmarks from Chrome to Safari.

Option 2 — Disable Accessibility Mode Using the Auto-Disable Chrome Flag

Chrome introduced an auto-disable accessibility feature that turns off Accessibility Mode when no assistive tool has been actively using it for 30 seconds. To enable this feature:

  1. Open Chrome and navigate to chrome://flags/#enable-auto-disable-accessibility in the address bar.
  2. Select Enabled from the dropdown.
  3. Relaunch Chrome when prompted.

This setting helps reduce the frequency of Accessibility Mode activation for users who do not rely on assistive technology tools.

 

Option 3 — Add the --disable-renderer-accessibility Flag to Force-Disable Accessibility Mode

Users who cannot switch browsers can add a startup flag to Chrome or Edge to permanently disable Accessibility Mode during their session:

  1. Follow the instructions at Run Chromium with Flags to add the --disable-renderer-accessibility flag to your browser launch shortcut. Please see Run Chromium with Flags for instructions.
  2. Contact your IT Help Desk or System Administrator if group policy settings restrict access to this flag.

    Note: This flag disables Accessibility Mode regardless of the browser's accessibility settings. It is recommended even if Accessibility Mode appears to be turned off in browser settings.

 

Option 4 — Restart the Browser When It Becomes Unresponsive

If Chrome or Edge becomes unresponsive during a Salesforce session, you can restart all browser processes without losing your open tabs:

  • Chrome: Open a new tab and type chrome://restart in the address bar, then press Enter.
  • Edge: Open a new tab and type edge://restart in the address bar, then press Enter.

This closes all active browser processes and reopens all pages and tabs, clearing the resource consumption caused by Accessibility Mode.

Номер статьи базы знаний

000389105

 
Загрузка
Salesforce Help | Article