search

w3c / matf

Guidance from the Mobile Accessibility Task Force (MATF)
https://w3c.github.io/matf/
Other
8 stars 3 forks source link

Success Criterion 1.4.5 - Images of Text - Level AA #29

Closed JJdeGroot closed 2 weeks ago

JJdeGroot commented 4 months ago

Placeholder for meeting of July 17, 2024.

WCAG2ICT guidance: https://w3c.github.io/wcag2ict/#images-of-text

Share your thoughts for applying to mobile apps as a comment below.

illai commented 4 months ago

@JJdeGroot Please change the WCAG2ICT link to: (https://w3c.github.io/wcag2ict/#images-of-text)

qbalsdon commented 3 months ago

Happy with this as is

arctouch-gleidsonramos commented 3 months ago

Should we add that when the text of an image is essential, the image needs to have an alt text for the screen reader? Or is that already implicit?

carolinacrespo commented 3 months ago

Good as it is

JJdeGroot commented 3 months ago
MATF meeting on July 31, 2024 [Source](https://www.w3.org/2024/07/31-matf-minutes.html#t02) JJ: Reading the WCAG2ICT description, mentioning the exception for logo's and essential content quintinb: Does this mean that logo's do not need alt text? Or should it just be the name of company? @JC to @quintinb 1.1.1 would still apply @JJ we need to put guidance on for testing purposes julianmka - does text scaling apply? Are we creating a standard that is not necessarily seen on web JJ feels it applies as is +1 What if the text is part of a background? It's decorative JJ then it does not apply Jamie - We should use WCAG as a base reference - we shouldn't discuss issues that are already on here Jamie we should consider system settings as well Jamie we should add techniques for testing for people who don't have access to code + 1 to what Jamie said. A lot of my thinking around this is very much a testing perspective and providing techniques for native. Totally agree with keeping things simple and not complicated things. Joe_Humbert: Thinks that a future goal should be for us to ask for manufacturers to give us guidance for testing with no source access

Summary:

quintinb asks if logos need alt text or just the company name. JJ responds that 1.1.1 still applies.

julianmka queries if text scaling applies and if a new standard is being created that isn't seen on the web. JJ feels it applies as is, and quintinb agrees.

quintinb asks about text as part of a background and concludes with JJ it's decorative and doesn't apply.

Jamie suggests using WCAG as a base reference and considering system settings, emphasizing the need for testing techniques for those without code access. Mick agrees, stressing simplicity and a testing perspective.

Joe_Humbert proposes asking manufacturers for guidance on testing without source access as a future goal.

julianmka commented 2 months ago

Based on previous task force conversation, this SC can be applied to native mobile apps and mobile web with minimal or no deviation from WCAG2ICT.

Proposal

In MATF's first draft of guidance, this SC's section will read as:

This applies directly as written, and as described in Intent from Understanding Success Criterion 1.4.5.

Would we also want to include the note on Closed Functionality?

NOTE See also the Comments on Closed Functionality.

Keanem6 commented 2 months ago

I've not come across experiences of closed functionality with mobile apps so I'd lean to leaving it out but perhaps others know of examples.

julianmka commented 2 months ago

After discussion and voting at the meeting today, the task force members present accepted the proposed language for the first draft of our guidance.

JJdeGroot commented 2 weeks ago

Closing this issue because the draft language has been accepted.