Content Usable Update and Discussion

<Rachael> google doc: https://docs.google.com/document/d/13ccnhFYKhI_jySeMDMDz1_Ugnb5tZ84YXrwgAXr5orU/edit#

<scribe> scribe: lisaseemankest

looking at the document

lisa is not happy with item 14t

some alternitve cvesions are made. proposal is:

The Objectives and Patterns presented in this document supplement the Success Criteria presented in the WCAG accessibility guidelines and address those user needs that are not fully met in accessibility guidelines. Following the guidance in this document does not affect conformance to WCAG, but wil

(for the abstract

The Objectives and Patterns presented in this document supplement the Success Criteria presented in the WCAG accessibility guidelines and address those user needs that are not fully met in current accessibility guidelines. Following the guidance in this document does not affect conformance to WCA

The Objectives and Patterns presented in this document supplement the Success Criteria presented in the WCAG accessibility guidelines and address those user needs that are not fully met in current accessibility guidelines. Following the guidance in this document does not affect conformance to WCAG

but will increase accessibility for people with cognitive and learning disabilities. The Objectives and Patterns build on the:\

+1

<Rachael> +1

micale likes it

<kirkwood> +1

(John added the word currently)

item 1

+1

makes the order inline with the document

process is silence is concent, people will pbject igf there is a problem

<Rachael> New Version: https://raw.githack.com/w3c/coga/changes-from-ag-meeting-may-2020/content-usable/index.html#

item 2 - no objections (reognization of document

open issue to use clear design, clear stucture, clear content in summary

lisa prefers what we had, but can live with it for wide revieq

changes would be editorial

<Rachael> +1

duesring wide review

issue 3 - change sentence to es that affect people with cognitive and learning disabilities about context, structure, language, usability, and other factors that are difficult to include in general guidance.

es that affect people with cognitive and learning disabilities about context, structure, language, usability, and other factors that are difficult to include in general guidance.

+1

john: change about to include

+1 from everyone

item 5

lisa: th revices does not achive the original one

the original expains why it is about accessibility, but the revised is less so

so we can leave it in but make it an issue

john agrees

1. Original

People with cognitive and learning disabilities may not be able to effectively use web content because of the design and content choices of the author.

1. Revised

Design, structure and language choices can make content inaccessible to people with cognitive and learning disabilities.

rachael: lets just drop of the auther so we have : People with cognitive and learning disabilities may not be able to effectively use web content because of the design and content choices

john agrees

reslution is if it comes up we will sugest new sentece, if not add as issue:People with cognitive and learning disabilities may not be able to effectively use web content because of the design and content choices

Original

However, for users with cognitive and learning disabilities, these difficulties are likely to be persistent and significant, so that they are unable to access content and may be forced to abandon tasks, without any way to complete them unaided.

2. Revised

However, for users with cognitive and learning disabilities, these difficulties are likely to be persistent and significant. As a result, they could be unable to access content and complete these tasks unaided.

lisa prefers first, but john prefers secone. so let's leave it

john cange the word unaided to independently

everyone agrees to that

<Rachael> everyone does not include Michael unless he weighs in.

john and lisa find it odd to to call out adhd like this

change People may also experience a co-occurrence of difficulties such as dyspraxia, ADHD, developmental coordination difficulties

we aggree on "People may also experience more than one type of cognitive and learning disability. "

6 - we are adding word current

everything else ok

7: alister said that if we wuse "do and dont" we need to make it all active viocing

rachael: lets add that as an issue for next

8 - typo

all ok with it

item 10 -all ok

(and item 9

item 11

the change is to make it less wcagy

everyone is ok

12 - no discrimation on small devlopers

all ok wiht change!

item 13

<Rachael> https://raw.githack.com/w3c/coga/changes-from-ag-meeting-may-2020/content-usable/index.html#x3-1-design-objectives

lisa: where is the pargraf

There have been different attempts to make testable statements for the design patterns. These include test processes, failure examples, etc.. In many cases, the results of these attempts only represent a subset of the coresponding design pattern. A full table of the draft testable options are available at Testable Statements for COGA Design Patterns.

The Cognitive Accessibilty Taskforce intends to continue working on these statements as a supplement to the design guide.

There have been attempts to make testable statements for each design patterns with corresponding test processes, failure examples, etc.

In many cases,

Note that, in many cases,

There are ongoing efforts to make testable statements for each design patterns w

ith corresponding test processes, failure examples, etc.

Note that in many cases, the testable statement only covers the part of the design pattern that is automatically testable. A full table of the draft testable options are available at Testable Statements for COGA Design Patterns.

The Cognitive Accessibility Taskforce intends to continue working on these statements as a supplement to the design guide.

we seem ok for wide review

Glossary https://docs.google.com/document/d/1AuM-06Alk5VgVgFPTsJD2DcadIrcGIRVDcNgFwPiQRc/edit?usp=sharing

we need a fuller meeting about the glossary

john: there are cultural problems with the glossary

rachael: and also where we put it

thanks rachael - was just looking up the syntax!

This is scribe.perl Revision of Date 
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: (no_one)
Present: (no_one)

WARNING: Fewer than 3 people found for Present list!

Regrets: Rachael Jennie
Found Scribe: lisaseemankest
Inferring ScribeNick: LisaSeemanKest

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)