- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Thu, 16 Sep 2021 23:17:14 +0100
- To: w3c-wai-gl@w3.org
My immediate concern would be that without a specific new role (and the necessary plumbing into platform accessibility APIs etc), I'm not sure how screen readers would know to also pass the down arrow keypress to the page, rather than consuming it themselves. Which would then make it impossible to open the split button with keyboard/AT. For mouse/touch/stylus users, I'm guessing you'd plan to implement some sort of complex click handling? A click handler on the button itself, and then a separate click handler on the "down arrow icon" part (making sure it doesn't then bubble up to trigger its parent button)? Lastly, how would speech recognition users trigger the down arrow part? P -- Patrick H. Lauke https://www.splintered.co.uk/ | https://github.com/patrickhlauke https://flickr.com/photos/redux/ | https://www.deviantart.com/redux twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Thursday, 16 September 2021 22:17:29 UTC