Meeting minutes
<janina> /join #rqtf
Agenda Review & Announcements
janina Pretty much standard agenda.
janina We'll be without Janina next week - she will be at the UN.
janina In two weeks, I am proposing, and I have ofered to EPUB that we could do a deep dive on all their specs. I want to narrow the focus to the ones that have elicited concern in the last couple of months, primarily the Fixed Layouts spec.
janina We have an alternate direction by way of which Fixed layoutt can work and get more accessibility.
janina I am very concerned personally on a personal view that htere is a note from EPUB talking about a11y and FL. The answer is that there are many aspects we consider important t that can't be met in FL.
janina I am not happy with that and I'm not sure what we are going to do with it.
janinaWe don't have any control over notes poublished by other WGs.
janina On the 19th, I'm expecting, it is proposed that we could have Gottfried for whom this was an EU concern. We also discovered concerns. And possible ways around it.
janina So that means an EPUB focused agenda a and not our standard agenda.
<matatk> https://
matatk: For proper formatting, we need a colon. That is a funny sentence.
matatk: Is anybody struggling with the W3C Calendar entry for this meeting?
Dr_Keith: I had a challenge to get into the meeting today. I got to a page with minutes from the main meeting. It took me a couple more clicks to get to the actual meeting.
janina: I was speaking for myself concerning EPUB but my sense is that APA would not be far away form what I'm saying.
Lionel_Wolberger: They have a pressing business case and balancing business against a11y may need some batting around.
janina: One concern is with the title of the report, that currently includes the word 'accessibility'
WCAG 2.0 issue - conformance levels
Fazio: I discovered that there is a 15 year gaping hole in WCAG 2.0. There has never been a deifnition of what conformance levels are. There is no definitions of what the leevels mean or where conormance criteria belong.
Fazio: This has caused a lot of issues.
Fazio: Perhaps we should make mentions of this in an ammended document.
Fazio: There is a Github issue for this issue.
<matatk> w3c/
<matatk> gb, off
<gb> matatk, issues and names were already off.
<NehaJ> WCAG level definition issue w3c/
PaulG: The thign I've been going through for years based on a W3C graphic is a pyramid, which seems to be rather well-known.
janina: We're into the details of what it should be in detaill. It needs to be a generally defined thing though.
PaulG: I read it on a W3C site.
janina: I've read it, too.
janina: It needs to be linked directly in the spec.
matatk: The issue here seems that it is not normative.
Fazio: It is a n example, not a definition, and defeinitely not normative.
<PaulG> https://
janina: It's not up to us to fix it anyway.
janina: Our participation as individuals is very welcome on that thread.
janina: Were we to weigh in, we would need to be very formal about it.
Epub (part 2) - data vis
janina: There is a lot of low vision stuff to consider here. I will pign Paul.
<matatk> Data Navigator article (HT Paul): https://
PaulG: At the lowest level the data navigator approach is to link the objects of a database relization in code, not unlike ARIA in making the associatiosn with the visuals. The system can then rea that and provide a bespoke navigation patern that matches the data visualization because of that linkage. That's the scaffold you have to add to the DV,
coming provided next to it, and that gives the system the ability to create these on-demand navigation features.
janina: You can get on-demand fixed layout anad that's default?
PaulG: That is a use case that I haven't seen a demo of. It should be possible though. Thedata is embedded in HTML. HTML can be altered to respond to reflow. It also responds to media queries. You can specify: when the media is in this shape, landscape, whaetever, then you have these specific featues that the system will provide you the navigation
for.
TPAC 2024 Planning
janina: I have started building a page for 24. I haven't gotten as far as giving you the link, but you may guess it if you want to .
<matatk> https://
janina: You may expect it shortly on list. there will be an area on that page for you to add things you would like to see covered in the week, something liek "Possile topics".
janina: A planning page has been begun and we have conversations on the side, including with EPUB (surprise!).
<Roy> https://
Roy: Now we have already started a room booking offering. You can book your hotel room through this link. There's good reates here!
matatk: Some permission issues right there.
janina: Roy, might you talke a look at that?
janina: Booking early is strongly, emphatically advised.
Task Force & Deliverables Updates
janina: Our CTAUR CfC was approved!
janina: We are working on messag9ing, I will give Roy messaging at the end of the week. Snawn Henry wil have some edits (always helpful!).
janina: There will be a WAI/announce e-mail going out. I invite you to look at the RQTF publication and share it with all your colleagues.
janina: We're very itnerested in signoff or issues we haven't been able to address yet.
New Charters Review https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22
Web Real-Time Communications Working Group Charter
<Roy> - charter: https://
<Roy> - issue: w3c/
Roy: Web RTC WG recharter!
Roy: They have already added us as a liaison WG and they want to work with us on a11y reqs.
janina: We have worked with them very happily thorugh RQTF.
janina: This is a very welcoming group!
+1
<janina> +1
<matatk> +1
janina: Signed off unanimously!
zakim next item
HR A11y Review Comment Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review
Add a principle that sites should not be _able_ to retaliate when users say no
<Roy> - issue: w3ctag/
Roy: Comment request.
Roy: This has somethign to do with Paul's suggestions on the design document.
matatk: This was Pauls suggestion on the Privacy Principles.
PaulG: I didn't write the topic - where'd that come from?
<Roy> w3c/
matatk: What they are saying is that they already have a similar principle in the Design Principles. But we "Jeffrey Yaskin and someone else)... I don't know what the question is...
PaulG: Mys tatement was that early adopters of this could be fingerprinted by this. They aren't just marked as optin gin or out but they have the opportunity to, which means they are on specific browsers. Their statement is that a web app should be able to distinguish between making the choice or having it by default. They've marked it backburner
to address it in the next version. I'm fine with that. They have the language. I was asking for it to be a little softer.
janina: This is a ll wonderful and a great result and unles someone thinks it needs to be handled now, there is no need to dive in deeper.
matatk: The link was to the a11y issue in the PP repo. The issue I was looking at was in our repo though... (Fredrik is confused)
matatk: We probably won't need to add "needs resolution" at this point, may e in a couple of months.
PaulG: Sound good.
Explicit Review Requests https://github.com/w3c/a11y-request/issues
Roy: Two this week.
Controllers Documents
<Roy> - issue: w3c/
<Roy> - spec: https://
Roy: FPWD Controllers Document Version 1
<Roy> https://
Roy: Comes from Verifiable Credentials WG. They have an a11y section and something in there, too. Looks good to me.
Roy: I think we can reiew the whole document.
janina: We should say what we need to say now, meaning June.
matatk: WE need more time.
Roy: It is an editor's draft. They need a rec by September this year.
<Roy> w3c/
Lionel_Wolberger: I traditionally take the VCWG items.
janina: you've got it!
Device Posture API
<Roy> - issue: w3c/
<Roy> - spec: https://
Roy: Device Posture API.
<Roy> https://
Roy: They also have an a11y considerations section.
mat: I can explain what this is.
mat: It is actually one of ours.
matatk: It's about foldables. The screen size changes when you open or close a device which is foldable.
matatk: It is about giving developers tools to know that an open or close has happened.
matatk: The MQs tell you the information you need to know.
janina: I'm noting that this hould be brought up with tthe FL in mind.
PaulG: It already says, "Content shouldn't be designed for just one posture: The idea of foldable devices is their versatility and the ability for the user to change the posture as they see fit. Similarly to the orientation, it is important to not always choose for the user as they might have other needs but allowing them to choose the UI that fits
their needs better. Ideally it is preferred to make the UI configurable."
matatk: It would be nice for someone other than me to look at this. I'm pretty familiar with it, to say the least.
janina: Do we nee d to tick a box here?
Roy: They want us to review the a11y conisderations section.
janina: I think our response is "Thanks, well done and thanks fo taking up our input so appropirately".
janina: "Also, its been a pleasure workign with you and please come back with your next spec."
PaulG: I'll let tthemknow.
<Roy> w3c/
Roy: Pointer coming!
new on TR http://www.w3.org/TR/tr-status-drafts.html
Roy: Controller spec.
CSS Update (Paul) https://github.com/w3c/css-a11y/issues
PaulG: thankfully nothing!
Actions Checkin (Specs) issues/assigned
matatk: There is something but we didn't have time. We were supposed to come back to fingerprinting this week but we'll have to do it next week.
matatk: Several of us are assigned to this and I've put a comment on it.
<matatk> Mark features that might expose accessibility tools - w3c/
matatk: If youre interested, the plot hath thickened.
janina: To be contineued. Next week.
Other Business
janina: Just a reminder on the EPUB side we have two conversations. They are likely to want to expand, we ware likely to want to focus. We are proposing a direction that we know we can't agree on on the 19th. It will take a lot more conersation, probably all the way to TPAC and beyond. We're finde with their business case ut hwo they charachtereise
their document and the implications thereof is our concern.
janina: I will put all of this to an e-mail that will go to the list.
janina: It#s not locked in yet.
Lionel_Wolberger: I deeply appreciate what you just did. Reverse those two points in the e-mail, though The secon dis a low-hanging frutit that they may snap up directly.
Lionel_Wolberger: I urge you to share more about the UN meeting.
janina: IT's ongoing management of the CRPD and a new 25 year plan.
janina: I will say more on this on teh 26th.
be done
janina: Thanks everyone for all your brilliant lovely participation.
janina: Sorry for honoring the whip and crackign your time.