Meeting: May 7, 2024, @ 9 AM PST

[cookiecrook]

Previous meeting: #110

This meeting will be May 7, 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, or comment below.

Next meeting is: #127

[cookiecrook]

Some proposed agenda items:

• 2024 Accessibility Focus Area
  • Currently at 87.6%
  • results progress, recent discussion, and related test changes
• 2024 Accessibility Investigation
  • Currently at 3.33%
  • Discussion in the last month (starting here) on the tree dump investigation.
  • Other issues with Agenda+ keyword
  • I suggest we assign DRIs for each of the major subtasks and issues if possible in Interop 2024 Accessibility Investigation #90. If not, mark each as at-risk.
  • Adjust scoring criteria if needed.

[spectranaut]

@cookiecrook as an agenda item, I'd like to talk about the accessibility API test suite we've been working on at Igalia: https://github.com/igalia/acacia

And the potential for automated WPT tests of accessibility APIs (replacing all the "manual" tests in core-aam/), here is the first experiment: Igalia/wpt#2

[rahimabdi]

One agenda item from me is sharing progress update on

• Accessibility test standardization, improvements and documentation #83

[cookiecrook]

Meeting ID is not valid for me. If @zcorpan doesn't post a new one here in the first 5m of the call time, I'll post my personal 45m room link.

[zcorpan]

I've created a new Zoom link. Invite sent.

[cookiecrook]

@rahimabdi's update re: documentation (Google Docs)

[zcorpan]

Meeting notes:

Attendees: lola, zcorpan, Nathan LePré, Jacques Newman, James Craig, Tyler Wilcock, Adam Page, James Nurthen, Abdirahim A., Cyns, Keith Cirkel, Chris Harrelson

Revisit moving the "orphaned role" tests to .tentative while ARIA issue discussed
Gecko is OK with changing the spec

Interop 2024 Accessibility Investigation
Aligned on AccessibleNode and wpt-level tree walking

Platform A11y API testing
Valerie: Igalia prototype
Igalia/wpt#2
How to identify the browser? PID, product name?
James Craig: currently wpt.fyi is mostly Linux. If you’re running Chrome on Linux, can you test macOS and Windows APIs? Separate tests?
Valerie: dependent on the platform.
ChrisH: Only gets the current configuration of the browser for a11y API node… The names would be in terms of the platform a11y API?
Valerie: yeah. Current focus is core-aam. Want to be able to test events.
Chris: Didn’t need to modify Chromium?
Valerie: right. Only using a11y API. Need to turn it on, like an AT.
James: test code has access to the a11y API.
Valerie: right
James: hmm, might be a security risk. Can the test do things with e.g. OS settings?
Valerie: haven’t considered that so much yet.
Cyns: In my old project, Windows-only and Edge. Connect UIA etc. Extends WebDriver. Code exists. See https://github.com/microsoftedge/a11y

Accessibility test standardization, improvements and documentation
Abdirahim: https://docs.google.com/document/d/1Q3A8Y-xcqcKL2BUYyakroWDdHSiYQjkxtxzx_twR0GQ/edit