– DRAFT –
MATF 24 September 2025

scribe quintinb

Mostly important to scribe who to work on what

Got it :P

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

Cross-platform Framework definition

<JJ> w3c/matf#84

ACTION: w3c/matf#84 still to be assigned

Change of Context

<JJ> w3c/matf#69

ACTION: w3c/matf#69 worked on by Tania and Jamie

<GleidsonRamos> I'm available for the cross-platform. Sorry the delay.

pauljadam I was wondering if it's as simple as removing "web" from the current definition. Normally that works

ACTION: w3c/matf#84 assigned to GleidsonRamos

User Interface Component definition

<JJ> w3c/matf#68

<Joe_Humbert> i guess I don't consider something applicable as written if we are changing wording and adding notes

ACTION: w3c/matf#68 assigned to quintinb

ACTION: Check with W3C technical staff for GitHub account linking for assigning GitHub issues

Out of scope issues

<JJ> https://github.com/orgs/w3c/projects/147/views/1 (Out of scope column)

ACTION: https://github.com/orgs/w3c/projects/147/views/1 (2.4.11) going beyond what we should focus on, just terms in WCAG. Joe_Humbert: surprised it's not already included in draft. Joe_Humbert to make a PR

ACTION: w3c/matf#240 to be closed

ACTION: w3c/matf#71 to be closed

ACTION: w3c/matf#229 to be closed

ACTION: forget action 8

ACTION: w3c/matf#245 to be closed

ACTION: w3c/matf#246 to be closed

ACTION: w3c/matf#91 to be reviewed

ACTION: w3c/matf#226 to be closed

ACTION: w3c/matf#197 to be closed

<JJ> `Changing the setting` of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.

<pauljadam> Maybe "changing the state" instead of setting?

Would changing font size be consiidered a setting?

In Android changing to dark mode triggers lifecycle events

ACTION: ignore action 15

ACTION: Raise issue for "Changing the setting" (SC 3.2.2) in AG WG

ACTION: w3c/matf#165 to be closed

ACTION: w3c/matf#172 to be closed

ACTION: w3c/matf#213 to be discussed (back in scope)

ACTION: w3c/matf#111 still has discussion points

ACTION: Raise issue for 2.5.2 - Pointer Cancellation - Clarification on "Abort or Undo" in AG WG

ACTION: w3c/matf#107 to be closed

ACTION: w3c/matf#65 to be closed

Closed issues

<JJ> https://github.com/w3c/matf/issues?q=is%3Aissue%20state%3Aclosed%20sort%3Aupdated-desc

or Windows phone or Blackberry

But I think that's good - staying agnostic is future-proofing

<JJ> JJ: Went through 20 or so issues explaining why they were closed, mostly because of duplication or outdated

ty bye bye!