W3C

– DRAFT –
MATF 8 October 2025

08 October 2025

Attendees

Present
GleidsonRamos, Jamie, pauljadam, quintinb, shoobe, shoobe01, Tanya
Regrets
-
Chair
JJ
Scribe
quintinb

Meeting minutes

Second Draft backlog

<JJ> https://github.com/orgs/w3c/projects/147/views/1

Playing by default? I hope it looks for reduced motion settings!

No strong opinions on how to move forward

<JJ> related to how many times to meet ^

2.4.11 Focus Not Obscured (Minimum)

<JJ> w3c/matf#274

No complaints recorded

Or comments

2.5.8 Touch Target Sized (Minimum)

<JJ> Touch Target Size issue: w3c/matf#157 (comment)

<JJ> Text size / dp + pt research: w3c/matf#260

Jamie confirming we're looking at 2.5.8

shoobe01 I am concerned about 24 being too small to be reasonable. What actually happens is that size can vary on position on the screen - another issue is that tablets are not the same.

<Zakim> quintinb, you wanted to ask about dynamic islands

quintinb just wondering if we want to make a note about the system adding dynamic regions around "more isolated" components. Apple do that, and so does React Native has a "hitslop" - I don't believe this is useful as the touch region will change depending on screen size and other surrounding elements

<shoobe01> Never heard of the dynamic region thing (!): totally +1 need to have a note about that and links to read up on it, decide how to add it in.

Happy to share a XCUITest with you that infuriates me

<shoobe01> Agree that it is likely too complex to specify physical sizes; I am using those for the math, but am seeking DIP/px sizing that works for the next draft.

Google are not the standards. We are the stanards!

He said spelling standards wrong

Tanya I was thinking about the SC from a tester perspective - this might be a little too technical for auditors. We should be careful about recommendations, because non-modified components may fall under an exception. Maybe we should have a general note and comment about the platform recommendations?

3.1.2 Language of Parts

<JJ> w3c/matf#173 (comment)

<Zakim> Tanya, you wanted to explain comment with proposal

Tanya we should avoid being very specific that can be outdated quickly

Recommend using examples to mention specific / OS behaviour

3.2.2 On Input

<JJ> w3c/matf#197 (comment)

I'm concerned a lot of people will fail if it's not related to a logical position and predictable behaviour

I was trying to pay a company, and the error message "Something went wrong" appeared at the top of the page. I had no idea why the "Take my money" button wasn't working

Not modified by author / provided by the user agent

<JJ> w3c/matf#80 (comment)

Minutes manually created (not a transcript), formatted by scribe.perl version 246 (Wed Oct 1 15:02:24 2025 UTC).

Diagnostics

Active on IRC: GleidsonRamos, Jamie, JJ, pauljadam, quintinb, shoobe01, Tanya