Scott O'Hara

More context of your situation needed. What you’re describing raises some concerns providing the markup snippet you are getting the warning about would also be helpful. Though if you’re getting...

I agree with the points @aardrian , @straker, and @yatil are raising. I would not expect this pattern to ever be used for a primary navigation, where the purpose of...

It's fine for the up/down arrow keys to move to the expanding buttons. that's what the APG example does. The problem I'm seeing here is that when using VO +...

Thank you for the detailed response @tlouisse. I can follow the decision path from the WAI Tutorial where they repeat the group name with the first form control (as both...

sorry @tombrunet. I think something happened to the test case? unfortunately these are hosted on tpg's github and I don't have direct access to them anymore from when I originally...

@shunguoy in the OP of this issue is a link to the PR of ARIA in HTML. The PR contains the link to the preview that has the change to...

@shunguoy letting you know that this change was merged into the spec

No, that does not work consistently nor is expected for generic elements which is what the linked ARIA 1.2 specification clarifies. The elements identified here map to generic elements, or...

oh hi @backwardok :) got the notification, so just dropping into provide a direct link to the [latest version of my script](https://github.com/scottaohara/accessible_modal_window), in case a comparison to how i handled...

Doing some [additional testing on this](https://codepen.io/scottohara/pen/LjyYbm) and I've identified that it's the negative margin that is specifically to blame for the incorrect reading order. If you either delete the negative...