<Kathy> https://drive.google.com/drive/folders/1Q9md2AvmeTgvsT9GB62BsGvCaalDGtE6

Kathy: document for the examples, and techniques list
... spent some time today going through those items and see if we get some examples or start thinking about some of these
... meeting on Tuesday – anything on any of the four from mobile

Jake: Just dragging

<Kathy> https://docs.google.com/document/d/1LaVX-RTaLQL0tN4G3NhOTlmj16swt0VzC7ssaAjqIwg/edit

Jake: keyboard alternative for dragging should be covered already for keyboard, again thinking if it should be part of pointer gestures and discussion about what is a drag versus a swipe

<Kathy> https://docs.google.com/document/d/13QWLthBoEU6xuJQ4UrYOwuvJp0a42Z70JRjAsjtv1m4/edit

Kathy: I do think maybe we should hold off on implementation examples for that one because were not sure where it's going to go
... there's been a lot of back-and-forth on that one in particular – thanks for the summary

Jake: I think Detlev is trying to get the dragging part in 2.5.1 and then there was some pushback, now thinking about making it just one success criteria

Kathy: this was taken out of 2.1 because of objections – we'll see how that goes. Will put that on the agenda for next week
... we need examples and we also need to start building out the techniques list
... let's focus on touch target, All functionality in both orientations
... all functionality in both orientations – where this is not implemented well is scanning a check in online banking
... often scanning a check will be locked into one orientation – that's a good example because is it essential or not for orientation?
... as far as being well implemented the majority of the sites that are out there have both orientations
... we can add examples – Amazon.com is a good example of going in both orientation

Jake: with orientation there's also something with locking the screen
... this example is just locking with width and height, the interesting part is you can see it in two different ways. In portrait mode it tells you please turn your mobile device, but when you turn your mobile device the only thing it does is show other content in another container. So you're not locking your content, just showing different content on the basis of the width and height.

https://m.nl.investing.com/commodities/crude-oil-advanced-chart

Kathy: success criteria isn't about locking

Jake: but in this case very usable for this success criteria, but if you go into the layer underneath how you technically solve this same technique is also used for orientation – that makes it a blend
... we can use this example would just to give you an idea – the only thing it does is look at the within the height and show one container or show the other container

Kathy: I think this is a good one to look at. We did have the essential type exclusion from that. So you could make the argument that there's no way to present the same information – need a minimum screen size to be able to look at that.
... I also wonder if we have a much larger device – more of a tablet size where you can go from portrait to landscape mode if that makes any difference – can you do it on that platform
... success criteria differences – would fail 2.1 because that states that all the functionality and content is available in both orientations
... this is what was taken out of the first one
... any other examples or implementations with issues

Jake: it would be good to have more – I will try to find a couple more

<scribe> ACTION: Jake will find a couple more examples for All Functionality Available in Both Orientations

<trackbot> Created ACTION-81 - Will find a couple more examples for all functionality available in both orientations [on Jake Abma - due 2020-01-16].

Kathy: Instructions for custom interactions
... do we know of any good websites that actually do have instructions for custom interactions?

Jake: I think it would be possible for us to define a standard list of standard interactions – I think that's getting some support. Standard interactions are those interactions which have been around for the last 20, 30 years for computers keystrokes and mouse.
... they work and hold over time, they are not changing
... Standard interactions have stood the test of time
... with Gmail, J or R etc. new post, those will all be custom interactions and those are documented. Also websites with access keys. Those are not standard. It would be great to see examples brothers not just one action attached more than one or revealing other ones using a slide.
... and then even more complicated gestures probably not documented
... but we need that list and consensus about list
... I can work on it a little more – I stopped halfway to get feedback.

Kathy: I think we should start putting in some examples based on that and we can still work on the definition of what a standard interaction is

Jennifer: one example I didn't notice until yesterday – on YouTube if you have your mouse hovered over the pause button it says pause and then in parentheses it says K, which I think means that you can use the K key to to pause YouTube videos

<MarcJohlic> Yep - it works

<Kathy> https://www.nngroup.com/articles/mobile-instructional-overlay/

github example – single key shortcuts, click on help at the very bottom of the screen if you're not signed in, click on avatar if signed in, not that easy to find, but it's there

Kathy: more examples for spacing between touch targets – maybe we can work on that later this week and regroup on that next week

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: JakeAbma, MarcJohlic, Jennifer, Kathy, kim_patch
Present: JakeAbma MarcJohlic Jennifer Kathy kim_patch
No ScribeNick specified.  Guessing ScribeNick: kim_patch
Inferring Scribes: kim_patch

WARNING: No "Topic:" lines found.

Found Date: 09 Jan 2020
People with action items: jake

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


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