When I designed the tool I've tried to mirror the experience of screen readers users instead of only displaying ARIA roles and properties.
For example you have to navigate the page with your keyboard only. If a dropdown isn't accessible - it's instantly clear for the user. Another example are tables. They present only one cell + their headers at the time. I think it's super close to the actual experience of screen reader users.
Comments
How does this compare to Chrome’s built-in tooling (https://developer.chrome.com/docs/devtools/accessibility/ref...)?
When I designed the tool I've tried to mirror the experience of screen readers users instead of only displaying ARIA roles and properties.
For example you have to navigate the page with your keyboard only. If a dropdown isn't accessible - it's instantly clear for the user. Another example are tables. They present only one cell + their headers at the time. I think it's super close to the actual experience of screen reader users.