InformAction Forums

As a suggestion from the elder or those with a bad eyesight.

i support a couple of retired or handicaped people in computing. as we prepare for the update to ff 57 (and the new ns 10) we noticed that we get problems with the ui-handling by people with not so good eyesight. the solution of "temporarily" allowing things with clicking on an merely sightable small icon on a non-white background is a regression. the size of this icons is also to small. the old solution with dedicated icons on a uni-colored-background was far more better.

as a side effect, even the "only-users" around me have noticed that with 10.1.2 one can't see the full url to be handled. we suggest to change that to the former way.

greetings from the retirees

The ui is hideous even for younger people but I'm glad you mentioned its problems from an accessibility perspective. I can't tell what Giorgio is thinking because he's put screenshots on noscript.net of the new UI as if it's what he likes. I've moved away from NoScript- maybe it'll be a different beast in a month or so - but it'll have to be user-contributed.

Personally, I outlined some design changes here:
https://forums.informaction.com/viewtop ... =7&t=23656 I don't know if you could comment on that thread if you like or dislike anything. Thanks!

Well, thank you for your effort on this draft.

as i am not the youngest too, i'm used to look into manuals before i get to work with something. its that technical briefing thing that i learned ages ago as useful before using new technical equipent for example. so the lack of a quick manual of the new ui is certainly a cause for the actual user-rumble. also the issue with removing items from the whitelist, i cant figure this out alone. a small textual hint would have done it...

after some studying and re-thinking the issues the webkit-frameworkbrougt with it, i think one can generally arrange with the actual UI, but to see the complete domain is essential.

i had a quick look at your suggestions. this would have been one way to solve it in a different way. but the clickie-think on changing permissions is not the way users want to deal with, i think. they want to see the options they have in the situation they are in and they want to know what action is taken if they click on sth once. i think this is one major point.