Chrome Extensions
AccessEase
A Chrome side panel that makes any web page easier to read, with bigger text, high contrast, a dyslexia-friendly font and calmer motion.

- Role
- Solo designer and developer
- Timeframe
- Sep 2026 - Nov 2026
- 95Unit test cases
- 47/47E2E checks passed
- 0Axe violations
- 0Runtime dependencies
- ~4,200 lines in 24 filesSource size
- 13Commits
Problem
Pages set text small, low in contrast and heavy on motion, and readers with low vision, dyslexia or motion sensitivity have to fight each site separately.
Approach
- A Chrome MV3 side panel applies text size, high contrast, a dyslexia-friendly font and reduced motion to the current page.
- Plain JavaScript ES modules with no runtime dependencies, built by scripts/build.mjs; settings live in chrome.storage.local.
- No backend and no telemetry, as documented in PRIVACY.md.
Result
Version 1.0.0 passes 47 of 47 end-to-end checks and axe reports 0 violations in light and dark. It installs unpacked from GitHub Releases; a Chrome Web Store listing is coming soon.
Problem
Many pages ship small text, weak contrast and constant motion. Readers who need larger text, a dyslexia-friendly font or less movement end up adjusting each site separately, or not at all. AccessEase puts those controls in one Chrome side panel.
Approach and decisions
The extension is plain JavaScript ES modules with zero runtime dependencies, built with scripts/build.mjs. Settings are stored in chrome.storage.local. There is no backend and no telemetry (see PRIVACY.md).
Two decisions are recorded in DECISIONS.md. The extension uses use_dynamic_url, so a page cannot fingerprint it by a fixed id. The inactive-control opacity was raised from 0.6 to 0.8 because 0.6 failed axe contrast.
What broke and how it was fixed
- Failed saves were lost.
createSavernow retries them by tracking dirty keys. - The panel could show a value that was never written. It now echoes from the written value and rolls back if enabling fails.
- Removing a tab could race with registration.
onRemovednow goes through the same save chain, and registration tolerates the race.
Results
13 commits between 2026-09-20 and 2026-11-05, about 4,200 source lines in 24 files, and 95 unit test cases across 7 test files. The end-to-end report (docs/e2e-report.md) records 47 of 47 checks passed on 2026-09-20, with axe reporting 0 violations in light and dark. GitHub Actions are pinned to commit SHAs, with an identity check and Dependabot.
Whatโs next and limits
There is no store listing yet. Version 1.0.0 is installed unpacked from GitHub Releases, and the Chrome Web Store listing is marked coming soon. The e2e figures are from 2026-09-20 and have not been repeated since. No usage numbers are claimed.
