From: David MacDonald [mailto:david100@sympatico.ca] Sent: Tuesday, June 28, 2016 5:09 PM In my experience, I've rarely found a mobile menu that works before remediation. This is one issue I would like to ensure is addressed in WCAG 2.1, without a loophole, which is why I say "changed menu mechanism". Perhaps there is a more precise way to define a mobile menu without actually saying it... I guess an inaccessible mobile menu has some functionality removed. Here is a specific list of common failures -hamburger menu doesn't get focus -Menu links don't follow the button, but are visually via css from the bottom of the page -Can't access sub menu items -Expanded collapsed state not announced etc... [Jason] The above are, as you noted, failures to conform to WCAG, whereas the question was about differences in information or functionality that would result in the page with the other sort of menu (for want of a better description) not being a “conforming alternate version” of the page with the “mobile-optimized” menu. Without knowing what those differences may be, we can’t tell whether you’re exemplifying the distinction drawn in the definition, or making a case to change it – a major contrast, since the definition is normative. ________________________________ This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. ________________________________
Received on Tuesday, 28 June 2016 23:13:31 UTC