Content
@
0 reply
0 recast
0 reaction
Darryl Yeo 🛠️
@darrylyeo
The WAI-ARIA accessibility tree is underrated, and it’s why web browser engines are still the best form factor for any serious multi-modal software application IMO. Also why it’s absolutely crucial to rely on semantic HTML elements and built-in browser behaviors, instead of replicating everything with `<div>`s and JavaScript and smoke and mirrors (which many site-builders and vibe-coding tools are prone to perpetuate). https://web.dev/articles/the-accessibility-tree https://developer.chrome.com/blog/full-accessibility-tree/ https://developer.mozilla.org/en-US/docs/Glossary/Accessibility_tree
2 replies
1 recast
8 reactions
Darryl Yeo 🛠️
@darrylyeo
Speaking of, these are absolutely NOT the thumbnails I was expecting for these URLs 🙈
0 reply
0 recast
1 reaction
Arti Villa
@artivilla.eth
lol can these agents just run through your codebase in the CI and update the semantic markup parsing through this accessibility DOM? I'm sure alums can figure out what's a header, what's body copy, what's an accent?
1 reply
0 recast
1 reaction