W3C home > Mailing lists > Public > public-cognitive-a11y-tf@w3.org > September 2019

RE: proposed SC Findable Help

From: James A. <A.James@soton.ac.uk>
Date: Sat, 14 Sep 2019 09:18:23 +0000
To: Jonathan Avila <jon.avila@levelaccess.com>, David MacDonald <david100@sympatico.ca>, "Delisi, Jennie (MNIT)" <jennie.delisi@state.mn.us>
CC: public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
Message-ID: <DB6PR0401MB234371DDC4D5560A66BE7EB5B0B20@DB6PR0401MB2343.eurprd04.prod.outlook.com>
It would be useful for this SC to be aligned to the requirements of the European WAD. This requires for an accessibility statement to be placed on every page which must include contact details for assistance with accessibility issues and accessing alternative formats. Organisations are also encouraged to provide details of accessibility functions and further support.

So could we also include the option for help to provided through an accessibility statement.

Finally should be specify that the help and support pages must be accessible. This is a separate requirement on the EN 301 549 accessibility statement – section 12.

Best wishes


From: Jonathan Avila <jon.avila@levelaccess.com>
Sent: 14 September 2019 01:54
To: David MacDonald <david100@sympatico.ca>; Delisi, Jennie (MNIT) <jennie.delisi@state.mn.us>
Cc: public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>; w3c-wai-gl@w3.org
Subject: RE: proposed SC Findable Help

HI David, I believe your proposal would weaken SC in terms of the stated user need to have this help information on every page rather than – if it exists make it consistent.


From: David MacDonald <david100@sympatico.ca<mailto:david100@sympatico.ca>>
Sent: Friday, September 13, 2019 3:31 PM
To: Delisi, Jennie (MNIT) <jennie.delisi@state.mn.us<mailto:jennie.delisi@state.mn.us>>
Cc: public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org<mailto:public-cognitive-a11y-tf@w3.org>>; w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>
Subject: Re: proposed SC Findable Help

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

How about something like the following friendly amendment? WCAG 2.x is is a page based conformance model, the only time we talk about more than one page at a time is with the term "Set of pages". Perhaps we can iterate on that concept.
When any of following information is available on a page within a set of pages

  1.  Human contact details – e.g. telephone number, email address
  2.  Human contact mechanism – e.g. messaging system/chat client, email form
  3.  Self-help option – Frequently Asked Questions/How Do I page, support page, or help content
Then the information is available in a consistent location on all of the pages in the set, or there is a link to that information in a consistent location on all of the pages.

> The above does not include options like chat bots.

Wouldn't a live agent chat be OK?

I don't think we can say "The above doesn't not include options like..." It's too ambiguous and unclear.

David MacDonald

CanAdapt Solutions Inc.

Tel:  613-806-9005





  Adapting the web to all users
            Including those with disabilities

If you are not the intended recipient, please review our privacy policy<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.davidmacd.com%2Fdisclaimer.html&data=01%7C01%7Ca.james%40soton.ac.uk%7Ca8b5af07372d477aca7908d738ae2777%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=Kr1tviWwFoF8zXgKKB0uFhopVU2Tzoas7uhTyMkIzGw%3D&reserved=0>

