See also: IRC log
<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
Melanie: issue – scaling to motion – two bullets to leave out in github – Kathy will move to get from wiki
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
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
<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
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Default Present: patrick_h_lauke, Kathy, JakeAbma, marcjohlic, Melanie, Kim Present: patrick_h_lauke Kathy JakeAbma marcjohlic Melanie Kim Found Scribe: patrick_h_lauke Inferring ScribeNick: patrick_h_lauke Found Scribe: Kim Inferring ScribeNick: Kim Scribes: patrick_h_lauke, Kim ScribeNicks: patrick_h_lauke, Kim Found Date: 12 Oct 2017 Guessing minutes URL: http://www.w3.org/2017/10/12-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]