joanmarie

Related: Let's say we remove the statement from step 1 and tweak the test case: ```html foo ``` We'll hit step 2F with a generic which does not support name...

Also related: Let's say we address everything above and we get to step 2F with a focusable generic for which name from contents is officially allowed as a repair. And...

See also https://github.com/w3c/aria/issues/899

The following comments were placed in https://github.com/w3c/aria/issues/696. In order to ensure that role-parity issues stay focused on role-parity, and ARIA issues stay focused what is specific to ARIA, I am...

> joanie: thinks the example of starting and ending with a space is sub-optimal authoring, but we should not trim To be clear: Joanie thinks other trimming is good (e.g....

The AccName tests which I added to Chromium as content browser tests were taken from expectations written during ARIA 1.1 when name prohibition wasn't yet a thing. I agree with...

As per today's ARIA WG discussion, I opened an issue against HTML-AAM regarding the ordering/preference of title versus placeholder. Since we want to be in sync with them, we should...

> From the comments in [w3c/html-aam#168](https://github.com/w3c/html-aam/issues/168) I think it is agreed that placeholder should come after title. @joanmarie should we keep this on the agenda for this week? If we...

The problem identified in the bug report makes sense as something we probably want to solve. But I'm not sure I agree with the solution described. Any time user agents...

> If there's a clean choice for label or heading, great. AccName should be updated to account for any logical pattern authors use. +1 > But the reality of the...