Jean-Yves Moyen
Jean-Yves Moyen
We will likely need to have `Native.toBlock` send a JSON object with unparsed CSS text, so we can use `CSSDeclaration.cssText` instead, and then `Block.fromJSON` (or a new version) use `alfa-css/syntax/Declaration.parse`...
Hi @tgrushka, thanks for using Alfa. Indeed, we haven't written that documentation yet… The reason is that [the corresponding ACT rule](https://github.com/act-rules/act-rules.github.io/pull/1919) is still in early development and I expect it...
Hi @tgrushka , we've written and published the documentation for [R111](https://alfa.siteimprove.com/rules/sia-r111) (and [R113](https://alfa.siteimprove.com/rules/sia-r113), for 2.5.8). Closing this. @jrpool, FYI.
Updating Cypress to version 13 resolves the problem as they now accept more modern ES syntax. See https://github.com/Siteimprove/alfa-examples/pull/39 for a detailed example. Closing this PR now.
🤔 `` without an accessible name do not have an implicit role (per [HTML AAM](https://www.w3.org/TR/html-aam-1.0/#el-form)), which we cannot really handle in the Accessibility tree building the way we currently do...
@offsetChris When trying to run R57 on that example, I get no error 🤔 ```typescript const form = ( Search Search ); const document = h.document([form]); main(); async function main()...
CG decision (April 25th): use secondary requirement for 4.1.2 (maybe also for 1.3.1?), and point to the Understanding 4.1.2 justifying that the name should be "accurate".
@tombrunet Yes. Well, not fully, we'll still keep secondary requirements, which show the rule is related to these SC, but acknowledge that we can't guarantee a fail-on-fail relation. Secondary requirements...
Looking at Accessibility Support and Background, it seems that at some point the handling of `iframe` and focus was inconsistent. If that has changed (especially if the conflict is consistently...