WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: SC 1.3.3 Question

for

From: Tim Harshbarger
Date: Dec 1, 2017 5:25AM


Maybe another way to state this criterion to make it easier to understand would be something like this:

When writing instructions to help your users more effectively use your web site or application, ensure those instructions do not solely rely on sensory characteristics of content. Characteristics of content, like shape, colour, spatial relationships, sounds, etc, are only available via a single sense (like vision or hearing.) You can and should use these characteristics in your instructions to help your users. However, you should also include information that will help the user that doesn't rely on them being able to see, hear, or otherwise depend on a single sense to use the instructions.

For example, use "click the green Save button" instead of "click the green button".

I don't think of this criterion as being "Don't do this" but more "If you do this, you need to do this other thing as well."

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Lovely, Brian via WebAIM-Forum
Sent: Thursday, November 30, 2017 3:09 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] SC 1.3.3 Question

I suppose there could be some situation where a specific shape would need to be described, but I think in most situations, this just means to ensure there is a perceivable equivalent to information that is otherwise communicated only visually. For instance, a list of tasks with some of them displaying a checkmark image next to them meaning that they have been completed. In this case, I don't think it's necessary to describe the shape of a checkmark, but just to indicate that the task has been completed. If the checkbox image is inline, it can be done using the image's alt attribute: <img src="path/to/image" alt="completed" />

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Jim Homme
Sent: Thursday, November 30, 2017 4:02 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: [WebAIM] SC 1.3.3 Question

Hi,
My interpretation of the below page is that the only way to ensure that 1.3.3 is satisfied is to have visible text labels that indicate what shapes mean. I have two questions about the content of the page. Which shapes are universally accepted? And is this interpretation too strict? One reason I ask this is that it is possible to have a universally accepted shape, and have text spoken by a screen reader that indicates the shape's meaning. Which people with learning disabilities would be impacted one way or other other?

https://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-understanding.html

Thanks.

Jim
=========Jim Homme,
Team Lead and Accessibility Consultant,
Bender HighTest Accessibility Team
Bender Consulting Services, Inc.,
412-787-8567,
<EMAIL REMOVED>
http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
E+R=O

The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.