Re: [w3c/WebPlatformWG] TPAC 2016/Monday proposed agenda items (#68)

> @@ -25,14 +25,22 @@ This meeting will take place on 19 September 2016 as part of [TPAC 2016](https:/
>  ### Accessibility: 11am?
>  * [Web Component ARIA Issue 552](https://github.com/w3c/webcomponents/issues/552)
>  * [Web Component and Extensibility Issue 553](https://github.com/w3c/webcomponents/issues/553)
> +* Tab index and ARIA role (existing role, not extensibility) for custom elements (see below.)
> +
> +Dominic (Google): `<button>` produces something that is focusable and has an ARIA role (button). If component authors want to make things focusable/have roles, they need to use attributes: `<my-widget tabindex="0" aria-role="button">`. Experience from three years building web components at Google has shown that relying on attributes is problematic for a few reasons I'll share. I propose we add a couple of options to customElements.define for the default tabindex and ARIA role of custom elements.

role="button" not aria-role

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/WebPlatformWG/pull/68/files/631698b80bc61e4acf7a82112c9c6188544b9254#r78331133