E-mail List Archives
Thread: SC 1.3.3 Question
Number of posts in this thread: 3 (In chronological order)
From: Jim Homme
Date: Thu, Nov 30 2017 2:02PM
Subject: SC 1.3.3 Question
No previous message | Next message →
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 ADDRESS REMOVED =
http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
E+R=O
From: Lovely, Brian
Date: Thu, Nov 30 2017 2:09PM
Subject: Re: SC 1.3.3 Question
← Previous message | Next message →
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" />
From: Tim Harshbarger
Date: Fri, Dec 01 2017 5:25AM
Subject: Re: SC 1.3.3 Question
← Previous message | No next message
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."