<Zakim> agendum 1. "Action review and WCAG 2.2 https://www.w3.org/WAI/GL/task-forces/coga/wiki/PlanningPage" taken up [from Rachael]

* Roy np

<kirkwood> Rachel: first item is action review

<kirkwood> … finishing up content usable draff for CSUN

<Rachael> There was a review by a MT. Sinai psychologist. Added comments into mental health. Stressed importance of keeping things as simple as possible...

<Rachael> ...applauded efforts. Simple and straightforward is the key. Felt we were doing that.

<Rachael> Lisa: Brilliant.

* Rachael passing scribing back to you John K.

* JohnRochford_ (~JohnRochford@team.cloak) has joined #coga

<kirkwood> Rochford: getting icorrelation between intellectual disability and cognitive disability, doing some work on this

<kirkwood> Steve: haven’t done quotes, doing now, have done some tweaks and wondering about possible quote format

<kirkwood> Lisa: got idea from WCAG

<JohnRochford_> Yesterday, I was awarded a contract to create and support promising practices that enable people dually diagnosed with intellectual and developmental disabilities and mental illness to be fully included in their communities and to have control over their own lives.

<kirkwood> LS: wnat to use same class, if ever want to take ours can

<kirkwood> Rachel” will follwoup with Jennie by email , not here today

<JohnRochford_> I also work on a project for U.S. veterans with mental illness and substance abuse issues.

<kirkwood> Steve: we started off working on undo with suggestions from WCAG

<kirkwood> Steve: we put in fron of WCAG is on agenda for next Tuesday

<kirkwood> Steve: we will see what they come up with

<kirkwood> LS: on Steve’s last point will put in email to send to you

<kirkwood> Rachael: infromation in steps ready for pr, taking controls, confimation ready

<kirkwood> Rachael: visual indicators ready to come back to group

<kirkwood> Rachael: they are going well

<Rachael> q?

* Zakim sees no one on the speaker queue

<kirkwood> Rachael: email from alistair with summary

<kirkwood> LS: steve to email then can on to his bit

<LisaSeemanKest_> https://www.w3.org/WAI/standards-guidelines/wcag/new-in-21/#about-the-personas-quotes

<LisaSeemanKest_> sent you view source

<kirkwood> Steve: could send link to personas examples and sent resource of one of them to get the idea

<Rachael> zakim, next item

<Zakim> agendum 2. "Review user story for extending media alternatives" taken up [from Rachael]

<kirkwood> Rachael: captions and subtitles continued to move forward on it

<kirkwood> LS: for captions and subtitles we can discuss

<kirkwood> LS: need to pass on to Janina the next steps, can agree on user needs have a doc basically couple of paragraphs cognitive wasnt really type of use case suggesting so wrote a new one

<LisaSeemanKest_> https://www.w3.org/WAI/standards-guidelines/wcag/new-in-21/#about-the-personas-quotes

<kirkwood> LS: EA commented on it as well, link to use case we made

<kirkwood> … need to talk about user needs for people who arent understanding

<kirkwood> … threatening, sarcastic, this is in a track, to pick up implied content that isn’t obvious

<kirkwood> … EA is saying use case for intellectual disabilities

<kirkwood> … what about aphasia, intellectual impairments

<kirkwood> … maybe need more… but not sure

<LisaSeemanKest_> https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2020Feb/0047.html

<kirkwood> LS: this a link to her comments maybe we need a bit more

<kirkwood> Rachael: do we agree on meeting the need, and maybe the names, comment now

<kirkwood> LS: think what EA is saying communication disorder is too vague

<Rachael> q?

* Zakim sees no one on the speaker queue

<Rachael> q+

* Zakim sees Rachael on the speaker queue

<kirkwood> +1 communication disorder is too vague

<kirkwood> Rachael: may be able to address not be applicable to all individuals

<Rachael> ack Rachael

* Zakim sees no one on the speaker queue

<kirkwood> LS: do we want to try for people who are non verbal?

<kirkwood> Rachael: do we want to allow flexibility

<LisaSeemanKest_> +1 contue with it

<stevelee> +0

<JohnRochford_> +0

<Rachael> scribe: stevelee

<stevelee> rachael: the proposal is to create a new track on videos alow us to explain content

<kirkwood> +1

<stevelee> ... probably a text track

<JohnRochford_> +1 to Easy Reading one

<stevelee> ... should we include and Easy Reading track as well?

<Rachael> non-concrete content instead of just implied content: include slang, acroymns, metaphors, etc as well

<LisaSeemanKest_> q+

* Zakim sees LisaSeemanKest_ on the speaker queue

<stevelee> JohnK: apart from abstract things like metphores the requirement is cross cognitive so help others

<kirkwood> good for translation

<stevelee> s/JohnK/JohnR

<stevelee> q?

* Zakim sees LisaSeemanKest_ on the speaker queue

<Rachael> ack LisaSeemanKest_

* Zakim sees no one on the speaker queue

<stevelee> lisa: I find easier wit hthe spoken content when watching but if implied then is usefull to have extra

<Rachael> q+

* Zakim sees Rachael on the speaker queue

<stevelee> ... do we want a easy language and summary track? Unless is too wordy?

<stevelee> ... reading by slow readers makes it less useful

<stevelee> JR: some in US may struggle as english is not native language eve nthough they read at level 5

<stevelee> ... I spoke to Ted talks who are starting to captioning their talks and asked about non native speakers

<stevelee> ... so can bring more if explain the dialog but didn't seem to interested

<Rachael> q?

* Zakim sees Rachael on the speaker queue

