Meeting: February 6, 2024

[zcorpan]

Previous meeting: #85

This meeting will be February 6, 2024 @ 9AM Pacific. The meeting is usually recurring the first week of the month.

Please let @zcorpan know if you'd like to participate in the meeting and he can add you to the calendar invitation. Use the Agenda+ label on issues in this repo to add agenda topics, and/or comment below.

Next meeting will be #107

[zcorpan]

Topic: Add nameFrom: heading tests once the AccName change is reviewed
Jcraig: I have reviewed these. The ARIA WG is changing their process for what makes it into the spec. Change involves name from heading.
Topic: Investigation: Accessibility Tree Dump API
Z has some PRs.
Boaz: Yes
Boaz: Z is at Bocoup, we’re working on an experimental feature in Chromium to dump the a11y tree. Foolip said this should have an wpt RFC. Discussion, seemingly is not going to work due to being vendor-specific.
Boaz: Idea to standardize a11y tree and tree dumping.
Jcraig: thanks. Will follow-up.
Jcraig: Maybe it could be tentative API that dumps a tree with any output for now. WebKit tree is different, Gecko tree is different. “What’s the tree for this leaf node?” Serialized. Might be possible to align on output of that format and develop in parallel with AOM 203.
Boaz: The tests we wrote were just one node. Property names and values are potentially different between browsers.
Lola: Mike started doing some accessible node stuff last year. Incomplete. If it’s connected, may be an opportunity to continue in that vein.
Boaz: WebDriver part …
Jcraig: Might be useful to develop the tree dump and accessible node in parallel.
Boaz: I can comment in the RFC. Can be made vendor-neutral at some point.
Testdriver vendor extensions https://web-platform-tests.org/writing-tests/testdriver-extension-tutorial.html
Rahim: The testing API would be common?
Zcorpan: Yes, but needs to be standardized in webdriver.
Jcraig: Yes but it will be different between browsers.
Jcraig: Chromium has getFullAXTree, WebKit has dumpAccessibilityTree, used in LayoutTests.
Boaz: We could have done the standards work first, but same goal.
Jcraig: This path has the benefit of standardizing the testrunner. One test runner, one test to author, multiple outputs that inform our ongoing investigations.
Topic: Remove the SVG-AAM image test until blocking issue resolved
Jcraig: FYI. Image test. I’ve filed a spec issue. In the meantime removing from the Interop 2024 Focus Area list.
Topic: Are /accessibility/crashtests tests valuable for Interop 2024?
Jcraig: Seems like tests are no longer included. I’ll follow up and close.
Topic: Write tests for click event handler addition on role="button"/tabindex=0 elements
Rahim: role=button and automagical addition of click event automatically?
Jcraig: I recall if you add tabindex or role=button, if you press the return key it would fire a click event.
Rahim: I can write a test
Jcraig: Save the time. Since it's already implemented in an interoperable way, there are many more important things to worry about.
Topic: Can we add file-level suggested reviewers in wpt-metadata?
Jcraig: Test change was landed and caused unexpected Interop tests.
Zcorpan: More general issue for Interop test changes.
Zcorpan: There’s a process for test change proposals for Interop, but no enforcement by the CI bots.
Topic: Interop 2024 Accessibility Investigation
Jcraig: Success last year from early discussions about scope.
Jcraig: Tree dump I think is good to include. Then other issues.
Zcorpan: Datalist was accepted as Interop 2024 investigation, but merged with accessibility.
Boaz: Rahim also has an issue open about documentation.
Boaz: #51 is the treedump API. Spec.
Topic: Issue triage
Accname Chromium tests, port to wpt? #41
New label “2024-investigation-candidate”

[cookiecrook]

Next meeting will be #107