chrome/browser/resources/accessibility/accessibility.html
Use this page to inspect the internal representation of accessibility in Chrome. You can see and modify the various accessibility modes Chrome has. You can also view the accessibility tree for a specific page, or for the Chrome app natively.
Check/uncheck accessibility modes to see how they change a page's accessibility.
Native accessibility API support
Allows Chrome to be controlled via native accessibility APIs specific to this platform.
Web accessibility
Accessibility support is enabled for web content.
Text metrics
Enables support for querying line breaks and the bounding box of arbitrary character ranges.
Extended properties
Exposes accessibility APIs needed only by advanced assistive technologies.
Screen reader
Exposes accessibility APIs needed only by screen readers.
HTML
Exposes HTML tag names and attributes via accessibility APIs.
Active assistive technology:
Is the active AT a screen reader:
UIA clients:
Number of accessible nodes available to accessibility tools (ATs): .
Number of accessible nodes referenced by one or more ATs: .
Number of previously active nodes no longer available in the browser: .
Accessibility features in Chrome are off by default and enabled automatically on-demand.
Suppress automatic accessibility enablement from platform API consumers such as assistive tech.
Changes to this setting will persist until the browser is restarted. This setting is the same as running with --disable-platform-accessibility-integration.
Lock the current accessibility mode from being changed except by this page.
To force accessibility to be enabled at launch, run Chrome with this flag:
--force-renderer-accessibility
To force the accessibility AXMode to one of the predefined bundles, run Chrome with the --force-renderer-accessibility flag and optional argument:
--force-renderer-accessibility=[basic|complete|form-controls]
If the optional parameter is absent, the AXMode bundle will default to complete.
To disable accessibility, run Chrome with this flag:
--disable-renderer-accessibility
API type shown in the tree: Error: Not able to load options
Use filters to match the attributes and attribute values you want included in the output. Filters can contain simple wildcards (*) only, they're not regular expressions. Attributes are separated by spaces.
Allow:
Include these attributes. Empty attributes are skipped.
Allow empty:
Include these attributes, even if they are empty.
Deny:
Exclude these attributes.
Set a delay, in milliseconds, before getting the native accessibility tree:
ms
Top Level Window support is not available on this platform.