- From: Sailesh Panchang <sailesh.panchang@deque.com>
- Date: Fri, 13 Nov 2020 17:04:19 -0500
- To: IG - WAI Interest Group List list <w3c-wai-ig@w3.org>
- Cc: "Patrick H. Lauke" <redux@splintered.co.uk>, gregg@raisingthefloor.org
As the reference is not to the pressed / active state of a button like a mute / video-on button, I imagine it is an action button like "Make payment", say in a bill-payment app. One would expect the app to display 'Thankyou for your payment' / 'Sorry request cannot be processed' type message pretty much instantly; else it is the app's functionality issue. If it the app is going to require a few seconds to process the transaction, I would imagine, "Please wait ... processing" message to be displayed. Otherwise all users would be at a loss. I would not flag it as an accessibility issue. Best wishes, -- Join me at axe-con 2021: a free digital accessibility conference. Read more at https://www.deque.com/axe-con/ Feel free to contact Deque marketing if you have any questions. Thanks! Sailesh Panchang Principal Accessibility Consultant Deque Systems Inc 381 Elden Street, Suite 2000, Herndon, VA 20170 Mobile: 571-344-1765 On 11/13/20, Gregg Vanderheiden RTF <gregg@raisingthefloor.org> wrote: > This would be sort of covered by 1.3.1 > > If there is ANY information passed to ANY users (beep, flash, tactile) then > that information has to be programmatically determinable. That is, it > needs to be accessible to AT. > > So AT should be possible to create that would allow you to add an accessible > presentation of this information. > > Unfortunately - most mobile OSs don’t have great AT support other than > themselves. So you should try sending a note to > Accessibility@apple.com > Accessibility@google.com > Accessibility@microsoft.com > > And telling them that this would be a very handy feature for them to add. > > They have been quite responsive to these suggestions to date. > > BE SURE to include in your email - that this idea is offered freely and > without and claim to rights - so they are free to use it. > > Sometime ideas are submitted that are hard to implement - if they are > complicated and the sender may have filed a patent on them. So nice to just > make it clear that at least the sender is not holding rights to it - or if > they are - that they are giving free license to use the ideas. > > I have gotten many ideas into the OSs in this manner. > > gregg > > ——————————— > Professor, University of Maryland, College Park > Director , Trace R&D Center, UMD > Co-Founder Raising the Floor. http://raisingthefloor.org > And the Global Public Inclusive Infrastructure (GPII) http://GPII.net > > > > >> On Nov 13, 2020, at 7:05 AM, Patrick H. Lauke <redux@splintered.co.uk> >> wrote: >> >> On 13/11/2020 11:51, Ms J wrote: >> >>> Is there anything about this in the guidelines? >> >> No, this sort of active confirmation / tap highlight is not covered by the >> guidelines (though no doubt somebody will bend / creatively reinterpret >> 2.4.7 Focus Visible to say it kind of does cover this, but normatively it >> doesn't). >> >> 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 Friday, 13 November 2020 22:04:33 UTC