Meeting minutes
<matatk> presetn+
<janina> Link to my recital: https://
<SteveF> note: I will only be here for 15 mins as I have a drs appointment
Agenda Review & Announcements
Task Force & Deliverables Updates
janina: no anouncement
matatk: agendum 2 was dropped, so nothing missing here.
janina: there is a wide review to do about maturity model.
janina: this is a major achievement, we really need people review. It's about how we track accessibility and maturation, over time.
New Charters Review
<Roy_Ruoxi> w3c/
Roy_Ruoxi: we have a new charter proposal for Publishing, ready for review.
janina: we need more time, we're not ready, we have to take the time to read all that.
matatk: i see no blockers here.
janina: it's not epub 4, only enhancements on epub 3, probably 3.4 so we should not block the review.
janina: we have our answer, you can close the issue Roy.
<SteveF> i gotta go, see you next week
CSS Update (Paul)
EXIF data, attribute, and other approaches
<PaulG> w3c/
PaulG: main discussion is about image orientation attribut, shall it work as it does or shall we change the behavior to allow shifts driven by user action
PaulG: it's an implementation problem as this information usually comes late and the reflow is done. Implementers are looking for predictability.
janina: it sounds our concerns are adressed.
reading-flow and related questions
<matatk> Some CSS questions, about reading-flow, but there are a few relevant sections of the docs...
<matatk> 3. Display Order: the order property - https://
<matatk> 3.1. Reordering and Accessibility - https://
<matatk> 4. Reading Order: the reading-flow property - https://
matatk: I try to figure how those CSS properties fit to accessibility.
<PaulG> https://
PaulG: we had demos.
PaulG: as things are moved around by the layout engine, visual order may not be important, but for keyboard users that's a way to follow an order. We offer flexibility for authors.
matatk: all exemples i've seen, are about interaction and tab focus order. My question is would virtual cursor rearange reading order?
PaulG: there is still work to do for implementation, but RS agents are confidents they could if they receive the information. CSS does not manipulate the dom the same way.
matatk: so my understanding is that the spirit would be to make it as accessible as possible ut not implemen,ted yet
/but/but/
PaulG: navigation is not affected by reading order, we'll have to add recommandations for implementation to cover as many use cases as possible.
janina: some better labels could be found maybe.
janina: it's important to coordinate with order problems faced by epub.
<Zakim> janina, you wanted to ask coord with epub a11y ordering
janina: because there user agents respond differently. We don't want different ways.
gautierchomel: The problem we have with fixed layout is that reading order may be shared between two different documents; haven't seen this in web pages. We need something like aria-flow but across documents.
… Not sure the use case exists in the web. Would be happy to know if someone has met this use case before.
<PaulG> I need to drop
matatk: back to css, i design an issue and we'll discuss next week.
Actions check-in
gautierchomel: the issue about FXL reading order is there : w3c/
EPUB 3.3 changes review
matatk: we found no issue here. Mike reviewed and was happy with the changes. As no one steps up for further look, we can proceed to closing this review.
matatk: a point about our review process, to be very transparent. We try to have a one voice to respond to external requests, after discussion in our calls. It's to make sure people don't misunderstand individual comments as official APA comment.
Vibration API review update
This one is a good exemple of review process where we have APA internal discussion in our issue and move the comments to the Group Issue tracker when we have an agrement between us. So the group gets a clear request from us and can integrate in it's workflow.
Here we asked for language written as a MUST instead a SHOULD. They responded and I think it's a clear respons with documented discussion. We should not block.
Other business
Be done
<janina> s/old/new/
<gautierchomel> s/impleme,ted/implemented/