Meeting minutes
Agenda Review & Announcements
AT Driver https://w3c.github.io/at-driver/
matatk: received feedback from one vendor only, need to collect more information
<Fazio> ATIA?
<Fazio> David Dikter
<Fazio> AAATE?
matatk: two vendors in discussion
New Charters Review https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22
<Roy> https://
Roy: no update as of yet
<Roy> w3c/
janina: we should give only a week time
matatk: no concrete answer from nvda
matatk: only internationalization is completed
matatk: very strict one week deadline
janina: waiting for responses from community
HR A11y Review Comment Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review
Roy: nothing new in this week but some are still pending
<matatk> gb, off
<gb> matatk, issues and names were already off.
select.showPicker()
<matatk> w3c/
matatk: we have a window to make changes to api for above mentioned subtopic
Allow additional elements to be considered labelable
<matatk> w3c/
<Fazio> I'm more concerned with show picker
matatk: idea to add lables to some more html elements eg. textarea
PaulG: lable should behave like a label only
janina: +1
PaulG: need testing with different browser and AT combination to check focusable property of editable content
Media query to prefer shapes over colours
<matatk> w3c/
<Fazio> stroop effect for color is a problem too
<Fazio> I continue to flip the wrong gas switch in peru because green minus means gas off and red flame means on
<Fazio> I interpret green as on red as off
matatk: why to prefer shapes over colours
<Fazio> I am neurodivergent
<Fazio> brain injury
<Fazio> More to neurodivergernce than autism and adhd
matatk: default should be both colour and shape and option should be there to switch between the two
Explicit Review Requests https://github.com/w3c/a11y-request/issues
Privacy Principles
<Roy> - issue: w3c/
<Roy> - URL of spec:https://
<Roy> https://
matatk: need to review this and need volunteers to do this
new on TR http://www.w3.org/TR/tr-status-drafts.html
MiniApp Addressing
<Roy> - spec: https://
CSS Update (Paul) https://github.com/w3c/css-a11y/issues
Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/actions/open
Task Force & Deliverables Updates
matatk: several issues from rqtf
Request for meeting from WebRTC
<matatk> https://
<Roy> A recurring topic at the intersection of WebRTC and accessibility has been the integration of real-time text (RTT) in WebRTC-based services. See for instance:
<Roy> https://
<Roy> https://
<Roy> https://
<Roy> We have been recently notified by the author of the relevant IETF RFC that that work has now concluded:
<Roy> w3c/
<Roy> Unfortunately, based on the assessment of two of the co-chairs of the WebRTC WG (including Bernard Aboba who is directly involved in the relevant FCC work in the US), the said RFC is not fit for purpose, nor implementable.
<Roy> To compound that situation, according to Bernard, that unsatisfactory solution is going to become part of the EU regulation on the matter, via:
<Roy> https://
<Roy> https://