W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2015

RE: ARIA and mainstream UI (was RE: ARIA 1.1: Deprecate @aria-grabbed and @aria-dropeffect)

From: Jonathan Avila <jon.avila@ssbbartgroup.com>
Date: Fri, 18 Sep 2015 22:07:13 +0000
To: "Patrick H. Lauke" <redux@splintered.co.uk>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <BY2PR03MB272F5DE77F6C3EFEDBDE00F9B590@BY2PR03MB272.namprd03.prod.outlook.com>
> Random interesting example from a while ago: IE10/IE11/Edge on touchscreen devices take aria-haspopup as a hint to simulate hover behavior (and not firing subsequent events like click, thus allowing for hover-based menus to work on mobile/tablet, for instance)

Historically haspopup has been applied to things that it should not.  With changes to ARIA 1.1 this use might be more appropriate.  Although it does raise some questions about developers going willie nillie adding aria-haspopup to everything.

On another topic related note people also use ARIA selectors in CSS to make visual changes.  For example, input[aria-required='true'] { border: thin solid red;}

Jonathan

-- 
Jonathan Avila
Chief Accessibility Officer
SSB BART Group 
jon.avila@ssbbartgroup.com

703-637-8957 (o) 
Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter


-----Original Message-----
From: Patrick H. Lauke [mailto:redux@splintered.co.uk] 
Sent: Friday, September 18, 2015 5:34 PM
To: w3c-wai-ig@w3.org
Subject: Re: ARIA and mainstream UI (was RE: ARIA 1.1: Deprecate @aria-grabbed and @aria-dropeffect)

On 18/09/2015 17:01, Richard Schwerdtfeger wrote:
> The issue is that user agents have a lot of issues to contend with wrt.
> their UI. They may introduce new interaction models or different 
> layout paradigm shifts. If we start specifying user agent behavior it 
> handcuffs them.
>
> However, should a host language or browser decide to leverage ARIA 
> (which I think would be wise in some cases) to provide a better user 
> experience then that is where the UI should be decided.
>
> This is why ARIA neither requires or forbids user agents from 
> enhancing native presentation and interaction behaviors.

Random interesting example from a while ago: IE10/IE11/Edge on touchscreen devices take aria-haspopup as a hint to simulate hover behavior (and not firing subsequent events like click, thus allowing for hover-based menus to work on mobile/tablet, for instance) https://msdn.microsoft.com/library/jj152135(v=vs.85).aspx

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

Received on Friday, 18 September 2015 22:07:45 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:58 UTC