> Someone said, "well, if it is my house, I should be able to chose", the > reason that rationale doesn't work is because the GNOME Shell experience > should be designed to be inclusive, so this is really closer to an office > building or an apartment building instead of a private house.
The flaw in your logic starts beyond the front door. Clearly the login process should be accessible, and the install and setup so that a user can always get their system set up. However at the point beyond login that ceases to be true. It's necessary that the accessibility starts available somewhere (or can be enabled accessibly in the login) but beyond that point the user should be able to disable it for their account. If someone needs accessibility to use my account then probably I've been hacked by someone disabled. Granted it could be I have become disabled but that hopefully doesn't happen to people suddenely very often. Sure it'll happen slowly by age to many of us. Also if you can force accessibility on as a login choice that is still ok. It seems to me you can meet both sets of requirements quite easily, and that an always accessible login with the ability to force a session to be accessible covers the corner cases too. Alan _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list