E-mail List Archives
Re: Burger Menus and necessary ARIA support
From: Vemaarapu Venkatesh
Date: Sep 13, 2017 3:03AM
- Next message: Brandon Keith Biggs: "Re: Remediation Cost Versus Inclusive Design Cost"
- Previous message:
: "Re: visually impaired front end developer" - Next message in Thread: Jonathan Cohn: "Re: Burger Menus and necessary ARIA support"
- Previous message in Thread: Fischer, Johannes: "Re: Burger Menus and necessary ARIA support"
- View all messages in this Thread
Hi Fischer,
If the purpose is served with the use of native HTML controls, it is always
best to use them instead of re purposing them using ARIA and that is what
even first rule of ARIA conveys. Your implementation with <div> will also
be OK if the button is keyboard accessible because ARIA doesn't provide any
keyboard accessibility like how HTML does.
If aria-haspopup="true" is used along with aria-expanded="false" NVDA
announces "<name of menuitem> collapsed submenu" which is very clear
otherwise it announces "<name of menuitem> collapsed". In either cases I am
not finding any impact but it is more about enhancing users experience.
Along with you even I am curious to hear from other experts how it impacts
screen reader users if aria-controls or aria-owns are not used on certain
widgets like menu buttons, tablists, treeviews etc.
Thanks,
Venkatesh
- Next message: Brandon Keith Biggs: "Re: Remediation Cost Versus Inclusive Design Cost"
- Previous message:
: "Re: visually impaired front end developer" - Next message in Thread: Jonathan Cohn: "Re: Burger Menus and necessary ARIA support"
- Previous message in Thread: Fischer, Johannes: "Re: Burger Menus and necessary ARIA support"
- View all messages in this Thread