From d64f700203a1c9fcbc5d20d51ba4fb44ddbd1fe8 Mon Sep 17 00:00:00 2001 From: Joel Einbinder Date: Fri, 26 Apr 2019 13:40:08 -0700 Subject: [PATCH] fix(docs): screen readers aren't the only kind of assistive technology (#4349) The docs incorrectly implied that screen readers were the only assistive technology to do filtering on the tree. @alice --- docs/api.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/api.md b/docs/api.md index 464cbeffb56..f7750903fd0 100644 --- a/docs/api.md +++ b/docs/api.md @@ -2076,14 +2076,14 @@ Shortcut for [(await worker.executionContext()).evaluateHandle(pageFunction, ... ### class: Accessibility -The Accessibility class provides methods for inspecting Chromium's accessibility tree. The accessibility tree is used by assistive technology such as [screen readers](https://en.wikipedia.org/wiki/Screen_reader). +The Accessibility class provides methods for inspecting Chromium's accessibility tree. The accessibility tree is used by assistive technology such as [screen readers](https://en.wikipedia.org/wiki/Screen_reader) or [switches](https://en.wikipedia.org/wiki/Switch_access). Accessibility is a very platform-specific thing. On different platforms, there are different screen readers that might have wildly different output. Blink - Chrome's rendering engine - has a concept of "accessibility tree", which is than translated into different platform-specific APIs. Accessibility namespace gives users access to the Blink Accessibility Tree. -Most of the accessibility tree gets filtered out when converting from Blink AX Tree to Platform-specific AX-Tree or by screen readers themselves. By default, Puppeteer tries to approximate this filtering, exposing only the "interesting" nodes of the tree. +Most of the accessibility tree gets filtered out when converting from Blink AX Tree to Platform-specific AX-Tree or by assistive technologies themselves. By default, Puppeteer tries to approximate this filtering, exposing only the "interesting" nodes of the tree.