- From: Steve Lee <stevelee@w3.org>
- Date: Fri, 19 Jul 2019 11:36:31 +0100
- To: w3c-wai-gl@w3.org
> I believe this is valid as long as the top > level is visible. Hmm. If the intent is that the controls a user is likely to want or need to use are not off the viewport then isn't a control hidden under another collapsible control equally bad? Perhaps it can be mitigated if the presence of the child hidden control can be easily deduced - but that's another can of worms eg the Cognitive Pattern - Sub-menu items are able to easily identify https://www.w3.org/TR/coga-usable/#pattern-sub-menu-items-are-able-to-easily-identify Steve On 18/07/2019 20:30, Rachael Bradley Montgomery wrote: > David, > > "Where does that place hamburger menus which are common and contain many > navigation links under them? " > > Most menu's include collapsed content within them, the hamburger menu is > just an extreme example. I believe this is valid as long as the top > level is visible. It is a similar situation with an actions menu in many > process applications. I think that is more clear further down in the > document, but I have really struggled to capture that as long as the > control's top level is visible, the lower levels are valid within the SC > text. Any suggestions on how to incorporate that into the wording? > > Regards, > > Rachael > > > On Thu, Jul 18, 2019 at 3:24 PM David MacDonald <david100@sympatico.ca > <mailto:david100@sympatico.ca>> wrote: > > Hi Rachael > > > Controls needed to navigate content and to initiate, progress or complete a process are visible without scrolling or using a pointer-hover when it is possible to progress, > > Where does that place hamburger menus which are common and contain > many navigation links under them? > > Cheers, > David MacDonald > > *Can**Adapt**Solutions Inc.* > > Tel: 613-806-9005 > > LinkedIn > <http://www.linkedin.com/in/davidmacdonald100> > > twitter.com/davidmacd <http://twitter.com/davidmacd> > > GitHub <https://github.com/DavidMacDonald> > > www.Can-Adapt.com <http://www.can-adapt.com/> > > / Adapting the web to *all* users/ > > / Including those with disabilities/ > > If you are not the intended recipient, please review our privacy > policy <http://www.davidmacd.com/disclaimer.html> > > > On Thu, Jul 18, 2019 at 2:51 PM Rachael Bradley Montgomery > <rachael@accessiblecommunity.org > <mailto:rachael@accessiblecommunity.org>> wrote: > > Hello, > > Based on feedback from the AG working group and the COGA task > force, I revised the2.2 SC Proposal for Essential Controls > <https://docs.google.com/document/d/1DPtCqWHjrhj3QZ4afsqzmWDd-zMSf39RsMqSpR2QGCg/edit#heading=h.4vsa10j1zo6f>. > If you have time, I'd appreciate further comments and > suggestions from the group. > > Best regards, > > Rachael > > -- > Rachael Montgomery, PhD > Director, Accessible Community > rachael@accessiblecommunity.org > <mailto:rachael@accessiblecommunity.org> > > > > > -- > Rachael Montgomery, PhD > Director, Accessible Community > rachael@accessiblecommunity.org <mailto:rachael@accessiblecommunity.org> > >
Received on Friday, 19 July 2019 10:36:38 UTC