Re: Current suggestion for subheading isn't accessible

simply adding an element does not add accessibility semantics (see my
response to denis)


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 <http://www.w3.org/html/wg/drafts/html/master/>


On 7 May 2013 16:47, Ian Yang <ian@invigoreight.com> wrote:

> On Tue, May 7, 2013 at 11:35 PM, Steve Faulkner
> <faulkner.steve@gmail.com> wrote:
> > Hi Ian,
> >
> >> There still need to be an HTML element for subheading/subtitle,
> >> otherwise screen readers will never have a chance to know the
> >> subheading/subtitle.
> >
> >
> > since there is no defined subtitle role in accessibility APIs i suggest a
> > first step would be to see if there is interest in adding one.
> >
> > probably a good place to start would be in ARIA you can suggest it on the
> > wai-xtech mailing list
> >
>
> Imho, introduce a new element is better than introduce a new ARIA role
> because a new element covers for both HTML semantics and
> Accessibility.
>
>
> >>>  in the second example the album name is also on a new line (which is
> >>>  conveyed to screen reader users)
> >
> >
> >> Could you please explain that? Do you mean screen reader users get
> >> notified of line breaks in HTML code?
> >
> >
> > screen readers discern line breaks in text on the page, also some
> browsers
> > (e.g. firefox) indicate the semantics of an element with display:block
> style
> > as IA2 role=paragraph.
> >
> > --
> >
> > Regards
> >
> > SteveF
> > HTML 5.1
>
> What if a paragraph is markup by a newbie developer as the following?
> Will screen readers announce all line breaks?
>
> <p>
> Lorem
> ipsum
> dolor
> sit
> amet,
> consectetur
> adipiscing
> elit.
> </p>
>
>
> Sincerely,
> Ian Yang
>