W3C home > Mailing lists > Public > public-html@w3.org > March 2012

[Bug 16503] New: [AAPI]:

From: <bugzilla@jessica.w3.org>
Date: Sat, 24 Mar 2012 03:02:04 +0000
To: public-html@w3.org
Message-ID: <bug-16503-2495@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16503

           Summary: [AAPI]:
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML a11y APIs (editor: Steve Faulkner, Cynthia
                    Shelly)
        AssignedTo: faulkner.steve@gmail.com
        ReportedBy: jason@accesscult.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


"summary"

Need to provide advice on what should happen with interactive content, e.g.,
links, nested in <summary> with role="button". Should nested links, for
example, be passed to the a11y API as accessible objects (as IE9 and FF11 do),
or should they be flattened to text and unavailable in the tree (as Safari
does)?

Nested interactive content is permitted as per the spec for <summary>, but is
contrary to what is expected in a typical <button>. What effect should
role="button" have in this case?

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Saturday, 24 March 2012 04:16:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:47 GMT