<jallan> wayne's revisions - https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2018Mar/0007.html

<shawn> scribe: JohnRochford

low contrast borders --https://w3c.github.io/wai-intro-accessibility/fundamentals/accessibility-intro/

<shawn> We are redesigning the WAI website. We plan to announce the prototype soon (but not yet, so please wait to share info :-).

<shawn> The current design iteration has low contrast underlines under h2s and around some boxes -- that are mostly in-page contents and "asides" -- with headers. These should be subtle, and thus we do not want them to have high contrast. Contrast is not necessary, given the headers/headings (and indentation).

<shawn> For example, please see <https://w3c.github.io/wai-intro-accessibility/fundamentals/accessibility-intro/>

<shawn> I just wanted to run this by the Task Force before we announced it, to get confirmation that this is good accessibility and usability considering all users.

Shawn: WAI Website is being revised.
...
... Correction: Wants to make sure the WAI pages is usable and accessible even if the borders can't be seen.

are usable

Jim: Borders are fine.

<allanj> +1 for those borders

<shawn> Jim: subtle ones are fine. important ones are good contrast.

<laura> +1

<shawn> Wayne: OK.

+1 from Wayne

+1 from me

<allanj> close item 1

Jim asks Steve about understanding doc for Hover.

Steve: It is not ready to go.

Jim: There's a survey out to review it.

Steve: Have not yet seen the survey.

<laura> https://www.w3.org/2002/09/wbs/35422/Clearing_Understanding/

<allanj> open item 2

<allanj> https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2018Mar/0007.html

Wayne: I noticed a few editorial things in the understanding doc.

<allanj> https://www.w3.org/WAI/WCAG21/Understanding/reflow.html

Wayne: For example, no need to say "complex data tables".

<allanj> understanding survey- https://www.w3.org/2002/09/wbs/35422/Clearing_Understanding/

Wayne: No reason that table content should overflow the screen.
... Common causes are long URLs, images, and nested tables.
... I can add info about how to present that from happening.

Jim: Anyone object to adding that info?

<allanj> to accept waynes edits type +1

+1

<laura> +1

<steverep_> +1

<alastairc> Just to check - does that modify the SC text? (something we can't do)

<laura> just the understanding doc.

<alastairc> ok

So, Alastair, +1?

<allanj> TSBVI had a fail because of form controls extending off right side.

<alastairc> Hmm, this isn't correct: "*A simple table cell is one that does not contain another table."

<alastairc> hold on, dialing..

<laura> wonder if it would be better as a technique.

Jim: I will investigate flexible table cells.

<allanj> find technique for flexible form controls depending on zoom level

<allanj> add technique for data tables and toolbars

Wayne: We could do techniques to get around tables going off the page.

<allanj> current sc text

<allanj> Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: Vertical scrolling content at a width equivalent to 320 CSS pixels; Horizontal scrolling content at a height equivalent to 256 CSS pixels; Except for parts of the content which require two-dimensional layout for usage or meaning.

Alastair: Asks Wayne what is meant about "simple" table cell.
... The exception is whether the page can scroll or not rather than if the table can scroll or not.
... If something requires two dimensional scrolling, it is exempted.

<allanj> add technique for css to word-wrap: break-word for long urls.

Note from John to Alaistair: Wayne gave 3 common causes: long URLs, images, nested tables.

<allanj> add technique for flexible images (scalable)

Wayne: Understanding doc is not normative. This info will help explain what we mean.

<allanj> add technique for reflowable tables

<allanj> add technique for avoiding nexted tables

I offer to help Wayne with editorial.

Jim, your voice is quite faint.

Wayne: We could put a max resolution of 300 pixels, but agrees with John that is not advisable because it would be dependent on screen resolution.

<allanj> https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2018Mar/0007.html

<allanj> close item 2

<allanj> open itme 3

<allanj> open item 3

Laura: BBC and Boston Globe are good examples of what Alastair said.

Wayne: Lowest resolution of Mac retina display requires 500% magnification.

<allanj> add technique for zooming and content that disappears (must have a way - some mechanism to get at all content that was on page before zoom)

Alastair: Window size could be reduced to compensate.

<shawn> Eric Eggert

Wayne: Is it worth making a CSS-unit table?

Alastair: I think that already exists in the CSS specs.
... at least for standard resolutions

<allanj> close item 3

<allanj> https://www.w3.org/2002/09/wbs/35422/Clearing_Understanding/

Jim: Please review and respond to survey I just listed.

<alastairc> Have a great CSUN, I won't be there I'm afraid

<laura> bye.

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/Wants to makes sure members can see the borders.//
Succeeded: s/understranding/understanding/
Present: Jim Wayne Laura Shawn JohnRochford SteveRepsher Alastair
Found Scribe: JohnRochford
Inferring ScribeNick: JohnRochford

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

Found Date: 15 Mar 2018
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.)