Accessible Platform Architectures Working Group Teleconference

26 Feb 2020


jasonjgw, Joshue108_, SteveNoble, janina


Real-Time Communication: preparation of draft for APA review.

<Joshue108_> https://raw.githack.com/w3c/apa/AccessibleRTC/rtc/index.html

Josh: working on some final adjustments to RTC
... blog post is in process
... is hoping for feedback on blog post

<Joshue108_> If I get the latest snapshot of the RTCAccessibility published today on the editors draft track then I can get the announcements etc ready sharpish

Josh: question on editors draft

Verifiable Credentials: accessibility-related use cases.

Discussion on editors draft in last APA call

Janina: may want to use email
... Email to editor to inform of the current status

Jason: if there are issues with the use cases, we should rectify those first

Janina: suggest service dog scenario be used as first, but the orders of others may not matter

The intersection of privacy, security, and accessibility: issue identification and discussion.

Jason: not an urgent agendum, but keeps coming back in many discussions

Josh: one that comes up is fingerprinting - identifying a person with a disability due to settings in the browser and such
... one example is using dark mode
... also using larger font in the browser

Jason: espcially if several such indicators are combined

<Joshue108_> https://lists.w3.org/Archives/Public/public-privacy/2020JanMar/0035.html

<Joshue108_> https://lists.w3.org/Archives/Public/public-privacy/2020JanMar/0047.html

<Joshue108_> Privacy threat model review https://lists.w3.org/Archives/Public/public-privacy/2020JanMar/0012.html

<Joshue108_> SOrry guys I gotta drop in 2 mins..

Janina: unclear how disability fingerprinting is especially different than other types of fingerprinting
... it could be deterimental for things like raising insurance rates, etc.

Jason: what might make things different is that the indicators may be different than typical practices for targeted advertisement
... we may need to inform those working on privacy issues about the potential characterists that might be tracked

<jasonjgw> Steve: expects browser history to be a rich/commonly used source of data for information about users.

<jasonjgw> Steve: Notes that Josh was referring to browser settings and other influences of assistive technology that indicate a person's disability status.

Jason: it may be that hiding such settings will do little to stop disability identification due to all the other types of data which gets tracked by Google and others

Janina: it may be that better regulation of what is collected and what they do with it is going to be the only real solution

Jason: we will table this discussion until Josh returns to better understand the threats and understand the issues, although with an understanding that some of this will require regulatory work

Meeting schedule and CSUN Conference.

Jason: we can informally tell people at CSUN about upcoming publications

Summary of Action Items

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/02/26 14:54:40 $

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)

Default Present: jasonjgw, Joshue108_, SteveNoble, janina
Present: jasonjgw Joshue108_ SteveNoble janina
No ScribeNick specified.  Guessing ScribeNick: SteveNoble
Inferring Scribes: SteveNoble
Found Date: 26 Feb 2020
People with action items: 

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]