Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues for SC 1.3.6 Identify Purpose #539

Closed
jake-abma opened this issue Nov 25, 2018 · 5 comments
Closed

Issues for SC 1.3.6 Identify Purpose #539

jake-abma opened this issue Nov 25, 2018 · 5 comments
Assignees

Comments

@jake-abma
Copy link
Contributor

Success Criterion 1.3.6 Identify Purpose


In the Understanding doc it says:

This success criteria requires the author to add the context, propose, and meaning of symbols, regions, buttons, links, and fields so that user agents knows what they do and can adapt them to make them understandable for the user.

In the normative text I only read the "purpose" is required not the "context and meaning". So, OR purpose, context and meaning in this case means exactly the same (and mentioning all three makes it more blurry and one will be sufficient) OR only purpose is required according to the normative text NOT the others in which the text must be re-written.


In the Understanding doc it says:

... requires ... and meaning of symbols

A symbol may mean different things, like phrases, emblem, pattern, badge, logo etc. and also icons.
So when a symbol is more than only an icon and in the normative text we only speak of icons, this must be changed in the Understanding doc.


Sufficient Technique

As the role region of WAI ARIA "requires" a purpose we can add another sufficient technique using the region role.

"Authors MUST give each element with role region a brief label that describes the purpose of the content in the region."

https://www.w3.org/TR/wai-aria-1.1/#region

Interesting fact here is that we don't provide a "complete list of all purposes in the world" so do wonder how UA or AT might subtract a self-made purpose required from normative WAI ARIA spec.

@detlevhfischer
Copy link
Contributor

context, propose, and meaning

The understanding text really has "propose" instead of purpose, so this typo should be changed ASAP.

@jake-abma I agree, I would suggest to drop 'context' and 'meaning' and home in on purpose to make the Unterstanding text align better with the SC text. It adds imorecision and might also be seen as inviting athours to overload elements.

requires ... and meaning of symbols

Again, I agree it will be easier to focus on icons (there is as far as I know no normative definition of icon, so even a little landscape sketch with an American-style postbox would quality as long as it is used as the metaphoric visual for a particular control (e.g. mail address).

No thoughts on the last point...

@jake-abma
Copy link
Contributor Author

@marcjohlic shall we take action on this one?

mbgower added a commit that referenced this issue Jul 29, 2019
Updates to the Understanding document in response to comments in #539
@mbgower
Copy link
Contributor

mbgower commented Jul 29, 2019

I took a shot at a first update to this Understanding document. Some of your comments seemed already to be resolved (i.e., I couldn't find what you were talking about). This could use a few more passes, but I think it is an improvement: #842

@mbgower
Copy link
Contributor

mbgower commented Jul 31, 2019

@jake-abma and @detlevhfischer I added you as reviewers on the PR

@mbgower
Copy link
Contributor

mbgower commented Feb 25, 2021

The PR was implemented.

@mbgower mbgower closed this as completed Feb 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants