W3C

– DRAFT –
Mobile Accessibility Task Force Teleconference

18 April 2022

Attendees

Present
Jennifer, Kim_patch, Perrin
Regrets
Jan Jaap, Sally, VJ
Chair
-
Scribe
Kim_patch

Meeting minutes

<Perrin> present!

Planning

https://docs.google.com/document/d/1VC5LSDhz_kJ5Icp9TgC0hngMc-fd5rqoyNGPusXZ-ZU/edit#

User issues

https://docs.google.com/spreadsheets/d/10LHkd9kJK2K1ARZ9igObCzPVWBLhXQzl0VYACZQrUFM/edit#gid=0

Discussion summary:

Making sure everything is available through single pointer interactions

How to easily switch to AT, use just one aspect, or use a mix of several types of AT

Voiceover and voice control – how to code things to make it work so you can switch. On the user side people who use talkback want similar words as voice access

Interoperability – cross impairment – does assistive tech work with each other

If you are using two types of assistive tech attention to cognitive load

Voice Control and Voiceover, people using the project relate beta that can translate their voices, but they want the other speaker to use live transcribe – they have to switch back and forth

At a high-level technology is very powerful but it's hard to rein in that power into smaller less intimidating assistive technology and it also doesn't work with other AT

In terms of research, would be good to know biggest pain point mobile interactions per impairment

Different outcomes depending on how much time and energy the user has to spend with the software, and there's also the issue of having to continually spend time making sure the AT works with other software because things change

Next MATF meeting April 25. No meeting May 2.

In the meantime, it would be great to get more items in the spreadsheets as you think of them

Minutes manually created (not a transcript), formatted by scribe.perl version 185 (Thu Dec 2 18:51:55 2021 UTC).

Diagnostics

No scribenick or scribe found. Guessed: Kim_patch