- From: Sailesh Panchang <sailesh.panchang@deque.com>
- Date: Tue, 10 May 2016 09:36:37 -0400
- To: "josh@interaccess.ie" <josh@interaccess.ie>
- Cc: Jonathan Avila <jon.avila@ssbbartgroup.com>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
Are these examples of JS events being triggered incorrectly? Accessibility aside for a moment, this impacts all users. So it is surely poor usability / functionality for all. Menus / popups can be implemented without such issues being manifested. Techniques that guide creation of such interfaces should be done right. This does not call for a new SC. Thanks, Sailesh Panchang On 5/10/16, josh@interaccess.ie <josh@interaccess.ie> wrote: > >>Ø When a site has a large and distracting Mega Menu that is often >>triggered accidently on a mouse over, for example, >> >> >> >>I’ve actually run into issues like this as well when things pop open >>because I moved my mouse over one item to reach something else but did >>not intend to open the pop up. On a related note I’ve also run into >>the issue when I wanted to select a sub level item from an open menu >>and the menu closed because I moved my mouse over something else or >>outside of the bounds of the menu on my way to the sub menu items. >> > Thanks for that Jon. I think its a common problem. > >>There are also situations like YouTube media players where when I move >>my mouse into the player to use the controls the controls disappear and >>when I move my mouse out of the player the controls appear. Certainly >>these issues are issues for all people – but I’d imagine they can >>negatively affect users with disabilities more. Once again, SC 3.2.1. >>and 3.2.2 seem to focus on changes of context for input and focus and >>not with the pointing device– so I’m not sure these pointing device >>issues fit into the current WCAG. >> > Yes, this is something for us to look at, definitely. > > Josh > >> >> >> >>Jonathan >> >> >> >>Jonathan Avila >> >>Chief Accessibility Officer >>SSB BART Group >>jon.avila@ssbbartgroup.com >> >>703.637.8957 (Office) >>Visit us online: Website | Twitter | Facebook | Linkedin | Blog >> >>Check out our Digital Accessibility Webinars! >> >> >> >>From:josh@interaccess.ie [mailto:josh@interaccess.ie] >>Sent: Tuesday, May 10, 2016 8:03 AM >>To:w3c-wai-gl@w3.org >>Subject: SCs for Mega Menu fails >> >> >> >>When a site has a large and distracting Mega Menu that is often >>triggered accidently on a mouse over, for example, >> >>I think this should be a flagged as an issue for many users. The >>question is, are distracting Mega Menus (DMMs ;-)) considered a fail of >>either 3.2.1 On Focus/3.2.2 On Input ? >> >>I personally don't think it's either but, I need a way of saying to a >>client - 'This thing is disorientating and will be confusing >> >>for some PWDs, and regular users will thank you for removing it' but >>if I can't call it out as a fail >> >>of a pertinent SC - then my advice will likely be ignored. >> >> >> >>So I'm wondering if (in the future) we need a new SC or change an >>existing one, to cover user input/interaction error? >> >>Or do you guys think 3.2.1 On Focus/3.2.2 On Input are sufficient (with >>a small s). >> >> >> >>Thanks >> >> >> >>Josh >>
Received on Tuesday, 10 May 2016 13:37:05 UTC