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

Mark features that might expose accessibility tools #459

Open
sandandsnow opened this issue May 16, 2024 · 3 comments
Open

Mark features that might expose accessibility tools #459

sandandsnow opened this issue May 16, 2024 · 3 comments
Labels
a11y-tracker Group bringing to attention of a11y, or tracked by the a11y Group but not needing response. Accessibility Agenda+ Privacy privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.

Comments

@sandandsnow
Copy link

The Privacy Interest Group (PING) Group Note Mitigating Browser Fingerprinting in Web Specifications Best Practice 3 states: "Where a feature does contribute to the fingerprinting surface, indicate that impact, by explaining the effect (and any known implementer mitigations) and marking the relevant section with a fingerprinting icon, as this paragraph is." and provides code that can be used.

While conducting privacy reviews, we have realised that it would also be helpful if specifications marked where a feature might expose accessibility tools in a similar way. I would like to suggest that the W3C team (or other interested persons) develop an appropriate icon and tooling to enable working groups to add this mark to specifications.

@w3c w3c deleted a comment from romankulkovsf May 17, 2024
@plehegar plehegar added Agenda+ Accessibility Privacy privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response. a11y-tracker Group bringing to attention of a11y, or tracked by the a11y Group but not needing response. labels May 17, 2024
@plehegar
Copy link
Member

@plehegar
Copy link
Member

Infra, (then bikeshed, and respec) would need updates.

@nigelmegitt
Copy link

There is no support yet in Respec or bikeshed for the fingerprinting icon, as far as I can tell - there's a hint that maybe it's something that should be in W3C stylesheets instead though. Ref w3c/tr-design#162

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. Accessibility Agenda+ Privacy privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.
Projects
None yet
Development

No branches or pull requests

3 participants