GNOME A11y: where do we need to improve? (Want input by 25-Jan)

["Ian Pascoe" <ianpascoe btinternet com>]

Will

Couple of thoughts.

Firstly, to ensure that the commonly shipped basic Gnome apps that appears
on base distros all have accessability enabled as fully as possible.  Maybe
a two stage process:

A.  Ensure that keyboard shortcuts are activated and supported - is there
such a thing as a Gnome standard for these, or an ISO type thing?

B.  Ensure that the apps utilise a widgets library that supports AT-SPI.

Secondly, and this is a bit off the wall, to provide an additional call to
AT-SPI that apps can directly access to provide additional information that
would not normally be needed by a visually unimpaired user?

For instance, a classic one that comes to mind is a graphical status bar
like the one used on Update Manager - the unimpaired user can see the
progress of the bar, but for an impaired user if the ap could send out
additional information like the progress of the bar, or changes to a status
bar ....  This could be used as an alternative to accessable widgets as
well.

Ian



-----Original Message-----
From: gnome-accessibility-list-bounces gnome org
[mailto:gnome-accessibility-list-bounces gnome org]On Behalf Of Willie
Walker
Sent: 23 January 2008 22:59
To: Francesco Fumanti
Cc: gnome-accessibility-list gnome org
Subject: Re: GNOME A11y: where do we need to improve? (Want input by
25-Jan)


Hi Francesco:

My goal for this exercise is to hear what the community thinks is the
most important stuff to get done.  As I see with the Orca project,
having end users directly involved in the decision making process makes
a world of difference in the outcome.  Without this, we can sometimes
end up in a situation where the architecture drives the user experience
and not the other way around.  We can also end up in a situation where
resources are misdirected towards a snazzy demo while sorely needed gaps
remain unfilled.

In addition, I think it's also important for the community to know how
the decisions were made, especially because their voice can influence
the decisions.  So, thanks to active people like yourself, opinions are
coming in.

Will

Francesco Fumanti wrote:
> Hello,
>
> Please don't get me wrong: In my previous post quoted below I did not
> want to say anything about the importance of the point about "having
> an onscreen keyboard that is more efficient for the users that..."
>
> I only wanted to say that it is a need that exists and that has been
> proposed in the GetInvolved page; thus it should be considered, even
> if at the end it does not belong into the top ten.
>
> By the way, what criteria do you intend to apply to establish the top
> ten list? Does it not depend on the resources available (a coder is
> not a documentation writer)? I assume there are things that need only
> little work while others need much work; the assistive technology
> needed by visually impaired users is probably not much related to
> that used by mobility impaired users,...
>
> Best regards
>
> Francesco
>
> At 8:22 PM +0100 1/23/08, Francesco Fumanti wrote:
>> Hello,
>>
>> Not knowing the state of the other ATs, I don't think that a top ten
>> list from my part would make any sense.
>>
>> However, I would like to ask you to whether you could take into
>> account the creation of an "efficient onscreen keyboard for users
>> that have good control of the movement of the pointer" (regardless of
>> them using a real mouse or some AT like a headpointer), but that are
>> not able to use a hardware keyboard.
>>
>> Regards
>>
>> Francesco
>>
>>
>> At 10:23 AM -0500 1/23/08, Willie Walker wrote:
>>> I've seen some good activity on the WIKI (thanks!).  I also need your
>>> help with identifying the top 5 to 10 things that need doing on this
>>> list.  Please be brave and speak up, especially those of you who have
>>> expressed concerns about where the community might be focusing or
>>> spending its energy.  This really is your chance to help influence where
>>> things go.
>> _______________________________________________
>> gnome-accessibility-list mailing list
>> gnome-accessibility-list gnome org
>> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
>
> _______________________________________________
> gnome-accessibility-list mailing list
> gnome-accessibility-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list

_______________________________________________
gnome-accessibility-list mailing list
gnome-accessibility-list gnome org
http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list