From 14ce8c740679768f6527a12f0fe32eb775eec701 Mon Sep 17 00:00:00 2001 From: Francois Daoust Date: Mon, 8 Jan 2024 11:41:09 +0100 Subject: [PATCH 1/6] Clarify that Baseline does not cover assistive technology This adds an item to non-goals to clarify that support in assistive tools that may be used along a browser is not (yet?) covered by Baseline. See discussion in https://github.com/web-platform-dx/web-features/issues/498 --- docs/baseline.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/baseline.md b/docs/baseline.md index 9205721ebd2..3ae423d6ece 100644 --- a/docs/baseline.md +++ b/docs/baseline.md @@ -59,6 +59,9 @@ Baseline status cannot or will not satisfy the following non-goals: Many Baseline features will not achieve 100% user reach soon or perhaps ever. If a web developer needs to support a globally uncommon or discontinued browser (e.g., Internet Explorer 11), then the developer needs to know the specific limitations of that browser, not a broad overview of developers’ most commonly required browsers. Baseline can’t be both. +* **Identify support in assistive technology.** + Baseline should cover core accessibility support in browsers but it does not cover support in assistive tools (e.g., screen magnifiers, screen readers, alternative keyboards) that may be used along a browser to meet the requirements of people with disabilities. + See also: [Future considerations](#future-considerations). * **Identify support in non-web environments.** Developers use web technologies in non-web settings, such as JavaScript in Node.js, Web APIs in Deno, or HTML and CSS in Electron-based applications. For good reasons, web technologies in non-web settings often depart from interoperability with web browsers. @@ -176,5 +179,6 @@ Here are some areas for future consideration and not currently in-scope for Base * Progressive enhancement safe (i.e., limited penalties for support failures) * Developer feedback requested * Buggy (e.g., supported but in ways that are surprising and semi-interoperable) +* Buggy or unsupported in assistive tools * Obsolete/deprecated/legacy/etc. (i.e., flagged as such in the specification or dropped from newer versions of the specification) * Having high-quality polyfills available From a166ed4ad53a46675427b478567e82f77f2c992c Mon Sep 17 00:00:00 2001 From: Francois Daoust Date: Fri, 19 Jan 2024 15:40:09 +0100 Subject: [PATCH 2/6] Reformulate per comments --- docs/baseline.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/baseline.md b/docs/baseline.md index 3ae423d6ece..a5baa24d3d1 100644 --- a/docs/baseline.md +++ b/docs/baseline.md @@ -60,7 +60,7 @@ Baseline status cannot or will not satisfy the following non-goals: If a web developer needs to support a globally uncommon or discontinued browser (e.g., Internet Explorer 11), then the developer needs to know the specific limitations of that browser, not a broad overview of developers’ most commonly required browsers. Baseline can’t be both. * **Identify support in assistive technology.** - Baseline should cover core accessibility support in browsers but it does not cover support in assistive tools (e.g., screen magnifiers, screen readers, alternative keyboards) that may be used along a browser to meet the requirements of people with disabilities. + Baseline does not cover support in assistive technology (AT), which includes screen readers, screen magnifiers, voice control, and so on. See also: [Future considerations](#future-considerations). * **Identify support in non-web environments.** Developers use web technologies in non-web settings, such as JavaScript in Node.js, Web APIs in Deno, or HTML and CSS in Electron-based applications. @@ -178,7 +178,6 @@ Here are some areas for future consideration and not currently in-scope for Base * Upcoming (e.g., not yet shipped in all browsers) * Progressive enhancement safe (i.e., limited penalties for support failures) * Developer feedback requested -* Buggy (e.g., supported but in ways that are surprising and semi-interoperable) -* Buggy or unsupported in assistive tools +* Buggy (e.g., supported but in ways that are surprising and semi-interoperable, not exposed to platform accessibility APIs (AAPIs) as specified) * Obsolete/deprecated/legacy/etc. (i.e., flagged as such in the specification or dropped from newer versions of the specification) * Having high-quality polyfills available From 3f17f45e8ea1c1ff00ce65c903cd536e459bed3d Mon Sep 17 00:00:00 2001 From: Francois Daoust Date: Tue, 30 Jan 2024 14:20:07 +0100 Subject: [PATCH 3/6] Split exposure to platform AAPI to separate bullet --- docs/baseline.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/baseline.md b/docs/baseline.md index a5baa24d3d1..bda56ca1513 100644 --- a/docs/baseline.md +++ b/docs/baseline.md @@ -178,6 +178,7 @@ Here are some areas for future consideration and not currently in-scope for Base * Upcoming (e.g., not yet shipped in all browsers) * Progressive enhancement safe (i.e., limited penalties for support failures) * Developer feedback requested -* Buggy (e.g., supported but in ways that are surprising and semi-interoperable, not exposed to platform accessibility APIs (AAPIs) as specified) +* Buggy (e.g., supported but in ways that are surprising and semi-interoperable) +* Not exposed to platform accessibility APIs (AAPIs) as specified * Obsolete/deprecated/legacy/etc. (i.e., flagged as such in the specification or dropped from newer versions of the specification) * Having high-quality polyfills available From 61a2f0ba04297dfdad530fede175d5ad0c004408 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fran=C3=A7ois=20Daoust?= Date: Wed, 21 Feb 2024 08:56:35 +0100 Subject: [PATCH 4/6] Refine non-goal description about assistive technology Co-authored-by: Daniel D. Beck --- docs/baseline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/baseline.md b/docs/baseline.md index bda56ca1513..6dde31e1bda 100644 --- a/docs/baseline.md +++ b/docs/baseline.md @@ -60,7 +60,7 @@ Baseline status cannot or will not satisfy the following non-goals: If a web developer needs to support a globally uncommon or discontinued browser (e.g., Internet Explorer 11), then the developer needs to know the specific limitations of that browser, not a broad overview of developers’ most commonly required browsers. Baseline can’t be both. * **Identify support in assistive technology.** - Baseline does not cover support in assistive technology (AT), which includes screen readers, screen magnifiers, voice control, and so on. + Baseline does not cover support for screen readers, screen magnifiers, voice control, and other assistive technology that browsers do not expose to developers. See also: [Future considerations](#future-considerations). * **Identify support in non-web environments.** Developers use web technologies in non-web settings, such as JavaScript in Node.js, Web APIs in Deno, or HTML and CSS in Electron-based applications. From 9f2c97fb1a369e2e9b6bf2db5f57973dca6e3c0d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fran=C3=A7ois=20Daoust?= Date: Thu, 21 Mar 2024 11:59:20 +0100 Subject: [PATCH 5/6] Update docs/baseline.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Philip Jägenstedt --- docs/baseline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/baseline.md b/docs/baseline.md index 6dde31e1bda..ff2943fad7d 100644 --- a/docs/baseline.md +++ b/docs/baseline.md @@ -60,7 +60,7 @@ Baseline status cannot or will not satisfy the following non-goals: If a web developer needs to support a globally uncommon or discontinued browser (e.g., Internet Explorer 11), then the developer needs to know the specific limitations of that browser, not a broad overview of developers’ most commonly required browsers. Baseline can’t be both. * **Identify support in assistive technology.** - Baseline does not cover support for screen readers, screen magnifiers, voice control, and other assistive technology that browsers do not expose to developers. + Baseline does not cover support for screen readers, screen magnifiers, voice control, and other assistive technology that is not built into browsers. See also: [Future considerations](#future-considerations). * **Identify support in non-web environments.** Developers use web technologies in non-web settings, such as JavaScript in Node.js, Web APIs in Deno, or HTML and CSS in Electron-based applications. From 118af6192bf7bbd3e4b37f6489739c958525c100 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fran=C3=A7ois=20Daoust?= Date: Thu, 28 Mar 2024 13:25:12 +0100 Subject: [PATCH 6/6] Update docs/baseline.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Philip Jägenstedt --- docs/baseline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/baseline.md b/docs/baseline.md index ff2943fad7d..3eb05b6adb3 100644 --- a/docs/baseline.md +++ b/docs/baseline.md @@ -179,6 +179,6 @@ Here are some areas for future consideration and not currently in-scope for Base * Progressive enhancement safe (i.e., limited penalties for support failures) * Developer feedback requested * Buggy (e.g., supported but in ways that are surprising and semi-interoperable) -* Not exposed to platform accessibility APIs (AAPIs) as specified +* Support in assistive technology that is not built into browsers. * Obsolete/deprecated/legacy/etc. (i.e., flagged as such in the specification or dropped from newer versions of the specification) * Having high-quality polyfills available