19 Jul 2018


janina, kirkwood, Glenda, LisaSeemanKestenbaum, Roy, MichaelC
Glenda, John_Rochford


<LisaSeemanKestenbaum> agenda

<scribe> scribe: janina

<LisaSeemanKestenbaum> scribe: Janina


None from me

jk: No, don't think so, but maybe

ls: Propose we'll keep meeting and work on the doc, even if we don't have quorum to make decisions
... JK? TPAC?

jk: No

<LisaSeemanKestenbaum> no quarum

ls: two items ready for review
... Looking for direction--they're close

<LisaSeemanKestenbaum> https://docs.google.com/document/d/1WcfVALVq8PS9CLXUuAfV9Op0wXvI2yJYedj5jO23GTk/edit#heading=h.msly33vnkwe6

<LisaSeemanKestenbaum> Make the structure and relationships clear

<LisaSeemanKestenbaum> Clear dividers between different sections that may have separate controls or a scroll bar

<LisaSeemanKestenbaum> Clear dividers around areas with different functions, such as call out boxes, navigation bars, and advertisements

<LisaSeemanKestenbaum> Sub-menu items that are clearly associated with the main menu items under which they fall.

<LisaSeemanKestenbaum> The tool bar and controls are visible

<kirkwood> ‘are always visible’ might be better?

js: Suggests cross referencing requirements on programmatic exposure of structure and groupings

ls: Notes examples, e.g. borders
... WCAG 1.3.1
... should it be separate that we want menu items clearly grouped and associated with the menu item under which they fall
... Should that be a separate comment?

jk: prefer separate req

ls: done
... controls that affect only portion of a page ...
... e.g. when there may be more than one scrollbar, each affecting a different region of the page ...

<kirkwood> Avoid multiple scrolling areas on a page

jk: Avoiding multiple scrolling areas/regions in a page?
... Each region and its associated controls just need to be clearly delineated

<kirkwood> visually apparant

<LisaSeemanKestenbaum> Each region and its associated controls can be clearly recognised

<LisaSeemanKestenbaum> Each region and its controls can be clearly recognized

<kirkwood> agree

ls: we'll suggest avoiding multiple scrollable regions
... Also have examples of failures--bad practice

<alastairc> Gov.uk has pretty recognisable regions. https://www.gov.uk/

<alastairc> screenshot of gov.uk with aria-roles highlighted. https://usercontent.irccloud-cdn.com/file/Zv08pNWw/gov-uk-sections.png

ls: Looking at the section that talks about supporting personalization ...
... complicated, and probably needs a bit more work to clarify things

<johnkirkwood> sorry due to a tech issue, kicked out of doc. could put link back in here

<LisaSeemanKestenbaum> https://docs.google.com/document/d/1WcfVALVq8PS9CLXUuAfV9Op0wXvI2yJYedj5jO23GTk/edit#heading=h.msly33vnkwe6

<LisaSeemanKestenbaum> https://docs.google.com/document/d/1WcfVALVq8PS9CLXUuAfV9Op0wXvI2yJYedj5jO23GTk/edit#heading=h.1c3z8hl2ynl6

ls: Will continue to work on this ...
... Asking people to work on design criteria language
... Believe we're not far away from publishing a useful draft
... Notes the first one is the best formulated so far, so a good example of what we need

<johnkirkwood> can you put a link to the first one ?

jk: asks for link

<johnkirkwood> mentioned as a good example

<LisaSeemanKestenbaum> https://docs.google.com/document/d/1WcfVALVq8PS9CLXUuAfV9Op0wXvI2yJYedj5jO23GTk/edit#heading=h.729zggqj0s8d

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2018/07/19 15:02:48 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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)

Default Present: janina, kirkwood, Glenda, LisaSeemanKestenbaum, Roy, MichaelC
Present: janina kirkwood Glenda LisaSeemanKestenbaum Roy MichaelC
Regrets: Glenda John_Rochford
Found Scribe: janina
Found Scribe: Janina
Inferring ScribeNick: janina

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting

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

[End of scribe.perl diagnostic output]