RE: wording for the introduction

+1
Michael Gower
IBM Accessibility
Research

1803 Douglas Street, Victoria, BC  V8T 5C3
gowerm@ca.ibm.com
voice: (250) 220-1146 * cel: (250) 661-0098 *  fax: (250) 220-8034



From:   Chuck Adams <charles.adams@oracle.com>
To:     David MacDonald <david100@sympatico.ca>, Andrew Kirkpatrick 
<akirkpat@adobe.com>
Cc:     "lisa.seeman" <lisa.seeman@zoho.com>, "W3c-Wai-Gl-Request@W3. Org" 
<w3c-wai-gl@w3.org>
Date:   2018-04-11 08:34 AM
Subject:        RE: wording for the introduction



+1 J
 
From: David MacDonald <david100@sympatico.ca> 
Sent: Wednesday, April 11, 2018 9:29 AM
To: Andrew Kirkpatrick <akirkpat@adobe.com>
Cc: Chuck Adams <charles.adams@oracle.com>; lisa.seeman 
<lisa.seeman@zoho.com>; W3c-Wai-Gl-Request@W3. Org <w3c-wai-gl@w3.org>
Subject: Re: wording for the introduction
 
Here's my suggestion riffing off of Charles amendment to the earlier text 
that several of us worked up.
 
Although these guidelines cover many important issues, they cannot address 
the needs of every individual and every type, degree, and combination of 
disabilities.  Significant challenges remain in addressing cognitive, 
language and learning disabilities while ensuring that success criteria 
are consistently testable and implementable across all web pages in many 
countries and languages.  Work will continue in this area as technologies 
mature in the marketplace.  We encourage authors to refer to our 
supplemental guidance on improving the user experience for people with 
learning and cognitive disabilities at: w3.org/XXX

Cheers,
David MacDonald
 
CanAdapt Solutions Inc.
Tel:  613.235.4902
LinkedIn 
twitter.com/davidmacd
GitHub
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 Tue, Apr 10, 2018 at 10:20 PM, Andrew Kirkpatrick <akirkpat@adobe.com> 
wrote:
Lisa,
Can you share what paragraphs you intend for these paragraphs to replace 
or add to?
 
If this is in the abstract, I’m concerned that we need to make sure that 
the topic is appropriately covered in the main body of the document. That 
is where the message needs to exist in its complete form as the abstract 
is a hyper-condensed version of the whole.
 
Thanks,
AWK
 
Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe 
 
akirkpat@adobe.com
http://twitter.com/awkawk

 
From: Chuck Adams <charles.adams@oracle.com> on behalf of Chuck Adams <
charles.adams@oracle.com>
Date: Tuesday, April 10, 2018 at 17:07
To: "lisa.seeman@zoho.com" <lisa.seeman@zoho.com>, WCAG <w3c-wai-gl@w3.org
>
Subject: RE: wording for the introduction
Resent-From: WCAG <w3c-wai-gl@w3.org>
Resent-Date: Tuesday, April 10, 2018 at 17:05
 
Hi Lisa,
 
I’ve taken a crack at re-wording the last paragraph.  I don’t wish to draw 
anything out, and I do not object to your wording (I formally agree with 
your wording).  But if time permits for suggestions and alternatives:
 
Although these guidelines cover many important issues, they cannot address 
the needs of every individual and every type, degree, and combination of 
disabilities.  Significant challenges remain in addressing 
internationalization, cognitive, language and learning disabilities while 
ensuring that success criteria are consistently testable and implementable 
across all web pages.  Work will continue in this area as technologies 
mature in the marketplace.  We encourage authors to refer to our 
supplemental guidance on improving the user experience for people with 
learning and cognitive disabilities at: w3.org/XXX
 
Thanks,
Charles Adams
 
From: lisa.seeman <lisa.seeman@zoho.com> 
Sent: Tuesday, April 10, 2018 11:33 AM
To: W3c-Wai-Gl-Request@W3. Org <w3c-wai-gl@w3.org>
Subject: wording for the introduction
 
I think this was the wording based on what was close to consensus from the 
back discussions
 
Web Content Accessibility Guidelines (WCAG) 2.1 covers a wide range of 
implementation recommendations serving a diverse range of people with 
disabilities. Following these guidelines will make Web content more 
accessible and results in improved access to an increasingly larger group 
of people using the web independently.
 
Disabilities include impairments related to blindness and low vision, 
deafness and hearing loss, limited movement, photosensitivity, cognitive, 
language and learning disabilities, and combinations of these. The 
guidelines also makes Web content more usable for ageing related 
impairment, short or long-term changing abilities, usage in different 
circumstances and devices, and often improve usability in general. 
 
Although these guidelines cover many important issues, they do not claim 
to address the needs of people with all types, degrees, and combinations 
of disabilities. Particularly, in the areas of cognitive, language and 
learning disabilities, trying to address issues of consistent  
test-ability, implement-ability across all web pages, and 
internationalisation continue to present a major challenge. Work will 
continue in this area as technologies mature in the marketplace. We 
encourage authors to consider our supplemental guidance on improving the 
user experience for people with learning and cognitive disabilities at: 
w3.org/XXX
 
 
Note that there were issues with this wording but I think this got the 
most close to agreement  (I made some changes added the italicized terms)
 
 
 
All the best

Lisa Seeman

LinkedIn, Twitter