W3C home > Mailing lists > Public > public-html-a11y@w3.org > September 2010

[Bug 9214] Allow role="presentation" img as conformance Criteria

From: <bugzilla@jessica.w3.org>
Date: Tue, 07 Sep 2010 15:10:17 +0000
To: public-html-a11y@w3.org
Message-Id: <E1OszoP-0007dd-2V@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9214





--- Comment #24 from Laura Carlson <laura.lee.carlson@gmail.com>  2010-09-07 15:10:15 ---
(In reply to comment #22)
> (In reply to comment #21)
> > (In reply to comment #20)
> > > Bug triage sub-team thinks this is fixed. Assigning to Steve to verify fix; if
> > > so, please change status to "verified", otherwise ping bug triage sub-team.
> 
> > This bug isn't fixed as @role="presentation" isn't a part conformance criteria
> > in HTML5. WAI CG recommended that it should be in their "Consensus Resolutions
> > on Text alternatives in HTML 5" document.
> > http://www.w3.org/2009/06/Text-Alternatives-in-HTML5
> 
> Laura, 
> 
> so far you have not offered any direct response to Ian's resolution in comment
> #16, other adding tracker request etc.  
> 
> Because of this, I find it hard to know whether I agree or disagree that this
> bug is solved.  I think it could be helpful if you pinpointed the exact things
> you disagree with in his resolution.
> 
> If you could also show a code example, and explain the problems with the way
> HTML5 currently requires  conformance checkers to check that piece of code,
> then that would be helpful too.
> 
> Thanks.
> 
> 
> PS: This is how I understand the conflict betweent the Consensus Document and
> HTML5:
> 
> Per the Consensus Document, then the very presence of role="presentation" -
> irrespective of empty @alt, non-empty @alt or no alt attribute at all,  would
> make the <img> valid. 
> 
> Whereas, in contrast, HTML5, section 4.8.1.1.14 (Guidance for conformance
> checkers) fails to list presence of role="presentation" as a condition when it
> would be permitted to not add the @alt attribute.  (Quote: "A conformance
> checker must report the lack of an alt attribute as an error unless one of the
> conditions listed below applies:" )
> 
> Thus, i suppose you want @role="presentation" to  make <img> elements which
> lack  any ue of @alt, as valid.

Yes, per WAI CG's Doc:

<quote>

NOTE: These recommendations assume that ARIA features referenced in this
document are included in HTML 5.

   1. <img> is only valid when at least one of the following is true:
          * @alt is present (empty or non-empty) OR
          * @aria-labelledby is present (non-empty only) OR
          * the <img> is located within a <figure> that has a non-empty
<legend> OR
          * @role="presentation"
      NOTE: The intent here is twofold.
         1. to allow different methods to be used for providing short text
alternatives (e.g. ALT or LABELLEDBY or LEGEND)
         2. to note that short text alternatives are not needed for content
that is "presentational" as defined by ARIA
   2. That
          * the proper use of @role="presentation" be taken from ARIA 1.0
          * and that an <img> without a @role attribute is assumed to be the
equivalent of <IMG @role="img"> (and would follow the rules in #1 above)

      NOTE: 'Presentation' should not be defined to be broader than what is
defined by ARIA
   3. For cases in which it is appropriate for user agents to ignore the
presence of an image (e.g. when the image is used for decoration, for
formatting, or when the image is invisible), one or both of the following may
be used:
          * @role="presentation"
          * @alt="" (also see (4))

      INTENT: That it is VALID to use either ROLE and/or ALT="" to mark
"presentational" content.
   4. alt="" WITHOUT an accompanying role="presentation" triggers a
non-critical validator warning recommending use of role="presentation" (but
@alt="" remains technically valid)

      INTENT: To encourage the use of role=presentation - by encouraging (but
not requiring) its use even when alt="" is used.
   5. We suggest new mechanisms for short text alternatives (e.g.
aria-labelledby, <legend>) should be capable of handling structured content.
Our primary concern is that short text alternatives be able to support inline
text structure, such as abbreviations, language changes, emphasis, etc.

      RATIONALE: It would be helpful for the short alternative text mechanism
to support structured text.

</quote>

http://www.w3.org/2009/06/Text-Alternatives-in-HTML5

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 7 September 2010 15:10:18 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:13 UTC