Why?

Cause

• As a developer using QtQuickView to embed QtQuick content into my Android app, I would expect the accessibility support from Qt to work.
• Some tools in the market use Android accessibility features
• Some apps use Accessibility like password apps

Customer

• See separate listing
• Qt Quick for Android users that want to use not just 3D from QtQuick

Cruft

• We have workaround to disable accessibility QTBUG-102168 If that is enough, why we would need this?
• Perhaps out customers focus it not in this level yet, first 3D

What?

Definition

• Accessibility (a.k.a A11y) features makes Android devices usable for people with various disabilities
  • Screen readers, Display adjustments, Interaction controls like voice and switch accesses, hearing assistance like live caption or sound assistance and accessibility suite 
  • Example: When using a screen reader, the accessibility descriptions should be read out loud as in a standard Qt for Android app.

Demarcation

• Accessibility support from Qt for any other platform is not in scope.
• Accessibility support from Qt for Android is not in scope of this. However if this depends on it, it will need to be listed to dependencies. 

Dependencies

• 1st make it working on childd windows (QTBUG-120685), since that's what embedded QtViews use.