Blake Bertuccelli-Booth

@lukecarbis, just ran into two cases for field conditions: First use case: It takes two fields to build a button in my block: a "button-text" field and a "button-url" field....

I agree, an option group would give it much closer functionality to the HTML `` element.

Either one works @eekbk - whatever you are most comfortable with

This is a great idea. I've been testing integration with https://github.com/A11yWatch and @j-mendez too, that possibly could reproduce the offending element visually

Equalify is focusing on issue management (see #198) vs scanning. This issue should therefore be dealt with by a third-party scanning service, like https://github.com/dequelabs/axe-core/. You can also check out an...

I'm re-opening this with a caveat... Since none of the automated scanning APIs offer screenshots, someone must either update a scanning API to include screenshots or write/find a new service...

I did a bit more scoping out of this. It would probably be best built as a plugin for axe core on our hosted axe distribution.

> The failed element images would certainly be a big driver to get people to subscribe to a hosted version. What was the tipping point in complexity that moved it...

@kevinandrews1 can you jump on this? You can report any issues here or as a separate issue in the repo.

Assigning @kevinandrews1 to this test. He wrote in an email to me: > Ya, I can absolutely do that!