W3C

- DRAFT -

Accessible Platform Architectures Working Group Teleconference

06 May 2020

Attendees

Present
jasonjgw, janina, scott_h, Joshue, Judy, SteveNoble, Joshue108
Regrets
Chair
jasonjgw
Scribe
scott_h

Contents


<jasonjgw> zakim clear agenda

<jasonjgw> zakim clear agenda

<scribe> scribe: scott_h

Introducitons to our new RQTF member

first Janina as Chair of APA

josh: hi Sonali - I"m emerigng web specialist at W3C

ex-co ahri of WCAG WG, owrkign a long time

Steve - hi Sonali, work full-time at Pearson, education company with school assessment divison

judy: good to see you Sonali, we'd met at CSUN. I'm the Director of W3C WAI

includes WCAG 2.2, 3.0 work

<Joshue108> SH: I wear different hats, as an academic and not for profit sector.

<Joshue108> Great to have you Sonali.

Scott- hi Sonali, I'm Scott Hollier from Perth, AUstralia

I'man academic andod some accessibility work and consultancy in the NFP sector

jason: hi Sonali, I"m Jason the convenor of this grup

I'm invooed in web standards work, starting int he 1990s

Sonali: I"ve ben at RNIB for 10 years, work on media and arts accessibility

VOD providers, museums. Purpose: improivng vieiwng experience for people with sight loss

Part of project making 360 videos accessible

<Joshue108> https://www.imac-project.eu

jason: remote meeting falls into two parts

1) best advice for condut and preparation for teleconference-style meetings

2) trying to o connect the work to W3C guidance and draft RTC User Requirements

can we connect these up?

judy: I have some thoughts

I"ve been looking at guidnace form other organisations, some good matierlas from Partnership with Employment, telewrk guidnace

what we ahve so far are some for hosts, some W3C gdiance, some application/platform level,

Scott had added in some sector guidance for education

and I"m starting to understand work in this space is massive and urgent

for me - we should lead by talking about relevance form published guidelines

i.e. WCAG, authoring tols, user agents, RTC

and reverse order of what's in the remote meetings page

Reverse order

ALso some discussion with Zoom supporting RTC

One possibility: do a separate document, public interface

we can do that within this document

One point of struggle: really want one thing people can point ot to give overall view on wwhat's in this space

Janina: like what you're saying about speaking to our strengths,

one of the things we want to promote is interoperability

We have that to some degree with web browser of choice,

but if its an extension we don't know how good it'll be

Bysupporitng RTC there's less devleopment,

It's also part of our core stuff and would be good to slide it in there

judy: adding seciton now about capturing bugs

janina: and standards support

judy: I"m adding the secitons in

janina: common story, e.g. e-mails. Now needs to be with teleconference clients

jason: idea of reordering material and clarifiying with what's being created in teh RAUR

and referring to toher resources, guidance

judy: revising the purpose

in relation to bugs, how to handle being vendor-neutraul?

jason: could make it a general place to report

judy: looking at design properties to promote, are there others along with interoperability

janina: side-benefit: if you are supporitng RTC

josh: challenge is recognising is where the control is , e.g. live subtitling

get the point also what 'good' looks like: what's sufficient?

judy: if I have two hours, would you review?

scott: what leve of review do you nee?
... happy to review

jason: basically its qa review that you'd only object ot if there was a major issue

<scribe> ACTION: Janina, Jason and Scott agreed to review for Judy when Judy has completed updates

<trackbot> Error finding 'Janina,'. You can review and register nicknames at <https://www.w3.org/WAI/APA/track/users>.

<Zakim> janina, you wanted to reinforce importance of interoperability -- ergo WebRTC -- less work for developers

Accessibility of remote meetings.

TPAC 2020 involvement.

Working drafts

Jason: receiving comments on two working drafts,

1) XAUR

2) RAUR

both under public review as first public working drafts

we're looking at comments received

judy: could we save a few mintues about organising at the end?

<Joshue108> 4.5 Interaction and target customization

jasoN; yes

<Joshue108> https://github.com/w3c/apa/issues/87

