You can use Dev Tools to see a page’s full accessibility tree:
Comment on Markdown everywhere
jadero@programming.dev 10 months agoThanks. This is the first I’ve heard of the Accessibility tree. A quick look kind of spooked me, but I’ll dig deeper.
ShortFuse@lemmy.world 10 months ago
jadero@programming.dev 10 months ago
Ok, thanks! That looks like a good start for me.
We’re getting closer to winter. I’ve got most of those preparations done. “Just” have to finish building the heater for my shop. My programming based project list is coming together: learn me some Rust, contribute some documentation to a project I’m following, look deeper into the potential of the Accessibility tree. That should keep me busy for a while!
OffByOneError@programming.dev 10 months ago
Looks kind of simple to me at first glance…
There are four properties in an accessibility tree object:
name
How can we refer to this thing? For instance, a link with the text “Read more” will have “Read more” as its name (find more on how names are computed in the Accessible Name and Description Computation spec).
description
How do we describe this thing, if we want to provide more description beyond the name? The description of a table could explain what kind of information the table contains.
role
What kind of thing is it? For example, is it a button, a nav bar, or a list of items?
state
Does it have a state? Examples include checked or unchecked checkbox states and collapsed or expanded states for the <summary> element.
developer.mozilla.org/en-US/…/Accessibility_tree </summary>
jadero@programming.dev 10 months ago
Well, it has been a decade since I’ve done anything other than dig holes (literally), drive school buses, and work in my shop. :)
Thanks for the jump start. I’ll add this to my ever growing list of tech stuff I’d like to tackle in my retirement.