- From: Kim Patch <kim@scriven.com>
- Date: Mon, 7 Nov 2022 16:32:08 -0500
- To: "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>, "ran@w3.org" <ran@w3.org>
- Cc: Jeanne Spellman <jspellman@spellmanconsulting.com>
- Message-ID: <8495e3b3-eaaa-0557-29f1-239b89de80db@scriven.com>
*MATF Minutes November 7, 2022
*
*Link**:****https://www.w3.org/2022/11/07-matf-minutes.html
Text of minutes:
*
Mobile Accessibility Task Force Teleconference
07 November 2022
Attendees
Present
Ilknur, JJ, Kim, Poornima
Regrets
Jennifer, Sally
Chair
Kimberly_Patch
Scribe
Kim_patch
Contents
1. introductions <https://www.w3.org/2022/11/07-matf-minutes.html#t01>
2. appt update <https://www.w3.org/2022/11/07-matf-minutes.html#t02>
Meeting minutes
<jjdg> Update for: https://beta.appt.org/en <https://beta.appt.org/en>
introductions
appt update
https://beta.appt.org/en <https://beta.appt.org/en>
Overview– Stats, Accessibility docs, Guidelines, articles
code samples, accessibility features – in-depth articles about assistive
technologies
All platforms are visible at all times
Link to contribute on Github to code examples
(JJ overview)
JJ: Working on content side now, also more code examples
JJ: added WCAG overview – at a glance
JJ: so where WCAG is lacking examples for native apps – that's where we
are giving solutions
JJ: we been adding all the references so everything goes to 2.2 instead
of 2.1, and looking at what kind of code examples are relevant to the
new success criteria's in 2.2
JJ: also transcripts and videos of users – explaining what barriers they
have
Poornima: this looks great – putting everything in one place, well
structured, accessibility a developer needs – this looks amazing
Ilknur: Very organized, very clear, hhas what developers need. I'll be
exploring this.
JJ: still trying to figure out how to manage difference between docs and
articles. One solution docs more like in-depth, articles more like blog
JJ: may add standards such as ADA, Australian guidelines, Apple design
guidelines. We may expand in the future
Poornima: suggestion – from W3C we have the mobile accessibility
guidelines – maybe that could be included
JJ: maybe ICT as well
<jjdg> Mobile mapping:
https://www.w3.org/TR/mobile-accessibility-mapping/
<https://www.w3.org/TR/mobile-accessibility-mapping/>
<jjdg> WCAG2ICT:
https://www.w3.org/WAI/standards-guidelines/wcag/non-web-ict/
<https://www.w3.org/WAI/standards-guidelines/wcag/non-web-ict/>
<Poornima> https://www.w3.org/TR/mobile-accessibility-mapping/
<https://www.w3.org/TR/mobile-accessibility-mapping/>
<jjdg> Accessible Mobile Apps Weekly newsletter:
https://www.getrevue.co/profile/accessible_mobile_apps
<https://www.getrevue.co/profile/accessible_mobile_apps>
JJ: maybe we can request a list of issues from Google member
JJ: sometimes it's frustrating because they do a lot with advanced
features but sometimes don't support the basics
Poornima: would like to the job easier for expand collapse elements.
Poornima: Added to user constraints as well – accessibility settings
https://docs.google.com/spreadsheets/d/1w17lC7HOT05cIE4tVwcWAgb91bVlWnBAfB97wq7JKTQ/edit#gid=0
<https://docs.google.com/spreadsheets/d/1w17lC7HOT05cIE4tVwcWAgb91bVlWnBAfB97wq7JKTQ/edit#gid=0>
Poornima: zoom into 200 or 300% some websites I still see it's not
passing. Whatever we have in WCAG for the resize text– it's lacking for
mobile device
New page on the comparison spreadsheet – taking a look at the 2015
mobile doc, this can help us take a look at what on their ended up in
the standard and what might still be missing, and what might not still
be relevant
https://docs.google.com/spreadsheets/d/1-SM3PY-phoBN4v3PStawv0fYV3RudhuLLLwoGixDOtg/edit#gid=1232524378
<https://docs.google.com/spreadsheets/d/1-SM3PY-phoBN4v3PStawv0fYV3RudhuLLLwoGixDOtg/edit#gid=1232524378>
Next meeting November 14
--
______________________________________
Kimberly Patch
(617) 325-3966
patchontech.com
@patchontech
scriven.com/kimpatch
______________________________________
Received on Monday, 7 November 2022 21:32:22 UTC