On Mon, Sep 9, 2019 at 11:20 AM Delisi, Jennie (MNIT) <jennie.delisi@state.mn.us<mailto:jennie.delisi@state.mn.us>> wrote:
Thank you to a large number of people that have been helping to craft the proposed success criteria for Findable Help/Make it easy for the user to find and get help.
Steve Lee and I have come to the understanding after a lot of work that we believe half of the original intent for the SC may be able to pass to the next stage (getting something on every page) but specifying the location most likely would not.
We have drafted some new language we would like reviewed and are sending to both lists. If you have would have a moment to review, share thoughts, it would be greatly appreciated. Feedback preference is to add comments into the Google Doc (https://docs.google.com/document/d/1fX4Iw169OGUny5RTd70S8qAneYy5e0hr7zupE21gPBM/edit#<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1fX4Iw169OGUny5RTd70S8qAneYy5e0hr7zupE21gPBM%2Fedit&data=01%7C01%7Ca.james%40soton.ac.uk%7Ca8b5af07372d477aca7908d738ae2777%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=wmp6WV5iyXCGW0ydLZ6xbf6%2B798DRuragyGJEw1Zy7s%3D&reserved=0>) but email would be fine as well. We would appreciate feedback by Thursday at 9am CST.
I will paste the latest draft after my name in this email. Thanks for considering this request for feedback,
Steve and Jennie

Full title: Make it easy for the user to find and get help.

Draft SC text:
On every page at least one of the following is provided in a consistent location:

  *   Human contact details – e.g. telephone number, email address
  *   Human contact mechanism – e.g. messaging system/chat client, email form
  *   Self-help option – Frequently Asked Questions/How Do I page, support page, or help content
The above does not include options like chat bots.

Plain English Summary:

The intent of this success criteria is to provide help beyond the support provided by the user interface alone, such as help features like spell checkers and instructional text at the beginning of a form.

When having problems completing a task on a website, people with some types of disabilities may not be able to work through the issue without help. Task abandonment, failure to correctly complete a task, or the requirement to get help from people who do not necessarily keep private information secure may be required when help is not available from the site or site support staff. Self-help methods beyond the site, such as using internet search to find contact information for an organization, can be too difficult. Further, their disability may make it more difficult to find the help available (such as a “contact us” link, phone number, or support page) if the information is not present within a few interactions (e.g. scrolling, complex navigation menu).

When a user is quickly able to find help, they are able to complete the task even if they encounter challenges.

When a human is available to help, the contact information or mechanism must be easy to find. This cannot require working through another multi-step format, or a complicated chat interface. This ease of use can be provided through methods such as providing:

  *   a telephone number,
  *   a built-in messaging option (i.e., chat client),
  *   an email form or address.
If a human is not available to help, other methods such as a Frequently Asked Questions page must be provided. If the site is no longer supported, this information must be present.
The preference is for the help to be visually present and available to assistive technologies in the top third of the website or app, preferably easy to visually identify without going into another mechanism (e.g. submenu).

By providing easy access to a human assistant, users unable to understand an interaction can complete the task. Users who have difficulty tracking two processes simultaneously (i.e. a multi-step help format and a multi-step task) will better be able to complete the task. Users that experience cognitive fatigue or cognitive shut down will be able to reserve their energy for the task, instead of using it to find support.

Test Procedure
On every page verify that there is at least one of the following:

  1.  human contact details - e.g. telephone number, email address
  2.  human contact mechanism - e.g. messaging system/chat client, email form,
  3.  self-help option - Frequently Asked Questions/How Do I page, support page or help content.

The above does not include options like chat bots.

Note: the link to self-help content or support can be:

  *   A frequently asked questions page
  *   A support forum
  *   A manual or other support documentation
  *   A form to submit for questions, or to have an issue addressed.

Note: the following do not satisfy the success criteria:

  *   Tool-tips
  *   Contextual help such as an “i” that on hover or click reveals more information
  *   Instructions that would already be included for completing form controls.

[End of draft text]
Jennie Delisi, MA, CPWA
Accessibility Analyst | Office of Accessibility
Minnesota IT Services | Partners in Performance
658 Cedar Street
St. Paul, MN 55155
O: 651-201-1135
Information Technology for Minnesota Government | mn.gov/mnit<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmn.gov%2Fmnit&data=01%7C01%7Ca.james%40soton.ac.uk%7Ca8b5af07372d477aca7908d738ae2777%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=l2FrVPoLsQpkiV5brVH9gz%2BlyMd90Orcb%2BVg1vGWrUQ%3D&reserved=0>
[Minnesota IT Services Logo]
[Facebook logo]<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.facebook.com%2FMN.ITServices&data=01%7C01%7Ca.james%40soton.ac.uk%7Ca8b5af07372d477aca7908d738ae2777%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=Qm8GWrlRuePA6QtlNEhbT1Q2s3ByOSP0NUICLakugtA%3D&reserved=0>[LinkedIn logo]<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fmn-it-services&data=01%7C01%7Ca.james%40soton.ac.uk%7Ca8b5af07372d477aca7908d738ae2777%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=YsFfq25mU3j6oqMbfWXvEaL4zoYAvQ1hHVNdwHHABm4%3D&reserved=0>[Twitter logo]<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2Fmnit_services&data=01%7C01%7Ca.james%40soton.ac.uk%7Ca8b5af07372d477aca7908d738ae2777%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=UFSFls7MkJdcTALbqauqa%2FNH%2FYnUm9v5eS3CTsGZ%2FeI%3D&reserved=0>

(image/png attachment: image001.png)

(image/png attachment: image002.png)

(image/png attachment: image003.png)

(image/png attachment: image004.png)

Received on Saturday, 14 September 2019 09:18:57 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:24:04 UTC