[Bug 20696] ARIA: Clarify if features with strong native semantics also may have presentation role.

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #8 from steve faulkner <faulkner.steve@gmail.com> ---
(In reply to comment #7)
> (In reply to comment #5)
> > (In reply to comment #4)
> 
> >   First: I believe that I disagree with your opinion on role="presentatiton".
> 
> Just to clarify: This bug says "clarify if". And will accept that
> presentation role for features with strong native semanics, is made
> unpermitted, if it is done in a coherent way, including that the
> justifications for why presentation role shold no longer be permitted is
> coherent. (For instance, why <hr/> should not be permitted to have
> presenation role?.)
> 
> * Currently, I see increase of coherence if the sentence I proposed in
> comment #2 is added, as the permission to use presentation role is sensible
> to mention not only when explaining 'no role', but also when in front of the
> table with straong native features.
> 
> * By contrast, to WONTFIX this bug does per se neither increase or decrease
> coherence. But the bug should not be WONTFIXed unless the bug filer and the
> editor are satisfied with what the spec says about presentaton role of
> native semantics. The bug filer is not satisfied. And it seems from what the
> editor says he is not satisfied either. Or else, why does he want that
> readers should ignore what HTML5 currently says and instead look in the
> 'Using WAI-ARIA in HTML' document? Why else does he say that that document
> has more detail?
> 
> * At the same time, it seems like the editor thinks that WONTFIXing this bug
> has other implications than it has. E.g. as told focusable elements occurs
> both in the table with weak semantics and the table with strong semantics.
> Refusing to clarify that features with strong native semantics can take
> presenational role, is not going to impact on focusable elements with weak
> semantics.

Hi Leif have taken what you have said on board and added conformance
requirements for role=presentation

EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the Editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the Tracker Issue; or you may create a Tracker Issue
yourself, if you are able to do so. For more details, see this document:

   http://dev.w3.org/html5/decision-policy/decision-policy-v3.html

Status: partially accepted
Change Description:
https://github.com/w3c/html/commit/9656927a1c615e8c65006e62cc493f3152f587c6

rationale: using role=presentation on interactive elements will almost
certainly result in a degraded user experience. There are currently no use
cases for using role=presentation on interactive elements. It makes sense to
therefore define usage restrictions in the spec so conformance checkers can
flag errors.

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

Received on Saturday, 6 April 2013 20:20:06 UTC