- From: Léonie Watson <tink@tink.co.uk>
- Date: Tue, 7 May 2013 18:03:43 +0100
- To: "'Ian Yang'" <ian@invigoreight.com>, "'Steve Faulkner'" <faulkner.steve@gmail.com>
- Cc: "'WAI Interest Group'" <w3c-wai-ig@w3.org>
At the risk of crossing the streams, or at least the threads, thoughts welcome on the following rough draft for a possible new element: http://www.html5accessibility.com/HTML5extensions/subline.html Simultaneous discussion taking place on the public HTML a11y list: http://tinyurl.com/d5m7l6l Léonie. -----Original Message----- From: Ian Yang [mailto:ian@invigoreight.com] Sent: 07 May 2013 17:27 To: Steve Faulkner Cc: WAI Interest Group Subject: Re: Current suggestion for subheading isn't accessible On Wed, May 8, 2013 at 12:02 AM, Steve Faulkner <faulkner.steve@gmail.com> wrote: > simply adding an element does not add accessibility semantics (see my > response to denis) How about introducing a new element and add accessibility semantics to it? People are used to using <h2>-<h6> elements for subheading/subtitle. That obviously is because we lack an element for that. > the example you provided is displayed in the browsers as > > Lorem ipsum dolor sit amet, consectetur adipiscing elit. > > the following example: > > > <p> > Lorem > ipsum > dolor > sit > <span style="display:block"> amet, > consectetur > adipiscing > elit.</span> > </p> > > > > is displayed > > > Lorem ipsum dolor sit > amet, consectetur adipiscing elit. > > > -- > > Regards > > SteveF > HTML 5.1 Yes, I know. But we cannot rely on CSS to indicate the semantics. Sincerely, Ian Yang
Received on Tuesday, 7 May 2013 17:04:14 UTC