- From: Gez Lemon <glemon@paciellogroup.com>
- Date: Wed, 6 Sep 2017 11:01:35 +0100
- To: Steve Faulkner <faulkner.steve@gmail.com>
- Cc: ARIA Working Group <public-aria@w3.org>
- Message-ID: <CAN-oN23ZQ6UH1D=8fd07w1VfoU2mey075CBw6jgXW33P8n33-A@mail.gmail.com>
Hi Steve, I think they are both required for the basic design pattern for menu buttons. aria-haspopup to indicate the menu, and aria-expanded to indicate the state. Regards, Gez On 6 September 2017 at 09:57, Steve Faulkner <faulkner.steve@gmail.com> wrote: > Hi all, > The use of both aria-haspopup and aria-expanded together is conforming in > ARIA 1.1, > > code example: > > <button aria-haspopup="true" aria-expanded="true">true +true</button> >> > > codepen with test cases: https://codepen.io/stevef/pen/MvxRVx > demo: https://s.codepen.io/stevef/debug/MvxRVx > > but I am wondering if this combination has any use cases? And also if the > combined state information could be confusing? > > -- > > Regards > > SteveF > Current Standards Work @W3C > <http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/> > -- --Gez Lemon *VFO™ *| Principal Accessibility Engineer The Paciello Group https://www.paciellogroup.com A VFO™ Company http://www.vfo-group.com/ Inclusive Design 24 #ID24 on November 16 https://inclusivedesign24.org/ -- The information contained in this communication is confidential, may constitute inside information, and is intended only for the use of the addressee. It is the property of VFO™. Unauthorized use, disclosure or copying of this communication or any part thereof is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by return email, and destroy this communication and all copies thereof, including all attachments.
Received on Wednesday, 6 September 2017 10:02:03 UTC