Eric Eggert

Hi Jens, Unfortunately there seems to nobody from W3C/WAI tasked with developing the tutorials further, or even merging pull requests/reviewing issues. I think this would be a great addition to...

Thanks, @MakotoUeki, for the suggestion. I wonder if that is a bit too voluminous (and WCAG-sounding, to be honest) for this description. I think the first half about context applies...

Hi @michaelwayneharris87, thanks for your report. I see how that can be confusing and we’ll look for more precise wording. Links are interactive elements, and most screen readers will read...

@niwsa I think your change is not what we want to say with this (terribly long and hard to understand) sentence. I think what we want to say is: >...

Hi @fergfluff, thanks for your suggestion. We’re in the (slow 😉) process of integrating the tutorials into the main WAI design and navigation structure, so your comment is coming at...

Hi @Felicia5, this is the repository for the accessibility tutorials. You might want to ask that question over at the aria-practices repository: https://github.com/w3c/aria-practices/issues

Version 2.0 of the page (integrating it into the current WAI design and fixing the most outrageous bugs), which was completed over 11 months ago, also still has aria-haspopup: https://wai-tutorials.netlify.app/tutorials/menus/flyout/...

Duplicate of #611.

Hi @stefanFarnetani! I’m happy to take a PR on this one! :-)

Hi @gordongrace – thanks for your contribution. I’ll look into it and see if/how we are going to use it.