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

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

Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |---
            Summary|ARIA: Clarify if features   |ARIA: Clarify that features
                   |with strong native          |with strong native
                   |semantics also may have     |semantics also may have
                   |presentation role.          |presentation role.

--- Comment #5 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> ---
(In reply to comment #4)


> Status: rejected
> Change Description: none
> 
> I do not agree that authors should apply role=presentation to focusable
> elements, as doing so leads to a poor user experience, which is why Using
> ARIA in HTML[1] provides more granular guidance as to use of
> role=presentation.
> 
> [1]
> https://dvcs.w3.org/hg/aria-unofficial/raw-file/tip/index.
> html#recommendations-table

Thanks for the link, which gives the impression that 'Using WAI-ARIA in HTML',
tries to create a table that can replace the HTML5’s current two tables about
weak and strong semantics, would have been relevant to know from the start.

However, sofar the strong table and the weak table are there. And I am going to
react to what is in HTML5 - not what is in other documents.


  First: I believe that I disagree with your opinion on role="presentatiton".

  Second: Let me remind you that when we, you and I discussed, <main> - which
you defined as having STRONG semeantics - you expressed the clear view that
HTML5 permits role="presentation" on all elements. This is also my view. And it
is in fact expressed in in the current version of HTML5.x. The only problem I
have is that this permission i expressed in a context which explains what 'no
role' means:

]] The entry "no role", when used as a strong native semantic, means that no
role other than presentation can be used.[[

Thus, to WONTFIX this bug, does not mean that you have taken away HTML5’s
permission to use role="presentation". It only means that HTML5 continues to
state, in a suboptimal way, that role="presentation" is permitted on all
features with strong semantics.

If you want to take away HTML5’s permission to apply role="presentation" on all
features with strong semantics, then you better do a proper job. If you are
*not* going to remove HTML5’s two tables over strong and wak semantics, then I
suggest going through the strong table and verify that you are OK with the
removal of the permission to apply role="presenation" on all those elements.

As to what you say about focusable, then there are focusable elements also in
the weak table.

So, in a summary, I expect you to EITHER accept my proposed, simple, minor fix.
OR to do a major job related to removing not only strong feature’s permission
to take presentation role, but also - it seems from what you say - remove from
some of the  weak element there permission to take presentation role.

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

Received on Saturday, 6 April 2013 18:33:06 UTC