From 50a2128e1bfcfd57a6fac08aaa9e11e0e4841b80 Mon Sep 17 00:00:00 2001 From: Jeffrey Yasskin Date: Thu, 5 Sep 2024 23:08:08 +0000 Subject: [PATCH] Copy-edit the AT section. --- index.bs | 16 +++++++++------- questionnaire.markdown | 2 +- 2 files changed, 10 insertions(+), 8 deletions(-) diff --git a/index.bs b/index.bs index 82d1cc8..186f70d 100644 --- a/index.bs +++ b/index.bs @@ -875,14 +875,14 @@ users at risk include: and whether (and which) actors on a page are able to access that information.

- Does your feature allow sites to learn about the users use of assistive technology? + Does your feature allow sites to learn about the user's use of assistive technology?

The Web is designed to work for everyone, and Web standards should be designed for people using assistive technology (AT) just as much as for users relying on mice, keyboards, and touch screens. Accessibility and universal access are core to the W3C's mission. -Specification authors though should keep in mind that Web users that rely on +Specification authors should keep in mind that Web users who rely on 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 @@ -891,18 +891,18 @@ discriminate against Web users who rely on assistive technology. Feature designers and spec authors should therefore be thoughtful and careful to limit if, and what, websites can learn about the use of assistive -technologies. Spec authors must minimize both what information about -assistive technology use their features reveal, both explicitly -and implicitly. Examples of explicit information about assistive technology +technologies. Spec authors must minimize the explicit and implicit information that +their features reveal about assistive technology use. +Examples of explicit information about assistive technology include device identifiers or model names. Examples of implicit information about the use of assistive technology might include user interaction patterns that are unlikely to be generated by a mouse, keyboard, or touch screen.

-The [[wai-aria-1.3]] defines additional markup authors can use to make +[[wai-aria-1.3]] defines additional markup authors can use to make their pages easier to navigate with assistive technology. The spec -includes the [`aria-hidden`](https://w3c.github.io/aria/#aria-hidden) +includes the <{html-global/aria-hidden}> attribute, that site authors can use to indicate that certain content should be hidden from assistive technology. @@ -1390,6 +1390,8 @@ urlPrefix: https://privacycg.github.io/storage-access/; spec: STORAGE-ACCESS text: third-party context; url: #third-party-context; type: dfn urlPrefix: https://html.spec.whatwg.org/multipage/; spec: HTML text: PDF viewer plugin objects; url: system-state.html#pdf-viewer-plugin-objects; type: dfn +urlPrefix: https://www.w3.org/TR/wai-aria-1.3/; spec: wai-aria-1.3 + text: aria-hidden; for: html-global; url: #aria-hidden; type: element-attr 

diff --git a/questionnaire.markdown b/questionnaire.markdown
index 9dfad6b..927a5e3 100644
--- a/questionnaire.markdown
+++ b/questionnaire.markdown
@@ -42,5 +42,5 @@ For your convenience, a copy of the questionnaire's questions is included here i
      (instead of getting destroyed) after navigation, and potentially gets reused
      on future navigations back to the document?
 19.  What happens when a document that uses your feature gets disconnected?
-20.  Does your feature allow sites to learn about the users use of assistive technology?
+20.  Does your feature allow sites to learn about the user's use of assistive technology?
 21.  What should this questionnaire have asked?