first draft of accessibility device section #158
Conversation
|
@hober heres a first go at text for this question. I fought with bikeshed locally for a while, and can't even seem to get current |
Fixed on main. Please rebase! :) |
pes10k
force-pushed
the
add-accessibility-device-question
branch
from
7f12486
to
69b9e4d
Compare
pes10k
force-pushed
the
add-accessibility-device-question
branch
from
69b9e4d
to
1ee702f
Compare
|
done and done! Also, should we be tracking index.html? Guessing not since there isn't one in the repo. If thats right, mind if I .gitignore it? |
the Makefile lands index.html in the build/ subdirectory, which is already in the .gitignore file. |
|
Ah, not sure why but somehow i got a |
| @@ -810,6 +810,52 @@ You may follow the guidelines for <a href="bfcache">BFCache</a> mentioned above, | |||
| as we expect BFCached and detached documents to be treated the same way, | |||
| with the only difference being that BFCached documents can become [=Document/fully active=] again. | |||
|
|
|||
| <h3 class=question id="accessibility-devices"> | |||
| Does your feature allow sites to learn about the users use of accessibility devices? | |||
There was a problem hiding this comment.
| Does your feature allow sites to learn about the users use of accessibility devices? | |
| Does your feature allow sites to learn about the users use of assistive technology? |
| Does your feature allow sites to learn about the users use of accessibility devices? | ||
| </h3> | ||
| The Web is designed to work for everyone, and Web standards should be designed | ||
| for people using assistive devices just as much as for users relying |
There was a problem hiding this comment.
| for people using assistive devices just as much as for users relying | |
| for people using assistive technology (<abbr title="assistive technology">AT</abbr>) just as much as for users relying |
| are core to the W3C's mission. | ||
|
|
||
| Standards authors though should keep in mind that Web users that rely on | ||
| assistive devices and technologies face some unique risks when using the Web. |
There was a problem hiding this comment.
| assistive devices and technologies face some unique risks when using the Web. | |
| assistive technology face some unique risks when using the Web. |
| The use of assistive technologies may cause those Web users to stand | ||
| out among other Web users, increasing the risk of unwanted reidentification | ||
| and privacy harm. Similarly, some Web site operators may try to | ||
| discriminate against Web users who rely on assistive devices. |
There was a problem hiding this comment.
| discriminate against Web users who rely on assistive devices. | |
| discriminate against Web users who rely on assistive technology. |
| and privacy harm. Similarly, some Web site operators may try to | ||
| discriminate against Web users who rely on assistive devices. | ||
|
|
||
| Feature designers and standards authors should therefor be thoughtful and |
There was a problem hiding this comment.
| Feature designers and standards authors should therefor be thoughtful and | |
| Feature designers and <abbr title=specification>spec</abbr> authors should therefore be thoughtful and |
| mouse, keyboard, or touch screen. | ||
|
|
||
| <p class=example> | ||
| The [[wai-aria-1.3]] defines additional markup site authors can use to make |
There was a problem hiding this comment.
| The [[wai-aria-1.3]] defines additional markup site authors can use to make | |
| The [[wai-aria-1.3]] defines additional markup authors can use to make |
|
|
||
| <p class=example> | ||
| The [[wai-aria-1.3]] defines additional markup site authors can use to make | ||
| their pages easier to navigate with accessibility devices. The standard |
There was a problem hiding this comment.
| their pages easier to navigate with accessibility devices. The standard | |
| their pages easier to navigate with assistive technology. The <abbr>spec</abbr> |
| <p class=example> | ||
| The [[wai-aria-1.3]] defines additional markup site authors can use to make | ||
| their pages easier to navigate with accessibility devices. The standard | ||
| includes the an [`aria-hidden`](https://w3c.github.io/aria/#aria-hidden) |
There was a problem hiding this comment.
| includes the an [`aria-hidden`](https://w3c.github.io/aria/#aria-hidden) | |
| includes the [`aria-hidden`](https://w3c.github.io/aria/#aria-hidden) |
| their pages easier to navigate with accessibility devices. The standard | ||
| includes the an [`aria-hidden`](https://w3c.github.io/aria/#aria-hidden) | ||
| attribute, that site authors can use to indicate that certain content | ||
| should be hidden from assistive devices. |
There was a problem hiding this comment.
| should be hidden from assistive devices. | |
| should be hidden from assistive technology. |
|
|
||
| A malicious site author might | ||
| abuse the `aria-hidden` attribute to learn if a user is using assistive | ||
| technology, possibly by revealing certain page content to assistive devices, |
There was a problem hiding this comment.
| technology, possibly by revealing certain page content to assistive devices, | |
| technology, possibly by revealing certain page content to assistive technology, |
| A malicious site author might | ||
| abuse the `aria-hidden` attribute to learn if a user is using assistive | ||
| technology, possibly by revealing certain page content to assistive devices, | ||
| while showing very different page content to other users. A malicious |
There was a problem hiding this comment.
Similar things are true for CSS feature detection for reduced motion or high contrast. Worth noting?
fixes ##157
First go at adding a new question to discuss risks of exposing accessibility devices, and that spec authors should minimize as much as possible this kind of information exposure
Preview | Diff