Meeting minutes
<FredrikFischer> Would a TPAC topic be a TPIC?
accessibilityFeature property in schema.org CreativeWork class: http://
Agenda Review & Announcements
janina: Two CfC are open: Publish XAUR, Comment on PiP spec.
TPAC Planning https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2021
janina: Will post proposed meetings on the Wiki. Around 14 perspective meetings.
… Will try to combine some of them.
… Cross-group meetings will be in the first week, starting Oct. 14.
… Meeting planned on existing accessibility APIs.
… Request to persons who have raised comments on this issue. Please attend this meeting in the second week.
… Plan to have a plan for our meetings by next week.
… We will be reaching out to other groups for joint meetings.
… Some of the 14 meetings were intended to be break-out sessions.
Task Force Updates
janina: RQ - XAUR ready to become a note.
… Still working on doc: Guidance on how to hold remote meetings accessibly.
… Will also include the experience of the last couple of years.
… Will have a first public wd by TPAC.
… Other docs are also on work by RQ.
… Pronunciation wg also working on github issues.
… Joint meeting with Coga requested.
FAST Update
MichaelC: Nothing to report.
New Charters Review https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22
MichaelC: No new charters.
A11y Review Comment Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review
<MichaelC> https://
MichaelC: Had already auto, thin and none.
… Do we care?
Gottfried: Quote: "This could create concerns for users with specific accessibility needs."
janina: I think that a braille display would use the wide value.
… The wider the scrollbar the better.
paul_grenier: The wide value controls the scroll bar.
paul_grenier: Accessibility concern is that the none option removes the scroll bar, and only mouse users can scroll.
… Maybe voice control would work.
Lionel: So one perceptual element is eliminated - that's the concern.
paul_grenier: It is recommended if using "none", other ways of scrolling should be provided.
Gottfried: Could the "wide" value being added be an a11y issue as well? E.g. for high zoom factors.
paul_grenier: "wide" could be overridden by a user style sheet.
… If "thin" is not a concern - why would "wide" be?
… "none" has to have big warning signs.
JF: They are specifying "auto" without defining what it means.
… We should provide feedback that "auto" should be defined.
janina: We should create a comment about "auto".
<JF> the scroll bar should zoom at the same degree as the on-screen content
paul_grenier: If "auto" is meant to vary between sizes, what does it mean when the user zoomes?
… If authors want to define break points for the size of the scrollbar, go for it.
<Lionel> A+
<Lionel> a+
<Lionel> a+
JF: "auto" should mean that the scrollbar should grow at the same pace as the font size.
paul_grenier: Could even be a user-selected setting.
… As a keyboard user, i don't need a larger target for the scrollbar.
… Let browsers get some experience with it, then define it.
JF: We should give feedback of the ways this could be interpreted. And ask them for clarification.
paul_grenier: Browser manufacturers should drive this.
Lionel: Two things: 1. Definition of "auto" is missing.
… 2. Alternative method for scrolling should be offered when the scrollbar is not displayed.
paul_grenier: If nobody else wants this, i can take it.
Action: paul_grenier to draft a comment on [css-scrollbars] Add wide value to scrollbar-width, https://
<trackbot> Error finding 'paul_grenier'. You can review and register nicknames at <https://
Action: PaulG to draft a comment on [css-scrollbars] Add wide value to scrollbar-width, https://
<trackbot> Created ACTION-2301 - Draft a comment on [css-scrollbars] add wide value to scrollbar-width, https://
new on TR http://www.w3.org/TR/tr-status-drafts.html
<MichaelC> CSS Fonts Module Level 5
MichaelC: We might want to review this one.
janina: Ian here?
… What was our concern?
MichaelC: Emojis... A lot of discussion.
… Paul could start with review of level 5 and then go up.
paul_grenier: Is there a link to the changes?
MichaelC: https://
MichaelC: Level 4 is still in WD.
… Best to complete the comments on level 4 first.
<MichaelC> EPUB 3 Text-to-Speech Enhancements 1.0
janina: Could be of some interest to pronunciation tf.
MichaelC: We should talk with pronunciation about this
paul_grenier: The old colon-namespace is not the model we are going for.
… I or Markku Hakkinen could address it
… They should better diverge from the XML namespacing.
MichaelC: It is a WG note currently.
… Not clear why they picked a different notation.
… Let's all sync up our proposals.
… Maybe they are not aware of the status of an "official note".
JF: They are talking about stand-alone reading systems, not necessarily a full-blown screenreader.
… I agree we got a better solution from the pronunciation tf.
… We can try and win them for our solution.
MichaelC: Browsers will not support two approaches.
JF: Thorium will read the page out loud.
<JF> https://
FredrikFischer: Agree with John. We should try to get them use the solution by pron tf.
<JF> +1 to Janina
MichaelC: We should try to do something about notes. This should be just a note, not a "normative note".
janina: I am concerned about the discrepancy between EPUB and our pron tf.
<FredrikFischer> What's the difference between a recommendationand a normative note other than the normative note having a somewhat less grueling review process?
janina: On our planned agenda for TPAC, we wanted to talk about schemas.
… We should add this to the agenda.
Action: FredrikFischer to review EPUB 3 Text-to-Speech Enhancements 1.0, https://
<trackbot> Created ACTION-2302 - Review epub 3 text-to-speech enhancements 1.0, https://
ACTION-2302 due 08/18/21
<trackbot> Set ACTION-2302 Review epub 3 text-to-speech enhancements 1.0, https://
<MichaelC> VISS version 2 - Core
janina: Scoping in automotive is not really related to accessibility
MichaelC: Next one is on transport. We can probably ignore that.
JF: Is messaging a concern for us?
janina: It is about temperature etc.
… Android auto seems to be the choice for the car dashboard.
JF: Section 6 has a subsection on privacy.
… At a minimum, we should have a statement on accessibility. "In terms of messaging, avoid a single modality".
janina: I don't think this is much about output for the dashboard. This is about datapoints.
JF: In-vehicle application best pratices.
… We should look more into this spec. Also talk about accessibility in the same way as for privacy.
Lionel: This might just be a best-practices of data handling.
<JF> https://
JF: At a minimum, we should review what they have on accessibility in https://
janina: Difficult to get accessibility in because of the way this spec has been scoped.
… They say accessibility is out of scope for those specs that are under w3c.
JF: They make this a non-normative requirement.
… Somebody should really review this accessibility section.
Lionel: I am interested.
Action: Lionel to review the accessibility section in the VISS Best Practices document, https://
<trackbot> Created ACTION-2303 - Review the accessibility section in the viss best practices document, https://
ACTION-2030 due 09/04/21
<trackbot> Set ACTION-2030 See if reporting api 1 https://
janina: Meeting adjourned
… Thanks everyone