James Craig

@scottaohara wrote: Thanks. > `complementary` may need a caveat added per the conditional complementary role for the `aside` element. To clarify, are you suggesting `nameFrom: heading` be removed from both...

> Re: complementary and form, yes would need to be clear that while these ARIA roles can get name from heading, the equivalent HTML elements may not (aside) or would...

Recycling reviews because I think this addresses all the feedback now. Affected roles now limited to the following for this PR. - `alertdialog` - `article` - `dialog` Others that are...

Merge of the aria-common script PR should happen before this one: - https://github.com/w3c/aria-common/pull/89 Otherwise, this is ready to go I think. @jnurthen can you r+ and merge those in order?

OK @jnurthen I added the 3 implementation and 1 WPT issues so I think this is ready to merge.

I believe we have informal commitment from at least two. @aleventhal @benbeaudry @jcsteh do you have any issues with "name from heading"? For clarity, this isn't my proposal or original...

@jcsteh wrote: > Is it reasonable for UAs to impose some limit on how many nodes we check? Certainly possible, but where to draw the line? Some web dev will...

> Removing my +1 until we get consensus on whether the top level document's documentElement/body is treated differently from the iframe's. If that's a deal-breaker for Aaron, I'd say let's...

@scottaohara wrote: > Is it potentially worth combining this proposal with #816 - specifically the `aria-headeralternative`? I see that as a separate use case. For example, the "terse label" and...

Committed @scottaohara's suggestions. r?