Matt King

@JAWS-test, based on our discussion in [FreedomScientific/VFO-standards-support#251](https://github.com/FreedomScientific/VFO-standards-support/issues/251), I think most of your confusion comes from reading the AccName spec and not quite understanding it. If you read only the APG...

As noted on the documentation page, this example is an early draft that still needs work. The design of the display page is not complete. It needs content both before...

BTW, one of the issues the feed pattern is intended to resolve is getting keyboard focus out of infinitely scrolling content in situations where the content cannot be contained in...

Sorry if I still do not understand why it would be better to place the delay menu at the top of the example. Doing so doesn't support the intention of...

What if we resolved this by recommending that that any tab with a context menu also have a visible menu button adjacent to the tab? That menu could be accessible...

Issues related to allowed children in composites: * w3c/aria#1486 * w3c/aria#1454 Still looking for issue directly related to allowing menubuttons in tablists.

Could be resolved by: [Secondary actions on items in composite widget roles · Issue #1440 · w3c/aria](https://github.com/w3c/aria/issues/1440) As well as by allowing buttons inside of tablists.

@mbgower mentioned that we could also change the 1.2 and 1.1 docs at the top where they point to latest. Currently, "Latest" and "Latest Editor's Draft" both point to out-of-date...

This is related to issues #13 and #287.

@yatil commented: > My basic decision tree is: If the menu items are links to other pages (including AJAX trickery), don’t use aria menu. If every menu item in the...