W3C

– DRAFT –
(MEETING TITLE)

08 January 2024

Attendees

Present
jjdg, Mick
Regrets
-
Chair
-
Scribe
jjdg

Meeting minutes

New facilitator

Jan Jaap de Groot is the new Task Force facilitator since 4th of January, 2024.

New direction

Focusing on installable apps on Android and iOS, e.g. any app which is an .apk / .ipa, thus; web apps are not included.

Responsive design is already covered in the Accessibility Guidelines Working Group. The Mobile Accessibility Task Force focuses on mobile apps.

Goal for 2024: publish Working Group Note for applying WCAG 2.2 to Mobile Apps

Covers all success criteria, including triple A, and not just the new WCAG 2.2 ones.

Subgoals: WCAG-EM for mobile apps, e.g. how to carry out an accessibility audit for a mobile app. Apps do not have URL's like websites, therefore some changes are needed to be able to follow WCAG-EM 1:1.

Aspirational goal: Techniques for mobile apps, ways to meet Success Criteria, including code samples for multiple frameworks/programming languages.

Archival goal: update relevant resources, deprecate outdated resources and ones that are no longer relevant

Testing goal: contribute to existing ACT Rules, add new ones for mobile apps

Collaboration goal: collaborate more often with COGA (The Cognitive and Learning Disabilities Accessibility Task Force) and APA Accessible Platform Architectures (APA) Working Group

Features goal: publish document listing available accessibility features on Android and iOS

Community goal: creating a place for the mobile accessibility community to come together

Timing change

Mick: prefers working hours, in GMT+0 timezone, evening also works

JJ: prefers working hours, in GMT+1 timezone, evening also works

Options: 7 PM GMT+0 would work for both JJ + Mick

Mick: Monday works nicely to kick-off the week, Wednesday/Friday don't work

JJ: Monday works well, other days are also ok, prefer earlier days in the week

WCAG 2.2 mapping

Review existing resources, wait for new partcipants before moving forward.

Considering using Markdown / Github to create the new Working Group Note

Work together async using Slack

New Task Force members

JJ: Lots of interested people in LinkedIn, hope to get 5+ people in the MATF as invited experts; have ±15 people in mind to reach out to.

JJ: Also try to get people interested to contribute outside of the MATF in the community

How can we make our resources beginner friendly?

Compare existing notes and figure out which ones are good examples.

COGA uses icons in their Note: https://www.w3.org/TR/coga-usable/

Getting started document: https://www.w3.org/WAI/GL/task-forces/coga/wiki/Getting_started

Ten tips guidance: https://www.w3.org/WAI/GL/task-forces/coga/wiki/%E2%80%9Cten_tips%E2%80%9D

Publish official note, and publish unofficial guidance on W3 Wiki / Appt.org?

Moving forward

Make samples in Markdown

Figure out how to collaborate efficiently

Reach out to potential MATF participants, try to plan meetings in January

Work out 1 Success Criteria to show how it could look like in the Note

E.g. do we map to mobile apps as a whole, or map to Android / iOS seperately

Figure out if we can collaborate with Google for Android and Apple for iOS

Check how we link to their existing resources, e.g. Material Design Guidelines / Core App Quality / Human Interface Guidelines

General guidance for all mobile operating systems, add exclusions for Android / iOS where applicable?

Guidance is mostly different on the techniques, e.g. how to achieve it, what should be achieved is the same; such as adding a label to images.

Minutes manually created (not a transcript), formatted by scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).

Diagnostics

No scribenick or scribe found. Guessed: jjdg

Maybe present: JJ, Options, Subgoals

All speakers: JJ, Mick, Options, Subgoals

Active on IRC: jjdg, Mick