Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessibility for Sight impaired : A 'fix' for fonts not scaling #7092

Open
musikBear opened this issue Feb 4, 2024 · 4 comments
Open

Accessibility for Sight impaired : A 'fix' for fonts not scaling #7092

musikBear opened this issue Feb 4, 2024 · 4 comments
Labels
enhancement response required A response from OP is required or the issue is closed automatically within 14 days.

Comments

@musikBear
Copy link

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:
image
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
image
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
image

Used in Piano-roll | Note-selector
image

Used on an instrument UI (is that possible?)
image

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).

@michaelgregorius
Copy link
Contributor

Wouldn't this rather be a job for the built-in accessibility tools of the operating system, e.g. the magnifier?

I think it might be confusing for user with better eyesight to have everything they read repeated to them via tool tips that are not even tool tips. An what about items that have usable tool tips which explain the purpose of an element? They cannot have two tool tips.

For all elements shown above except for the song editor block it should already be possible to increase their font size.

@musikBear
Copy link
Author

I think it might be confusing for user with better eyesight to have everything they read repeated to them via tool tips that are not even tool tips

That why i wrote de-selectable in Settings. Only those who has issues reading lmms' font, would invoke the feature.

a job for the built-in accessibility tools of the operating system

It is quite difficult/ annoying to use.
You can try it your self.
Just hold win-key and press + n times (win-key and esc to get out)
At least in win10 there is only 2 options:
zoomed == 200% (or more)
Not zoomed == 100%
OFCAUSE MS should have made it 100+10 pr press, but ..No 200% is minimum.... 🙄
Not lmms' fault, but Navigating inside lmms at 200% is confusing to say at least
Constant scrolling searching for opened items, but then the item searched for is behind and not in view at all -its a drag
You will find your self constantly toggle between zoomed and zoomed out.
The usage becomes cumbersome. After ½ h you quit. Its not fun.
Its just a constant reminder of your handicap ..

tool tips which explain the purpose of an element

That "What is this" feature was removed, so is the qMark in the tool-line. Its gone.

@DomClark
Copy link
Member

I think effort would be better spent fixing the underlying font issues rather than implementing a workaround. @michaelgregorius has done a lot of work towards this (as he alludes to in his comment) - see recent discussion in #2510.

Also, as I mentioned in #5240 (although there it was in reference to file dialogs), I don't think it's LMMS's responsibility to work around poorly designed OS features. If you want a better magnifier, there are numerous third-party programs specifically designed to do this. LMMS, while it should be accessible as possible to as many users as possible, is not an accessibility tool.

@michaelgregorius
Copy link
Contributor

Can this issue be closed @musikBear?

@DomClark DomClark added the response required A response from OP is required or the issue is closed automatically within 14 days. label Mar 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement response required A response from OP is required or the issue is closed automatically within 14 days.
Projects
None yet
Development

No branches or pull requests

3 participants