- From: Thomas Logan <thomas@equalentry.com>
- Date: Fri, 30 Dec 2016 16:45:56 -0500
- To: public-aria@w3.org
- Message-ID: <CAEqWofeG4X0EjGGBK1zopFpAg5qYU+Mgek3rM3FLAp98QWsNuA@mail.gmail.com>
Hello, I am currently working with a company that is building a new set of user interface elements. One scenario that they are building is a single show/hide control to be used to display additional buttons that can be used to control the UI. >From reviewing the https://www.w3.org/TR/wai-aria-practices-1.1/ <https://www.w3.org/TR/wai-aria-practices-1.1/> there was some confusion because the primary mention of show/hide functionality is in the accordion <https://www.w3.org/TR/wai-aria-practices-1.1/#accordion> section. Because this UI pattern is only a single collapsible/expandable container it does not meet the criteria of being a vertically stacked set of elements for a container. I checked with Bryan Garaventa and it appears the best implementation would be a "to use a button and aria-expanded, plus a named region that uses aria-labelledby that points back to the toggle." I put a sample implementation on codepen <http://codepen.io/EqualEntry/pen/jyNEjZ/> for your review and confirmation. I would like to request that this UI pattern be included in the WAI-ARIA-Practices 1.1 documentation. It could be an additional piece of information listed in the button <https://www.w3.org/TR/wai-aria-practices-1.1/#button> section. I would suggest the accordion <https://www.w3.org/TR/wai-aria-practices-1.1/#accordion> section should also indicate that a single expandable collapsible container should follow the show/hide functionality documented in the button section rather than the guidance in the accordion section. - -- Thomas Logan Owner Equal Entry <http://www.equalentry.com> - “Contributing to a more accessible world”
Received on Sunday, 1 January 2017 16:51:31 UTC