Skip to main content

Create Workarounds

Workarounds are user-devised or community-shared solutions that bypass inaccessible features. These may include custom scripts, browser extensions, hacks, or alternative interaction flows. Users resort to them when accessibility was not adequately addressed during development, leaving them to "patch" access themselves.

Role in the ENABLE Model​

This post-launch compensation arises when upstream care -- especially during design, development, and testing -- has failed. The burden shifts from the builder to the end-user, who is forced to adapt or be excluded.

warning

Workarounds run the risk of normalizing the idea that institutions don't have to change since we've figured out how to live around them.

Why it happens​

Workarounds happen when developers neglect inclusive practices and fail to anticipate diverse user needs. With no built-in solution, users must either quit or find their own. This is especially common when organizations prioritize speed or aesthetics over compliance and usability.

Examples​

  • Writing a Greasemonkey or Tampermonkey script to re-label buttons with accessible text
  • Injecting custom CSS to make focus outlines visible
  • Using bookmarklets to simulate keyboard shortcuts
  • End-users create a shared Google Doc or Notion page as an alternative, parallel resource because a workplace tool is inaccessible to screen readers.

Compensation sounds like​

"I wrote a script that adds keyboard focus to the menu."
"I had to override the styles just to read the text on this website."
"I created a Chrome extension that fixes this for me." "My whole team uses Slack, but I'm stuck using email because the keyboard shortcuts in Slack don't work consistently for me."

Burden sounds like​

"I had to learn JavaScript just to use my own school's site."
"Why do I have to fix this myself when they have an entire dev team?"
"I'm afraid the next update will break my workaround." "Everyone else is using it at work, but I can't. So I'm always behind or left out of team updates."

Real-world Scenario​

Jade, who has a motor disability, visits a university's registration portal that traps keyboard focus inside a calendar widget. Rather than abandon the process, she writes a quick JavaScript snippet to force focus past the widget.

Two weeks later, a site update breaks her fix. She must now maintain it across multiple devices while juggling classes and assignments. The institution never knew her name, but her burden was real.