Re: Current suggestion for subheading isn't accessible

Hi Ian,

>How about introducing a new element and add accessibility semantics to it?

that involves 2 things
1. getting a new element added to HTML (i.e. implemented by browsers)
2. defining the accessibility semantics (which is not done in HTML, its
traditionally defined via accessibility APIs, of late some new role states
and properties have first been defined in ARIA then have made there way in
native HTML features).

>People are used to using <h2>-<h6> elements for subheading/subtitle.
>That obviously is because we lack an element for that.

if you look at the markup patterns authors use <hx>title<hx>subtitle is but
one of a range of methods people use. It is in no way the most common
method.

>Yes, I know. But we cannot rely on CSS to indicate the semantics.

the example you cited does not as duff suggests the distinction is
stylistic not semantic.


--

Regards

SteveF
HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>


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

> 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
>