E-mail List Archives
Looking for input on appropriate ARIA states for mobile navigation menu button
From: Marc Solomon
Date: May 2, 2016 2:42PM
- Next message: Thomas Lee McKeithan II: "Re: Accessibility training?"
- Previous message: Paul J. Adam: "Re: Using title attribute on non-anchor elements?"
- Next message in Thread: Bryan Garaventa: "Re: Looking for input on appropriate ARIA states for mobile navigation menu button"
- Previous message in Thread: None
- View all messages in this Thread
After reviewing the ARIA authoring practices for related widgets (e.g. menu button, menu, pop up menu) and a number of high profile accessibility focused websites, there seems to be a few different ways to handle the implementation. In my opinion, the element that triggers the navigation menu should have a role of button. I don't think I will get many arguments on this. I would also like to use aria-haspopup and aria-expanded to notify AT users of the widget's function and current state. What do you consider to be best practice from a usability perspective and does this differ from what is required from a WCAG standards perspective?
Thanks,
Marc
- Next message: Thomas Lee McKeithan II: "Re: Accessibility training?"
- Previous message: Paul J. Adam: "Re: Using title attribute on non-anchor elements?"
- Next message in Thread: Bryan Garaventa: "Re: Looking for input on appropriate ARIA states for mobile navigation menu button"
- Previous message in Thread: None
- View all messages in this Thread