W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2017

Re: Technolog Agnostic / Independent

From: David MacDonald <david100@sympatico.ca>
Date: Mon, 10 Apr 2017 18:21:18 -0400
Message-ID: <CAAdDpDbD2OtdbmigrqhS0YxmHyMk2KbFrxQ2bG+ViPJ04KOsBw@mail.gmail.com>
To: "White, Jason J" <jjwhite@ets.org>
Cc: Wayne Dick <wayneedick@gmail.com>, "Patrick H. Lauke" <redux@splintered.co.uk>, WCAG <w3c-wai-gl@w3.org>
> Now, by all means, let's discuss technology - do we need SCs that vary
depending on viewport width? do we need SCs that only apply to devices that
have touch, and can this be detected? But don't use inappropriate "mobile",
"desktop", "tablet", "phablet", etc categorisations.

I'm fine with or without the rigid distinctions. Most wire frames I get
from major communications and advertising agencies these days use those
terms, but perhaps that will change, and I'm fine with exploring small vs
large screen. break points

Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*

Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

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
<http://www.davidmacd.com/disclaimer.html>

On Mon, Apr 10, 2017 at 4:53 PM, White, Jason J <jjwhite@ets.org> wrote:

>
>
>
>
> *From:* Wayne Dick [mailto:wayneedick@gmail.com]
> *Sent:* Monday, April 10, 2017 4:35 PM
>
> Today technology Independence means that a person with a disability will
> only have access to the least capable systems even if their professional
> software runs on a system with greater capability.
>
> *[Jason] The concept of “technology independence” (at least as it has
> historically been used in the development of WCAG) always referred to the
> implementation technology – HTML, SVG, PDF, etc. – not to the capabilities
> of the user agent. It has long been understood that the latter may vary –
> there exist a variety of user agents with different features, strengths and
> weaknesses.*
>
> *All that is required of authors is that they use (implementation)
> technologies such as markup languages and APIs in ways that are
> “accessibility supported” under the WCAG definition.*
>
> *At some point, I think we’ll need to recognize that certain
> implementation technologies simply won’t be able to support WCAG
> requirements as the latter evolve to enhance the accessibility of Web
> content. However, I think that’s a separate discussion from what Wayne is
> engaging in here; and I’m concerned that we should be sure to avoid
> confusion by distinguishing clearly between “technology independence”, as
> explained above,  and any decisions based on differences in the
> capabilities of widely available user agents that support a given
> technology (e.g., HTML 5).*
>
>
>
> ------------------------------
>
> 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 Monday, 10 April 2017 22:21:53 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 08:04:09 UTC