Meeting minutes
<Lionel_Wolberger> present?
Agenda Review & Announcements
janina: Happy Thanksgiving to our American participants, no meeting next week Nov 24th
CfC on CAPTCHA https://lists.w3.org/Archives/Public/public-apa-admin/2021Nov/0000.html
janina: Reminder to APA members, cfc open for the Captcha note
… updating the note with some work from Cloudflare
… Our consensus is, we need a good Turing test (bots are bad), but the current Captcha fails accessibility and fails for other reasons
… We can go beyond the 'note' which is only our opinion
… and turn this into a statement by the W3C
… this new process to elevate the NOTE to a STATEMENT, as well wanting to add more info regarding the CLoudflare updates
… process: (1) publish fpwd of this note, then (2,3...) you can read in the cfc in email
Fredrik: Is cloudflare interested in being included in our process, and if so, how?
janina: Cloudflare did show interest in being involved. Let's complete our cfc then reach out (if we decide we want to reach out)
… let's go one step at a time. First complete the cfc, then get consensus
… likely will also push to have them become W3C members
Fredrik: What are they proposing?
janina: Research Questions has pulled together the technical process they are suggesting, using the W3C API for validating the person,
… we will likely also involve Lionel to evaluate the authorization and authentication process as he has experience in identity issues
… cloudflare has data on how captcha failures are hurting e-commerce
… these facts will be super useful to add to the paper
… good captcha is another "curb-cut"
anevins_: We recently audited Captcha against 2.1
MichaelC: We will add Andrew to Research Questions
<MichaelC> https://
anevins_: Please put a link to the git for this Captcha/a11y repo, and the preview
<MichaelC> https://
anevins_: Regarding the audit. Google Recaptcha version _ against WCAG 2.1 AA
janina: This note on captcha was reviewed by a Google engineer and they did not find issues with it
Task Force Updates
janina: Research Questions has a lot of documents in the air
… is ready to take the Captcha note onto their 'plate'
… in addition to the XAUR, remote meetings, nat'l language, (and janina listed five others)
janina: Personalization is doing well with its i18n issue
Lionel_Wolberger: Yes, we got the symbols thanks to Steve Lee
janina: P11n (pronunciation) is doing a panel presentation on the specification
… TPAC gave feedback as well
janina: COGA working on providing feedback on RQTF documents and are working to meet the timeline
… COGA's desire to work on mental health issues likely requires an update to their work statement
… they are gathering potential issues that may be useful to address
<anevins_> Regarding the audit. Google Recaptcha version 3 against WCAG 2.1 AA
FAST Update
MichaelC: Framework for Accessible Specification of Technologies (FAST) is a bit stalled
… not much to report in the last week
New Charters Review https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22
<MichaelC> https://
<MichaelC> https://
MichaelC: Second Screen Working Group
janina: That group has high turnover
MichaelC: Adding "define APIs to query windows positions and position windows on multiple screens" and more...
janina: We want this spec to speak about "discovering devices" and not just displays
… "second screen" does not mean a second SCREEN, it means multiple devices
… "second screen" is a shorthand idiom to speed discussion, such as "watching a movie"
… we know it's not a movie, it's an idiom to simplify discussion
… second screen refers to many different devices
Lionel_Wolberger: The spec says " e-book readers, phones, tablets, laptops, auto displays, and electronic signs."
… allow these devices to use secondary audio and video presentation devices available in the local environment, attached by wired connections or remotely with wireless, peer-to-peer media.
… can you tell us more about these multiple screens
janina: In the Media Accessibility User Requirements we spoke about how the alternative representations (such as captions, or audio descriptions)
… will often be available on other devices
… in a Broadway theater the audio descriptions can be made available by wifi to people's personal android devices
… these secondary devices are critical
… refreshable braille displays, bluetooth headphones, chromecast devices, any technology that will participate in consuming a media resource
… the primary display carries the primary, and the secondary can carry the secondary
Lionel_Wolberger: The name "second screen" obfuscates
janina: But the alternative name was really long, awkward and hard to remember
… like blind people 'watch TV' using the proximate meaning
… using an even tempered scale metaphor--losing the perfect fifth enabled us to integrate more notes and melodies
… A good moment to remind people about the MAUR (Media Accessibility User Requirements)
… this was the first *AUR
… HTML5 brought the media support that APA asked for
… with the exception of one item
… we accomplished this with use cases, user scenarios, a markup technology that could support an extensible list of these support version
… we invented a term which we called the PRIMARY video resource and then the ALTERNATIVE
… the video provided as video and the video provided as text
… we are still developing what we have developed for HTML 5
A11y Review Comment Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review
MichaelC: Nothing new this week
CSS Update https://github.com/w3c/css-a11y/issues
janina: Need a new representative from CSS. Amy has moved on, thanks to Amy for the splendid job she did keeping us synchronized
… We have spoken with the CSS chairs and will follow-up after Thanksgiving
<janina> https://
CCSS highligh API
An example: In data analysis, highlights are used to indicate any number of things - errors, outliers, or like the example in my comment in the issue: user sentiments. Highlights are also used in data analysis for medical literature to highligh medical conditions or symptom keywords.
Issue 6498 on how the CSS highlight API is exposed to the accessibility tree ( https://
janina: Do we agree to track this?
… No one disagrees.
… If a site associates certain color highlights with certain semantic meanings, that is something that APA would be interested in
Fredrik: Personalization would seem to be in scope of semantics like this
janina: Maybe we can write an accessibility section that points to Personalization, where we could specify how a highlight color is associated with a color
Lionel_Wolberger: ARIA-labelled_by could handle this
janina: But this is wider than just assistive technology, it would be helpful to keep it in Personalization scope
… colorization is becoming more sophisticated and deserves to be associated with semantics
MichaelC: "Figure out how highlights are exposed to the accessibility tree" is in our tracker
… shall I block?
janina: Let's block
new on TR http://www.w3.org/TR/tr-status-drafts.html
janina: Thanks everyone for a productive meeting, see you in two weeks.
r symptom keywords. [19:50] <Lionel_Wolberger> Issue 6498 on how the CSS highlight API is exposed to the accessibility tree ( https://