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.

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

Assistive technology emphasis adjustments #498

Open
nigelmegitt opened this issue Jul 8, 2024 · 0 comments
Open

Assistive technology emphasis adjustments #498

nigelmegitt opened this issue Jul 8, 2024 · 0 comments

Comments

@nigelmegitt
Copy link

This issue is not really a specific actionable request right now, more a call for discussion in the hope of some editing improvements that would address the concerns I list below.


The emphasis in §2.9 Don't reveal that assistive technologies are being used reads to me as (I understand this is not exactly what the words say, I'm talking about the impression/steer that the words provide):

  • All assistive technology usage constitutes sensitive information
  • Therefore don't reveal any information about any such usage

I would like us to add some nuance to this that would be helpful-and-not-harmful to users of the web. The problems I see with the current wording and tone are:

  1. There is some usage of assistive technology that is so widespread that it does not constitute sensitive information, and nobody could sensibly infer from its usage any sense that the user is more vulnerable. In particular, subtitles and captions are used by significantly more people to overcome situational barriers to access (in a noisy place, sound turned down low deliberately etc) than to overcome inherent personal barriers (deafness, hearing loss etc). However they fall under the blanket term "assistive technology".
  2. Related point: assistive technology is actually not very well defined and can be situational: I don't think of my device reading messages out while I'm walking along using earbuds as "assistive technology" but it's very hard to distinguish from screen reader text to speech applications, from a definition perspective. Maybe the same constraints should apply anyway; there's a big grey area there.
  3. A strict reading of the current wording would be "it's okay to ask for user consent to share information, but don't do it otherwise", but to my eyes anyway, the permission to readers to ask for consent seems buried.

The wider issue I have here is that, while I agree that it must be safe to visit web pages, the people who make web pages typically like to be able to adjust them over time to make improvements, and it is commonplace to use data, including experimentation, to decide on which changes are improvements. By preventing access to data about usage of assistive technology, the principle constitutes a judgement that exposure of information is more important than product improvement. However this in itself is a form of discrimination against users of assistive technology, since it cuts off those users from generating data for product improvements. My fear is that the effect over time is stagnation of accessibility features and a limiting of developer effort down to "whatever ticks the legal boxes we are required to tick".

Can we find some wording changes to provide additional encouragement to seek limited consent to share information, and to continually improve web pages and web-based products in general so that they work well for everyone, while continuing to safeguard vulnerable users?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant