See also: IRC log
<trackbot> Date: 04 December 2014
<Kathy> https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Platform_Capabilities
<Kim> Kathy: as we are thinking of things in the note it's good for us all to have an idea of what the capabilities are, what the limitations are so what were talking about this we can either add some examples or generic examples to the document. Discussion document is in the wiki – just for task force.
<scribe> Scribe: Jan
Kathy: Think we should talk about
different device actions
... Let's start with BT keyboard
... iOS keyboard support in VO
... Limited in non-VO
... Some TAB control to different form controls...some keyboard
shortcuts
Detlev: Is it more productive to
split up capabilities into different sections
... I could take care of support for visual impairment
... Re: Zoom and text resizing
Kathy: OK great idea
... OK let's brainstorm topics
... As we go through looking at how wcag applies and uaag,
stems from device capabilities
... Important as we forward and talk about keyboard
access
... Kim updating wiki page?
Kim: Topics?
Detlev: Built in screen reader support?
Kathy: Android, iOS, Windows Phone
Jan: And BlackBerry OS
Detlev: What about Windows 8.1?
Kathy: Screen reader,
keyboard,
... Switch control
Jan: Assistive touch-type
Alan: Voice control
Kim: Mouse control
Jan: Zoom functions
Detlev: Inverse colours
Jan: Braille display support
Kathy: Color-blindness
adaptation
... Other alternative device controls (shaking,
tilting)...
... Who wants a section?
Jan: I can plug in here and there
Brent: I can put a few things in
Kim: I cabn do some speech, keyboard
Kathy: Feel free to edit list
<Kim> Jan: subsections – I tried to have a paragraph on why this is an issue. Are people assuming the keyboards are not important? Several WCAG sections are relevant – noted those. Sections on groups this can help.
<Kim> Kathy: I like this format – I think it's easy to read
<Kim> Kathy: feedback – things you think we should add, comments on the content or the way Jan has laid this out
Alan: Just wondering about keyboard functionality...
<Kim> Alan: wondering about the keyboard functionality of a device in particular – other devices that emulate keyboard
<Kim> Jan: that's one of the reasons you want to have it because if someone is using a device that emulates a keyboard
Detlev: Main case for keyboard is easier to type more text
<Kim> Detlev: the main case for keyboards is if you want to put in more text, it's slightly more efficient than using a virtual keyboard. Mobile devices replacing PCs more and more, that's an important use case.
<Kim> Detlev: discussing focus
<Kim> Jan: iit's possible on DOS where you could imagine an interface where you would need a focus, that's why the AA. But on mobile devices there isn't and a device out there which has an MS-DOS like interface so always important
Detlev: Fine point, no replacement on mobile
Kathy: Maybe add a little bit to 2.4.7 rationale
Jan: Will look at adding another sentence
Kathy: OK removing it?
All: No objection.
<scribe> Scribe: Jan
Jan: Think its confusing
Kathy: Any example of a device with physical keyboard...where this isa problem
Jan: I will add a sentence about native device buttons to keyboard accessiility
Kathy: So will remove this sections
All: No objection.
Jan: Wants to remove
Detlev: Concern with numbering...might confuse with WCAG
<jeanne> I agree that we don't want to be confused with WCAG. We could use letters.
Kathy: A lot of other notes have
numbering
... But what is confusing here, is that some of the same
numbering as WCAG
Alan: What about letters?
Jan: A.1, A.2 etc.
Alan: or maybe "m" for mobile
Kathy: OK, we will adjust
Detlev: Not mobile specific enough
All: Remove
All: Remove
Jan: Suggest remove
kathy: Mixes up numbering
Jan: Let's keep it here, and put pointers up above in gestures area
Kathy: Other comments?
Alan: Will be commenting on "Provide clear indication that elements are actionable"
Kathy: OK please keep going
through notes.
... Upcoming meetings ...Dec 11, 18
... Then 2 weeks off
Kathy: Thanks everyone
<Kathy> https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Main_Page
Kathy: If you have time go into the Platform Capabilities page
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: Jan Inferring ScribeNick: Jan Found Scribe: Jan Inferring ScribeNick: Jan WARNING: No "Present: ... " found! Possibly Present: AWK Alan Alan_S Alan_Smith All Brent Detlev IPcaller Jan Jeanne Kathy_Wahlbin Kim Kim_Patch MichaelC https joined kathy mobile-a11y trackbot You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy Regrets: Jonathan_Avila Tim_Boland Agenda: http://lists.w3.org/Archives/Public/public-mobile-a11y-tf/2014Dec/0000.html Found Date: 04 Dec 2014 Guessing minutes URL: http://www.w3.org/2014/12/04-mobile-a11y-minutes.html People with action items:[End of scribe.perl diagnostic output]