Jean-Yves Moyen
Jean-Yves Moyen
> > add background note that stuff out of the accessibility tree still need to respect this but won't cause user problem > > will "wont' cause user problem" be...
A similar idea: checking that a form has a submit button (`` or ``). This would secondary fail 1.3.1 / 3.2.2 under the assumption that 3.2.2 requires a way to...
IIRC, that should be solved if we include the `html` element in the test case, then it won't be added incorrectly. We'll need to also keep the `lang` attribute and...
But I don't think that updating the Failed Example solves the problem. As long as the code (currently) in Failed Example 1 is failing the rule, the rule is problematic....
True. I'm challenging the assumption as to how often it is actually met. Additionally, our [Test case design document](https://act-rules.github.io/pages/design/test-cases/) states: > The decision of what the edge cases to test...
Seems to be related to https://github.com/act-rules/act-rules.github.io/issues/1426 🤔
"Table header cell has assigned cells" [d0f69e]: UA/AT seems to do more association than HTML specs.
> As for your above example, the row header looks like a row header but it is not exposed as a row header when using VO/Safari. I think it is...
"Table header cell has assigned cells" [d0f69e]: UA/AT seems to do more association than HTML specs.
Ah, no! the cells are numbered from the top left corner, not bottom left 🙃 That kind of makes sense because the "first row" of the table is the top...
"Table header cell has assigned cells" [d0f69e]: UA/AT seems to do more association than HTML specs.
> It's clear that the table is being built from top down but it does not necessarily mean that once the UA finished building the table the Y axis needs...
Chrome is giving this link (and image) no name, while Firefox give them a name of "W3C" 🙈 So, I guess we're both somewhat right…