<stevelee> Rachael, sound slike we have 2 very different use case that may conflict

<Rachael> ack Rachael

* Zakim sees no one on the speaker queue

<LisaSeemanKest_> q+

* Zakim sees LisaSeemanKest_ on the speaker queue

<stevelee> ... and if John writes up Easy Reading then can start approaching separately

<LisaSeemanKest_> https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2020Feb/0047.html

<Rachael> ack LisaSeemanKest_

* Zakim sees no one on the speaker queue

<stevelee> JR yes, and will existing text asa model

<kirkwood> agree with Rachael seeing both points and that handling speaprately as different use cases

<stevelee> lisa: should user research once we have 2 use cases to check

<Rachael> q+

* Zakim sees Rachael on the speaker queue

<stevelee> s/check/check real need

<Rachael> ack Rachael

* Zakim sees no one on the speaker queue

<stevelee> Rachael, a couple of sample would help

<LisaSeemanKest_> Q+

* Zakim sees LisaSeemanKest_ on the speaker queue

<stevelee> hR: i have been doing research in area of text simplifications but spoke ot EA who is using symbols

<stevelee> ... might combine

<Rachael> ack LisaSeemanKest_

* Zakim sees no one on the speaker queue

<stevelee> s/hR/JR

<stevelee> Lisa: needed separate caption track might not be so useable for video - need t ocheck

<Rachael> ACTION: Rachael to send John R instructions and what Lisa wrote

* trackbot is creating a new ACTION.

<trackbot> Created ACTION-323 - Send john r instructions and what lisa wrote [on Rachael Montgomery - due 2020-02-27].

<Rachael> q?

* Zakim sees no one on the speaker queue

<Rachael> zakim, next item

<Zakim> agendum 3. "Discuss how to handle technical details in content usable" taken up [from Rachael]

<Rachael> https://www.w3.org/TR/coga-usable/#objective-help-users-understand-what-things-are-and-how-to-use-them

<stevelee> Rachael: we are trying to get this out

<LisaSeemanKest_> https://www.w3.org/TR/coga-usable/#technical-details-6

<stevelee> Lisa: each pattern has section of technical details -

<stevelee> ... this was info we felt might back up the SC proposal when there was a lot of discussion

<stevelee> ... could put in an appendix, or leave it where it is.

<stevelee> ... might be useful to people who want testability as it provides alternatives pass/fail etc

<stevelee> q+

* Zakim sees stevelee on the speaker queue

<stevelee> ... third change heading name t something 'like testable alternatives'

<Rachael> ack stevelee

* Zakim sees no one on the speaker queue

<Rachael> Steve: It is useful information and its always hard to prune things out but I am concerned that if we include it here or in an appendix, that we will have to make sure it is in good shape. Maybe we just have one reference to that information.

<LisaSeemanKest_> Q+

* Zakim sees LisaSeemanKest_ on the speaker queue

<Rachael> q+

* Zakim sees LisaSeemanKest_, Rachael on the speaker queue

<Rachael> ack LisaSeemanKest_

* Zakim sees Rachael on the speaker queue

<Rachael> Lisa: If you need the specific language, then this links directly.

<LisaSeemanKest_> Q+

* Zakim sees Rachael, LisaSeemanKest_ on the speaker queue

<stevelee> ... could have make it an 'expando' for more details.

<Rachael> Steve: I think that we need to keep the quality

<stevelee> Rachael, one option is to rename as 'testable alts' or 'additional resources'

<Rachael> ack LisaSeemanKest_

* Zakim sees Rachael on the speaker queue

<Rachael> ack Rachael

* Zakim sees no one on the speaker queue

<stevelee> ... that relaxes the quality

<LisaSeemanKest_> https://github.com/w3c/wcag21/issues/26

<Rachael> STeve: I'm sure I saw some that seemed less quality. There are additional resources. I am bit concerned this may be too much information. Can overwhelm. The wcag issues are worth leaving. Not sure about some of the others

<stevelee> ... worked hard for the quality as were submitted to AG

<stevelee> JK: think's they should be referenced

<LisaSeemanKest_> Technical details

<LisaSeemanKest_> The following are proposals for WCAG. They experiment with more testable language.

<LisaSeemanKest_> alteritve versions

<LisaSeemanKest_> The following are alteritive versions that may be more testable

<LisaSeemanKest_> The following are alteritive versions with possible test processes

<LisaSeemanKest_> +1

<kirkwood> “with some suggested”

<stevelee> +1 or with "example test techniques"

<Rachael> The following are alternative versions with some suggested test techniques

<LisaSeemanKest_> +1

<kirkwood> +1

<Rachael> +1

* JohnRochford_ has quit (Ping timeout: 180 seconds)

RESOLUTION: Leave technical details in patterns but renamed "Alternative versions" and "The following are alternative versions with some suggested test techniques."

<scribe> scribe: kirkwood

This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)


WARNING: No "Present: ... " found!
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy
        <amy> Present+


WARNING: Possible internal error: join/leave lines remaining: 
        <Roy>  * JohnRochford_ (~JohnRochford@team.cloak) has joined #coga


No ScribeNick specified.  Guessing ScribeNick: Roy
Found Scribe: kirkwood

WARNING: No "Topic:" lines found.


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: Possible internal error: join/leave lines remaining: 
        <scribe> * JohnRochford_ (~JohnRochford@team.cloak) has joined #coga



WARNING: Possible internal error: join/leave lines remaining: 
        <scribe> * JohnRochford_ (~JohnRochford@team.cloak) has joined #coga



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


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


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.)