Amelia Bellamy-Royds

I would definitely be wary of standardizing too many assumptions about which CSS content is text or which is decorative. Currently, the correct accessible markup for font icons is to...

Hmm, I double-checked, and the same problem is now happening in SVG-AAM, so it's probably really an issue for the aria-common repo. I'll file an issue there, and leave this...

I don't think there would be anything platform-specific. This is about mapping the DOM tree(s) to the accessibility tree, and mapping IDRefs to accessible nodes. Once the accessibility tree is...

@isiahmeadows Sorry I missed your comment when you made it. So your idea is to skip the Class declaration and just use an options dictionary instead? I don't see any...

As much as I like the idea of eventually being able to polyfill every type of function we might want in CSS, I agree with @FremyCompany that it makes sense...

OK, thinking through all the implications of Tab's comment, I think I have another item to add to the list of things that won't be tackled until level 2: -...

For type parsing, whatever future solution is chosen, I hope it has a way to apply to variables as well as to functions. But for our Level 1 Custom Functions,...

@majido I was also thinking about that during yesterday's discussion on easing functions, but it is a much more complex case, because the ”value” returned from the CSS function would...

> whereas a value that contains null would have the entire declaration quietly declared invalid. We have something like this in CSS, as the initial value of a custom property,...

> The contents of a function are, philosophically, no different from the value of a property, I agree that this is the best way to think about the parameters. But...