W3C

- DRAFT -

Mobile Accessibility Task Force Teleconference

30 Apr 2015

Agenda

See also: IRC log

Attendees

Present
Kim_Patch, Detlev, Marc_Johlic, Jeanne, jon_avila, Henny, AWK
Regrets
David_MacDonald, Alan_Smith, Kathy_Wahbin, Jan_Richards
Chair
Kimberly_Patch
Scribe
Detlev

Contents


<trackbot> Date: 30 April 2015

<scribe> scribe: Detlev

Perceivable Best Practices

http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Perceivable_Techniques

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

<Kim> http://w3c.github.io/Mobile-A11y-TF-Note/

Kim: M-numbered techiques from original assignments
... Anything under small screen size that can translatr to best practice or technque?

Jon: Difference betweeen small screen size and magnification

Jon; sent an email about that to list

<Kim> https://lists.w3.org/Archives/Public/public-mobile-a11y-tf/2015Apr/0026.html

Jon: Under zoom there is a larger topic: resize text, restrictions on elements that will not zoom, for example

Marc: Is that adressing failures or techniques?

Jon: Failures should be mire general, techniques more specific
... issues with VW units
... issues arise because screen size is smaller

Jeane: what is this CSS issue (esantd zto pick up elsewhere)

Jon; VW units define size relative to the screen width

<jon_avila> http://codepen.io/vcurd/full/ByerKw

Jon: used to preserve the look of something regardless of font size
... There's a discussion on the mobile a11y list around that
... Issues aries on mobile due to small size - needs more testing

Jeanne: Text did enlarge in Firefox (desktop)
... VW units does not restrict resizing but defines the way it does
... many things thst crop up that go unnoticed so importsant to call them out

Kim: looking at example on iphone and all lines are enlarging

Marc: Looking on it on an Android and it works there, too - not just increasing the font size but everything

Kim: different scenarios, mobile and desktop - different to define common rules

Marc: middle line starts of smaller than on desktop (Chrome on Android)

Jeanne: Need to set up better test - having a hard time finding out how it is coded, there are many other things in that example

Kim: Opening it in Vivaldi - lines initially the same size

<marcjohlic> .vws {

<marcjohlic> font-size: 1vw;

<marcjohlic> }

<marcjohlic> <p class="vws">

<marcjohlic> The font size of this paragraph is set in viewport…

<marcjohlic> </p>

Jeanne: aparently very different browser implementations

Kim: Other issues / technique?

https://www.youtube.com/watch?v=eMC3Ev7CaDw

Captions not visible on mobile devices - they can be made visible on desktop, not in Chrome on Android - possibly leading to a technique .. not sure

Jon: are captions turned on on the OS settings? In this video they are nit displayed even with captions enabled on the OS level

Kim: anyone with devices where captions are enabled and ARE shown?

may be control missing

Kim: No luck in Safari iOS

Henny: in Youtube app on iOS it says no captions available

<jeanne> jeanne: I have captions turned on in iOS 8.3 and am not seeing captions or a control to turn on captions in Ted.com player in Safari.

Marc: wondering if the auto-generating feature does not work on mobile or if they supplied a caption file

Kim: How would a TED video be different?

Marc: works fine in TED app

Jeanne: DId not open captions in Safari

Marc: Android /Chrome does not offer a caption option to enable captiond

Andrew: on iOS and Android it is doen for OS preferences / caption setttings

Marc: Captions on on Nexus five, still not shown
... Player doesnot honour settings - is it an issue for web developers?

Kim: Not getting captions on TED video when downloading

Andrew: three verical dots show caption button -

Jon: but not on the example sent earlier -

Marc: may be down to being explicitly provided vs. auto-generated

<jon_avila> https://www.youtube.com/watch?v=BEQ-wfJisBA

Marc: TED app on android dod provide captions not seen via Chrome

<AWK> I'm sure that we could get the low-down on how youtube does this via Loretta or Ken Harrenstein

UAAG or WCAG issue?

Jeane: more a UA issue should be flagged

Kim: should be put into the use cases
... TED app works on ANdroid, browsers did not
... jeanne, where's the best place for it?

Jeanne: taking note for UAAG
... Separate WIKI page for UAAG issues related to mobile

Kim: Also check on a variety of browsers
... Getting back to perceivable techniques related to small screen size? Everythign covered?
... ANythign on zoom mag issues
... Contrast? Anything mobile techniques / best practices here?

Jon: Issues related to calculate point size at which you apply lower contrast requiremnets (3:1)
... We need a sufficient technique for people to test that - its in the mobile note
... Will come up with wording
... Possibly also advisory techniques with more stringent contrast requirements

Detlev: Check where a11y features set at OS apply to browser content

Jon: If it works users can be asked to turn on settings to achieve higher contrast

Kim: What is the situation across OSs?

Jon: easy on iOS but there are many Android skins where OS setting may be supported or not

Kim; can we rely on that then? How do we handle that?

Jeanne: WCAG can say where the technique applies (bound to OS ect)
... has to be handled by differentiating betwen different OS / UA etc

Like Accessessibility support - if not sufficiently supported then it is not a good candidate for a sufficient technique

Jeanne: Zakim is going to be phased out (end of June)

MIT has stopped funding Zakim so we need to move to WebX

<jeanne> WebEx

WebEx can call US!

Zakim will not tell us who is on the call

Jeanne: we are losing some and gaining some

Andrew: Trials to day with iOS app - worked well - there may be a11y issues
... Talking about a11y settle ment (quoted above)

<marcjohlic> http://www.html5rocks.com/en/tutorials/track/basics/

<marcjohlic> http://iandevlin.github.io/mdn/video-player-with-captions/

Andrew: mobile TF was referenced even if it wasn't normative

<marcjohlic> https://developers.google.com/youtube/2.0/developers_guide_protocol_captions

Marc: HTML5 video & track element seems to work -
... Note at broad audience to look at features - some confusion due to different numbering of mobile note vs. WCAG numbering

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.140 (CVS log)
$Date: 2015/04/30 16:05:14 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: Detlev
Inferring ScribeNick: Detlev
Default Present: Kim_Patch, Detlev, Marc_Johlic, Jeanne, jon_avila, Henny, AWK
Present: Kim_Patch Detlev Marc_Johlic Jeanne jon_avila Henny AWK
Regrets: David_MacDonald Alan_Smith Kathy_Wahbin Jan_Richards
Agenda: https://lists.w3.org/Archives/Public/public-mobile-a11y-tf/2015Apr/0023.html
Found Date: 30 Apr 2015
Guessing minutes URL: http://www.w3.org/2015/04/30-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]