- From: Sailesh Panchang <sailesh.panchang@deque.com>
- Date: Thu, 31 Jul 2008 10:16:58 -0400
- To: <wai-xtech@w3.org>
>A conforming specification must specify that the language used to declare >the user interface of a widget be either HTML or a language that is >accessible at various levels: it should provide keyboard access to >interactive graphical elements, and provide means to access the widget's >functionality through an non-graphical UI. The declared interface may also >be accessible to screen readers, allowing relevant sections of text and >functionality to be accessed by non-visual means. Steven Faulkner comments: >Also why is that the "declared interface may also be accessible to >screen readers"? again for it to be considered accessible would it not >be that a widget MUST be accessible to AT or abkle to be made >available using the language of choice? Maybe it should say that it is accessible to AT such as screen readers. The focus of the requirement appears to be on non-visual access and that's why I suspect the emphasis is on screen readers and keyboard operability. I certainly do not mind if it were worded in more general terms to incorporate needs of all user groups. Screen reader users as a group are more disproportionately impacted by inaccessible widgets when their role, name and state are not exposed to AT. Sailesh Panchang Accessibility Services Manager (Web and Software) Deque Systems Inc. (www.deque.com) 11130 Sunrise Valley Drive, Suite #140, Reston VA 20191 Phone: 703-225-0380 (ext 105) E-mail: sailesh.panchang@deque.com -----Original Message-----
Received on Thursday, 31 July 2008 14:08:13 UTC