W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2013

Re: Current suggestion for subheading isn't accessible

From: Ian Yang <ian@invigoreight.com>
Date: Wed, 8 May 2013 10:30:31 +0800
Message-ID: <CABr1FseXvx809bmT4ueebKpt5G21cqOpGLSuWHoQVXOrM-zn-A@mail.gmail.com>
To: Steve Faulkner <faulkner.steve@gmail.com>
Cc: WAI Interest Group <w3c-wai-ig@w3.org>
On Wed, May 8, 2013 at 2:42 AM, Steve Faulkner <faulkner.steve@gmail.com> wrote:
> 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).

Are the 2 things what <subline> element trying to achieve?

Ian Yang
Received on Wednesday, 8 May 2013 02:30:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:44 UTC