Hi Wilco, BAD TF,
For your information, I am currently working on an expand/collapse
functionality similar to the one we've implemented for BAD [1].
Some of the comments we received relate to use of links rather than
buttons for the functionality. In particular, some argue that the
expand/collapse all should become a toggle rather than be a link.
Below you can find a test page in which I'm looking into using the
button elements with WAI-ARIA instead [2]. Any comments are welcome.
[1] <http://www.w3.org/WAI/EO/Drafts/PWD-Use-Web/2009/>
[2] <http://www.w3.org/WAI/EO/Drafts/PWD-Use-Web/2009/test.html>
Best,
Shadi
-------- Original Message --------
Subject: a little bit of script testing?
Date: Sun, 05 Sep 2010 15:41:54 +0200
From: Shadi Abou-Zahra <shadi@w3.org>
Hi folks,
Ref: <http://www.w3.org/WAI/EO/Drafts/PWD-Use-Web/2009/test.html>
Thank you for your feedback on the expand/collapse script so far. I'm
looking at some ways to improve its accessibility and would appreciate
if any of you can spare some additional time to do more testing.
The main changes are:
- use of the button element rather than links, for all functions
- use of WAI-ARIA roles and states to communicate what is happening
- more descriptive button names to better communicate their purpose
Some known issues are:
- the expand/collapse button still appears at the beginning of the
heading text rather than at the end. It is not a trivial task to get
this to happen across some particular browsers. Any suggestions or
tipps/tricks are highly welcome.
- the visual styling will be looked at in more detail, especially to
make it more consistent across different browsers (buttons are quite
tricky in some browsers). Liam was suggesting the "silk" icons from
Famfamfam <http://www.famfamfam.com/>.
What I'm particularly looking for is:
- how well does this functionality work with different browsers and
assistive technology (note that screen readers read aloud the button
names, types, and states differently, sometimes even when you use the
same screen reader but with different browsers).
- how understandable and usable is the functionality, especially if
you imagine that you are working with it for the first time.
Any other comments or suggestions are welcome too.
Many thanks,
Shadi
--
Shadi Abou-Zahra - http://www.w3.org/People/shadi/ |
WAI International Program Office Activity Lead |
W3C Evaluation & Repair Tools Working Group Chair |