W3C

- DRAFT -

Mobile Accessibility Task Force Teleconference

04 Sep 2014

See also: IRC log

Attendees

Present
Alan_Smith, Jeanne, Kathy_Wahlbin, Brent_Shiver, Detlev, jon_avila, Jan, +1.408.425.aaaa, Tim_Boland
Regrets
Chair
SV_MEETING_CHAIR
Scribe
jon_avila

Contents


<trackbot> Date: 04 September 2014

<scribe> scribe: jon_avila

kw: currently working through development of techniques. Survey has been created with new techniques that we have been discussing. Names are not final.
... Time in each call to talk about techniques. Our goal is to have a good set - either revision or new by November 18th (deadline by WCAG working gropu)..
... Asking everyone to pick up assignments. If you have not done so already please go in and select a few that you would like to work on. We have different status columns where you can mark status.

<Kathy> http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Technique_Development_Assignments

kw: All techniques need to be approved through survey process as some people can't be on call and we want to encourage people to work offline if they can't attend.
... Once approved in the TF they will then go to WCAG WG. As techniques are approved here in TF then we will send them over to the WG for approval. That way we can address issues early on so we are not in crunch in November.
... Any questions?

alan: comments on g83 about comments not being applicable direclty to mobile and only html5.

kw: fine to say that -- updated columsn and these can go to survey.
... different keyboards change for input type.

<Kathy> jon: since the technique is not about HTML5 form controls this is not applicable to mobile

detlev: If we find other things that coudl be worked on -- how should we indicate that?

kw: Fine to note that -- we won't make those changes in the TF but we will send to the WCAG WG for them to review.

<Kathy> https://www.w3.org/2002/09/wbs/66524/20140901_survey/results

kw: moving on to survey results.

Survey results

Survey item #1. New Mobile techniques

detlev: comment that survey forced him to enter an answer for each question. Different from other W3C surveys. Error message came back and all data was wiped out.

kw: could be the way it was setup -- we will check it out so it doesn't happen to other people.
... Go through people's comments so people can talk about it.

<Kathy> jon: three comments, M18 menus being resized - I need more resized, maybe should be advisory, M11 avoid using bluetooth, m7 suggest being advisory could map to principle same thing with M4 -- map Guideline 2.1

<Kathy> Jon - people are open to the idea of mapping to Guidelines

detlev: discussion of back buttons for m10 -- do developers have control over this on a web page?

kw: addressed m10, m11, m7, and m4.
... need more discussion on m18 to understand whether it is sufficient.

detlev: is this about all menus or navigation bars? Need to be more clear.

kw: including notes which each technique so we don't forget.

ja: concern over term bluetooth in m11.

detlev: also had comments on Bluetooth whether web developers have control over all aspects -- for example, different ways are available.

mike: Add to general text that big reminder that there is keyboard access to mobile deives.

kw: want to comment on what to expect in iOS and Android.

mike: whether it is Bluetooth or USB keyboard

ja: we need to define external or physical keyboard.

kw: Potentially incorporated with G202.
... Whoever does G202 should look at M11 to see if they should be separate or together.

detlev: M6 specifying input type -- sounds like g89 expecting data format examples.
... m6 and m8 seem similar.

mike: keyboard can support different types of input so it's not one to one.
... m8 is differnet from m6.

detlev: g89 and m6 could be rolled together.

kw: any objections to combine m6 and g89? None heard.

alan: m2 and m19 look to be duplicates.

kw: have differnt SC.
... sounds like m19 should be removed.
... any objections to remove M19?

jan: 1.4.4 applies better as it is the only thing that talks about the size?

detlev: expect to touch without having to resize.

jan: should be able to be resized but it has to be big enough in the first place.

detlev: seems like poor design to force the user to zoom to touch a target.

kw: I'm hearing "touch accurately without zoom".

detlev: m2 and m19 should be same thing. We could decide later what SC we map it to.

+1

kw: Any objections to marking it as same as m2 for now and whoever writes it out can decide if it needs to be separate.

Alan: m3 has a typo.

detlev: there is a touchend event -- so that is not a typo.

alan: m13 has font - does that mean font size or type?

kw: could be either but mapped to 1.4.4 so perhaps it was font size.
... changed to font size.

jan: This may not be the perfect list -- is there still opportunity to add or remove items?

kw: Yes, we have room to go back and forth on these.
... any objections for us to start assigning these out for work?
... Like to get these out by Nov 18, so please sign up for the sufficient ones. Those would be higher priority than advisory.

<Kathy> https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Technique_Development_Assignments#Mobile

kw: We'd need to write these from the template -- it takes more work than just making changes.

Survey item #2 G4

kw: any objections to g4?

RESOLUTION: G4 Accepted as propposed

Survey item #3 G9

kw: any objections?

RESOLUTION: Accepted as ammended

<Kathy> Jon: should be consistent with non-mobile

Survey item #4: g53

detlev: are there ways to explore conteext of link without leaving it using the touchscreen?

kw: include user agent notes for iOS and Android.
... Jan had the same comment.
... can leave open for now.

RESOLUTION: leave open and continue work on it

Survey item #6: SRC37

kw: Detlev had a comment about wording that it could be done in a better way.

<Kathy> https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/SCR37

kw: Do you want to keep it and send it or leave it open.

detlev: fine with that so far.

kw: If not objections, accept as proposed?

mike: is this saying that the same keystroke needs to be supported on all platforms?

RESOLUTION: leave open

kw: happy to answer questions.

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.138 (CVS log)
$Date: 2014/09/04 16:04:59 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.138  of Date: 2013-04-25 13:59:11  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: jon_avila
Inferring ScribeNick: jon_avila
Default Present: Alan_Smith, Jeanne, Kathy_Wahlbin, Brent_Shiver, Detlev, jon_avila, Jan, +1.408.425.aaaa, Tim_Boland
Present: Alan_Smith Jeanne Kathy_Wahlbin Brent_Shiver Detlev jon_avila Jan +1.408.425.aaaa Tim_Boland

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

Found Date: 04 Sep 2014
Guessing minutes URL: http://www.w3.org/2014/09/04-mobile-a11y-minutes.html
People with action items: 

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


[End of scribe.perl diagnostic output]