E-mail List Archives
Re: Recommending Widget Markup that Doesn't Work in Reality
From: Brooks newton
Date: Feb 11, 2016 1:08PM
- Next message: Lippy, Tiffany [USA]: "Re: Saving PDF files"
- Previous message: _mallory: "Re: Recommending Widget Markup that Doesn't Work in Reality"
- Next message in Thread: Matt King: "Re: Recommending Widget Markup that Doesn't Work in Reality"
- Previous message in Thread: _mallory: "Re: Recommending Widget Markup that Doesn't Work in Reality"
- View all messages in this Thread
Many thanks to the honest responses to the questions I posed in post regarding implementing ahead of the curve accessibility solutions. I have had the privilege of working with some of the best minds in this business, some of who responded to my inquiry in this forum. Thanks for your feedback and for pointing me in the right direction to learn more. If only software manufacturers were held to the standards we are asking our developers to code to, we might have a faster path moving from theoretical accessibility to business as usual digital accessibility. And many kudos to those who have the imagination to conceive of theoretical solutions at the W3C. We have to able to imagine change before we can actually go about the nuts and bolts work to make it happen.
Sent from my iPad
> On Feb 11, 2016, at 8:30 AM, Patrick H. Lauke < <EMAIL REMOVED> > wrote:
>
>> On 11/02/2016 12:00, Steve Faulkner wrote:
>>> On 11 February 2016 at 09:51, Alastair Campbell < <EMAIL REMOVED> > wrote:
>>>
>>> For ARIA these come to mind:
>>
>>
>> and there is also - Notes on Using ARIA in HTML
>> http://w3c.github.io/aria-in-html/
>
> And it gets *real* fun once you see how any sufficiently complex ARIA patterns (which were devised with a quite clear keyboard/desktop centric view) fall apart for touch devices http://w3c.github.io/aria-in-html/#aria-touch - with the advice I've given to many clients recently to simply NOT implement certain patterns as per ARIA and instead fall back to much simpler approaches. Most recent example: combobox (autocomplete/type-ahead search type text field with suggested values, which can be navigated using arrow keys on keyboard) simply isn't workable for touch/AT users (I believe this was mentioned on this list not so long ago).
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>
- Next message: Lippy, Tiffany [USA]: "Re: Saving PDF files"
- Previous message: _mallory: "Re: Recommending Widget Markup that Doesn't Work in Reality"
- Next message in Thread: Matt King: "Re: Recommending Widget Markup that Doesn't Work in Reality"
- Previous message in Thread: _mallory: "Re: Recommending Widget Markup that Doesn't Work in Reality"
- View all messages in this Thread