Q4 2009 Accessibility Goals
David Bolter
Marco, Alexander, and I have started banging out our platform goals for
the final quarter of this year. You can watch them take shape here:
https://wiki.mozilla.org/Accessibility/GoalStaging
They are still rough, and there is lots of time to influence things.
Your input is welcome!
(Please follow up on the list of your choosing -- I know not everyone is
on both)
cheers,
David
Willie Walker
Just a quick question - do you have Firefox regression testing set up
and running on a regular basis for the GNOME platform? If so, great!
If not, it would be great to add that.
Many thanks for sending this out,
Will
> _______________________________________________
> dev-accessibility mailing list
> dev-acce...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-accessibility
David Bolter
Yes we have automated accessibility regression tests for Linux, Windows,
and Mac. We have decent coverage for gecko's core accessibility engine,
but we don't have automated tests for our platform specific layer. Once
we have nearly full coverage for the core, will tackle the next layers.
cheers,
David
Willie Walker
be clear - you not only have the tests, but you also run them regularly
on Linux?
David Bolter
Thanks for asking! Our constantly running test machines are displayed here:
http://tinderbox.mozilla.org/Firefox/
I know it is ugly. If you look along the top column for "Linux
mozilla-central unit test" and then look down the column at the various
box-ish things... those are runs of the tests. In the box at the end you
should see "mochitest-a11y" test information. Over 10,000 tests and
counting :)
cheers,
David
Silvia Pfeiffer
audio) accessibility. There are now some patches that parse a11y tracks from
Ogg files and display them.
I will continue to experiment with those to eventually come up with the
right proposal for HTML5 standardisation of audio/video a11y. Then,
hopefully, we will be the first ones to have an actual implementation.
Don't want to add it to the wiki because it won't go into any releases at
this point, but I thought it good to share.
Cheers,
Silvia.
Gregory J. Rosmaita
one of the items that need to be considered is that HTML5 dropped
accesskey as it was defined in HTML 4.01 -- the PF (Protocols &
Formats) working group at the W3C has a long-standing list of
accesskey replacement requirements, drafted by RichS, and available
at:
http://esw.w3.org/topic/PF/XTech/HTML5/AccesskeyRequirements
perhaps there can be som synthesis of effort on this? mozilla
could be an integral aspect of fixing accesskey,
gregory.
-----------------------------------------------------------------
Egg-heads of the world unite -- you have nothing to lose but your
yolks. -- Adalai Stevenson
-----------------------------------------------------------------
Gregory J. Rosmaita: oed...@hicom.net and una...@concentric.net
Camera Obscura: http://www.hicom.net/~oedipus/
Oedipus' Online Complex: http://my.opera.com/oedipus
-----------------------------------------------------------------
---------- Original Message -----------
From: David Bolter <david....@gmail.com>
To: Mozilla Accessibility Developer <dev-
access...@lists.mozilla.org>, dev-pl...@lists.mozilla.org
Sent: Tue, 15 Sep 2009 00:03:07 -0400
Subject: Q4 2009 Accessibility Goals
> Hi all,
>
> Marco, Alexander, and I have started banging out our platform
> goals for the final quarter of this year. You can watch them
> take shape here: https://wiki.mozilla.org/Accessibility/GoalStaging
>
> They are still rough, and there is lots of time to influence
> things. Your input is welcome!
>
> (Please follow up on the list of your choosing -- I know not
> everyone is on both)
>
> cheers,
> David
> _______________________________________________
> dev-accessibility mailing list
> dev-acce...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-accessibility
------- End of Original Message -------
Charles McCathieNevile
<oed...@hicom.net> wrote:
> aloha, david!
>
> one of the items that need to be considered is that HTML5 dropped
> accesskey as it was defined in HTML 4.01 -- the PF (Protocols &
> Formats) working group at the W3C has a long-standing list of
> accesskey replacement requirements, drafted by RichS, and available
> at:
>
> http://esw.w3.org/topic/PF/XTech/HTML5/AccesskeyRequirements
>
> perhaps there can be som synthesis of effort on this? mozilla
> could be an integral aspect of fixing accesskey,
Actually, HTML5 re-added accesskey, with some improvements on the original
spec (the markup is OK, but the implementation advice was seriously
broken).
Basically, accesskey needs to be modally seperated from things like
find-as-you-type or general single-key shortcuts. Opera has had this for a
while (since 9.5? try shift-esc on a page with accesskeys), although there
are more things we want to do...
The user agent should be responsible for deciding what the activation is
for things with accesskey. In some cases a gesture with a mouse might be
more appropriate, in others a gesture on a touch screen, in others the key
that the author thought was memorable. The HTML 5 draft is meant to allow
this. It's also meant to deal with stuff like assigning a voice command,
or just changing the activation key to one the user actually has available
(or more readily available, if you know the keyboard layout).
Accesskeys also need to be discoverable, and since the user agent decides
how they work, the UA really needs to take responsibility for exposing
them, rather than having the traditional author page of accesskeys listed
with half-baked instructions for using them (which tend to go out of date
or be plain wrong).
The benefit of doing this instead of going the whole XHTML2 <access>
element hog is that it is completely compatible with existing sites that
use accesskey - which generally seem to come out at a bit over 1% of the
web at large, and the vast majority of the usage is correct by spec.
So seeing Mozilla do something that helps fix accesskey would indeed be
nice.
cheers
Chaals
--
Charles McCathieNevile Opera Software, Standards Group
je parle français -- hablo español -- jeg lærer norsk
http://my.opera.com/chaals Try Opera: http://www.opera.com
David Bolter
Thanks for the update. As you know, I'm really excited about the video
accessibility work. Does anyone else have plans for Mozilla
accessibility in the remainder of this year? Any Add-on work? (Hi
firebug people).
cheers,
David
On 15/09/09 6:53 PM, Silvia Pfeiffer wrote:
> I can add to this that I am continuing experimentation with video (and
> audio) accessibility. There are now some patches that parse a11y tracks from
> Ogg files and display them.
>
> I will continue to experiment with those to eventually come up with the
> right proposal for HTML5 standardisation of audio/video a11y. Then,
> hopefully, we will be the first ones to have an actual implementation.
>
> Don't want to add it to the wiki because it won't go into any releases at
> this point, but I thought it good to share.
>
> Cheers,
> Silvia.
>
>
> On Tue, Sep 15, 2009 at 2:03 PM, David Bolter<david....@gmail.com>wrote:
>
>