First we'll start by breaking the browser and everything that integrates with it.
FTFY
First we'll start by breaking the browser and everything that integrates with it.
FTFY
There are many shortcomings to HTML, yes. "Just replace it" is not the right answer. It has never been, for the same reasons that you don't "just rewrite" an old code base. There's more value than the naked eye can see.
(Oddly, the web has just the example for that - Netscape 6.0. That was a from-scratch-rewrite, and oh my, was it painful)
Kinda wish we'd stop with this whole "replace the middle of the word with a number" trend, but oh well.
a11y seems to be slightly later. My memory whispers something about mid-90s.
So, maybe not quite as much a "trend" as you assume :)
By "trend", I more mean the trend of continuing to use these sorts of weird numeric contractions of words instead of just saying "localization" or "internationalization" or "accessibility" now that we have computers that can handle big words without breaking a sweat.
I m2n, w2t is t2s, t1e o3n d2s of t2t m5es?
You can argue till you're blue in the face, it's an established shorthand by now. And shorthand has a point - I don't see you writing "random access memory" instead of RAM either.
I'll concede it's easier to write on a whiteboard, but for other situations, it seems rather silly (and very different from the concept of an acronym or initialism).
Poorly.
That strongly suggests that any Qt accessibility stuff will be thrown out the window.
Not unlike HTML DOM, QML builds a tree of objects from the declarative representation (.qml source code) with discoverable properties. It would be straightforward for accessibility tools to traverse this tree and extract information from it.
As user jcelerier already mentioned, QML has accesssibility features built-in. It provides a tool to annotate any part of the UI with accessibility metadata. HTML has nowhere near such a consistent approach to accessibility.