Thread Subject: Re: 3-w at-interoperability and 3-V

Note

This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.

From: Tom Brett
Date: Wed, Sep 05 2007 1:10 PM

I do not think that the screen reader or other AT can be totally eliminated
from the testing formula. While I agree that we should inspect the objects
first.either by code examination or by a functionality that would expose the
object features and that this should be the first step in testing.it is
important that AT be used in the testing process at a minimum to insure that
there are unidentified bugs with the AT or network configuration.



Tom Brett



_____

From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Hoffman,
Allen
Sent: Wednesday, September 05, 2007 2:37 PM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] 3-w at-interoperability and 3-V



Yeah, thinking Ferret here.

If they are behind the times maybe they need think catching up?



I think a semi-standardized object inspection functionality available widely
would go a long way towards eliminating the screen reader from normal
testing procedures.



So, for example, if I know the name of an element is there, its value, its
relationship, etc--and the screen reader isn't reading it right, its the
screen readers fault.





Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303





_____

From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Peter Korn
Sent: Wednesday, September 05, 2007 2:26 PM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] 3-w at-interoperability and 3-V

Hi Allen,

That is interesting. It would actually be easy to add that to existing 3-V,
where we have a new bullet, something like "be able to demonstrate that all
of this information is provided to AT through the use of an accessibility
services exploration tool". In parallel, we might note that such a tool
should be provided by a platform, as part of the platform accessibility
services.

I don't believe this is in either ISO or WCAG/ATAG has anything like this,
so doing this would mean we have a country-specific, non-harmonized
requirement.


Regards,

Peter Korn
Accessibility Architect,
Sun Microsystems, Inc.




Hi all:

I won't get my comments in today on the AT Interoperability area so will
post here:

AT is used to test because there are mostly no reliable testing tools easily
available that will show what object information is being exposed. AT
requires a great degree of knowledge to be used as a testing tool, and often
fails in that purpose. The trick is to determine if the bug is the AT, the
platform, or the application, and this can be really tricky.

So:

I suggest that we add an item in to 3-w to require that platforms provide a
method to allow the user to walk through or "inspect" objects to identify if
they meet the requirements from 3-v.

In web this is different since so many testing tools can do this, even in
automated ways.











Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303

<!--[if !supportLists]--><!--[endif]-->






_____

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University