HTML Standard Tracker

Filter

File a bug

SVNBugCommentTime (UTC)
2868[Authors] [Conformance Checkers] Accessibility of <canvas> is not optional. (credit: sf)2009-02-25 02:24
@@ -21778,22 +21778,22 @@ interface <dfn>CueRangeCallback</dfn> {
   graphs, game graphics, or other visual images on the fly.</p>
 
   <p>Authors should not use the <code>canvas</code> element in a
   document when a more suitable element is available. For example, it
   is inappropriate to use a <code>canvas</code> element to render a
   page heading: if the desired presentation of the heading is
   graphically intense, it should be marked up using appropriate
   elements (typically <code>h1</code>) and then styled using CSS and
   supporting technologies such as XBL.</p>
 
-  <p>When authors use the <code>canvas</code> element, they should
-  also provide content that, when presented to the user, conveys
+  <p>When authors use the <code>canvas</code> element, they must also
+  provide content that, when presented to the user, conveys
   essentially the same function or purpose as the bitmap canvas. This
   content may be placed as content of the <code>canvas</code>
   element. The contents of the <code>canvas</code> element, if any,
   are the element's <span>fallback content</span>.</p>
 
   <p>In interactive visual media, if <span
   title="concept-n-script">scripting is enabled</span> for the
   <code>canvas</code> element, the <code>canvas</code> element
   represents an embedded element with a dynamically created image.</p>
 

|