Drafts for 2.4.6, 2.4.4, 2.5.3

[JJdeGroot]

Adds draft text for:

• 2.4.6: https://deploy-preview-117--wcag2mobile.netlify.app/#success-criterion-2-4-6-headings-and-labels
• 2.4.4: https://deploy-preview-117--wcag2mobile.netlify.app/#success-criterion-2-4-4-link-purpose-in-context
• 2.5.3: https://deploy-preview-117--wcag2mobile.netlify.app/#success-criterion-2-5-3-label-in-name

NOTE: Only the .md files need a review, the index.html is generated

This will:
resolve #50
resolve #36
resolve #39

[netlify]

✅ Deploy Preview for wcag2mobile ready!

Name	Link
🔨 Latest commit	a23ef36
🔍 Latest deploy log	https://app.netlify.com/projects/wcag2mobile/deploys/68405c5a5e07940008a92457
😎 Deploy Preview	https://deploy-preview-117--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.

[jha11y]

@JJdeGroot For https://deploy-preview-117--wcag2mobile.netlify.app/#success-criterion-2-5-3-label-in-name, should it be "the name must include most of the primary visible label but is not required to contain all presented text."?

Also, "name" in the above phrase should link to the definition like in the SC text, correct? Otherwise the other changes look good. apologies for the delayed review.

[jha11y]

Notes from June 11 MATF meeting

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

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

Nothing from me

Apple says this about Voice Control:

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.

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

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.

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

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

Also no definition of "primary visible label" and "presented text"

^

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

Summary:
PRs for 2.4.6 and 2.4.4 are good with the group
Group is not completely happy with drafted note for 2.5.3
Action: jamieherrera will propose and updated draft note and possible modifications to normative text

[JJdeGroot]

@jha11y based on group decision, I will create a new PR for 2.4.4 and 2.4.6 to get those merged, and keep 2.5.3 in this PR.
In the future, it's probably better to create 1 PR for each issue.

[JJdeGroot]

I'm not sure what happened, but after merging #222 this PR also got auto-merged somehow. Will create a new PR for 2.5.3.

[JJdeGroot]

New PR: #223