Details
-
Suggestion
-
Resolution: Unresolved
-
Not Evaluated
-
None
-
None
-
None
Description
As far as my understanding of QML a11y goes, one needs to use the attached Accessible.* properties to tell the OS's a11y system about the controls and components in the current view hierarchy.
Some controls do feature default a11y properties, such as the button which propagates its text to the screen reader. However, it does not automatically react to Accessible.pressAction() to (e.g.) emit the clicked() signal.
Therefore, one would either implement a simple "custom" button which connects the two aforementioned signals or define it wherever a button is used.
It seems, that most controls and component do not define any default a11y properties.
- Is this by design?
- Would it be more comfortable for the components to define some reasonable a11y properties?
- Do these even exist in general or are the usages of any controls most likely too specific to have default properties?