Jean-Yves Moyen
Jean-Yves Moyen
https://github.com/act-rules/act-rules.github.io/issues/1572
Since [the ACT rule seems at risk](https://github.com/act-rules/act-rules.github.io/issues/1879#issuecomment-1184560674), we're parking this for now.
The extra difficulty with widgets is that we should test contrast in various "states" (visited links, focused widget, …) The rule initially excluded them because we didn't want to handle...
See also the discussion at #1763 and [yesterday's CG call](https://www.w3.org/2022/02/10-act-r-minutes.html#item04) where we agreed we can drop the "no widget" restriction and we'll see later if/how we do something about states…
These security restrictions are also triggered without the presence of a `:visited` selector in rules: ```html a { color: red; text-decoration: none; } a:link { color: blue; text-decoration: underline; }...
As a consequence, the second expectation of R62 can almost never fail (once this is fixed) (if the first one passes): * `hasTextDecoration`, `hasOutline` and `hasBorder` => only the color...
CG resolution: remove the visibility condition, plus add an assumption that sighted users can understad the video.
See also https://github.com/act-rules/act-rules.github.io/issues/1851
Might be handled together or not… Currently, we can't really deeplink to specific sub-sub-headers in changelog because the are numbered from top to bottom. That is, https://github.com/Siteimprove/alfa/blob/main/CHANGELOG.md#fixed-9 is not going...
Maybe also look at https://github.com/changesets/changesets