- From: Steve Faulkner <faulkner.steve@gmail.com>
- Date: Sun, 24 Nov 2013 10:11:37 +0000
- To: Sailesh Panchang <sailesh.panchang@deque.com>
- Cc: WAI Interest Group <w3c-wai-ig@w3.org>
- Message-ID: <CA+ri+VngYYqHMwW2Es9qTxncg8eHddbBz9fdNKS_GRQ-6wGBxw@mail.gmail.com>
Hi sailesh, -- Regards SteveF HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/> On 24 November 2013 00:25, Sailesh Panchang <sailesh.panchang@deque.com>wrote: > Hello Steve, > Thanks for responding. > I did file 23888 and 23889 I closed 23889 as invalid as it should be filed against ARIA 1.1 > and added the following to 23888: > Well I could make the validator error go away if I put the UL tag in a > div and placed role=alert on the DIV tag innstead of the UL tag. > I get the same functionality but that is more code that I have to > insert needlessly. The role=alert does not change the semantics of the > UL tag like role=navigation or role=menubar etc. > this is incorrect as per the ARIA spec and as per what is exposed in accessibility APIs, depending on AT and browser used headings/lists roles are ignored as the heading/list roles are overridden by role=alert > So it does not make sense to insert a div tag or not use <ul role=alert> > testing shows otherwise. > > === > Thanks, > Sailesh > > > On 11/21/13, Steve Faulkner <faulkner.steve@gmail.com> wrote: > > Hi Sailesh, > > the reason it is flagged as an issue now rather than previously is that > the > > implementation of the conformance requirements on use of ARIA in HTML5 is > > an ongoing process. The restriction on use of role=alert on ul has been > in > > the spec for years. > > > > Note also that the http://validator.nu has different rules in some > cases as > > its rule set is based on the whatwg spec not the W3C HTML spec. > > > > The conformance requirements (which ARIA attributes can be used on which > > elements) are specified in the following tables: > > > http://www.w3.org/html/wg/drafts/html/master/dom.html#sec-strong-native-semantics > > > http://www.w3.org/html/wg/drafts/html/master/dom.html#sec-implicit-aria-semantics > > > > If you consider that any requirements are incorrect, please file a bug > > (provide a rationale for a change) against the HTML spec ( > > > https://www.w3.org/Bugs/Public/enter_bug.cgi?comment=%22No%20role%2C%20with%20the%20aria-hidden%20state%20set%20to%20%22true%22%22&component=HTML5%20spec&product=HTML%20WG > ) > > > > > > > > -- > > > > Regards > > > > SteveF > > HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/> > > > > > > On 20 November 2013 21:48, Sailesh Panchang > > <sailesh.panchang@deque.com>wrote: > > > >> Bug 23877 – Checker fails use of ARIA role=alert on UL element > >> submitted on Nov 20, 2013 > >> I used http://validator.w3.org/check > >> and also http://validator.nu > >> The validator fails use of role=alert on a UL tag > >> Row 53 Column 44: Bad value alert for attribute role on element ul.<ul > >> id="errlist" role="alert" tabindex="-1"> > >> ✉ > >> Test the page at > >> http://mars.dequecloud.com/demo/form-alert2.htm > >> > >> I did not see this error a few months ago on the same page and code. > >> So I am surprised why it is being flagged as an issue now. role=alert > >> is a valid role as per ARIA specs. > >> http://www.w3.org/TR/wai-aria/roles#alert > >> Thanks and regards, > >> Sailesh Panchang > >> > >> > > >
Received on Sunday, 24 November 2013 10:12:45 UTC