- From: Gregg C Vanderheiden <greggvan@umd.edu>
- Date: Fri, 3 Feb 2017 15:20:32 +0100
- To: "Patrick H. Lauke" <redux@splintered.co.uk>
- Cc: GLWAI Guidelines WG org <w3c-wai-gl@w3.org>
> seemed to be saying that the mechanism is available, EXCEPT where the > platform/UA itself does not provide it, which seemed rather paradoxical. Actually it says: The author provides the mechanism UNLESS it is already provided by the browsers, ‘ “The mechanism is available” one way or the other. Gregg C Vanderheiden greggvan@umd.edu > On Feb 3, 2017, at 3:08 PM, Patrick H. Lauke <redux@splintered.co.uk> wrote: > > On 03/02/2017 13:46, White, Jason J wrote: >> [Jason] The "a mechanism is available" requirement is meant to ensure >> that the content author supplies the mechanism if the user >> agents/assistive technologies don't. It's the descendant of the >> infamous WCAG 1.0 "until user agents" clause. > > Exactly, which is my point since (going back to the thread starter and > the actual proposed SC https://github.com/w3c/wcag21/issues/57) here we > seemed to be saying that the mechanism is available, EXCEPT where the > platform/UA itself does not provide it, which seemed rather paradoxical. > > 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, 3 February 2017 14:21:14 UTC