- From: Steve Faulkner <faulkner.steve@gmail.com>
- Date: Wed, 6 Sep 2017 11:29:49 +0100
- To: Gez Lemon <glemon@paciellogroup.com>
- Cc: ARIA Working Group <public-aria@w3.org>
- Message-ID: <CA+ri+Vka0FnitLvT6=qdvSQZ9zkKGWKeRk2cy4GAGXn957bY+g@mail.gmail.com>
taking a look at some native menu buttons it appears that both expanded/collapsed state and haspopup are exposed, so I think it does appear to be a known pattern, i learn something new everyday. thanks both -- Regards SteveF Current Standards Work @W3C <http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/> On 6 September 2017 at 11:22, Gez Lemon <glemon@paciellogroup.com> wrote: > > > On 6 September 2017 at 11:01, Gez Lemon <glemon@paciellogroup.com> wrote: > >> 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? >>> >> > > Thinking about this further, I think I know what you mean. If the button > has focus, the menu must be closed. If the menu is open, the button doesn't > have focus. So it does seem like they're not both required for a menu > button. > > Regards, > > Gez > > > --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. >> >> > > > -- > > --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:30:56 UTC