open item 3
jim: conflation of touch separatiohn is different from visual separation
wd: buttons with good borders have no spacing separation but have visual separation and you know they are two different buttons.
sr: its complicated.
mobile question: How many pixels in between 2 active elements on a screen meets user need on the low-vision side? Mobile TF have it at two pixels.
wd: tends to agree, because pinch zoom make space bigger
sr: agree with wayne. depends on
visual affordances on the buttons themselves - borders,
boundaries, contrast. etc
... should base it only on touch.
wd: button with wide bevels are easy to see, or inset/outset are easy to see
sr: shadows make a big difference.
jim: seems wrong to specify 2 px of background color between active elements.
sr: very complicated visually - color, contrast, borders, boundaries, bevels, inset/outset and combintations
s/copmbintations/combinations
wd: need something about inactive area, "effective separation"
<scribe> ACTION: jim to write mobile about "effective separation" - explain combinatorics for separation
<trackbot> Created ACTION-107 - Write mobile about "effective separation" - explain combinatorics for separation [on Jim Allan - due 2019-02-07].
close item 3
open item 2
jim: need people and time
wd: have biggest cell phone and still listen alot.
Jim will talk with mobile about working together.
wd: Needs help with <pre>
text. what format actually needs to be visually formatted with
<pre>. Calls out 'code'. its just easier.
... e e cumming Falling Leaf, Buffalo bill.
... there are neccessary and unnecessary uses of <pre>
... needs example to classify.
jim: elementary math, chemistry,
ascii art.
... send a request to IG list or WebAIM for <pre>
examples
close item 2
open item 1
https://docs.google.com/spreadsheets/d/1gwp30K0OJ46mtjKCwo__cCIHn6mgTl-fvn2A_ADzwEc/edit#gid=0
jim: overview.
sr: page refresh should be a
failure technique for 2.2.4
... proximity of related information - can't think what it is a
failure for.
wd: color is very difficult. spacing works ok.
sr: menu, arrow is only actionable item to expand a menu item is an issue
<wayne> https://github.com/w3c/wcag/upload/master
<wayne> div { background-color: black !important; color: white !important; }
<steverep> Regarding tiny triangles for accordions or "required" off in noman's land, see my proposal for target size - https://github.com/w3c/wcag21/issues/60#issuecomment-302480005
jim: these seem more "functional affordance" rather than "visual affordance"
trackbot, end meeting
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) Succeeded: s/topic: Wayne's stylesheet tool// FAILED: s/copmbintations/combinations/ Default Present: Jim, Wayne, SteveRepsher Present: Jim Wayne SteveRepsher Regrets: lauara shawn jason No ScribeNick specified. Guessing ScribeNick: AllanJ Inferring Scribes: AllanJ WARNING: No "Topic:" lines found. WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 31 Jan 2019 People with action items: jim 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.)[End of scribe.perl diagnostic output]