com.samsung.accessibility Copy

A Samsung-signed system package labelled simply "Accessibility" on Galaxy devices. Unlike most of the Samsung components documented on this site it is something a user reaches: this site records it as user-facing on 63 of its 65 observations. It is Samsung's own accessibility component in One UI, and is not the same thing as Samsung's build of TalkBack (com.samsung.android.accessibility.talkback) or Google's Android Accessibility Suite, both documented separately here. The honest limitation: Samsung publishes no package-level documentation for it, so exactly which accessibility features live in this package rather than in Settings or in TalkBack is not sourceable, and this note does not guess at a feature list. Version note: no change of role across Android releases could be sourced, and nothing in the data here suggests the package has been superseded or moved into a module. It is observed from API 28 through API 37, and Samsung's own application lists record it on Android 9-era Galaxy S10+ firmware at version 10.0.02.24 and on Android 11-era Galaxy S20 FE firmware at version 12.0.00.59. Those version numbers show continuity of the package name across two firmware generations and nothing more: they do not establish what changed inside it between them. If its scope has shifted as One UI has added accessibility features, that could not be established from any source, so treat the package boundary as undocumented rather than stable by assumption. For Android Enterprise, EMM and kiosk use, treat accessibility as a policy question rather than a package question, and note an important limit on that policy. A device owner or profile owner can restrict which accessibility services a user may enable through DevicePolicyManager.setPermittedAccessibilityServices, available since API level 21 and exposed by the Android Management API as permittedAccessibilityServices; an empty list permits only the built-in system services. The Android documentation states that system accessibility services are always available to the user and that this method cannot disable them, so locking down third-party accessibility services will not remove an OEM's built-in accessibility surface. Whether a specific Samsung component counts as built-in on a given device is worth testing rather than assuming. Disabling this package is rated caution: it is not bloat, users with accessibility needs may depend on what it provides, and on a shared or kiosk device removing it can make the device unusable for them.

• DevicePolicyManager.setPermittedAccessibilityServices - Android API reference →
• REST Resource: enterprises.policies (permittedAccessibilityServices) - Android Management API →
• Galaxy S10+ LTE (G975F) application list - Samsung Knox CC Mode documentation →
• Galaxy S20 FE 5G (G781B) application list - Samsung Knox CC Mode documentation →
• Package provenance for com.samsung.accessibility - Android System App Database →

• Signed by the device maker's own signing key (Samsung), so it is an OEM preinstall, but 2 different certificates appear across the fleet, so OEMs ship their own builds of it. It also signs the Android framework, so it is a platform-level key on its device(s). Inferred from the certificate appearing only on Samsung devices (508 packages, 10196 observations).
• Its largest observed manifest declares 66 permissions: 6 runtime (user-granted), 20 signature or system-level, 14 install-time and 26 vendor or uncatalogued.
• APK size ranges from 13.0 MB to 20.4 MB across the reporting device profiles, so the build differs substantially between them.
• Reported as an updated system app on 2 of 22 profiles - a newer build is installed over the one in the system image there.