X
Tap here to go to the mobile version of the site.

Support Forum

Working around lack of accessibility implementations.

  • No replies
  • 1 has this problem
  • 2 views
Posted

Considering Mozilla has an article regarding this: https://developer.mozilla.org/en-US/docs/Web/Accessibility I am unsure why they themselves fail on basics like re-bind-able keys and adjusting font sizes within their mainline products.

Relying on someone else to write an extension to provide accessibility features, for a product developed by a proponent for accessibility on the web - just boggles the mind. More so that all those extensions have been broken with recent updates - leaving a gap where people like me lose the ability to use Firefox properly.

So every day it seems like I find some bananas issue that I have to fix. Today, it's the fact that someone at Mozilla thought binding / to a hotkey that steals focus from your input to drop you into some specialized search tool. I don't really care what 'quic kfind' does, I dislike right now on the principle that it shouldn't be activated by a plain key press, especially one that is used for developer apps and DIVISION. One might as well have bound 'select all' to the 'A' key - was there some reason this couldn't have been CTRL-/, much like other common hotkeys like say... 'select all'?

But yes I brought up accessibility, and I use a keyboard just fine - if not better. My issue is I have problems with vision, and as there is no option to change font scale for Firefox itself, on larger resolution monitors I struggle to read text on the UI. So I was a bit peeved that I needed to write CSS to do what other apps have an options in their settings for, or some hot (VS Code as several in fact, and they are RE-BIND-ABLE as well). Even better that it's buried in %AppData% - a folder typical users don't even know exists. Luckily I have little issue getting this working on my own... but why? I am not a 'Firefox developer' nor do I write Firefox extensions - so why do I need to muck around with it's files as if I was one, just to get it to do basic things like this? Stop relying on 3rd parties to add in features like this for you.

These problems have been solved time and again elsewhere in other programs, by other companies - usually as convenience to the average user - yet they are important for people who depend on such features to accomplish daily tasks.

So why is it that Mozilla of all companies, has failed to do what they say other developers and designers should do?

So anyways - what file do I need to edit to change hotkeys now? Evidently Quantum broke every extension that addressed this and I can't find anyone who's fixed theirs yet.

Considering Mozilla has an article regarding this: https://developer.mozilla.org/en-US/docs/Web/Accessibility I am unsure why they themselves fail on basics like re-bind-able keys and adjusting font sizes within their mainline products. Relying on someone else to write an extension to provide accessibility features, for a product developed by a proponent for accessibility on the web - just boggles the mind. More so that all those extensions have been broken with recent updates - leaving a gap where people like me lose the ability to use Firefox properly. So every day it seems like I find some bananas issue that I have to fix. Today, it's the fact that someone at Mozilla thought binding / to a hotkey that steals focus from your input to drop you into some specialized search tool. I don't really care what 'quic kfind' does, I dislike right now on the principle that it shouldn't be activated by a plain key press, especially one that is used for developer apps and DIVISION. One might as well have bound 'select all' to the 'A' key - was there some reason this couldn't have been CTRL-/, much like other common hotkeys like say... 'select all'? But yes I brought up accessibility, and I use a keyboard just fine - if not better. My issue is I have problems with vision, and as there is no option to change font scale for Firefox itself, on larger resolution monitors I struggle to read text on the UI. So I was a bit peeved that I needed to write CSS to do what other apps have an options in their settings for, or some hot (VS Code as several in fact, and they are RE-BIND-ABLE as well). Even better that it's buried in %AppData% - a folder typical users don't even know exists. Luckily I have little issue getting this working on my own... but why? I am not a 'Firefox developer' nor do I write Firefox extensions - so why do I need to muck around with it's files as if I was one, just to get it to do basic things like this? Stop relying on 3rd parties to add in features like this for you. These problems have been solved time and again elsewhere in other programs, by other companies - usually as convenience to the average user - yet they are important for people who depend on such features to accomplish daily tasks. So why is it that Mozilla of all companies, has failed to do what they say other developers and designers should do? So anyways - what file do I need to edit to change hotkeys now? Evidently Quantum broke every extension that addressed this and I can't find anyone who's fixed theirs yet.

Additional System Details

Application

  • User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0

More Information