Simon Pieters
Simon Pieters
This is also a problem for full test coverage for https://github.com/whatwg/html/pull/10547
@annevk interesting idea. The tests would assert that the appropriate mapping is used (e.g., core-aam "aria-autocomplete=inline, list, or both" or html-aam "input (type attribute in the Color state)").
Reporting results to wpt.fyi separately for each (OS, accessibility API, browser) combination allows for side-by-side comparison. However, we wouldn't want to run all of wpt for each accessibility API. Maybe...
`interestfor` SGTM
https://www.ietf.org/rfc/rfc2119.txt defines what the keywords mean. aria-practices is about best practice. It shouldn't recommend "should not" things and not explain why it's violating it.
Scripting being disabled is a state that web content can opt into (e.g. with `sandbox`), even if users don't disable JS. https://software.hixie.ch/utilities/js/live-dom-viewer/saved/13806 Currently Chrome and Safari don't show UI and...
> I think dropping the privacy requirements just because they haven't been implemented isn't a good approach "they haven't been implemented" wasn't in my list of reasons why I think...
> The reality is that some browsers implement this without any privacy protections This is incorrect. See https://webkit.org/blog/8821/link-click-analytics-and-privacy/ > and some browsers don't implement it because of the privacy harm....
> If site owners are comfortable tracking their users' clicks, then I don't see why they would be bothered by transparency about that to the end user. Sites that use...