SV_MEETING_TITLE -- 11 Jul 2016

<Lisa_Seeman> agenda: this

<Lisa_Seeman> next item

<scribe> scribe:maryjom

<Lisa_Seeman> scribe: maryjom

<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/track/actions/open

<Thaddeus> + Thaddeus

LS: Process for the first public working drafts are well under way.

<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Open_Issues

LS: We have some actions for work items that need to be worked on that are open issues that have been open for more than a year for people that have left the task force. We'll put them on our list of things to do and closed as actions.
... Actions for reviews of issue papers that have been done have also been closed.
... Issue of review of ISO work as it pertains to COGA - need status.

MP: Will look at the User Needs ISO work to see if anything is missing from our COGA work.

LS: Question for John Kirkwood. Attention span for ADHD - is there any research on that?

JK: Did find some research. Spoke to a neuropsychologist at Mount Sanai - no time ranges to give to that due to the wide variation between the members of the AD/ADHD population. More research would be required.
... Intellectual disabilities vs. aging vs. brain injury is also a wide variation so a specific number is not able to be specified.

LS: So we should just state, like in multimedia that natural breaks, or change of topics should be used rather than a specific length of time for going back to re-review material in multimedia.
... Timeline for next publication - target right before TPAC for the next round of tables and updates to the user research that we have been working on.
... We want time during TPAC to talk to the ARIA working group face-to-face. Need 2 hours at least.

RS: Will set that up.

LS: Topic - COGA, whether it belongs in ARIA. We think it does.
... Doubtful we could make another public draft in a month, so maybe simply an updated Editor's Draft.

<Lisa_Seeman> next item:

<Lisa_Seeman> next item

LS: We will be writing a cover for the review of the first public working draft of the issues papers and gap analysis.
... We've filled in the tables of user needs quite a bit since sending the gap analysis to the WCAG and APA working groups for approval for the first publication. So what specifically should we ask for feedback on?

<Lisa_Seeman> https://rawgit.com/w3c/coga/master/gap-analysis/table.html

<Lisa_Seeman> https://w3c.github.io/wcag/coga/gap-analysis.html

<Lisa_Seeman> https://rawgit.com/w3c/coga/master/gap-analysis/#roadmap---tables-of-user-needs

LS: It will take a couple of weeks to get the updated tables ready to publish, so we can make an editor's draft before TPAC so we can use that draft to talk about there.

<Lisa_Seeman> next item

LS: User testing - should that be an issue paper? David MacDonald had done some user testing and in that thread it came out that there are issues and there may be a need for guidelines for user testing.
... We could create a wiki page for guidance on user testing. There are more complicated issues, and it might be worth putting together as an issue paper.
... Does anyone want to take on such an issue paper.

Thaddeus: Thinks this is an important topic to cover.

LS: Will add this item to the list of open issues.

<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Open_Issues

LS: We also need the issue paper on metadata worked on.
... Do we need someone to work on the voice menu issue paper when it is voice activated that people need to find the right words.

DD: I think it is pretty well covered in that issue paper.

LS: The use of bots such as chat bots, and how cognitive disabilities work with them. Like if you want to ask for help or lose your context and how that will work. Things that look interactive and you think you're speaking to a person but they aren't really.

JK: Will look into the chat bot issues.

DD: Would be willing to help with that topic.

