Kathy: I'll explain what we're
doing with the mobile app
... we've primarily been working on mobile web accessibility –
we've created success criteria the of gone under number two
point one and number two point two. We're not clear whether or
not there's going to be a 2.3.or not but were going to put our
brainwork into silver
... a question that comes up a lot is how does mobile apps come
into this
... WCAC ICT document applicable to software – needed one
standard to reference for both web and software and Section 508
standards
... the new guidelines have an explanation of web mobile and
how that's applicable to apps so that will be one of our
reference points but the idea here is to create a document that
is WCAG – how the mobile is applicable to mobile apps
especially since mobile apps are being used more and more for
all sorts of different things
... so this is an important focus
Kathy: there's a coordination
group between AG and the taskforces – one thing they asked is
what should we be focusing on – this outlines what other things
that we should be looking at
... in the beginning we identified a lot of different areas –
some were things that didn't fit within the web content
accessibility guidelines framework as it stood. So were getting
those over to the silver task force. Filling out anymore of the
two point two techniques and writing those. We have a number
that have been written already that are in there, but if
there's any others that we think we should add to that we can
be worki[CUT]
... we already talked about the mobile apps note
... this also the Internet of things – there's a working group,
but we might want to think about that as well when we're
looking at mobile apps as well as kiosks and how those are
being used. There is kiosk accessibility guidelines but they're
not published under the W3C so in looking at the kiosk and what
is required there's definitely some key things and the Web
content accessibility guidelines also apply to the kiosks so we
mig[CUT]
... all of those are being used more and more today
Detlev: our task force or someone else
Jennifer: almost a silver thing
Kathy: the idea here was were
looking at alternative interfaces and devices and so we can if
we are finished all the rest of the stuff we can shift into
looking at these other areas
... techniques, candidates and our primary focus will be on
mobile apps
Detlev: I'm sure there's a lot of interest in that and a lot of contentious issues. You may have noticed there was quite some vitriolic arguments aboutwhether reflow should be considered for mobile apps and others saying you don't know what you're talking about. It's quite a loaded thing. I think we will have quite a lot to do and we would also need may be more technical advice at some points that I could give because I'm not a native [CUT]
add a few things, but I'm not as well acquainted from it.
Kathy: both Jennifer and Sakriti
have app development, and I've also developed. I think where
you come in, Detlev, is history. I think we have the right
people. We also have others who can come in with examples.
Jennifer, I think DQ has some if we need additional
assistance
... Sukriti – you may know others as well. It's not just
relying on this group but also going into to others
Detlev: things like text spacing – what does that mean for mobile. Assess ability guidelines or every app would have to have a menu that would allow you to increase text spacing. I think those are the kinds of things you have to answer and that follow-up document.
Kathy: where we have resources – please add them
https://docs.google.com/document/d/1cSlYZQUG5Erj2lG1Xx871TGUGhVR2_qKiPR98iAwnJs/edit#
Detlev: might just be a PDF version
<Detlev> http://www.etsi.org/deliver/etsi_en/301500_301599/301549/01.01.02_60/en_301549v010102p.pdf
Feel free to add resources to the resource section of the document
<Detlev> https://www.etsi.org/deliver/etsi_en/301500_301599/301549/02.01.02_60/en_301549v020102p.pdf
Kathy: the existing guidelines are going to be important for us to harmonize with
Detlev: draft is from May 2019
Kim: logistics reminder – click what looks like a page of the top left and you get an outline
Kathy: we put in some resources,
feel free to add more, also feel free to add questions we need
to answer in that document
... Jennifer – can you find the document Glenda Sims together –
spreadsheet about how WCAG relates to mobile
apps
Kathy: found the link and added – WCAG SCs that relate to mobile apps
https://drive.google.com/drive/folders/1Q9md2AvmeTgvsT9GB62BsGvCaalDGtE6?usp=sharing
Kathy: this will be the start of our information gathering and this, and we can work on this for the next couple weeks
Kim: so that document and also feel free to add resources to the mobile app note document
We'll be off the next two weeks, back on September 10
This is scribe.perl Revision of Date 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: Kim_Patch, Jennifer, Kathy, Detlev, Sukriti Present: Kim_Patch Jennifer Kathy Detlev Sukriti No ScribeNick specified. Guessing ScribeNick: Kim_Patch Inferring Scribes: Kim_Patch WARNING: No "Topic:" lines found. Found Date: 20 Aug 2020 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]