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

Add a principle that sites should not be _able_ to retaliate when users say no #418

Open
jyasskin opened this issue May 8, 2024 · 2 comments
Labels
a11y-tracker Group bringing to attention of a11y, or tracked by the a11y Group but not needing response. backburner

Comments

@jyasskin
Copy link
Collaborator

jyasskin commented May 8, 2024

w3c/a11y-request#74 (comment) by @AutoSponge suggested

(user agents) (API designers) Global opt-out and lack of consent should be indistinguishable to any website from a user agent that is not capable of presenting its user an opt-in or choice to consent.

We have a statement to this effect in https://w3ctag.github.io/design-principles/#device-ids:

A web app should not be able to distinguish between the user rejecting permission to use a sensor/capability, and the sensor/capability not being present.

but we think it would also make sense to mention in https://w3ctag.github.io/privacy-principles/#non-retaliation, which is currently only addressed to sites. However, we don't think we should delay this version of the W3C Statement on this, so I've marked this backburner to address for the next version.

@pes10k mentioned that there are some cases where regulations create different requirements on websites if they get an explicit "no" instead of "I can't", so perhaps we should say that users should have the option of being explicit if they want to.

@hober
Copy link
Collaborator

hober commented Jun 5, 2024

@torgo
Copy link
Member

torgo commented Jun 5, 2024

As we discussed today, there is wording in the Design Principles doc:

"A web app should not be able to distinguish between the user rejecting permission to use a sensor/capability, and the sensor/capability not being present."

under §9.1 so maybe we don't need additional text here since already talk about non-retaliation in §2.14. However we may need a cross-link or something similar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a11y-tracker Group bringing to attention of a11y, or tracked by the a11y Group but not needing response. backburner
Projects
None yet
Development

No branches or pull requests

4 participants