<LisaSeemanKestenbaum> clear agenda
<LisaSeemanKestenbaum> scribe: JohnRochford
<steve> boy webex is getting complex to join!
Lisa: we want to get publications out as soonn as possible
<kirkwood> had a really difficult time with webex… dialing in…
Lisa: Is the proofing
complete?
... Steve and Jan added a lot of changes.
... Anyone need more time to review?
Steve: Doc is very hard to read - is it in landscape mode?
Shari: Yes to Lisa's offer of another week for review.
<LisaSeemanKestenbaum> https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2018Aug/0030.html
Lisa: We discussed modifying John Rochford's easy-reading summary. Is it necessary to change it given doc recent modifications?
<LisaSeemanKestenbaum> ACTION: jan to make second draft of easy reading summary
<trackbot> Created ACTION-293 - Make second draft of easy reading summary [on Jan McSorley - due 2018-09-13].
<LisaSeemanKestenbaum> https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2018Aug/0030.html
John R is very interested in how Jan will make his easy-to-read summary easier-to-read.
Steve says the word "abstract" is abstract itself.
Jan: I understand what what Lisa and Alastair are saying is that the W3C has its own format.
Alastair: Yes, there are restrictions.
Jan: W3C's format may not the best for cognitive disabilities if it excludes easy-to-read summaries.
Alastair: There may be other places, such as the WAI section, which have a better format for reading, are less restricted, and easy-to-read versions could be placed there.
Jan: Asks Alaistair for the guidance about why an easy-to-read summary would not be included in standards docs.
Alastair: Will try.
John R admires how much better Jan expresses his concerns than he is.
Lisa: Suggests we consult with Janina about this.
Lisa suggests we change abstract to easy-to-read summary.
<kirkwood> +1 to abstract being an easy reading summary
Lisa suggests we add editor's notes that say we will make sections easy-to-read and that follow the correct format.
Lisa: My strong suggestion is that we copy over content from WCAG.
<Jan> Jan present+
Steve: Downside is that some sections are quite large.
<LisaSeemanKestenbaum> more works - coping the wcag proposal beifits section and text with editors knows to redo for easy reading and tempate
<LisaSeemanKestenbaum> +1
<Jan> 0
0
<steve> +1
<Jennie> 0
Lisa: Should we do a few of them
and evaluate?
... Should we do it because there are no objections?
<LisaSeemanKestenbaum> 4. Make it clear what are controls and how they should be used (Technical details: On (Jan)
<LisaSeemanKestenbaum> coga github: visually-clear-controls.html wcag issue 36
<LisaSeemanKestenbaum> https://github.com/w3c/wcag21/pull/103)
<LisaSeemanKestenbaum> https://github.com/w3c/wcag21/issues/36
Lisa: I think we should do it since there are no objections.
<LisaSeemanKestenbaum> https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2018Aug/0056.html
Lisa: Which ones are people prepared to do of the ones we have on that page?
<LisaSeemanKestenbaum> - Avoid too much content on the page - Make the purpose of each section clear merge - Make it clear what are controls and how they should be used - Make it easy to find the most important things on the page(john kirkwood) - Use a clear navigation (half) - Make it easy for the u
<LisaSeemanKestenbaum> - Avoid too much content on the page
<LisaSeemanKestenbaum> - Make the purpose of each section clear merge
<LisaSeemanKestenbaum> - Make it clear what are controls and how they should be used
<LisaSeemanKestenbaum> - Make it easy to find the most important things on the page(john
<LisaSeemanKestenbaum> kirkwood)
<LisaSeemanKestenbaum> - Use a clear navigation (half)
<LisaSeemanKestenbaum> - Make it easy for the user to undo actions
<LisaSeemanKestenbaum> - Avoid data loss and “time outs”
<LisaSeemanKestenbaum> - Provide feedback (Shari)
<LisaSeemanKestenbaum> - Tell the users about any fees and charges at the beginning of a task
<LisaSeemanKestenbaum> - The user knows when the content changes
<LisaSeemanKestenbaum> - Avoid interruptions
<LisaSeemanKestenbaum> - Avoid too much content on the page
<LisaSeemanKestenbaum> - Provide help (which includes make it easy to find)
<LisaSeemanKestenbaum> - Provide human help
Steve agrees to do a couple.
Jennie offers to do a couple.
<kirkwood> yes
John K will do the ones with his name listed on them.
<kirkwood> ok I should put my name next to one or two of them correct.
John R to John K: Your name is already listed next to one or two.
<LisaSeemanKestenbaum> Help users understand what things are and know how to use them
<LisaSeemanKestenbaum> Understand Actionable Elements
<kirkwood> interactive elements?
<kirkwood> clickable?
<kirkwood> ok then we can remove
Lisa: Do we orient our terminology to Web developers or others?
<LisaSeemanKestenbaum> Help users understand what things are and how to use them
Lisa: Are we using Stack Overflow terminology?
<LisaSeemanKestenbaum> users understand what things are and how to use them
<LisaSeemanKestenbaum> undandandable elements
<LisaSeemanKestenbaum> undandandable elements - users understand what things are and how to use them
<Jan> +1 to understandable elements - users understand what things are and how to use them
John R suggests "understandable elements (what things are and how to use them)
<shari> +1 to understandable elements - users understand what things are and how to use them
<LisaSeemanKestenbaum> +1 to understandable elements - users understand what things are and how to use them
<Jan> +1 to John R's suggestion
John R suggests format "technical term (simple explanation)
"
Steve asks who our audience is.
John R to Lisa: Must go now. Will be out the next 2 weeks.
<LisaSeemanKestenbaum> 1. wide an audence inside content devlopers including people just adding text to a template
<LisaSeemanKestenbaum> 2. limit to "profetional web devlopers " (mid level and up )
<Jan> Sorry - had to drop for another call
<LisaSeemanKestenbaum> +1
<LisaSeemanKestenbaum> (with an advanced tag)
<LisaSeemanKestenbaum> steve : use advaced tag)
<steve> 1
<Jennie> I like the advanced tag idea
<steve> with Advanced tag
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/There may be other places, such as the WAI section, in which easy-to-read summaries should be placed./There may be other places, such as the WAI section, which have a better format for reading, are less restricted, and easy-to-read versions could be placed there./ Succeeded: s/quire/quite/ Succeeded: s/some/a couple/ Succeeded: s/are/our/ Present: LisaSeemanKestenbaum JohnRochford Jennie kirkwood shari Found Scribe: JohnRochford Inferring ScribeNick: JohnRochford WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting 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: jan 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.)[End of scribe.perl diagnostic output]