[Bug 23888] Not allowing role=alert on UL / OL / LI / H- tags. etc. is a needless constraint

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23888

steve faulkner <faulkner.steve@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #3 from steve faulkner <faulkner.steve@gmail.com> ---
(In reply to Sailesh Panchang from comment #2)
> 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.
> So it does not make sense to insert a div tag or not use <ul role=alert>  
> 
> ===
> Sailesh

this is incorrect as per the ARIA spec[1] 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.
try this simple test case:
https://www.dropbox.com/sh/j7389jjoecghf0d/LtNgHsgOAi

using an object inspection tool suach as inspect.exe or aViewer. When
role=alert is present on an element the native role is overriden.

[1]http://www.w3.org/TR/wai-aria/host_languages#host_general_conflict
"When a WAI-ARIA role is provided, user agents MUST use the semantic of the
WAI-ARIA role for processing, not the native semantic"

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Sunday, 24 November 2013 10:25:17 UTC