- From: Kim Patch <kim@redstartsystems.com>
- Date: Thu, 12 Oct 2017 12:18:45 -0400
- To: "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>
- Message-ID: <59DF95E5.1030902@redstartsystems.com>
*MATF Minutes 12 October, 2017 link:
https://www.w3.org/2017/10/12-mobile-a11y-minutes.html*
Mobile Accessibility Task Force Teleconference
12 Oct 2017
See also: IRC log <http://www.w3.org/2017/10/12-mobile-a11y-irc>
Attendees
Present
patrick_h_lauke, Kathy, JakeAbma, marcjohlic, Melanie, Kim
Regrets
Chair
Kathleen_Wahlbin
Scribe
patrick_h_lauke, Kim
Contents
* Topics <https://www.w3.org/2017/10/12-mobile-a11y-minutes.html#agenda>
1. Device sensors
<https://www.w3.org/2017/10/12-mobile-a11y-minutes.html#item01>
2. concurrent input mechanisms
<https://www.w3.org/2017/10/12-mobile-a11y-minutes.html#item02>
3. Orientation
<https://www.w3.org/2017/10/12-mobile-a11y-minutes.html#item03>
* Summary of Action Items
<https://www.w3.org/2017/10/12-mobile-a11y-minutes.html#ActionSummary>
* Summary of Resolutions
<https://www.w3.org/2017/10/12-mobile-a11y-minutes.html#ResolutionSummary>
------------------------------------------------------------------------
<Kathy> Kim - i am having network issues. I am trying to join the webex
<Kathy> I am still trying to connect to WebEx
<Kathy> is anyone else having problems?
<MelanieP> not here
<patrick_h_lauke> working for me (using app directly, rather than
phoning in)
<Kim> Working for me, I phoned in
<patrick_h_lauke> early warning: will need to leave around 20 minutes to
the hour to go pick up my little one i'm afraid
<Kathy> Is Kim on
<Kathy> Please start without me
<Kathy> I am trying to get this to work but WebEx will not connect
<marcjohlic> I was able to get in.. no issues here
<patrick_h_lauke> scribe: patrick_h_lauke
Kim: any questions on device sensors?
Melanie: updated based on last week's feedback, but need help with github
<scribe> scribe: Kim
Device sensors
https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Device_Sensors_Understanding#Understanding_Device_Sensors
Melanie: issue – scaling to motion – two bullets to leave out in github
– Kathy will move to get from wiki
<Kathy>
https://rawgit.com/patrickhlauke/wcag21/concurrent-input-mechanisms/understanding/21/concurrent-input-mechanisms.html
concurrent input mechanisms
https://rawgit.com/patrickhlauke/wcag21/concurrent-input-mechanisms/understanding/21/concurrent-input-mechanisms.html
Patrick: it would impact everybody the same way not necessarily folks
with disabilities I'm kind of okay with that
Kathy: actually a lot of WCAG 2.0 impacts all users, but impacts people
with disabilities more
Patrick: if we have good examples that would illustrate that
... will push to github
<patrick_h_lauke> (just say when you're done reading the proposed text)
<MelanieP> Web content does not restrict use of input modalities
available on a platform except where the restriction is essential,
required to ensure the security of the content, or respect user settings.
Kathy: I think we need to have something in there about security of the
content or to respect user settings
... discussion about security was that if a certain input mechanism
compromises the security aspect of what they're entering in you can
block a particular input method – so if there's a security risk you
don't need – if I have to enter it only using a keyboard for some
security reason that's an exception
A speech input user has trouble using the mouse keyboard, so use in
speech when possible, but when talking with a colleague intermittently
switches speech off and uses the mouse.
Another example: A speech input user has trouble using the mouse and
keyboard, so uses speech when possible, but when talking with a
colleague intermittently switches speech off and uses the mouse.
Patrick: if someone relies on using a mouse or mouse like interface and
can't use the touchscreen they'll be heavily impacted
... resources – I'm not sure what level we want to keep these
Kathy: we should keep those in there, including your article
... we need to have things published out there on these topics and
there's not a whole lot out there. If anybody has an article for things
on there that relate – we need these
... does anybody have anything else – I think this is good
Patrick: I'm assuming we don't have to have the techniques done
Kathy: correct – we don't need that right this moment. The next steps
are that these are going to go to the other taskforces,they'll give
feedback and then it goes to the working group. They can get other user
examples or other nuances they can put into these
Orientation
https://rawgit.com/w3c/wcag21/orientation/understanding/21/orientation.html
Marc: added examples where orientation is not locked
<marcjohlic> Orientation SC: Content is not locked to a specific display
orientation, and functionality of the content is operable in all display
orientations, except where display orientation is essential for use of
the content.
Marc: put NA in resources
Kathy: could link to the original document we did about how this applies
to mobile
Marc: using the word mobile all the time – this can apply to nonmobile too
<patrick_h_lauke> I suggest replacing "mobile application" with "web
content"
Melanie: is this applicable outside of mobile apps – browsers don't care
Kathy: you can do CSS
Patrick: CSS device adaptation – no browser yet supports but you can say
only lock the display to portrait or landscape. Also the cheap version
of that is just check width and height of viewport and say please turn
your device – don't display anything untiil you've turned the device. So
it is applicable to web content as well
... not purely on mobile – also desktop depending on aspect ratio – it
may trigger the same kind of problem
... another quick comment – YouTube videos I would generalize that, just
say videos can be displayed
Kathy: example 3 title E reader app
... people will think of this as being an actual application – web app
Marc: mobile applications and web apps on first reference?
Melanie: can we say mobile and web-based applications?
Marc: I'll clean up the rest of the mobile applications references
<Kathy>
https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Accessible_Name_Understanding#Intent
<Kathy>
https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Character_Key_Shortcuts_Understanding#Resources
<Kathy>
https://www.w3.org/TR/2011/WD-html5-20110525/editing.html#the-accesskey-attribute
https://cdn.rawgit.com/chriscm2006/wcag21/2f25bd2c13b16363b19a07796112bf3eda19d3cb/understanding/21/contextual-information.html
<Kathy> https://www.w3.org/WAI/GL/wiki/Accepted_WCAG_2.1_SC
Kathy: will put Kim's, Melanie's, Patrick's on and update document. and
I'll email Lisa and Jim to tell them those are ready to review. We'll be
working on techniques next time for the mobile stuff.
we didn't look at change of content – if you have comments on that let
me know
Jake – mobile applications – technology agnostic we also have hybrid –
we should have some kind of clear definition starting wiith ourselves
Jake: when we talk about native apps, hybrid version, also for this
understanding – what Marc is working on. Definition would be useful
Kathy: we are working with the education and outreach group writing more
for mobile, define things for mobile on the EO side. I can bring up your
concern and make sure that we've got covered
Jake: for myself I talk about native specifically iOS and android.
Hybrid some web content in the native. Web application web document with
some functionality. It stays somewhere in the gray area for different people
Kathy: will touch base with the EO on that
Summary of Action Items
Summary of Resolutions
[End of minutes]
------------------------------------------------------------------------
Minutes formatted by David Booth's scribe.perl
<http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/scribe/scribedoc.htm>
version 1.152 (CVS log <http://dev.w3.org/cvsweb/2002/scribe/>)
$Date: 2017/10/12 16:16:40 $
___________________________________________________
Kimberly Patch
President
Redstart Systems
(617) 325-3966
kim@redstartsystems.com <mailto:kim@redstartsystems.com>
www.redstartsystems.com <http://www.redstartsystems.com>
- making speech fly
www.linkedin.com/in/kimpatch <http://www.linkedin.com/in/kimpatch>
___________________________________________________
Received on Thursday, 12 October 2017 16:19:10 UTC