josh: 4.5 interaction and target customisation

useful for people with tunnel vision and multiple disabilities such as mobility

about expanding out the requirement

<Joshue108> https://www.w3.org/TR/xaur/#interaction-and-target-customization

user with limited mobility may need ot hit larger target:

The comment made the point that this would be useful for other groups, not just mobility

Sonali: looking at a broader user case,

e.g. apps - if you need simultaneous action if buttons are well spaced and good sized,

could be useful

Not really needing additional UR, just expanding scope

<Joshue108> Makes sense to expand this out for other user groups.

janina: do we see a use case where you need to hit multiple buttons? sticky keys?

Sonali: 4C - not needing ot hit multiple keys

judy: useful for physcial disabilities as well

josh: thanks helps to expand, and janina also expands

<Joshue108> JOC: This would be very useful for a range of users, and +1 to the Sticky keys use case also :-)

josh: issue 88 -

<Joshue108> https://github.com/w3c/apa/issues/88

<Joshue108> 4.6 Voice commands #88

voice command

user need: limited mobility needs voice commands to navigate XR

to ensure navigation can be controlled b in XR

The comment - also good for people with sight loss,

1) voice activaiton should use native screen readers

rather than external devices, avoid need to pair devices

janina: not sure what's native - e.g. is 'ok google' native?

<Joshue108> Suggested requirement 5b: Voice activation should preferably use native screen readers / voice assistants rather than external devices to eliminate the additional step needed to pair devices.

<Judy> [JB: Thinks that we need to write up a performable version of a use case on this!]

janina: needs to fit into mainstream to write the skill to tie into a digital assistant,

API doens't need to be something specific for the screen reader

Sonali: going back to why - accessing IMAC player would have voice control through Alexa, but did not work for end users

as they kept asking 'why can't I use my screen reader?'

janina: screen raders don't usually suport voice control

jason: recent work by Apple on using voice input to control entire machine, haven't integrated with screen reader

these should be better integrated

could we sort out the use caes?

integrating the different assistive technology services?

<Zakim> Joshue, you wanted to ask what the user need is here? It seems like it is around pairing devices?

josh: general issue around the integration of AT with generic devices in teh envrionment

another user need around now environment support a user without the overhead - digital assistant, screen reader etc.

Josh Sonali - was pairing devices at the head of it?

sonali: yes,

janina: familarity vs learning something new

perhaps?

josh: yes, part of it

imporant: digital literacy, get the most out of AT

sometimes users don't know rather than access,

but this is important issue - thanks Sonali for flagging it

judy: very quick thing

trying ot bring people into this work, but issue is not having a clear landing page for RQTF

Really need it fixed

premissions issues on the pages

<Joshue108> lets come back to this next week and the new REQ 5c: Feedback to the user must be audible..

<Joshue108> https://github.com/w3c/apa/issues/88

RQTF not clearly showing what we're doign

<Judy> https://www.w3.org/WAI/APA/task-forces/research-questions/

Same things for the APA page

but for RQTF, can we fix it?

janina: it's on our list

if you need something for AC, which one?

janina: RQF page?

judy: yes, with current work and current links

might e minor changes

Action - Janina will edit the RQTF page

<trackbot> Error finding '-'. You can review and register nicknames at <https://www.w3.org/WAI/APA/track/users>.

Summary of Action Items

[NEW] ACTION: Janina, Jason and Scott agreed to review for Judy when Judy has completed updates
 

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2020/05/06 14:08:24 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/Chari/Chair/
Succeeded: s/educiaotn/education/
Succeeded: s/ehad/head/
Succeeded: s/pairng/pairing/
Succeeded: s/ca't/can't/
Succeeded: s/envronmetn/environment/
Succeeded: s/htat/that/
Succeeded: s/1) XAU/1) XAUR/
Default Present: jasonjgw, janina, scott_h, Joshue, Judy, SteveNoble
Present: jasonjgw janina scott_h Joshue Judy SteveNoble Joshue108
Found Scribe: scott_h
Inferring ScribeNick: scott_h
Found Date: 06 May 2020
People with action items: janina

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


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]