Accessibility for Sight impaired : A 'fix' for fonts not scaling
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 1.3k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Description
Enhancement Summary
Suggest using mouse-rollover to create a large hint in a specified position on screen.
Justification
Accessibility for Sight impaired. The biggest issue for all Sight impaired users are the fonts used in menus and bars.
LMMS fonts are not readable.
Explanation
By chance i got this idea that could be a 'fix' for qT fonts not being scaleable on our UI.
It is already partly implemented.
If we have a named block in songeditor and let mouse roll-over that block, this happens:
The blocks name is shown in a mouse-hint next to the block.
The blocks name is not readable
The Hint is readable!
My thought was that is we made this roll-over/ rest feature globally for all text-objects
like here for the Samples in folder Flack
Then it would no be an issue that lmms own fonts are absurdly small and absolutely impossible to read.
The sight-impaired would instead read the hint next to the un-readable item
Some examples:
Mockup
Used in Menu| File
Used in Piano-roll | Note-selector
Used on an instrument UI (is that possible?)
As a sight-impaired user, i would then only look at the hints, not the actual lmms-text. I would only drag the mouse down over the tiny text, but read what was inside the hints, then click in the menu, without actually reading anything in it.
The feature could be de-selected in Settings for those that did not want those hints, but even users with decent eyes says they have to lean over to read lmms' fonts, so perhaps this hint-feature would have more general interest.
The size of the actual hints would best be a CSS thing, that would make the feature ..scaleable (pi).
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by tracing how hover hints are currently shown for named Song Editor blocks, then review the menu, Piano-roll note selector, sample browser and instrument UI examples. Determine whether a global hover-hint setting can cover these text objects and how it would interact with Settings. Done means the proposed accessibility behavior, scope, and opt-out are implemented consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- accessibility, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100