Compatibility Definition

Allow one and only one managed profile to be created [ Resources, 50]
Use an icon badge (similar to the AOSP upstream work badge) to represent the managed
applications and widgets and other badged UI elements like Recents & Notifications
Display a notification icon (similar to the AOSP upstream work badge) to indicate when
user is within a managed profile application
Display a toast indicating that the user is in the managed profile if and when the device
wakes up (ACTION_USER_PRESENT) and the foreground application is within the
managed profile
Where a managed profile exists, show a visual affordance in the Intent 'Chooser' to allow
the user to forward the intent from the managed profile to the primary user or vice versa, if
enabled by the Device Policy Controller
Where a managed profile exists, expose the following user affordances for both the
primary user and the managed profile:
Separate accounting for battery, location, mobile data and storage usage for
the primary user and managed profile.
Independent management of VPN Applications installed within the primary user
or managed profile.
Independent management of applications installed within the primary user user
or managed profile.
Independent management of accounts within the primary user or managed
profile.
Ensure the default dialer can look up caller information from the managed profile (if one
exists) alongside those from the primary profile, if the Device Policy Controller permits it.
MUST ensure that it satisfies all the security requirements applicable for a device with
multiple users enabled (see section 9.5), even though the managed profile is not counted
as another user in addition to the primary user.
3.10. Accessibility
Android provides an accessibility layer that helps users with disabilities to navigate their devices more
easily. In addition, Android provides platform APIs that enable accessibility service implementations to
receive callbacks for user and system events and generate alternate feedback mechanisms, such as
text-to-speech, haptic feedback, and trackball/d-pad navigation [Resources, 51].
Device implementations include the following requirements:
Android Automotive implementations SHOULD provide an implementation of the Android
accessibility framework consistent with the default Android implementation.
Device implementations (Android Automotive excluded) MUST provide an implementation
of the Android accessibility framework consistent with the default Android implementation.
Device implementations (Android Automotive excluded) MUST support third-party
accessibility service implementations through the android.accessibilityservice APIs
[Resources, 52]
Device implementations (Android Automotive excluded) MUST generate
AccessibilityEvents and deliver these events to all registered AccessibilityService
implementations in a manner consistent with the default Android implementation
Device implementations (Android Automotive and Android Watch devices with no audio
output excluded), MUST provide a user-accessible mechanism to enable and disable
accessibility services, and MUST display this interface in response to the
android.provider.Settings.ACTION_ACCESSIBILITY_SETTINGS intent.
Additionally, device implementations SHOULD provide an implementation of an accessibility service
on the device, and SHOULD provide a mechanism for users to enable the accessibility service during
Page 22 of 74