alekssrkv
Re:Web accessibility for 2019
on Tuesday October 23, 2018 @02:55AM (#18281278)
Having these concepts exposed to the web doesn't repeal the necessary of standardization, i.e. both web developers and AT vendors has to stay in agreement on content semantics they operate with, but it will make the agreement process simpler than it's now, because it doesn't require implementation from browsers for each and every new feature. Also it will enable experimenting on the web, where web developers and AT vendors can try new things before stuffing them into standards, which should boost the accessible web.
Re:Web accessibility for 2019
on Monday October 22, 2018 @04:00AM (#18272924)
Those five concepts are not random, they go from the assistive technologies world: most if not all desktop APIs use these terms.
Agreed, the state concept (or even role concept) can be technically mapped into attributes, but I keep using them just to stick closer to existing terminology.
When it comes to ARIA, all browsers map ARIA taxonomies into desktop APIs, and thus I think it's fair to say ARIA is mapped into those concepts as well.
But this post wasn't an attempt to define accessibility concepts as such. It was rather about answering a question, whether a large set of accessibility problems can be solved, if the web came with a technology that provides greater access to express semantics to web devs.
Re:Web accessibility for 2019
on Monday October 22, 2018 @12:10AM (#18272114)
Agreed, however I bet making a website JSless may be a challenge in some cases.
So I'd be cool to have something more powerful and flexible than ARIA is to not limit web devs in choosing the techs.
Re:Web accessibility for 2019
on Sunday October 21, 2018 @11:56PM (#18272072)
I would love to have some examples. I believe there are cases which don't make a perfect fit for metadata mappings, but keeping it on radar could help to evolve techs right way and address such cases.