W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > October to December 2020

Re: Advisory Techniques followup

From: Shawn Henry <shawn@w3.org>
Date: Thu, 15 Oct 2020 18:04:19 -0500
To: Hidde de Vries <hidde@w3.org>, Andrew Arch <andrew@intopia.digital>, Shadi Abou-Zahra <shadi@w3.org>
Cc: "EOWG (E-mail)" <w3c-wai-eo@w3.org>
Message-ID: <4a015510-0e71-412f-5daa-f8a02e2d7f59@w3.org>
RE: "...I would look for something that gives me the confidence that it will work, that there are many benefits to it and that it is very stable. Many of our Advisory Techniques meet those criteria, and would be suitable to use in production, so I wonder if we may be able to say so with less caveats."

I agree that many (probably even most) Advisory Techniques meet those criteria, and would be suitable to use in production.

The question is: How do we better communicate that? (more specifically: what specific edit suggestions do we offer to AG WG?)

Best,
~Shawn


On 15-Oct-20 2:57 AM, Hidde de Vries wrote:
> Hi all,
> 
> I feel the current description on that Understanding page has so many caveats that, as a developer, I would stay away from using any Advisory Technique.
> 
> Whether it be “suggested” or “potential”, caveats like “may not be sufficient”, “may not be accessibility supported”,  “may not be […] practical” and “not yet stable”, which all appear in this text, read to me as “do not use”. Other developers in last Friday’s EOWG meeting agreed with that.
> 
> If the documentation of an API endpoint, JavaScript library or code example would include this, and I would look at using it for a client, I would not. Instead, I would look for something that gives me the confidence that it will work, that there are many benefits to it and that it is very stable. Many of our Advisory Techniques meet those criteria, and would be suitable to use in production, so I wonder if we may be able to say so with less caveats.
> 
> Best,
> Hidde
> 
>> On 14 Oct 2020, at 02:30, Andrew Arch <andrew@intopia.digital> wrote:
>>
>> Hi Shawn,
>>
>> I agree that some judicial bolding may assist. Also wondering about
>> * changing "suggested ways" to "potential ways" (especially given some of the bullets)
>> * adding in a note that they should be tested with users
>>
>> Andrew
>> ____________________________________
>> Andrew Arch
>> Principal Accessibility Consultant, Intopia
>> p: +61 (0)447 389 137 | t: @Intopia  @amja
>>
>>
>>
>> -----Original Message-----
>> From: Shawn Henry <shawn@w3.org>
>> Sent: Saturday, 10 October 2020 2:09 AM
>> To: Hidde de Vries <hidde@w3.org>; EOWG (E-mail) <w3c-wai-eo@w3.org>
>> Subject: Advisory Techniques followup
>>
>> Hi EOWG,
>>
>> In followup on the brief discussion on Advisory Techniques, please see:
>>
>> https://www.w3.org/TR/UNDERSTANDING-WCAG20/understanding-techniques.html#ut-understanding-techniques-advisory-head
>>
>> which says:
>> [[
>> Advisory techniques are suggested ways to improve accessibility. They are often very helpful to some users, and may be the only way that some users can access some types of content.
>>
>> Advisory techniques are not designated as sufficient techniques for various reasons such as:
>> 	* ...
>>
>> Authors are encouraged to apply all of the techniques where appropriate to best address the widest range of users' needs.
>> ]]
>>
>> I think the bullets get most people's attention, and the sentences are lost for some. Thus, the interpretation can be opposite of what is intended.
>>
>> I wonder if bolding some words in the sentences might help?
>>
>> Best,
>> ~Shawn
>>
> 
> 
Received on Thursday, 15 October 2020 23:04:24 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 15 October 2020 23:04:25 UTC