Add draft for 2.5.3

[JJdeGroot]

Adds draft text for 2.5.3

This will:
Resolve #39
Resolve #109

[netlify]

✅ Deploy Preview for wcag2mobile ready!

Name	Link
🔨 Latest commit	00b12bb
🔍 Latest deploy log	https://app.netlify.com/projects/wcag2mobile/deploys/69020d6302851700082ad6e3
😎 Deploy Preview	https://deploy-preview-223--wcag2mobile.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[JJdeGroot]

The draft was discussed in the MATF meeting on June 11, 2025

11 June 2025

Source

Joe_Humbert summarises [w3c/matf#36](https://github.com/w3c/matf/issues/36)

No input needed unless you want more edits - issue will be closed soon

Nothing from me

<pauljadam> Apple says this about Voice Control:

<pauljadam> Match Voice Control labels to the visible text. If the Voice Control label is different from the visible text in your app (for example, “Leave call” instead of “End call”), users may be confused.

<pauljadam> https://developer.apple.com/help/app-store-connect/manage-app-accessibility/voice-control-accessibility-evaluation-criteria

pauljadam also mentions Apple's "Nutritional labels" - they also don't mention using just using the first word. How much of the string is required is not exactly clear

pauljadam There are a lot of inconsitency in what should be in the label. We need to be cautious around what the normative wording that we don't contradict.

rachaely What about the existing note in WCAG where the label is in the front of the name. We need to keep that somewhere

<pauljadam> Should there be a note to say something about that Best practice being I'm important for Voice Control so they see the first word of the visible label text shown as the Name of the control when they do the Show Names command?

Jamie I appreciate the suggested change to the note, but I feel like it can be very confusing. For us to add on extra stuff we need to define what we mean as we add to confusion. We're not overwhelming people when they try to understand what we've said.

<pauljadam> All text shown on the focussed control = the label text so all that text must be contained in the accessible name.

Jamie we need to change the phasing

<pauljadam> There's no difference between primary visible label and presented text

<pauljadam> Also no definition of "primary visible label" and "presented text"

<Jamie> ^

<Jamie> change the *phrasing

pauljadam what is a "primary visible label" - is there a secondary visible label?

ACTION: Joe_Humbert to add some notes and Jamie to contribute to improving the wording on 2.5.3

<Jamie> thanks quintinb keeping me accountable

Summary:

• Group is not completely happy with drafted note
• Action: @jamieherrera will propose and updated draft note and possible modifications to normative text

[TanyaVanWorkum]

I have a question regarding the note:
“Some user interface components such as tiles, cards, or list items may include multiple text components. The text that serves as the primary label must be contained in the name. Other visible text components may be exposed through other accessibility properties.”

What does “other visible text components may be exposed through other accessibility properties” mean in practice?

For tiles or cards where all texts are grouped and receive combined focus, it’s important that all text is announced by the screen reader, because otherwise the user might miss part of the information.

I think what is meant here is that not all text within a tile or card serves as a label for the control (for activating it with voice control). Or do we intend here to point out that grouping multiple elements/texts within tiles or cards is not a recommended practice?