@gezimos I talked to our team & here’s their response:
Thank you for your detailed feedback, for providing the example screenshot, and for so clearly explaining the impact of the missing Accessibility permission dialog. We sincerely apologize for the frustration and disruption this has caused.
We understand how critical this permission is for many applications, including your own launcher and tools like key mappers that add valuable functionality for users. We agree that its current state has broken the ability to use Lock Screen app you presented.
First and most importantly, this was not an intentional change. You are correct that the standard Android permission dialog has been unintentionally broken in the latest update, and for that, we are very sorry.
We have confirmed this behavior and reported it as a bug to our development team. Restoring this menu is now a priority for us.
We immediately looked for a workaround for you. Normally, it should be possible to access these settings via a hidden menu (Developer Options -> Search -> Accessibility -> Accessibility (Display)), but we have tested this and can confirm that this path is also not working correctly at the moment. We are very sorry to say that at this time, there is no immediate way to grant this permission.
While the removal of this specific dialog was a bug, it does highlight a challenge inherent to our design philosophy.
Our phone was designed with minimalism in mind, and to create a more focused experience, some standard Android options were intentionally hidden or streamlined. However, the Accessibility permission is a core function that should not have been affected.
We must also emphasize that this situation demonstrates the risks associated with sideloading applications. While we allow it, apps that require deep system permissions like Accessibility to modify core system settings can cause potential instabilities. The interaction between our streamlined OS and the complex requirements of such apps can lead to unexpected issues. Please be assured that our team is looking into this bug. We understand its importance to you and other advanced users. We are genuinely grateful for your detailed report, as it helps us identify and correct these issues much faster.