APA Weekly Teleconference

21 Feb 2024


Fredrik, janina, Lionel_Wolberger, m-alkalbani, matatk, mike_beganyi
Irfan, Paul, Rita
Janina, Matthew

Meeting minutes

Agenda Review & Announcements

matatk: Quantum chairing arrangement.

matatk: Muad, an XR wiz at Samsung, is joining the call to get marinated in W3C stuff.

<matatk> gb, off

<gb> matatk, issues and names were already off.

Introductions galore for Muad#s benefit.

matatk: Matthew is on holiday next week.

New Charters Review https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22

Second Screen Working Group Charter

<matatk> - charter: https://w3c.github.io/secondscreen-charter/

matatk: Roy is on holiday this week, but Matthew is doing new charters review.

<matatk> - issue: w3c/strategy#444

matatk: It's the Second Screen WG charter!

janina: We have a long time investment and interest in Second Screen. We want as smooth an interaction as possible with them moving forward.

janina: I'm up for looking at the charter.

matatk: I'll give you an action.

matatk: ]

matatk: (Reading from the charter.)

janina: Already have commenbts on the scope of the charter.

janina: Here#s a pointer to the use cases in the MAUR.

ACTION: janina: Review Second Screen WG charter

<janina> https://www.w3.org/TR/media-accessibility-reqs/#requirements-on-secondary-screens-and-other-devices

<matatk> gb, status

<gb> matatk, the delay is 15, issues are off, names are off, full issues are printed 10 at a time; and the repository is w3c/apa

HR A11y Review Comment Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review

Requirements for light and dark colors returned by `contrast-color(<color>)`

<matatk> - issue: w3c/csswg-drafts#9970

Explicit Review Requests https://github.com/w3c/a11y-request/issues

DeviceOrientation Event Specification

<matatk> w3c/a11y-request#71

<matatk> Due: 2024-02-29

matatk: The devices and sensors workign group asked us to turn our draft a11y considerations section into a PR. That is what we will do.

matatk: If I just make a pull request, we could do a CFC which we can approve next week and then do the pull request. Or I could send the proposed text to the list.

matatk: Anyway, it would be good if we could get that done until next week.

janina: I thought we got to a resolutions amongst ourselves.

matatk: We posted the issue to the group (Devices and Sensors) - they asked for a PR. If we should do a CFC on the wording of the PR text we should do that before DSWG does their thing.

Accessible Rich Internet Applications 1.3

<matatk> w3c/a11y-request#72

<matatk> Due: 2024-02-23

<matatk> Tracking issue: w3c/apa#341

matatk: I have a couple of things I wanted to mention. There is a lot of really good stuff in here that is going to make a big positive difference. It's a good release.

matatk: The shape of thigns to come is great.

matatk: There is one small bug in that there is a section in the document, the spec, about translatqable attributes and it talks about the value of the attribute is going to the user. aria-label and aria-description. Aria-description isn't included in the list, though.

matatk: The second thign that I wanteed to bring up, I've been meaning to CC Fredrikand Mike on this: The question is, should we suggest slightly stronger wording than exists right now in the spec to discourage the use of ARIA-label, ARIA-description and ARIA-roledescription? The reason I ask this is that there is a good text about not using Brailel labelling unless you know exactly what you are doing.

matatk: A little more discouragement from using it might be appropriate.

matatk: I'm asking for yoru thoughts on the change to existing wording. IN the thread that we've got, the tracking issue, I will put a link to the bits that I'm talking about. There is already some text about it already.

matatk: Anybody is welcome to join in on that tracking issue with comments.

<Zakim> janina, you wanted to ask about braille support

janina: Let me just say that I would just love a solution like CSS Color Contrast. If we'#re relying on content developers to do the right thing with sending a different string to abraille display, we are setting us all up for failure.

mike_beganyi: My immediate thoruhgt is the best use of ARIA is the not use of it all. Having a bit stronger wording would probably be a good idea.

matatk: One thign we have to bear in mind when doing this is that there are very legitimate use cases for ARIA-label and also ARIA-description. The concern is that people are going to overuse it. The spec still has a right to have that stuff in it. The materials that EO produces and also the ARIA-APG team all have that warning you gave.

matatk: They very strongly discourage content authors from providing braille strings. They don't want authors to do it unless they really know what they are up to.

matatk: They may be relying on AT to do it. In some cases the content author may know better, but handle with care.

matatk: Maybe a note to say "Please consider making the text available in the DOM if it isn't because that may help more people".

Summary of action items

  1. janina: Review Second Screen WG charter
Minutes manually created (not a transcript), formatted by scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).


All speakers: janina, matatk, mike_beganyi

Active on IRC: Fredrik, janina, Lionel_Wolberger, m-alkalbani, matatk, mike_beganyi