Skip to content

Conversation

JJdeGroot
Copy link
Member

@JJdeGroot JJdeGroot commented Jul 4, 2025

Adds draft text for 2.5.3

This will:
Resolve #39
Resolve #109

This reverts commit 0721e98.
@JJdeGroot JJdeGroot requested a review from jamieherrera July 4, 2025 15:14
Copy link

netlify bot commented Jul 4, 2025

Deploy Preview for wcag2mobile failed. Why did it fail? →

Name Link
🔨 Latest commit e7a3997
🔍 Latest deploy log https://app.netlify.com/projects/wcag2mobile/deploys/68c175048e03ba00089dd811

@JJdeGroot
Copy link
Member Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

2 participants