W3C home > Mailing lists > Public > public-pfwg-comments@w3.org > January to March 2008

ARIA best practices doc

From: Sailesh Panchang <sailesh.panchang@deque.com>
Date: Thu, 21 Feb 2008 15:56:34 -0500
To: <public-pfwg-comments@w3.org>
Message-ID: <47bde3bd.3ce9220a.2a55.5524@mx.google.com>

Refer to
Issue 1:
Under 3.1.3 it says:
The author must indicate through styling and/or markup which element in the
widget has focus. 
At end of 3.2.2 it says: ... but it must be styled using CSS to indicate the
active status. 
Comment: For both of the above, the author should indicate via markup else
it may nott be exposed to AT. Styling is optional. Right? If yes, the above
statements need to clarify this.

Issue 2:
Under 3.2 it says:
One way to provide keyboard support in (X)HTML is with form and list
elements that accept keyboard focus by default. 
Comment: You  mean links (hyperlink / anchor) and not list, right?

Issue 3:
Refer to tabindex values table: for Negative - tabindex="-1"
Please clarify that it should always be -1 and cannot be any negative

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
Received on Thursday, 21 February 2008 20:49:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:45:56 UTC