Re: [w3ctag/spec-reviews] Review WAPA (Accessibility) proposal (#63)

Sorry for the slow reply.

So reading the [Script Based Web Accessibility explainer](https://github.com/cyns/wapa/blob/master/ScriptAccessibility.md) (yay! an explainer!), it seems like it's a few different things all at once:

 - A last-chance way for ARIA data to be plumbed back into the document when ARIA attributes aren't already present. This feels like a great way of explaining how ARIA might work programmatically!
 - High level ("Intention") events (although it isn't clear if there are examples of this in the doc). Using IDL to describe the API instead of exmaple code to show how it works makes understanding some of this difficult.
 - Mappings (whose purpose isn't clear to me from either the prose or example code)
 - Virtualization

The last one feels like something that we might want to consider in combination with other aspects of delayed content loading. There's work on Intersection Observer to make it easier to build the sort of paginated lists that developers strive for and I'd be intrested to see if there's overlap in the assumed models between them. If not, it might box users into a single way of building pagination and that way might not be the most optimal.

Something I'd like to see here is a way to extend ARIA. Having the events is great, and it makes it much eaiser to feed ARIA data into elements, but not being able to extend the language itself makes handling composite widgets difficult.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/spec-reviews/issues/63#issuecomment-203978882