See also: IRC log
<trackbot> Date: 06 June 2014
<Kathy> http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/New_WCAG_2.0_Techniques
<Kathy> http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/New_WCAG_2.0_Techniques
<KimPatch> http://lists.w3.org/Archives/Public/public-mobile-a11y-tf/2014Jun/0000.html
kw: follow-up discussion on item 13 design clickable objects to look clickable
jeanne: Last week we talked about
button appearance is inconsistent across platforms. Talked
about testability.
... meet w/ Kathleen, and Alan and talk about different
platforms and small group decided that it was an accessibility
issue for people with cognitive impairments
<jeanne> http://www.w3.org/WAI/UA/IMPLEMENTING-UAAG20/#sc_131
jeanne: couldn't find specific
WCAG SC but there is a UAAG 1.3.1 and for 1.3.2 requires class
of objects with custom appearance and different ways these can
be highlighted.
... small group recommend leave as BP for now because there is
no WCAG SC but reference UAAG 1.3.1 and 1.3.2. Advise to tell
author to code them so they have semantics as buttons that way
the platform can change how they are rendered to appear as
buttons.
kw: Are you recommending a new
name for this?
... suggested new name might help it to fall under WCAG 1.3.1
Info and Relationships
... any comments or disagreement? None heard. Thanks for
organizing meeting
<Kathy> https://www.w3.org/2002/09/wbs/66524/20140512_survey/results#xq5
RESOLUTION: Modify item #13 from survey text and name and reference UAAG and be a ST under 1.3.1
<jeanne> New title: Code active elements semantically so they can be customized by the user agent
TOPICI: #4 from Survey
kw: wanted to ask about what it was saying - are we talking about HTML5 input type?
jan: Thinks it is related to
HTML5 semantic input text. Has concern that user agent needs to
be smart about when keystrokes are ignored, e.g. letters don't
enter when it expects number.
... also concerned about format.
kw: If we did this specific to HTML5 and then reference techniques for instructions rather than including it. Would that cover it?
jan: possibly technique under 1.3.1
kw: agress under 1.3.1
alan: what about mobile apps? We could have another technique.
kp: question about speech users
where app is not listening for what you are speaking.
... User needs to know what key type app is listening to.
ja: SC 3.3.2 may also be relevant
to this technique.
... relevant to desktop but more an of an issue to mobile.
kp: Affects VO and speech users.
kw: put in Jon's point about affecting what keyboard is shown on mobile device -- will add and see how we can incorporate this into the technique - will likely require multiple techniques for #4.
kw: Comments all over the board. Some people may want to focus specific settings.
jan: technique should be very granular. How do you program this in iOS vs. Android. Windows has a high contrast mode whereas other's have invert colors.
<scribe> scribe: jon_avila
kw: should we break up or keep together? Differences between platforms would be hard to maintain. If we did this as one, would this be advisory, best practice, of ST? and what SC?
jan: captions are one example of play captions if user has set them. Do something smart with user settings. Different from SC 1.2
ja: UAAG perhaps, also Section 508 type requirement.
jan: can generic refer to flags that browsers and apps can set.
ja: iOS 8 has new flags to check for user requesting bold text, etc.
kw: Mark as new SC/best practice because it currently doesn't map to WCAG or UAAG, any objections?
kw: responses were all over the place?
jan: may depend on if it was apps or web.
kw: this would apply to native
apps as we already have prior one for HTML5?
... perhaps 4.1.2?
... may not have SC and something we should consider down the
road.
kw: Detlev says page scroll will
vary a lot based on device. Jan had similar comment.
... no mappings to SC at this point.
ja: h2 sounds a lot like this.
kw: Any thoughts on why this might be an advisory?
jan: thinking about situations where one group awakens another controls - a larger relationship.
ja: ST under 1.3.1 for grouping links.
kw: is this already covered under current ST?
RESOLUTION: would be to very and make sure we have this covered under current ST and add a mobile example to those.
kw: varying comments
jan: what's the alternate, there might be times were you want a long banner.
kw: anyone disagree with keeping this a bp?
jan: concern over width - mm would be better than percents as device sizes are different.
kw: don't see falling under any SC
ja: reachability about using with
one hand while holding and pressing a button.
... best practice
kw: keep at best practice
... last one to go through for this meeting.
... last call wed did 11,12,13,and 14. Next call we will pick
up on #15 from the survey.
... can pick up and talk about iOS and browser settings if you
have time.
... Any questions?
list attendees
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) Succeeded: s/techniques/comments/ Found Scribe: jon_avila Inferring ScribeNick: jon_avila Default Present: +1.617.577.aaaa, Kathy, Kim_Patch, Jeanne, wuwei, Jan, [IPcaller], Alan_Smith Present: +1.617.577.aaaa Alan_Smith Jan Jeanne Kathy Kim_Patch [IPcaller] jon_avila wuwei Regrets: Kathleen Gavin Detlev Found Date: 06 Jun 2014 Guessing minutes URL: http://www.w3.org/2014/06/06-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]