Jean-Yves Moyen
Jean-Yves Moyen
I've: * Updated the title and description of the rule to match the new content. * Beefed up the background note with technical mumbo-jumbo, cleaned up the description of Failed...
@giacomo-petri Agreed with your comments. I try to manage both sides (frontloading test target and being correct) by negating stuff (matching the expectation). Let me know what you think of...
Dates: 6 and 7 October 2022. Location: Dublin, Ireland. Hybrid meeting (face-to-face + online). We'll try to have sessions for beginners; and sessions for tasks other than rule writing (website...
Suggestion: put all the used assets in an expandable `` between `## Test Cases` and `### Passed`. Try it out statically on a few rules, then think about automation.
Do prototype in https://github.com/w3c/wcag-act-rules Full code wrangling will need to be done in https://github.com/act-rules/act-tools
Find list of affected rules. R54.
@dd8 Tried to sum up the discussion about `auto` in an assumption + note in the definition.
Checking same/equivalent resource: only look at URLs, if different, assume the destination is different (avoid asking questions).
Visible label is part of accessible name (2ee8b8): Expectation seems to have unintended consequences
Example 2 of [Failure technique F96](https://w3c.github.io/wcag/techniques/failures/F96) seems to close the case of adding text in the middle of a label to create an accessible name (which, as far as I...
@kasperisager is this fixed by https://github.com/act-rules/act-rules.github.io/pull/1269/files#diff-e5855eef878bfc5e2ac47f8ae6846dc4R24 ?