joanmarie

Regarding the history, here's the commit where the change was made (happened back when all the specs were in a single repo): https://github.com/w3c/aria/commit/dc7cf538. If you look at what is in...

@stevefaulkner: AAMs are the specs that user agents use to implement support for platforms. I get that history might have once dictated otherwise, but they should not be descriptive; they...

As a screen reader developer, I think that such controls are more naturally/conceptually children of the widget they control; not siblings. And while I agree with @mcking65 that we need...

The other problem with using `role` is that `role` maps to something on platform accessibility APIs. Using it for other purposes raises two concerns in my mind: 1. Risk of...

> @joanmarie Any suggestions for how to document something like this in Core-aam? The new row proposed by @cookiecrook makes sense to me. If you look in the states and...

@mcking65: Thanks for your reactions and thoughts and also for bringing it back to practical/real-world stuff. So, I'll take the sightee challenge, using your bring shirts example, with "bring" replacing...

@feerrenrut and @jcsteh: Thoughts? Thanks in advance!

Sanity check: If this change were made, wouldn't ATs have to do more work to distinguish landmarky headers and footers from non-landmarky ones? `banner` and `contentinfo` are landmark roles and...

> Said another way, IA2 HEADER/FOOTER won't be used unless it's to be treated as a landmark (uses ARIA role or HTML tag scoped to body). I wonder if this...

@DavidMacDonald ok, now I'm confused. You moved this from the ARIA issues (good and thank you). But you closed this one?