Meeting minutes
<janina> /join #rqtf
scott: Started adding content noting there are so many possible directions
scott: We'll need to scope re a11y
scott: working on identifying main players and how they're supporting pwd
scott: process is key -- have started notes on what would be beneficial
scott: e.g. alt text; already tools that do that
scott: some app environments do better than others with that
raja: The a-i interpreter is just not ready in any way
scott: Could it help? Potentially
Oops!
Date 08 May 2024
< janina> scott: Started adding content noting there are so many possible directions
< janina> scott: We'll need to scope re a11y
< janina> scott: working on identifying main players and how they're supporting pwd
< janina> scott: process is key -- have started notes on what would be beneficial
< janina> scott: e.g. alt text; already tools that do that
< janina> scott: some app environments do better than others with that
< janina> q+ to suggest users should be able to specify their preferred ai * Zakim sees janina on the speaker queue
< janina> present+ Raja * Roy janina, I guess you are in wrong channel
< janina> raja: The a-i interpreter is just not ready in any way
< janina> scott: Could it help? Potentially
/join #rqtf
meeting
meeting?
Agenda Review & Announcements
Gottfried: Workshop on collaborative editing, https://
<janina> APA's Collaborative Tools work is here:
<janina> https://
Gottfried: CTAUR could be a good intro into the workshop
janina: This document is close to publication. We need a wider community review. Will probably be finalized in July.
TPAC 2024 Planning Begins
janina: We need to get a Wiki page started.
… Active request from media interest group.
… Revisit our minutes from last year. What do we want to achieve with them?
… We could talk about things such as AI
matatk: Deadline for us to tell organizers is looming.
… Break-out might be useful for dissemination of APA results.
CSS View Transitions w3c/a11y-review#192
<matatk> gb, off
<gb> matatk, issues and names were already off.
<matatk> w3c/
matatk: Peter Linz raised this issue.
… View transitions should be disablable
… The question is how to do this.
… Media query is for reduced motion, not "no motion".
<Fazio> ask that phd student that presented to us
matatk: TAG discussed this.
… Do we want to see a resolution to this issue? (Tag "a11y-needs-resolution")
… If i receive no objection, i will put that label on.
(no objection)
janina: Mechanism how to do this is not important for us.
Fazio: Remember the presentation we had on Media Queries from a few years back: https://
RESOLUTION: APA would like to see view transitions disablable.
<Fazio> Thx Matt. It's a really goood presentation
New Charters Review https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22
EAA and Ebook Requirements
Gottfried as per latest european a11y act says ebooks should follow WCAG 2.0
Gottfried WCAG 2.0 A level compliance discripancy between ebooks , pdf and epub
Gottfried changes in the act may take longer time
Gottfried goal is to comply with WCAG 2.2 AA
janina focus should be can we resolve this discripancy
acj janina
<Zakim> janina, you wanted to suggest we need to bring in epu a11y people for options based on what's achievable
<Fazio> Turkey requires ebook accessibility for all new publications
PaulG ebooks are covered under products section
PaulG links for discripancy may be helpful to recheck
janina links are added in email thread
Gottfried EAA applies to b2c and not for b2b
Discussion on APA email list here: https://
Gottfried point should be a11y standards should be same for epub and pdf
Here is the exempt for ebooks:
https://
Document: https://
page 2: "In line with feedback received from European Publishers and confirmed by representative organizations of persons with disabilities referring to the availability of EPUB accessibility technical specifications under W3C e-books and dedicated software should be excluded from this request."
janina that's not what W3C agreed to - my recollection is there was an exemption for small publishers only
HR A11y Review Comment Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review
Roy: Request for comments from CSS
[mediaqueries-5] `prefers-interaction-side` media query & `interaction-side` property
<Roy> - issue: w3c/
PaulG: Very interesting read. Very specific use cases. Ultra-wide monitors, but proper JS eventing needed, because changing orientation is more complicated.
… If you have other use cases or ideas, should be added.
matatk: Operating systems and software have catered for ultra-wide monitors. MacOS, Unix, InkScape, ... This needs to be supported in the native app. On the Web, we don't have that restriction.
… Scope creep?
… Long thread, but good diagrams.
… Two issues: (1) General preference of where the active controls should be. (2) Purposely reposition a toolbar due to preferences. Can we solve both issues with this?
Explicit Review Requests https://github.com/w3c/a11y-request/issues
Roy: Nothing
matatk: There is something old.
Ethical Web Principles
matatk: We got good feedback on privacy principles from TAG. Now focus on ethical web principles.
… Many ways of embodying these principles - more general.
… Let us know if you have feedback.
… For feedback, use our mailing list. We need to wrap this review up as quickly as we can.
… We are looking for high-level feedback. Is there anything important missing?
… Let's talk about it next week.
… The UN recently mentioned the TAG's ethical web principles.
Task Force & Deliverables Updates
janina: Still activity of FAST tf.
… I will follow up on this with Michael Cooper.
… This is an area of ongoing interest - good to see this happen in the community group.