<scribe> scribe: Marc

KW: We need to put items we agree on for 2.2 into the Template

<Kathy> https://docs.google.com/spreadsheets/d/1wRAViPfAJ4Ytqc71tGZp6gU07HNd2QQaNgtJsog-D90/edit#gid=124994642

KW: First one is Spacing Between Touch Targets
... any thoughts or concerns on this one or ready to write it up?

JA: Do we have this one in the template

KW: We have a shell, I'll finish it up

<scribe> ACTION: Kathy to finish draft for Spacing Between Touch Targets

<trackbot> Created ACTION-73 - Finish draft for spacing between touch targets [on Kathleen Wahlbin - due 2019-02-28].

KW: Next one is the Orientation one: "All functionality must be available in both landscape and portrait display orientations.

(Level A)" - Does someone want to take this one on?

JA: This happens mostly in native apps - possible to fill in web, but still looking for some examples. The examples I've found have been native.
... hybrid versions I've found seem to fit under the new Reflow SC
... found that there are more options in my mobile phone - we need to have some clear examples where these fail in mobile websites.

KW: This SC would be specific about adaptive layouts - not responsive

JA: Would it be a good idea to have 2 or 3 examples before we start on this one?
... my initial examples were all native - wasn't clear that native wasn't in scope initially.

KW: It's not that WCAG guidance can't apply to native, but rather that as we write these we write them with a web focus. If you look at examples of adaptive layout you'll see where this issue happens.
... Does anyone want to try to get some examples of apps using adaptive layout to demonstrate this?

JA: I'll try to search for some

KW: Next SC would be Indication of Gestures: "When (hidden) functionality is available via gestures or movement, the user is informed of / instructions are available for, the method on how to use them, can be turned off, and can also be operated by user interface components via alternative ways.

(Level AAA) or Technique"

MJ: If this is AAA is it worth pursuing right now?

KW: It's worth pursuing to get folks thinking about these issues - and as technology improves this could be handled

KP: Agree

KW: Jake will take that one on

<scribe> ACTION: JakeAbma to put Indication of Gestures into template

<trackbot> Error finding 'JakeAbma'. You can review and register nicknames at <https://www.w3.org/WAI/GL/mobile-a11y-tf/track/users>.

<scribe> ACTION: Jake to put Indication of Gestures into template

<trackbot> Created ACTION-74 - Put indication of gestures into template [on Jake Abma - due 2019-02-28].

KW: Next SC is the States Discernable - AAA
... Point of this one - the affordance - is having something that indicates that an item is actionable

MJ: Will check to see if there is anything spelled out in our new Carbon Design System - or IBM Design Language around this.

KW: Will share sample SC language for consideration
... Jake do you have some suggestions or anything from designers on some language to start this draft?

JA: Maybe we tell folks that it must be distinguishable from all other content - rather then telling them specifics that they have to do to items

<Kathy> https://docs.google.com/spreadsheets/d/1wRAViPfAJ4Ytqc71tGZp6gU07HNd2QQaNgtJsog-D90/edit#gid=124994642

JA: Are we talking about that it's clear what items are - buttons are buttons, links are links? Or are we talking about states?

<kim> Here's the link to the folder that includes the spreadsheet: https://drive.google.com/drive/folders/1Q9md2AvmeTgvsT9GB62BsGvCaalDGtE6?usp=sharing

DF: In terms of being distinguishable that's usually a given - the question is whether something like a link that looks like a link but has a role of button and acts like a button - would that fail?

<JakeAbma> https://github.com/w3c/wcag/issues/559

KW: We'll regroup next week on this one. I've put next steps into the Google doc.

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)

Default Present: (no_one)
Present: (no_one)

WARNING: Fewer than 3 people found for Present list!

No ScribeNick specified.  Guessing ScribeNick: MarcJohlic
Found Scribe: Marc

WARNING: No "Topic:" lines found.


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

Found Date: 21 Feb 2019
People with action items: jake jakeabma kathy

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