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

Failure F26 links to the wrong SC? #258

Closed
spanchang opened this issue Dec 22, 2016 · 6 comments · Fixed by #767 or #776
Closed

Failure F26 links to the wrong SC? #258

spanchang opened this issue Dec 22, 2016 · 6 comments · Fixed by #767 or #776

Comments

@spanchang
Copy link

From a reading of SC 1.3.3 I gather that it does not relate to images but to instructional text that
refer to other components identifying them by their shape or other
visual attribute.
In my opinion, F26: "Failure of Success Criterion 1.3.3 due to using a graphical symbol alone to convey information" does not seem to have anything to do with 1.3.3. It is a failure of SC 1.1.1 because the symbol has no text alternative.

Thanks,
Sailesh

@patrickhlauke
Copy link
Member

Coming in late, but - as this has recently come up in a discussion - I'd agree with Sailesh that F26 feels like a 1.1.1 failure.

@patrickhlauke
Copy link
Member

bump... @alastc

@alastc alastc self-assigned this Mar 19, 2019
alastc added a commit that referenced this issue Jun 10, 2019
@alastc
Copy link
Contributor

alastc commented Jun 10, 2019

It is closely related, but for 1.3.3 should really focus on the instuctions aspect, created #776 to update.

@electronicwoft
Copy link

does this mean that a new failure technique for conveying 'instructions for understanding and operating content' that rely on 'sensory characteristics' is required? That is, the intelligibility of icons, symbols, etc.?

@alastc
Copy link
Contributor

alastc commented Jun 11, 2019

Hi @electronicwoft, that's an option. It would be hard to specify (e.g. is the home symbol well enough known? Print? Where do you draw the line?).

There is another potential SC about describing icons, which might help with that.

@electronicwoft
Copy link

Hi @alastc ... what about a success criterion that uses a 'prescription of purposes' a la 1.3.5 for which there is a symbol from something like ISO graphical symbols? That is, if something performs A, then it is represented by B. One problem I see with describing icons is the sense often given to 'describe' as 'exhaustively listing the characteristics of' such that what is signified is lost in elucidation thereby being of little utility.

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

Successfully merging a pull request may close this issue.

4 participants