Enable accessibility by default

[ethindp]

Description

Currently, the Chromium browser only enables accessibility on Windows and Mac OS, and only if a screen reader is determined to be running at the time the chromium engine performs the check. The reasoning, at least according to the Electron documentation, is that enabling accessibility by default causes a performance hit. I have found no evidence to support this claim. (See https://electronjs.org/docs/tutorial/accessibility and https://www.chromium.org/developers/design-documents/accessibility#TOC-How-Chrome-detects-the-presence-of-Assistive-Technology for information.) I do not believe accessibility effects the browser experience for people who are not using a screen reader. Please enable accessibility by default, whether a screen reader is running or not, so that people with disabilities on platforms such as Linux can use it.

Steps to Reproduce

1. On Linux, install Brave and the Orca screen reader.
2. Launch Orca and Brave.
3. Try to navigate the brave window.

Actual result:

Orca is unable to interact with the Brave window whatsoever (other than reading the title bar). The Chromium browser accepts the option "--force-renderer-accessibility", however Brave seems to ignore this flag and accessibility is still not enabled.

Expected result:

Orca should be able to interact fully with the Brave window (including add-on windows that use the Brave HTML renderer).

Reproduces how often:

This problem reproduces itself every time Orca is running and Brave is launched.

Brave version (brave://version info)

Brave Browser 79.1.2.41

Version/Channel Information:

Stable channel

• Can you reproduce this issue with the current release? Yes
• Can you reproduce this issue with the beta channel? Yes
• Can you reproduce this issue with the dev channel? Yes
• Can you reproduce this issue with the nightly channel? Yes

Other Additional Information:

• Does the issue resolve itself when disabling Brave Shields? N/A
• Does the issue resolve itself when disabling Brave Rewards? N/A
• Is the issue reproducible on the latest version of Chrome? Yes, except that --force-renderer-accessibility does enable accessibility (though there are still accessibility problems).

Miscellaneous Information: