You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While conducting privacy reviews, we have realized that it would also be helpful if specifications marked where a feature might expose accessibility tools. This could be useful for privacy reviews, and also for implementers who may wish to provide particular protections to users of accessibility tools.
Similar to fingerprint/tracking-vector icon, it might be useful to develop an appropriate icon and tooling to enable working groups to add this mark to specifications.
Reviews of the ARIA specs have touched on some of the different mechanisms that might currently be used to detect use of assistive technology. I'm not an expert here, but it seems like not a short list: w3c/aria#1371 (comment)
The TAG also has a summary of some of the features for detectability, and some context on the use of an icon to mark where features can enable detectability: w3ctag/design-principles#293
What is the issue with the Infra Standard?
While conducting privacy reviews, we have realized that it would also be helpful if specifications marked where a feature might expose accessibility tools. This could be useful for privacy reviews, and also for implementers who may wish to provide particular protections to users of accessibility tools.
Similar to fingerprint/tracking-vector icon, it might be useful to develop an appropriate icon and tooling to enable working groups to add this mark to specifications.
cc @sandandsnow @pes10k w3c/strategy/issues/459
The text was updated successfully, but these errors were encountered: