Esper.io notes that Google won’t entirely stop sideloaded apps from accessing accessibility services. Users can grant access by heading over to the app info screen and tapping “allow restricted settings” in the top right corner. This could be helpful for users or developers who like to install non-Play Store apps that they trust. In any case, Google wants to make it more apparent to Android 13 users that sideloading apps could be dangerous. As Android Police points out, malicious apps could circumvent the new restrictions via the aforementioned “allow restricted settings” feature. So Google could think about bringing additional changes to this feature’s behavior. Accessibility features are built-into devices to aid people with disabilities. It also allows developers to curate features for other purposes, such as call recording or alarm apps. However, the ever-evolving nature of malware and phishing attacks has meant that these tools are also used to infect devices. So it’s understandable that Google wants to discourage developers from using accessibility permissions altogether, or at least limit their use, if necessary. Google recently released the Android 13 Beta 1, while the second beta is not too far away. Users can install it on their compatible Pixel devices from the link here. We expect several more features to become public as we inch closer towards fall, which is when the stable version will likely begin rolling out.

Android 13 Limits Accessibility Services For Sideloaded Apps - 73Android 13 Limits Accessibility Services For Sideloaded Apps - 82Android 13 Limits Accessibility Services For Sideloaded Apps - 30Android 13 Limits Accessibility Services For Sideloaded Apps - 54Android 13 Limits Accessibility Services For Sideloaded Apps - 40Android 13 Limits Accessibility Services For Sideloaded Apps - 36