<Kim> Detlev: wondering about automatic testing for single key shortcuts – hit every Character and shift-character to see if anything happens

<Kim> Marc: I'll see if I can find out if there's a script

<Kim> Detlev: another potential for automatic is mousedown, pointer down – we want to look at all those and see whether that triggers something – same thing. Maybe there's a way of looking at scripts attached to the page and finding those

<Kim> Marc: you're right that should be fairly easy one to check for

<Kim> Detlev: I'm not sure whether such a tool would catch everything – I imply don't know

<Kim> Kathy: I can check as well. Marc if you have something already that would be great or another way of doing it

<Kim> Detlev: I can create an issue for that on get hub and we can put all responses there

<scribe> scribe: Detlev

Kim: Looking at the Low Vision thought in column H of Google sheet: https://docs.google.com/spreadsheets/d/1wRAViPfAJ4Ytqc71tGZp6gU07HNd2QQaNgtJsog-D90/edit#gid=124994642

Spacing between targets : LV confirms there is a need for that

Kathy: We should ask LV TF what would meet the need
... 2px enough?

Detlev: relationship to actual target size - if they are huge there may be no need for spacing

Jake: already mentioned that

2. Equal content requirement portrait / landscape

Detle: Is just one orientation a requirement now?

Kathy: No, not under 2.1. This would be new in 2.2 - will create a lot of pushback from designers. Some areas of sites may struggle with that requirement. May be met by spreading functionality to other views/screens

Kim: Important that LV gets involved here
... Next is Indication of gestures with e.g. icons, touch and/or device movements
... LV said it resonates with them, linked to visual affordance

Detlev referring to his note in the doc on relation to 2.5.1 and 2.5.4

Detlev: How should this information be provided? (Q to jake)

Jake: May be alleviated by alternative input means.. user had a similar question - swiping to delete email or swipe half way for further options

<MarcJohlic> Would that be a UX issue vs an AX issue?

Kim: Have examples - good work - when you first open something you get hints - glance mode with tapping, marks something, tap once or twice - in that mode you get a hand and a questionmark in a corner to toggle on and off - just as an option to provide help

Detlev: hard to turn into a requirement - might be AAA

Kim: Unclear how hard that is to implement

Marc: Is that not a UX issue?

Kim: More an AX issue because it affects ppl with motor impairments more

Jake: Back to default email client - delete or swipe half way - not clear if you do it as non-visual user
... was doabvle with SR on, but nothing exposed

Marc: Non-Visual user might not be aware of that

Jake: You could end up with the half-way situation

Marc: Still questioning if it clearly falls under AX not UX

Kim: Reducing need to swipe helps users
... Elegant instructions can support use
... when things take longer it amplifies the problems (?)

Kathy: Question to LV, is there anything on affordances that could be grouped with this one?

Kim: Next one is "Focussed elements disappearing under sticky headers/footers"
... resonated with LV TF as well

Detlev: Will be dificult to test depending on viewport width, zoom factor etc.

Kim: Next one is "Focus management when zooming / rotating / deleting elements"
... We should walk with LV on that, page refresh, context
... any questions to LV?
... Next one is "Custom gestures not preserving default / breaking touch"

Jake: had conversation with Chris - will have another call tomorrow - will explain the ins and outs on that
... will have more info soon

Kim: Jake, please update the google sheet with info gained from Chris

Jake: Will do

Kim: We should have meet-up with LV periodically, it is useful

Kathy: We should draft a proposal, then get their feedback

Kim: We could send a message to Jim with questions

Kathy: Ok, sounds good

Kim: We have draft proposals, no numbers yet

Kathy: we should get feedback from LV, then proceed

Kim: Do we have questions on bimetrics and states discernable?
... If you have more comments, put them right into the google sheet

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)

Default Present: Detlev, Kim, JakeAbma, Kathy, MarcJohlic
Present: Detlev Kim JakeAbma Kathy MarcJohlic
Found Scribe: Detlev
Inferring ScribeNick: Detlev

WARNING: No "Topic:" lines found.


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

Found Date: 17 Jan 2019
People with action items: 

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