Adding an Accessibility Category to the Desktop Menu Specification?

[Stefan Blachmann]

I have to correct myself, sorry.

> Thus, Gnome and KDE advocates should be aware that this is an
> issue that does affect only people that do _not_ use DEs.
This is wrong.
As Samuel explained very well:

> Thinking again about it, this makes unattended launches more difficult.
> Such launches can be useful when a sighted user is working, and a
> non-sighted co-worker comes to work over something. Starting the screen
> reader from a launcher just for the time when he is there, and not
> permanently through configuration, makes complete sense.

Let me explain this problem using another disability as example. As I am deaf,
I have to use screen flashing utilities as a replacement for the beeper.
(See here for example:
http://serverfault.com/questions/19743/is-there-a-visual-bell-in-linux-that-works-in-x
)
Thus if I have to do things on another ones' computer account which
require me to
notice beeps I would be forced to change settings, and change them back to
original settings after finishing. In other words, I would be forced
to change the
system configuration _twice_.
If I could just go the menu path Utility->Accessibility->Visual_Bell
to run the utility,
then there won't be any need to tamper with the system configuration.

Thus a category "Accessibility" makes perfect sense imho.


On 5/24/16, Stefan Blachmann <sblachmann at gmail.com> wrote:
> If I understand Sam correctly, his suggestion is about adding an
> additional category Utilities→Accessibility. (see
> https://standards.freedesktop.org/menu-spec/latest/apas02.html )
>
> First, Gnome and KDE are not xdg menu specification compliant.
> Second, these DEs have a settings menu. Window managers like FVWM do
> not have such.
> Thus, Gnome and KDE advocates should be aware that this is an issue
> that does affect only people that do _not_ use DEs.
>
> Thus imho it makes perfect sense and is actually overdue to add such a
> subcategory “Accessibility” to the xdg menu spec.
>
>
> On 5/24/16, Samuel Thibault <samuel.thibault at ens-lyon.org> wrote:
>> Bastien Nocera, on Mon 23 May 2016 11:54:44 +0200, wrote:
>>> We also prefer to have any accessibility utilities integrated directly
>>> in the Settings panel, instead of launching separate applications. This
>>> is the reason why we removed the orca launcher in GNOME now.
>>
>> Thinking again about it, this makes unattended launches more difficult.
>> Such launches can be useful when a sighted user is working, and a
>> non-sighted co-worker comes to work over something. Starting the screen
>> reader from a launcher just for the time when he is there, and not
>> permanently through configuration, makes complete sense.
>>
>> Samuel
>> _______________________________________________
>> xdg mailing list
>> xdg at lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/xdg
>>
>