Meeting minutes
<matatk> present
Agenda Review & Announcements
<matatk> Baseline info: https://
<Fazio> TPAC meeting?
WebDX community group working on the gap between Baseline information accessibility issues. Lola, from this group asked APA group to analyse this gap by scheduling a meeting. We will setup a meeting and will communicate with all.
matatk: there will probably be a break out session
<Fazio> We should have a more significant TPAC meeting about Baseline
janina: We need AC representative should vote as a member organization
TPAC 2025
We have quite a few sessions in TPAC
matatk: I will contact Lola for Baseline and a11y during TPAC
Horizontal Review process update
<matatk> Reminder of the new documentation on proposing spec review comments: https://
matatk: This needs to be divided into sections and update wiki page.
matatk: Next time whoever is doing this review follow this process and give us a feedback
New on TR
CSS Positioned Layout Module Level 4
<Roy_Ruoxi> - tracker: https://
<Roy_Ruoxi> - spec: https://
Roy_Ruoxi: New FPWD publication
Roy_Ruoxi: we have time to review this document and who wants to review this document?
matatk: It is update to standard positioning in CSS
matatk: Paul, is there any change in this document? Are yopu aware of this by any chance?
<Roy_Ruoxi> here is review history for level 3: https://
PaulG: If there is a scrollable area and there no element inside it which does not get focus then scroll bar will get focus, and this is a part of chrome update. But not sure if this is the part of new update or not.
PaulG: There were also hicups in implementing pop overs but if this is the part of new update or not, not sure
matatk: anyone have anything to add to this scroll bar focus thing, although focus word does not appear in the this document
matatk: if someone wants to review web neural network then please follow above mentioned process in the link
matatk: we dont have naything new on spec review
Comment review requests
[css-fonts-5] Feature for making text always fit the width of its parent
<matatk> source: w3c/csswg-drafts#2528
<matatk> tracking: w3c/
PaulG: I did not add any comment but couple of people have already mentioned that it is terrible
PaulG: zoom example is explained how bad it is
matatk: may be we should open separate issue to tackle a11y side of this?
<matatk> Patrick pointed out Resize Text here with a demo: w3c/
janina: To us it appears it voilate WCAG SC
violate*
PaulG: we can say +1 to Patrick and add some comments
Fazio: Do we have to mention it strongly? or just mention?
matatk: We are not sure we should comment at this stage or not
matatk: There is not request fom there side to review it, PaulG noticed this
matatk: We should comment from APA side in polite words, janina and I can work on wording
janina: Is this a normative document?
matatk: Yes
matatk: I like the point of David about barriers
PaulG: Shall we say this does not respond to Zoom
<matatk> Comment on zoom: w3c/
PaulG: zoom in and zoom out functionality and make sure it does not violate WCAG SC
Fazio: If we do not use proper wording like must, it creates a lot of concerns
<Fazio> instead of accessible experience say to meet accessibility requirements
Connect HTML spec up to new CSS `interactivity` property
<matatk> source: whatwg/html#10956
<matatk> tracking: w3c/
<matatk> See Sarah Higley's comment: whatwg/
<matatk> This was the latest on how it's being shipped in Chrome: w3ctag/
matatk: This is on tag design review
matatk: Is this aligned with WG pull request?
PaulG: I dont see a PR
PaulG: I think there is some work on CSS interactivity
matatk: They are trying to hormanize HTML and CSS approach
PaulG: I can dig into it and try to understand more
matatk: Jen can also help on this