W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2017

Re: Mechanism Disclaimer

From: David MacDonald <david100@sympatico.ca>
Date: Mon, 23 Jan 2017 09:33:56 -0500
Message-ID: <CAAdDpDZ3qut_oOuuhsKYtzMKv_kAsja6VPA2T-qnffcPnR7Ffw@mail.gmail.com>
To: Gregg C Vanderheiden <greggvan@umd.edu>
Cc: Alastair Campbell <acampbell@nomensa.com>, John Foliot <john.foliot@deque.com>, IG - WAI Interest Group List list <w3c-wai-ig@w3.org>

David MacDonald

*Can**Adapt* *Solutions Inc.*

Tel:  613.235.4902



GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>

*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy

On Sun, Jan 22, 2017 at 10:36 PM, Gregg C Vanderheiden <greggvan@umd.edu>

> On Jan 22, 2017, at 8:45 PM, Alastair Campbell <acampbell@nomensa.com>
> wrote:
> John Foliot:  I am becoming increasingly concerned that this phrase -
> ‘mechanism is available’ - is fast becoming the new "Until user agents...",
> I had already thought that's what 2.0 did instead, wasn't it? E.g. Bypass
> blocks, if user-agents supported landmarks for keyboard-users we wouldn't
> need skip links anymore, for many cases at least.
> Mechanism is available is a very powerful and forward looking approach.
> It says “if the mech isnt there in browsers - or you do something to break
> that one — then you need to provide the mechanism yourself (this also
> speaks to Alastair’s #4).     But it also allows that when browsers add
> things (like browsers that all added zoom or font sizing with wrap)  that
> authors no longer have to do that — as long as they don’t break it.
Received on Monday, 23 January 2017 14:34:30 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 January 2017 14:34:32 UTC