feat: Pull Request - Accessibility Implementaion
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- accessibility, frontend
Research direction
Start in Settings → Appearance and review the proposed implementation at the linked pull request. Confirm the Readability section, text contrast slider, bold-text toggle, border contrast ceiling, and UI Scale placement are implemented and accessible before considering the work done.
Written by the indexing model from the issue text.
Description
@tjbck
I really like this product, but I was struggling to see some of the text. While you already have some good features, I’ve added some additional ones with the help of Claude. I would love to see these implemented. I’m happy for you to just take the code, make it your own, align it with how you do things, or allow me to open a PR.
Main features implemented
- Text contrast — new slider (0–100%) in Settings → Appearance that lifts all secondary text: muted labels, hints, timestamps, icons and input placeholders. Raises light-theme muted text from 3.19:1 to 7.81:1.
- Bold text — new toggle that raises the inherited body weight 400 → 500 and steps each explicit weight utility up one notch, so headings stay distinct.
- Border contrast ceiling raised — the existing control was capped at a 16% mix, topping out at 1.28:1 (an invisible border). Ceiling raised to 100%, making 3:1 reachable and a solid rule available at maximum.
- New "Readability" section — groups the above with UI Scale (moved up from the bottom of the panel), placed directly under Theme for discoverability.
- Dominant language
- Python
- Stars
- 620
- Forks
- 85
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from open-webui/computer
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-webui/computer#293 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-webui/computer#286 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
open-webui/computer#276 · 1 comment · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-webui/computer#271 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
open-webui/computer#269 · 1 comment ·
All issues in open-webui/computer
Similar issues
-
upstream update
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conan-io/conan-center-index#31098 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
john-kurkowski/tldextract#382 ·
-
comp/tools duplicate P2 sweeper:risk-compatibility tool/mcp type/bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
NousResearch/hermes-agent#132042 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
deepset-ai/haystack#13092 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
feder-cr/invisible_playwright_mcp#1408 ·
Maintainers usually reply within 1 day