7 ms·
If you look at any platforms accessibility APIs, there’s a lot more to it than just exposing text. The simplest example: how do you indicate a graphic or piece
by realityking 8y ago
If you look at any platforms accessibility APIs, there’s a lot more to it than just exposing text.
The simplest example: how do you indicate a graphic or piece of text is a button or link? How do I set the alternate text if it’s a graphical button.
- amelius 8y agoThe render engine still has to do that. But that isn't much different from how it works now, where the website has to provide the necessary information. Besides, nobody says we can't have a protocol for some additional accessibility information.
- ljm 8y agoAnd then somebody says "how about we abstract this into some kind of markup language?" and we've come full circle.
- amelius 8y agoA common markup language would be great! As long as we use it in a way that keeps us far away from compatibility problems.
- jononor 8y agoYou only get away from compatibility problems if either: 1. No-one uses it 2. There is only 1 implementation, and it is never updated
- wvenable 8y agoBut you have to make it extendable because you can't predict every possible use-case. So some kind of Extensible Markup Language, perhaps.
- ljm 8y agoMaybe we make a sort of 'hyper' extension that comes with all kinds of baked in behaviours, so that we don't have to implement that behaviour ourselves when we deserialise it.
- wvenable 8y agoThat's a good idea. Maybe we need a series of standards but all based on some kind of Standard Generalized markup.