<Lisa_Seeman> ACTION: JohnK and Debbie Dahl to draft issue paper on coga use groups using bots including spelling,, asking for help, losing context, making mistakes, need to write the right words [recorded in http://www.w3.org/2016/07/11-coga-minutes.html#action01]

<trackbot> Error finding 'JohnK'. You can review and register nicknames at <http://www.w3.org/WAI/PF/cognitive-a11y-tf/track/users>.

<Lisa_Seeman> ACTION: John Kirkwood and Debbie Dahl to draft issue paper on coga use groups using bots including spelling,, asking for help, losing context, making mistakes, need to write the right words [recorded in http://www.w3.org/2016/07/11-coga-minutes.html#action02]

<trackbot> 'John' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., jfoliot, jkirkwoo, JohnRochford).

<Lisa_Seeman> ACTION: JKirkwood and Debbie Dahl to draft issue paper on coga use groups using bots including spelling,, asking for help, losing context, making mistakes, need to write the right words [recorded in http://www.w3.org/2016/07/11-coga-minutes.html#action03]

<trackbot> Error finding 'JKirkwood'. You can review and register nicknames at <http://www.w3.org/WAI/PF/cognitive-a11y-tf/track/users>.

<Lisa_Seeman> ACTION: jkirkwoo and Debbie Dahl to draft issue paper on coga use groups using bots including spelling,, asking for help, losing context, making mistakes, need to write the right words [recorded in http://www.w3.org/2016/07/11-coga-minutes.html#action04]

<trackbot> Created ACTION-173 - And debbie dahl to draft issue paper on coga use groups using bots including spelling,, asking for help, losing context, making mistakes, need to write the right words [on John Kirkwood - due 2016-07-18].

<jkirkwoo> think my user name is jkirkwoo

<jkirkwoo> nick name is johnk, sorry

LS: Will send a list of the issues to the group to see if there's any interest in developing them.

<Lisa_Seeman> next item:

<Lisa_Seeman> next item

LS: Reviewing tables take a lot of time on calls, so would like to have more preparation done prior to those calls.

<Thaddeus> Sorry I have to run a little early. I have a pull request in on emotional disabilities paper as well as modifications to task completion that I will submit a push request on.

<Lisa_Seeman> jkirkwoo

<Lisa_Seeman> https://rawgit.com/w3c/coga/master/gap-analysis/table.html

<Lisa_Seeman> action lisa rich and maybe thud to review tables as subgroup

<trackbot> Created ACTION-174 - Rich and maybe thud to review tables as subgroup [on Lisa Seeman - due 2016-07-18].

<Lisa_Seeman> next item

RS: Can focus on the tables after ARIA 1.1, might have time for that.

LS: We will look now at the end of table 2, about distractions.
... Need reminders to be available in different user-settable modalities.
... Last row - you could also have different levels of reminders for different groups of people, and how many disturbances you can handle at a time.
... The semantics need some more work

<Lisa_Seeman> https://rawgit.com/w3c/coga/master/gap-analysis/semantics.html#reminders

<Lisa_Seeman> Requirement: We require an attribute that enables different users to experience different amount of reminders based on personal preferences. Reminders are a wonderful tool for many people with cognitive disabilities. However too many reminders will be annoying or distracting for some other users.

<Lisa_Seeman> Proposed attribute: coga-reminder

<Lisa_Seeman> Supported values:

<Lisa_Seeman> basic: Reminders that over 90% of users would want,

<Lisa_Seeman> more: More would be used by over 20% of the population.

<Lisa_Seeman> extra: Extra would be used by over 5% of the population, and

<Lisa_Seeman> maximum: Maximum would be helpful for 5% of the population or less.

<Lisa_Seeman> Example:

<Lisa_Seeman> <div role="alert" coga-reminder="basic"> It is your daughter's birthday</div>

MP: Not sure if authors will know how to determine what might/might not be important to users. Levels of importance should be at the end-user level.

LS: For timeouts or urgent or critical pieces of information, the author would know

MP: Agree, but for user-specific things it is hard for the author to second-guess what are the right levels, what is important to the user. It's pretty individual.

LS: There needs to be some kind of 2-way mechanism where the generator of the message can have an initial view of what is important, and the user can tweak that through user settings.
... Maybe we can define the levels at Critical, medium and low - where critical is very time-sensitive and important information.

<Lisa_Seeman> message, messagefrom

<Lisa_Seeman> coga-message, coga-messagefrom

JK: We could have some level of relationship management and categorizing them.

LS: We would want that setting available at the operating system level.

<Lisa_Seeman> thank you mary jo

- DRAFT -

SV_MEETING_TITLE

11 Jul 2016

Attendees

Contents

Summary of Action Items

Summary of Resolutions

Scribe.perl diagnostic output