| 00:05 | <rniwa> | aklein, smaug____, Domenic: indeed, it's hard but i'm hoping that we'll be able to find a way. |
| 00:05 | <rniwa> | it would really suck if custom element's contract was different from builtin such that you could never use custom element API to implement a builtin element for example |
| 10:49 | <hsivonen> | contemplating replying to Shane on public-html about EPUB and RDFa |
| 11:11 | <Ms2ger> | That does not sound like a good idea |
| 11:15 | <SteveF_> | Ms2ger: it's a resonable idea to provide counter arguments to ARIA is a good vehicle to allow RDFa EVERYWHERE in HTML |
| 11:16 | <SteveF_> | Domenic: Annevk: thoughts on https://lists.w3.org/Archives/Public/public-webapps/2015AprJun/0622.html ? |
| 12:58 | <Domenic> | SteveF_: probably change it from role="button" to behavior="button" to get past the compat hurdle. Then, spend a lot of time speccing exactly what that means, cross-platform. Doing that will be 80% of the way to exposing the individual primitives (since you've now specced them); ideally then do the extra 20%, but that's optional I guess. |
| 13:02 | <SteveF_> | Domenic: sounds like something beyond my technical capabilities, I was looking for a relatively simple way to extend current label behaviour to custom buttons etc. on a somewhat related note this may be of interest if you haven't seen https://wiki.mozilla.org/Accessibility/WebAccessibilityAPI |
| 13:02 | <SteveF_> | stuff being worked on by surkov from mozilla |
| 13:03 | <Domenic> | Haven't seen; very interesting. |
| 13:03 | <SteveF_> | some discussion of above on Google browser acc list https://groups.google.com/d/msg/browser-accessibility-dev/7M9fUOQmkc4/Ix2x-7m8EZsJ |