In short, you have understood, accessibility is extremely fragile. That's why some components are accessible while some others aren't why a given component can be accessible under one OS but not at all under another and why a component can be accessible in version N of the toolkit but not the same component in version N+1. The gap between the features offered by the native OS components and those proposed in the toolkit is often closed by emulation, and some of the emulations aren't made accessible, or simply can't be made accessible for various (more or less excusable) reasons. This isn't a peasure to give this answer but in fact, if you want to make sure your app is 100% screen reader accessible, your only way is basicly to stop using GUI toolkits and exclusively use the native components offered by the OS for which accessibility is well documented and therefore of course develop as many different apps as OS you intent to support.Īs soon as you are using a GUI toolkit, you are adding a layer, and may lose some accessibility (and often more than less) in the process. There is no uniformity at all between OS, screen readers and GUI toolkits, and probably no combination working everywhere in all cases. That's the only way to discover what works well for your particular scope, and what doesn't.

The only reasonnable answer is just trying and testing a maximum of different combinations of OS, screen readers, GUI toolkits and components, as much as you can.

Sadly, there's probably no magic solution here.

Qt toolkit accessibility screen reader