[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

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

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

--- Comment #10 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> ---
(In reply to comment #9)
> have tweaked previous commit so it makes sense
> 
> https://github.com/w3c/html/commit/1e2718be4929a8c2d1f8c48ecf91a5004d315c86

Glad you saw it yourself. Wonder why you RESOLVED this bug as FIXED *before*
you saw it ...

(In reply to comment #8)
> (In reply to comment #7)
> > (In reply to comment #5)
> > > (In reply to comment #4)

> 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 did many changes, so one could argue that you should have opened some new
bugs and linked to this bug. However, I tried to through all the changes you
made (and did not make). Here are my results.

      OK: Interacive features, weak and strong: OK with solution   
          (partly due to lack of power to disagree).

Not sure: Other strong features: why not allow presentation on
          <script>, <body> etc? On the other side, it seems like
          adding role="presentation" to <script> doesn't really
          add anything, not even if the content is made visible 
          via CSS. But feel free to reconsider.

Not sure: Regarding <meter> and some such: Why not allow
          presentation there? OTOH, I have no use case.
          But feel free to reconsider.

      OK: Regarding the definition of "no role", I OK with the
          rewording.

  Not OK: The only thing I have an explicit issue with right now, is the
<object> element and the <iframe> element. Both of those elements can logically
be images, including presentational images. As such they should be permitted to
take presentational role. Also, if one <object> is nested inside another
<object>, the inner object should probably sometimes just be presentational,
rather than introducinga new role.

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

Received on Saturday, 6 April 2013 23:04:50 UTC