@mcc @ChartreuseK @indrora AIUI, the accessibility API you get on a linux GUI, at-spi2, offers a tree with applications at the top level, window below that, and then a tree of containers and nodes that can have roles like "has text in it", "the text can be selected, here's the selection", you have support for formatted text as well, scrolling, images, you can simulate inputs or interact with nodes in a more idealised form ("activate" instead of "clicked with mouse button"), all that stuff.
the built-in stuff you get if you just build your program from, say, QT, can be all-right, but if you make custom widgets, and don't test how an at-spi2 client (accerciser lets you inspect and test all this) causes events to happen and just implement stuff based on for example key events, things may just not work in boring or fascinating ways
all that said, i don't think wayland puts a barrier in this very particular piece of a11y. but the vast majority of tools don't use at-spi2 to do their work i'm pretty sure