Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarify that Baseline does not cover assistive technology #519

Merged
merged 6 commits into from
Mar 28, 2024
Merged

Clarify that Baseline does not cover assistive technology #519

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
14ce8c7
Clarify that Baseline does not cover assistive technology
tidoust Jan 8, 2024
a166ed4
Reformulate per comments
tidoust Jan 19, 2024
3f17f45
Split exposure to platform AAPI to separate bullet
tidoust Jan 30, 2024
61a2f0b
Refine non-goal description about assistive technology
tidoust Feb 21, 2024
9f2c97f
Update docs/baseline.md
tidoust Mar 21, 2024
118af61
Update docs/baseline.md
tidoust Mar 28, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/baseline.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
tidoust marked this conversation as resolved.
Show resolved Hide resolved
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.
Expand Down Expand Up @@ -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
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because this is a future consideration and Baseline is not going to add AT support, I suggest something a bit more straightforward as a future goal (since it keeps the scope strictly with browsers and does not require AT):

"Confirm if features are exposed to platform accessibility APIs (AAPIs) as specified."

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reformulated, but my goal here was to minimize changes and this is more a list of candidate baseline states than a generic list of areas for future consideration. I merged the two "Buggy" bullets into one, using your wording.

* 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