universalaccessd, the daemon behind Accessibility
It is the daemon that keeps Zoom, Sticky Keys and Mouse Keys running, one run since login at about four seconds of CPU a day. Measured on a 29 day Mac.
By Chethan Kumar S N · Updated
Press Option-Command-F5, or tap the Touch ID button three times fast, and a panel slides onto the screen with a column of checkboxes: zoom, sticky keys, voice over, hover text. Tick one and the Mac changes shape. The panel is Apple’s front door to a subsystem the Settings app calls Accessibility, that older documentation called universal access, and behind both names stands one small process that has been keeping the lights on since you logged in.
Its name is universalaccessd, and it is the least frightening entry in this series to look at and one of the strangest to describe. A daemon, by the conventions this series has measured, runs as root or under a reserved underscore account, lives in /usr/libexec, and sits in the system domain. This one runs as you, lives at a /usr/sbin address, and sits in your login session. It breaks every convention and keeps the oldest name in the building.
Three sentences from 2011
The manual page is the shortest quoted in this series, and the oldest by feel:
“universalaccessd - universal access server. universalaccessd provides universal access services. There are no configuration options to universalaccessd. Users should not run universalaccessd manually.”
Dated October 6, 2011, and still shipped unchanged on macOS 27. Sixteen words of description, half of them telling you not to interfere. There is something almost poetic about a server whose entire documented configuration surface is the phrase no configuration options, in a subsystem whose entire purpose is configuration: magnification levels, key delays, pointer sizes, dozens of settings, all of them stored elsewhere and served by this process.
The name is a fossil, and so are its keys
Universal access was the name of the System Preferences pane from the early 2000s until OS X 10.8 Mountain Lion renamed it Accessibility in 2012. The pane changed its name, the private framework underneath did not, and the daemon inherited the older word along with the framework. Every Mac running today carries a process named after a setting panel that has not existed under that name for fourteen years.
The daemon’s own preference file is where the features it serves are listed by their internal names, and reading it is the fastest decode in this series:
closeViewHotkeysEnabled
closeViewZoomDisplayID
closeViewZoomFactor
liveSpeechEnabled
mouseDriver
slowKey
slowKeyDelay
stickyKey
useStickyKeysShortcutKeys
CloseView is Zoom. That is the whole secret of the strangest name on the list: the screen magnifier has been called close view inside Apple since before it had a marketing name, and the daemon still stores your zoom level in a key called closeViewZoomFactor. The rest read plainly. Live Speech, Mouse Keys, Slow Keys with its delay, Sticky Keys with its shortcut toggle. Nine keys, five features, one file, and a History section where the daemon journals its own life: 50 entries on the measured Mac, running from October 13 to November 18, each stamped with a date, a state and a reason. The reasons are LoadingPrefsA, forty one times, and SessionChangedIsDisabled, nine times. The daemon re-reads its settings every time you change one, and it notes the occasion.
One run in twenty nine days
The launch file explains the process’s whole temperament, and it is the opposite of the on-demand daemons measured elsewhere in this series. It is not a LaunchDaemon at all. It is a LaunchAgent, from /System/Library/LaunchAgents, with RunAtLoad set, which means the instant your login session exists the process exists with it. The counters agree: started once, running for the full 29 days of the measured Mac’s uptime, zero restarts, zero crashes, currently holding a pid in the low thousands that has not changed since the day you typed your password.
The launch file’s personality keys all point the same way. ProcessType App, so the scheduler treats it like an application, not a background utility. EnablePressuredExit false, so the system has promised never to reclaim it under memory pressure, the same promise the push daemon holds and almost nothing else does. A minimum runtime of 10 seconds, so even if it did die at login launchd would not mistake it for a crash loop. And two Mach doors named com.apple.universalaccessd.startup and com.apple.universalaccessd.running, the first with a HideUntilCheckIn flag, which is launchd’s way of saying the service does not truly exist until its owner has phoned home. The binary polices its own singularity with a string that reads like a cloakroom rule: someone has already checked in my running label, exiting. Two copies cannot hold the job, and the second one to arrive walks out on its own.
The session types are the quiet surprise. Most agents load for Aqua, your desktop. This one loads for Aqua and LoginWindow both, which means the same job definition is standing by at the sign in screen, where nobody has signed in yet. Apple’s user guide documents the human side of that: System Settings, Lock Screen, Accessibility Options, where VoiceOver or Zoom can be turned on for the login window, and the guide adds that the options are enabled for all users of your Mac. The plist entry and the Settings pane are the same door, one labeled for launchd and one for people. The door itself belongs to loginwindow, the process that draws the sign in screen, takes the password, and then spends the session keeping the books on every app that opens.
The hour of audio
What does a settings clerk actually do all day? The unified log answers for one honest hour, and the answer is unexpected: 120 lines, every single one of them CoreAudio. Not accessibility subsystem lines, not settings lines. Audio client chatter, a proxy connection to the audio server with a numbered context, paused and resumed over and over as sounds come and go.
The daemon holds an audio connection because the features it serves speak. Alert sounds paired with screen flashes, the beep when sticky keys pick up a modifier, the chirp when zoom engages, the voice of Live Speech reading a sentence aloud. Something in this stack has to be an audio client so the rest can make noise on cue, and the clerk got the job. It is the best one line answer to why this daemon shows any activity at all on an idle Mac: it is not working, it is listening, the way a stagehand stands still in the dark holding a flashlight.
The cost of the whole arrangement is four seconds of processor time a day and under six megabytes of memory. In the cheapest band of every daemon this series has measured.
The family in one ps
The daemon never works alone, and a single process listing shows the division of labor better than any diagram:
universalaccessd 5,952 KB 1:57 29 days
universalAccessAuthWarn 8,064 KB 1:10 28 days
AXVisualSupportAgent 31,040 KB 0:00 37 seconds
axassetsd 5,664 KB 0:15 2 days
The pattern is instant. The clerk holds settings and audio and costs almost nothing across a month. The warner, universalAccessAuthWarn, is the gatekeeper for the Accessibility API, and its binary carries the enforcement string in plain text: a pid is not allowed to access the accessibility API, with a path. That is the mechanism behind the warnings you see when an untrusted app tries to drive your Mac through accessibility hooks, the same hooks the Privacy and Security pane’s Accessibility list governs, and the list itself belongs to tccd, which has its own page.
The visual support agent is the family’s heavy lifter, thirty megabytes of memory within its first minute of life, spawned on demand the moment something needs rendering, zoom overlays, hover text panels, pointer effects. It arrives, does the drawing, and is gone; on the measured Mac it was 37 seconds old at the moment of reading, which means it had been summoned, used and was about to be dismissed again while the clerk watched. That is the real answer to any universalaccessd high memory search: the daemon you can spell is the cheap one, and the expensive relatives do not keep a fixed address.
Even axassetsd, the loader for accessibility voices and assets, is quietly doubled on machines with iPhone simulators installed, one copy per simulator runtime, the same simulator trick this series caught with the Siri daemon.
What Apple says, and does not
The macOS 27 user guide, checked at publication date, documents the features this daemon serves in detail: the shortcut panel under quickly turn accessibility features on or off, which names Option-Command-F5 and the triple Touch ID press, and the login window options page under Lock Screen settings. Across both pages, and the Accessibility chapter they sit in, the name universalaccessd appears zero times.
That is not an oversight, it is the pattern this series keeps finding. Apple documents every door a person can walk through and names none of the staff. The features get a chapter, the daemon gets a sixteen word manual page from 2011, and the gap between those two is filled by this guide.
See for yourself
Three commands and one panel, all read only. man universalaccessd for the sixteen words. defaults read com.apple.universalaccess for the feature keys and the journal, closeViewZoomFactor and all. launchctl print gui/501/com.apple.universalaccessd for the counters, swapping 501 for your own user id, where runs = 1 and the two Mach doors are listed by name. And Option-Command-F5 for the panel itself, the one place the whole subsystem answers to a keystroke. Tick zoom, watch a sibling agent spring into existence in Activity Monitor, and you have watched the clerk call for help.
If you want the measured companions: launchd explains the domains and the plist gates this agent lives by, tccd holds the permission list the warner enforces, and coreaudiod is the server on the other end of that hourly audio chatter. The bill for all of it lands in the slow Mac ledger, at four seconds a day.
Questions
What is universalaccessd on my Mac?
It is the server behind the Mac's Accessibility features, the process that keeps Zoom, Sticky Keys, Slow Keys, Mouse Keys and Live Speech alive from the moment you log in. Apple's manual page calls it the universal access server and gives it three sentences, one of which is there are no configuration options to universalaccessd. Universal access is the old name for Accessibility: the System Preferences pane carried that name until 2012, and the daemon kept it. It does not appear in the Accessibility pane or in any Apple documentation, because it is plumbing. People meet it in Activity Monitor, often with its full address, which is why the most specific search row for it asks what is usr/sbin/universalaccessd.
Why is universalaccessd using CPU or memory?
Almost nothing, measured. On the Mac measured here, a MacBook Pro on macOS 27.0.1 with 29 days of uptime, it had spent 1 minute 57 seconds of processor time in total, about four seconds a day, holding under 6 MB of memory. It had also been started exactly once, at login, and never restarted. When its log does move, the lines are almost all audio: the daemon holds a CoreAudio connection that wakes when sounds play, because the features it serves announce themselves out loud. If something in this family is genuinely heavy, it is usually a sibling: the visual support agent that does the rendering for zoom and hover text, which can be thirty megabytes within a minute of starting.
What are universalaccesscontrol and universalAccessAuthWarn?
Siblings from the same private framework, and the three run as a set. universalaccesscontrol holds the same pair of startup and running doors as universalaccessd, one layer up in the control stack. universalAccessAuthWarn is the bouncer: its binary carries the string AccessibilityAPI: pid is not allowed to access the accessibility API, and it is the process behind the warnings when an app that was never granted the Accessibility permission tries to drive your Mac through it. The permission itself, the one you toggle in Privacy and Security under Accessibility, is kept by a different daemon, tccd, which has its own page in this series. The family is bigger than the three you are likely to see: the same framework ships agents for the accessibility keyboard, live transcription, motion tracking and the heads up display.
Is universalaccessd a virus or malware?
No, and the check takes one look. The real daemon lives at exactly /usr/sbin/universalaccessd on the sealed system volume, and its code signature chains through macOS Software Signing to Apple Code Signing Certification Authority to Apple Root CA, the standard ladder for a first party process. It also runs as your own user account, not root, so it never had the privileges malware wants. There are no virus search rows attached to this name at all, which matches the shape: a quiet clerk that holds settings state. The honest test, as always, is the path column in Activity Monitor. A process calling itself universalaccessd running from a downloads folder or a browser profile would be a costume, and worth a very different conversation.
Can I quit or disable universalaccessd?
You can, and you get almost nothing for it. launchd starts it at login and would start it again, and the features it serves stop working until it returns: no zoom, no sticky keys, no mouse keys, no live speech. The manual page says it in its own flat way, users should not run universalaccessd manually, and the inverse holds too, there is no supported way to unrun it. The lever you actually have is the features. Turn them off in System Settings under Accessibility, or press Option-Command-F5 for the shortcuts panel and untick everything, and the daemon has nothing left to serve. It will keep running, at four seconds a day, which is the price of having the door open at all.
Why does universalaccessd run in the login window?
Because some people need Zoom or VoiceOver to type their password. The daemon's launch file carries two session types, Aqua, your desktop, and LoginWindow, the screen you sign in on, so the same job definition loads in both places, at the sign in screen and again in your session. Apple documents the front door in the user guide: System Settings, Lock Screen, Accessibility Options, where you can turn on options such as VoiceOver or Zoom for the login window, and the guide notes they are enabled for all users of your Mac. That sentence and the LoginWindow entry in the plist are the same fact written in two languages, one for people and one for launchd.
Ready? Buy Ribbon for $15, or read all the guides.