On Thu, 2015-11-12 at 16:20 +0100, Samuel Thibault wrote: > llcfree, on Thu 12 Nov 2015 13:42:22 +0100, wrote: > > To this, I would add the possibility of filtering out all > > mess that we are forced to download automatically from the web. > > Could you be more specific?
I'll try with an example. When I read a page on the web, I would like to be able to download only what I need, usually the text, and by text I mean text, in unicode. Next step would be to be able to increase the font size using the keyboard only. This, together with the possibility of choosing background and foreground colours are the minimum requirement for usability. It was so when I was able to see without problems and it is still the same now that I do have rather serious problems. > But what is "features that everybody needs"? When answering such > questions, one would typically tend to simplify the answer, in order to > manage to cover 90% people without making things too complex. And then > disabilities go completely overlooked. I think for visually impaired people (not blind) the issue is indeed only colours, contrast and fonts size. At least, this is so for me. If I could easily set background and foreground colours for ALL applications at once (this was possible when applications respected the x settings), if I could have the same shortcut for increasing and decreasing font size in console and graphic mode, and if I could use my favourite editor for all applications, my life would be greatly simplified. > In the matter at stake, the debian-installer is already using the gtk3 > toolkit, so we already have support for all the personalization that it > allows. It's now mostly a question of providing shortcuts etc. to use > make use of it. Again, I would rather have the possibility to easily define my own shortcuts rather than trying to find the ones that fit everybody's need. A minimum set of shortcuts and stability are the basic requirements for an easy to use system. By "stability", I mean the possibility of achieving the same result in the same way over time, and this way should be the one I choose. If I am used to ctrl+ to increase font size, I should be able to use that for all applications, but if somebody else uses another combination, then he or she should be able to continue to use that other combination. In any case, the real problem is not when I am producing content, but when I am consuming somebody's else content, usually but not only on the web. There, I guess the only way is insisting on web accessibility, starting with the public administrations, and focusing on the standardisation of character set, free fonts, and document formats. But this is certainly not an accessibility issue only, it is a universal requirement. Loredana
