Live data from Hacker News

Show HN: Visualization of website accessibility tree

chromewebstore.google.com

1–10 of 35 posts

Show HN: Visualization of website accessibility tree

#1
When COVID-19 started I needed something to get busy to not go crazy. I happened to work on our app WCAG compliance for a few months at the time and was frustrated by the state of of accessibility-related tools for developers.

I've spend two months delivering a tool that is easy to understand and helps catching accessibility issues on my apps. A few years later it's pretty popular despite being mostly abandoned.

I will be happy to work on this further but honestly lost my enthusiasm some time ago. I'd love to get in touch with some company in the accessibility testing space and discuss how to improve it.

Show HN: Visualization of website accessibility tree
chromewebstore.google.com

Re: Show HN: Visualization of website accessibility tree

#5
post #4

Looks neat, and way more clean than https://wave.webaim.org/

Thank you! I really think there's a lot of potential in ARIA DevTools. It's quite popular (at least for my standards) but I never had any connection with people that live and breathe web accessibility. And the devil is in the details here so to be fully fair, WAVE is most probably more accurate.

Re: Show HN: Visualization of website accessibility tree

#6
A very handy tool for spot checking, but also training. My benefit from this visualization will be demonstrating to non-technical how to people to think about accessibility (specifically screen readers). Half the challenge with WCAG is getting our stakeholders to think beyond ticking boxes for compliance.

Re: Show HN: Visualization of website accessibility tree

#10
post #8

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.

Post reply on HN