W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2013

[Bug 23551] New: name and description section of HTML-AAPI oversimplifies step order; appear to conflict ARIA; needs rewriting

From: <bugzilla@jessica.w3.org>
Date: Thu, 17 Oct 2013 17:31:24 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-23551-2486@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23551

            Bug ID: 23551
           Summary: name and description section of HTML-AAPI
                    oversimplifies step order; appear to conflict ARIA;
                    needs rewriting
           Product: HTML WG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML a11y APIs (editor: Steve Faulkner, Cynthia
                    Shelly)
          Assignee: faulkner.steve@gmail.com
          Reporter: jcraig@apple.com
        QA Contact: sideshowbarker+html-a11y-api@gmail.com
                CC: mike@w3.org, public-html-admin@w3.org,
                    public-html-bugzilla@w3.org,
                    public-html-wg-issue-tracking@w3.org

The "name and desc" section of HTML-AAPI oversimplifies the steps to determine
alternatives when encountering specific HTML elements. For example, the AAPI
doc says that aria-label should always trump value on controls, when that's
only the case if it's not being calculated recursively for another element. The
simplified lists with instructions like "use aria-labelledby" even seem to
conflict with the ARIA algorithm in places.

http://www.w3.org/TR/2013/WD-html-aapi-20131001/#accessible-name-and-description-calculation

I would recommend rewriting the section to include the following changes:

1. Remove all the processing order lists. Defer to the ARIA spec for these.
2. Add a new section declaring the order and importance of host language
labeling mechanisms (e.g. table>caption, img[alt], and so on) for each element.
Note in the section that these will be used in rule 2A bullet 3 of the ARIA
computation.
3. Add a new section declaring whether each element is a control (e.g. input)
whose value should be used in the rule 2B of the ARIA. Remember to define how
to determine the control value per element.
4. Declare any special-case attribute usage (e.g. @placeholder) in the same
section where you declare the tooltip attribute (e.g. @title).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Thursday, 17 October 2013 17:31:26 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:45 UTC