W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2008

Re: Action Item for everyone: Accessibility Support

From: Tim Boland <frederick.boland@nist.gov>
Date: Tue, 09 Sep 2008 13:26:10 -0400
Message-Id: <5.1.1.5.2.20080905094453.00c44008@mail.nist.gov>
To: w3c-wai-gl@w3.org

I tried the first test (H30) with JAWS 7, and was able to locate "contact 
us" using TAB..

I tried the next test (Hz can be used to identify abbreviation) and the 
"Hz" was read like the other text,
with the letters read out individually, but there was no special indication 
that this was an abbreviation (but
maybe I wasn't using Jaws correctly - still new at it) - or maybe some work 
needed on the test (how should the
abbreviation be unambiguously indicated/identified as such apart from other 
content?)

Will continue on..

At 07:33 PM 9/4/2008 -0700, you wrote:

>At today's teleconference, we talked about the Accessibility Support
>Database tool 
><http://trace.wisc.edu/wcag_wiki/index.php?title=Accessibility_Support_Database>
>as a repository for accessibility support information, at least for
>meeting our CR Exit Criterion. It is important that we decide how we
>are going to demonstrate documenting accessibility support.
>
>Ben and Gregg have taken a crack at how to organize the information
>and how to write up test cases. We'd like you to try it out this week
>so we each have some experience. There are only about 10 test cases in
>the database right now. If you have any access to assistive
>technology, on any platform and with any browser, we would like you to
>use the tool to try the current test cases and record your results.
>Assuming you have such an environment, we don't think it will take
>long.
>
>We won't normally expect this many independent tests of specific uses.
>This exercise it to get all of us thinking about the issues so that we
>can develop a proposal we can all support.
>
>To summarize an issue that emerged from today's discussion, our exit
>criterion is not to demonstrate whether particular technologies are
>accessibility supported. Accessibility support is a complex question
>depending on which features of a technology are used and what
>environments are supported. Rather, we need to demonstrate what it
>means to document accessibility support for a technology on a
>platform, and show that this works across multiple platforms and
>technologies.
>
>Thanks, Loretta
Received on Tuesday, 9 September 2008 17:26:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:54 GMT