- From: White, Jason J <jjwhite@ets.org>
- Date: Fri, 3 Feb 2017 13:46:59 +0000
- To: "Patrick H. Lauke" <redux@splintered.co.uk>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
> -----Original Message----- > From: Patrick H. Lauke [mailto:redux@splintered.co.uk] > The disconnect for me comes when UAs/platforms that don't provide that > particular functionality/mechanism are then also excluded...so effectively we're > saying "a mechanism for X should be available, which in most cases is already > taken care of by the UA, except this SC doesn't apply if the UA doesn't provide > this sort of mechanism"? [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. ________________________________ This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. ________________________________
Received on Friday, 3 February 2017 13:47:32 UTC