And then we'll reimplement it. Poorly.

marcosdumay · on July 31, 2017

Hum... Nope, QML has a better DOM (for applications, not text) from the start.

eropple · on July 31, 2017

A DOM that doesn't work with a screen reader is definitionally not a better one.

jcelerier · on July 31, 2017

Thankfully, it does: http://doc.qt.io/qt-5/qml-qtquick-accessible.html

eropple · on July 31, 2017

> instead of manipulating the DOM, we can write our own presentation code using the canvas element

That strongly suggests that any Qt accessibility stuff will be thrown out the window.

martin_ky · on Aug 1, 2017

I (author) meant that as an example of how you could achieve portability and consistency with HTML5. The canvas approach is NOT what QML does, however.

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.

eropple · on Aug 1, 2017

That's great, but the problem is that the web is and will remain HTML, and as such you kinda have to play ball with exactly what it gives you. Being trivial doesn't stop you from being nonstandard and I really dunno--unless you're going to get every browser under the sun to play with something that isn't any sort of standard, it's spitting into the wind.

marcosdumay · on Aug 1, 2017

Yes, it throws the HTML DOM out of the window. But if it's built as a native standard, nobody will have to reinvent a DOM, because QML has one, and it's better than HTML's one for applications.