W3C

– DRAFT –
APA Weekly Teleconference

20 Nov 2024

Attendees

Present
Dr_keith, Fazio, gautierchomel, janina, JonCohn, matatk, NehaJ, niklasegger, Roy_Ruoxi
Regrets
Fredrik_Fischer, Gottfried_Zimmerman, Steven_Faulkner
Chair
Matthew
Scribe
NehaJ

Meeting minutes

Agenda Review & Announcements

matatk: next week no meeting

matatk: next meeting will be on 4th Dec

Spec review requests

Vision for W3C

<Roy_Ruoxi> - issue: w3c/a11y-request#93

<Roy_Ruoxi> - Note: https://www.w3.org/TR/2024/NOTE-w3c-vision-20241018/

Roy_Ruoxi: nothing new this week

<matatk> Last week's catch-up on the vision doc: https://www.w3.org/2024/11/13-apa-minutes#ccfe

matatk: Fredrik pointed out that statements are not actionable, was decided to log an issue

matatk: can we sign off? are there any objections?

matatk: hearing none

Comment review requests

Roy_Ruoxi: no new

<matatk> gb, off

User remapping in WebXR Gamepads Module - Level 1

<matatk> source: immersive-web/webxr-gamepads-module#61

<matatk> tracking: w3c/a11y-review#214

matatk: issue is about WebXR Gamepads Module

matatk: just wanted to highlight that this is logged, no action from our side is needed

Check against a11y checklist for CR transition

<matatk> source: WebAssembly/spec#1805

<matatk> tracking: w3c/a11y-review#206

matatk: we can rename our tracking issue

matatk: this is a tracking issue, we do not have to look into it, need to check for a way to close these issues politely

any questions?

Reference Target

<matatk> source: w3ctag/design-reviews#961

<matatk> tracking: w3c/a11y-review#200

matatk: this is related to design review

matatk: customizable web elements accessibility

matatk: difficult to make these elements accessible specially input elements

matatk: TAG is planning to solve this in stages

matatk: research is around shadow DOM element

matatk: Complexity increases with more number of these elements

matatk: no action is required from APA group

matatk: if concerns we can reach out to TAG group

any question?

matatk: we will follow the development on this

[focusgroup] clarify and handle cases where scrollable regions have focusgroups (accessiblity)

<matatk> source: openui/open-ui#1008

<matatk> tracking: w3c/a11y-review#190

matatk: this is regarding scrollable regions of focus groups

matatk: custom select is interesting to work with was a popular choice in a proposal

matatk: more stuff is getting added in native HTML but accessibility is checked for those

matatk: https://codepen.io/scottohara/pen/abMaxNx example to look at

matatk: feedback is asked from APA group

matatk: Paul had replied with a proposal

Actions check-in

Accessibility Conformance Testing (ACT) Rules Format 1.1

<matatk> w3c/a11y-request#89

matatk: it is a first public working draft so we have some time to work on this

matatk: we have a group looking into this issue

Other business

anything?

Minutes manually created (not a transcript), formatted by scribe.perl version 238 (Fri Oct 18 20:51:13 2024 UTC).

Diagnostics

All speakers: matatk, Roy_Ruoxi

Active on IRC: Dr_keith, Fazio, gautierchomel, janina, JonCohn, matatk, NehaJ, niklasegger, Roy_Ruoxi