For the next iteration of menu elements which are for links instead of menuitems, what should the a11y mappings be and how does that constrain what the HTML markup can be? There may have been discussions about this already somewhere.
It seems like there are two relevant APG examples:
Should each "item" which opens a submenu be mapped as a button or a menuitem? Should each list of links and buttons which open submenus be mapped as a menu or as a list?
The disclosure navigation menu wraps all of the markup in one nav element, but the structure we are currently going for with menulist/menubar/menuitem doesn't use nesting to put the entire thing in one element. Can we still avoid nesting for the HTML to keep it consistent with application menus and navigation menus?
@scottaohara
For the next iteration of menu elements which are for links instead of menuitems, what should the a11y mappings be and how does that constrain what the HTML markup can be? There may have been discussions about this already somewhere.
It seems like there are two relevant APG examples:
Should each "item" which opens a submenu be mapped as a button or a menuitem? Should each list of links and buttons which open submenus be mapped as a menu or as a list?
The disclosure navigation menu wraps all of the markup in one nav element, but the structure we are currently going for with menulist/menubar/menuitem doesn't use nesting to put the entire thing in one element. Can we still avoid nesting for the HTML to keep it consistent with application menus and navigation menus?
@scottaohara