open-webui / open-webui/computer

feat: Pull Request - Accessibility Implementaion

Open
#265 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
569
Forks
79
PR merge metrics
No merged PRs in 30d

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.

https://github.com/aaronbolton/computer/pull/1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Domain
accessibility, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.