Melanie Sumner

Even after I add `@ember/string` as a devdep, I'm still getting a test failure in the 5+ scenarios...but only on the first component test. The rest of the tests pass...

Reading through specs to answer my own question, AccName spec doesn't include this in the name calculation, but I am finding it in html-aam: https://w3c.github.io/html-aam/#accname-computation , specifically 4.1.1 step 2....

Discussed in working group; what we'll do here is note that for HTML elements that don't have aria attributes, html-aam is the specification that applies, not accname.

@scottaohara looking through the spec and HTML-AAM is definitely referenced: For description:  For name (in the steps themselves): 

I think my concern is still that there feels like a disparity: > I expect browsers to stop at the first valid accessible label then stop. I'm going to try...

https://github.com/w3c/aria/pull/2503

Adding this to the whitespace deepdive. In this example, the accessible name calculation follows these rules: 1. No `aria-label`, `aria-labelledby`, or `title` present, so the accessible name comes from the...

BTW @cookiecrook since I can't reproduce can you confirm if this is still an issue for you?

Are we suggesting that this should be explicitly outlined in ACCNAME spec? FWIW,I think that what's reflected in the DOM is what should be reflected to the user (via screen...

I'd encourage everyone to read the existing CSS specification text in the OG post. Browsers have purposefully chosen to do the opposite of CSS Spec, and now **we're suggesting to...