APA Weekly Teleconference

29 May 2024


Dr_Keith, Fazio, Iali, JenStrickland, Lionel_Wolberger, matatk, Matthew, mike_beganyi, NehaJ, niklasegger
Fredrik, Paul
Lionel_Wolberger, matatk

Meeting minutes

<Dr_Keith> I can't get into the zoom :(

<Dr_Keith> in now :)

Agenda Review & Announcements

<janina> Link to W3C Calendar on git hub ...

<janina> w3c/calendar

matatk: Please file issues or let APA know if there are any issues with the calendar.

janina: There is a CfC open for CTAUR, please respond by midnight Boston time.

<janina> https://lists.w3.org/Archives/Public/public-apa-admin/2024May/0004.html

Fazio: This is Collaboration Tools Accessibility User Requirements

<JenStrickland> CTAUR=Collaboration Tools Accessibility User Requirements

<JenStrickland> Thanks, Lionel!

<Dr_Keith> https://www.w3.org/WAI/WCAG2AA-Conformance

Lionel_Wolberger: +1, the info is not here https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-levels-head

<Dr_Keith> one more: https://www.w3.org/WAI/WCAG22/Understanding/conformance#levels

TPAC 2024 Planning

<Fazio> I looked at both links last weekend. No definition of A, AA, AA

matatk: We need to plan our meetings

janina: Need to meet with groups dealing with Media, e.g. MIG (media interest group)

janina: The AUR (Accessibility User Requirements) series began when HTML5 kicked off
… MAUR was the first one, invented at the time, we had coordination with Apple and other large corporations
… this MAUR helped guide HTML5

<matatk> Digital Accessibility User Requirements: Digital Accessibility User Requirements

janina: that kicked off the series of AUR

<matatk> Digital Accessibility User Requirements: https://www.w3.org/WAI/research/user-requirements/

Task Force & Deliverables Updates

HR A11y Review Comment Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review

Mark features that might expose accessibility tools

<matatk> gb, off

<gb> matatk, issues and names were already off.

<matatk> Tracking issue: w3c/a11y-review#194

matatk: There is a mark currently defined to surface the risk of fingerprinting
… this considers having a similar signal, when there is a risk of detecting AT
… I would like to widen the discussion to considering what exactly is AT

Lionel_Wolberger: this topic is of deep interest to me. There's subtle differentiation. This feels like 3 topics. Where this is born is: could the thing you're adding to the browser contribute to fingerprinting?
… e.g. if you have a unique font, that can contribute to fingerprinting.
… contributing to fingerprinting is not the same thing as detecting AT
… You (matatk) opened it up to 'what is AT?' - a wider discussion
… Finally: the browser _must_ be aware of the AT - it creates the accessibility tree and it helps the screen reader. Right now privacy protection of AT is based on handshakes all 'round.
… Google says, for example, that Chrome doesn't expose it. Browsers could though. But everyone stays away from this.
… The topic came up in our recent era because there ware ways to detect AT based on user behavior on the page. That's a distinct, 4th, topic.

janina: Sounds like the proposal is a badge on the spec to say it presents such a risk?

Lionel_Wolberger: Difference between fingerprinting and behavior-based detection.
… A fingerprint is a mark you leave behind - a set pattern of the stuff you've done to it (extensions, fonts, versions, ...)

Fazio: We need to be very specific, as Lionel is indicating
… is it as an individual, or as a disability type
… "this browser is set up this way" is unlikely to be able to parsed into, "the user has this disability"

janina: If it only identifies a class of users, that might be ok

Fazio: +1 to the label, "class of users"

<Dr_Keith> we do need to read the spec. The data can be paired with other data to be a personal identifyer and even ID of a class of users could be something that leads to deeper issues around discrimination

matatk: Keep in mind, if fingerprint can identify uniquely a particular browser, that is problematic enough

Explicit Review Requests https://github.com/w3c/a11y-request/issues

HTML Ruby Markup Extensions 2024-05-23

ISSUE: w3c/a11y-request#83

matatk: Ruby is a scripting language used for "interlinear annotation... short runs of text alongside the base text". Often useful in adding accents to characters, and Asian languages. Spec, https://www.w3.org/TR/html-ruby-extensions/

janina: We know some people in Japan who may be interesting in doing this review

new on TR http://www.w3.org/TR/tr-status-drafts.html

CSS Update (Paul) https://github.com/w3c/css-a11y/issues

Actions Checkin (Specs) issues/assigned

Other Business

Adapt at TPAC

Lionel_Wolberger: Let's clarify the meetings that Adapt would want


matatk: On the issue of symbols, we have movement from AP that needs answering

be done

Summary of issues

  1. w3c/a11y-request#83
Minutes manually created (not a transcript), formatted by scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).


No scribenick or scribe found. Guessed: Lionel_Wolberger

Maybe present: janina

All speakers: Fazio, janina, Lionel_Wolberger, matatk

Active on IRC: Dr_Keith, Fazio, Iali, janina, JenStrickland, Lionel_Wolberger, matatk, mike_beganyi, NehaJ, niklasegger