NewApp Digest
search bot

screen readers

Microsoft brags Copilot key has main character energy on Windows 11, but you can soon remap it
Winsage
July 3, 2026

Microsoft brags Copilot key has main character energy on Windows 11, but you can soon remap it

Microsoft promoted the Copilot key on social media, branding it as a button with “main character energy,” despite acknowledging that it has negatively impacted productivity for some users. The company plans to allow remapping of the key in an upcoming Windows 11 update. User reactions to the promotion were largely critical, with many expressing dissatisfaction and calling for the removal of the Copilot key. Microsoft had previously admitted that the key caused disruptions in productivity and accessibility workflows. Additionally, only 3.3% of Microsoft 365 users are paying for Copilot, indicating low adoption. Microsoft has distanced its flagship products from the Copilot branding and users have reported preferring alternatives like ChatGPT and Claude over Copilot.
Microsoft admits Windows users 'experienced some challenges' with the forced CoPilot key — now it's finally doing something about it
Winsage
May 18, 2026

Microsoft admits Windows users ‘experienced some challenges’ with the forced CoPilot key — now it’s finally doing something about it

Microsoft introduced a dedicated Copilot key with its Copilot+ PCs, marking a significant change in Windows keyboard design after three decades. Users have expressed dissatisfaction with the key, particularly those who rely on the Right Ctrl or Context menu keys for shortcuts and assistive technologies. Microsoft acknowledged these challenges and announced that a future Windows 11 update will allow users to remap the Copilot key to function as either the Context menu key or Right Ctrl key. While some PC manufacturers have provided their own remapping solutions, they often require additional steps. The timeline for the update is unspecified, but major updates typically occur in October or September.
Advanced Protection Mode in Android 17 prevents apps from misusing Accessibility Services
AppWizard
March 16, 2026

Advanced Protection Mode in Android 17 prevents apps from misusing Accessibility Services

Android 17 has introduced Advanced Protection Mode (AAPM) to enhance user security by preventing non-accessibility applications from using the Accessibility API, which has been exploited by malware. AAPM allows only verified accessibility tools to utilize the API and implements stricter security settings, including blocking installations from unknown sources, limiting USB data access, and mandating Google Play Protect scans. Applications must declare themselves as accessibility tools with the attribute isAccessibilityTool="true" to use the Accessibility Services API. Additionally, Android 17 features a new contacts picker that allows applications to request access to specific contact fields instead of the entire address book, enhancing user privacy.
Android 17 Blocks Non-Accessibility Apps from Accessibility API to Prevent Malware Abuse
AppWizard
March 16, 2026

Android 17 Blocks Non-Accessibility Apps from Accessibility API to Prevent Malware Abuse

Google is piloting a security enhancement in its Android Advanced Protection Mode (AAPM) that restricts certain applications from using the accessibility services API. This update is part of Android 17 Beta 2. AAPM, introduced in Android 16, enhances device security by blocking app installations from unknown sources, restricting USB data signaling, and mandating Google Play Protect scanning. Developers can integrate with AAPM through the AdvancedProtectionManager API to adapt their apps based on the security mode's status. The new restriction prevents non-accessibility apps from accessing the accessibility services API, allowing only verified accessibility tools like screen readers and voice-based input tools. Non-accessibility apps, including antivirus software and password managers, will have their access revoked when AAPM is activated, and users cannot grant permissions to these apps unless AAPM is disabled. Additionally, Android 17 introduces a new contacts picker feature that allows developers to specify which fields to access from a user's contact list, providing more granular control over data access.
Android 17 Beta 2 starts clamping down on apps that misuse accessibility services
AppWizard
March 13, 2026

Android 17 Beta 2 starts clamping down on apps that misuse accessibility services

Google has enhanced its Advanced Protection Mode with the rollout of Android 17 Beta 2, introducing stricter security measures that restrict non-accessibility applications from accessing the AccessibilityService API. This update prevents non-accessibility apps from obtaining accessibility permissions, revoking them from apps that already have them while the mode is active. Users cannot grant these permissions when Advanced Protection Mode is enabled. For example, the dynamicSpot app cannot receive necessary accessibility permissions under this mode. In contrast, the stable Android 16 QPR3 build allows dynamicSpot to function with Advanced Protection Mode activated. Applications that identify as accessibility tools, like screen readers, remain unaffected by this restriction. This change may cause compatibility issues for users who enable Advanced Protection Mode, offering a choice between enhanced security and access to certain applications.
Android's Advanced Protection Mode now targets your favorite customization, automation apps
AppWizard
February 13, 2026

Android’s Advanced Protection Mode now targets your favorite customization, automation apps

Google is refining its Advanced Protection Mode to enhance security for high-risk individuals by implementing new restrictions on the AccessibilityService API. This API, while beneficial for users with disabilities, has been misused by various applications, leading to security vulnerabilities. Google now requires applications that assist users with disabilities to declare their status as Accessibility Tools by including the isAccessibilityTool attribute in their metadata. Recent updates in the Android Canary 2602 release allow Advanced Protection Mode to disable access to the Accessibility Service API for apps that do not qualify as Accessibility Tools, revoking any previously granted permissions. When enabled, Advanced Protection Mode restricts apps like dynamicSpot, which rely on the Accessibility Service API, while allowing classified Accessibility Tools to function normally. This change aims to improve security by treating non-Accessibility Tools as incompatible with a secure environment.
Search