> From: Anne van Kesteren [mailto:ann...@annevk.nl]
> Sent: 06 May 2015 15:25
> Open issues are kept track of here:
>   https://wiki.whatwg.org/wiki/Custom_Elements
> I think we reached rough consensus at the Extensible Web Summit that is=""
> does not do much, even for accessibility. Accessibility is something we need
> to tackle low-level by figuring out how builtin elements work:
>   https://github.com/domenic/html-as-custom-elements

If we use ARIA to feed accessibility information into the examples in this 
project, we should end up with some useful blueprints.
> And we need to tackle it high-level by making it easier to style builtin
> elements:
>   http://dev.w3.org/csswg/css-forms/
> And if the parser functionality provided by is="" is of great value, we should
> consider parsing elements with a hyphen in them differently.
> Similar to how <script> and <template> are allowed pretty much
> everywhere.
> Therefore, I propose that we move subclassing of builtin elements to v2,
> remove is="" from the specification, and potentially open an issue on HTML
> parser changes.

My understanding is that sub-classing would give us the accessibility 
inheritance we were hoping is= would provide. Apologies if I've missed it 
somewhere obvious, but is there any information/detail about the proposed 
sub-classing feature available anywhere?


Léonie Watson - Senior accessibility engineer, TPG
@LeonieWatson @PacielloGroup

Reply via email to