See also: IRC log
<trackbot> Date: 19 February 2015
<scribe> scribe: Detlev
Kathy apologizes due to snow emergency
Jeanne knows where commenrs are - checking
<marcjohlic> http://w3c.github.io/Mobile-A11y-TF-Note/
(Michael checking github for note comments)
Kim: We got approval to publish
note
... Version will be published as draft
... Comments can be worked through then
<MichaelC> https://www.w3.org/WAI/EO/wiki/Mobile_Accessibility_Note_-_EOWG_Review_Feb_2015
MC found something on EO mailing list
(everyone taking a few minute to read comments)
MJ: Wondering about techniques that are "poor development and UX practices"
<Kim> https://www.w3.org/WAI/EO/wiki/Mobile_Accessibility_Note_-_EOWG_Review_Feb_2015
One comment: "Mobile" screen size is the wrong term
"viewport?"
MJ: alternatives more wordy
JA: Physical screen size also
important
... Is comment specific to place, or general?
Kim: probably wider
... Can't see a better version
AS: The browser viewport not the desktop as a whole
<marcjohlic> How about appending the bullet w/ part of her sentence: "web pages utilizing responsive design can transition into a "mobile" screen size even on a desktop/laptop when the browser viewport is resized or zoomed in"
JA: We want to express the
commonality between different environments like desk
... likes Marcs suggestion
<jon_avila> +1
MJ: quotes were used ti indicate that mobile was not to be taken literally
<Alan_Smith> I like Marc's revision as well.
*
1+
RESOLUTION: Take Marc's suggestion above top amend 1.1
+1
<marcjohlic> +1
<jon_avila> +1
<Kim> +1
<jeanne> +1 publish
<Alan_Smith> +1
RESOLUTION: Note published as first public working draft
JS: We asked for feedback to
getting input on where we should go
... explaining feedback questions
... 2nd Queston: is info helpful for developers?
... If people have suggestions, that would be good
Kim: Q 2 might be too narrow - we want to reach beyond app developers
JA: There are gov agencies, testers etc who are also addressees
TB: use "designers, developers, and testers"?
JEanne: not to forget policy makers
JA: or come uip with a term that
includes everybody
... have customers that do not consider mobile scenarios
... stuff behind government firewalls
Kim: aren't they also using mobile devices?
JA: mobile may be rules out (cameras, mics)
JS; add policy makers
Kim: differentiate mobile content and mobile apps
JS: we want to make sure that native apps are included
<Kim> mobile apps or content that can be viewed with mobile devices
AS: Likes Kims suggestion "content that can be viewed on mobile, and mobile apps"
<jeanne> Is the format of this information helpful for designers, developers, testers and policymakers of content that can be viewed on mobile, and mobile apps?
JS: rephrasing audience description for notw
<jeanne> Is the format of this information helpful for content, designers, developers, testers and policymakers that can be viewed on mobile, and mobile apps?
JS: Group should approve this
today if possible
... question whether reframing WCAG techniques is useful for
mobile content / app creators?
<jeanne> In Appendix A, is listing potentially applicable existing WCAG 2.0 techniques helpful for mobile content and mobile app developers?
AS: suggests "applicable" (rlevant, useful)
<jon_avila> +1 to relevant
<jeanne> In Appendix A, is listing relevant existing WCAG 2.0 techniques helpful for mobile content and mobile app developers?
+1
<Alan_Smith> +1 for relevant
<marcjohlic> +1
JA: Q4 (is it comprehensive?)
could generarte a lot of comment
... Are we asking people to contribute stuff beyond WCAG
JS: There is already stuff in the
note that cannot be attrivuted to particular SC /
guidelines
... "related to WCAG principles"
<jeanne> Are there additional accessibility needs in mobile content related to the WCAG principles that we should address?
JA: better say "mobile content"
rather than "mobile devices", then link to WCAG
principles?
... Accessing content in a mobile environment.. to get away
from devices?
<jeanne> Are there additional accessibility needs in mobile envirnonment related to the WCAG principles that we should address?
1+
<jon_avila> +1
<marcjohlic> +1
<Kim> suggested rewording of #2:
<Kim> Is the format of this information helpful for designers, developers and testers of content that can be viewed with mobile devices and in mobile apps? Is it useful for policymakers?
<jon_avila> +1
+1
JS: we have to be careful not to
imply that we are changing WCAG
... Are there suggestions for any other questions?
... people tend nto to answer too specific questions
Kim: Do we cover the issue that content will often be directed both at desktop and mobile? Is that covered?
<Alan_Smith> Sorry had to drop on one browser and open in another on my tablet
Kim: There was a big discussion on keyboard accessibility for mobile
<jeanne> Have we sufficiently explained why keyboard interface and modality independent controls are needed in the mobile environment?
1+
<jon_avila> +1
<marcjohlic> +1
<Alan_Smith> _-1
<Alan_Smith> +1
(Discussion on face 2 face at CSUN)
<jon_avila> Thanks!
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) WARNING: Bad s/// command: s// Found Scribe: Detlev Inferring ScribeNick: Detlev Default Present: Kim_Patch, Alan_Smith, TomB, Detlev, Marc_Johlic, +1.978.760.aaaa, Jeanne, Michael_Cooper, +1.703.637.aabb, jon_avila Present: Kim_Patch Alan_Smith TomB Detlev Marc_Johlic +1.978.760.aaaa Jeanne Michael_Cooper +1.703.637.aabb jon_avila Regrets: Jan_Richards Agenda: http://lists.w3.org/Archives/Public/public-mobile-a11y-tf/2015Feb/0020.html Found Date: 19 Feb 2015 Guessing minutes URL: http://www.w3.org/2015/02/19-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]