Sebastian Zartner

I've filed #218 to come up with a way to save the results. Regarding a basic version of this feature, I could imagine to get away without a real DB....

> How would we store data to it? Manually? The strategy is to run the tests on different browser versions using BrowserStack, export the data from there and merge it...

I have just added individual spec. links to each feature, which paved the way to add more reference info to them. With more reference links added the current badge-style display...

All of what you wrote sounds very reasonable to me. Having checkboxes instead of the drop-down list is a very good point but also requires some thoughts regarding the UI/UX...

See also #57 for an advanced solution. I think allowing to export the results in a structured way is a good first step in this direction. Sebastian

I've dug a little into this topic. ## Specifications There are actually two different definitions for `speak`. [In CSS 2.1](https://www.w3.org/TR/CSS21/aural.html#speaking-props) (and [CSS 2.2](https://www.w3.org/TR/CSS22/aural.html#speaking-props)) it is defined as ``` normal |...

@cmxl wrote: > Adoption seems to be pretty wide-spread: > https://caniuse.com/?search=speak > > Some update on this issue? None of the entries on caniuse.com actually refers to the `speak` CSS...

@OmgImAlexis Well, as I wrote earlier, screen readers might interpret it properly, though I have no experience with them. Browsers still need to fix or add their implementations related to...

>> Note that the values related to at-rules are also syntaxes, and are even shared among at-rules and properties in some cases. > > I talk about syntaxes that use...

@jwhitlock How does the connection to our localization then look like? Sebastian