W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2015

Re: Minimum viable custom elements

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Wed, 4 Feb 2015 19:29:12 +0000
Message-ID: <CA+ri+VkZfJbTHKBff4TOcDMTb5wiZxM-2ecuXmyJOPhkjsihAQ@mail.gmail.com>
To: Alice Boxhall <aboxhall@google.com>
Cc: Brian Kardell <bkardell@gmail.com>, Ryosuke Niwa <rniwa@apple.com>, Chris Bateman <chrisb808@gmail.com>, Anne van Kesteren <annevk@annevk.nl>, WebApps WG <public-webapps@w3.org>
On 4 February 2015 at 19:05, Alice Boxhall <aboxhall@google.com> wrote:

> So then how do we treat it as "fallback content" i.e. un-rendered, while
> allowing it to be accessible to to the AT layer?


I suggest as in the working canvas example i provided, it not only be
exposed AT but also to keyboard interaction, and that the content inside
can be targeted for relationships such as

<label>
<x-checkbox>
    <input type="checkbox" checked="true">
</x-checkbox>
sign up
</label>

--

Regards

SteveF
HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>
Received on Wednesday, 4 February 2015 19:30:19 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:25 UTC