This appears to be a recurring issue with Accessibility Options as the root cause. It is possible that another application is using Accessibility features which are causing this issue.
You can refer to the following ML answer discussion and follow the steps provided by Jon Gotow in his answer to resolve the issue.
