# Sensory Characteristics: Instructions for Everyone

Source: https://allyway.ai/glossary/sensory-characteristics

Sensory characteristics is WCAG success criterion 1.3.3. Instructions for understanding and operating content must not rely solely on characteristics such as shape, color, size, visual location, orientation or sound – they also need a name, label or other cue.

Sensory characteristics are cues such as shape, size, position on the screen or a sound. WCAG 1.3.3 says instructions must not rely on them alone: "click the round button on the right" tells a blind visitor nothing. Add the button's name, and the same sentence works for everyone.

## What it means

[WCAG 1.3.3 Sensory Characteristics](https://www.w3.org/WAI/WCAG22/Understanding/sensory-characteristics.html) is a Level A criterion in [WCAG 2.2](https://allyway.ai/regulations/wcag-2-2). Instructions for understanding and operating content must not rely solely on sensory characteristics of components. W3C names these characteristics:

| Characteristic | Instruction that fails on its own | Instruction that works |
|---|---|---|
| Shape | "Press the round button" | "Press the round **Continue** button" |
| Size | "Use the large field" | "Enter your message in the large **Message** field" |
| Visual location | "See the box on the right" | "See **Opening hours** in the box on the right" |
| Orientation | "Swipe the slider upward" | "Use the **Volume** slider" |
| Sound | "Continue after the beep" | "Continue after the beep or the message **Ready**" |
| Color | "Required fields are red" | covered by [use of color](https://allyway.ai/glossary/use-of-color) (guideline 1.4) |

The point is not to remove visual cues – W3C stresses that shapes and positions help many people, including people with cognitive disabilities. The rule is that the same information must also be available in another way, usually a visible text label that matches the control's [accessible name](https://allyway.ai/glossary/accessible-name).

Who is affected: people who are blind or have low vision, people using a [screen reader](https://allyway.ai/glossary/screen-reader), and anyone whose layout differs from the one the author saw – on a phone, the box "on the right" often sits below the content.

> **Note:** > **"Below" and "above" can be fine**
> W3C allows references such as "choose one of the links below" when the content follows in the reading order and the reference is unambiguous. Describing tactile cues of physical hardware ("the round key on the right side") is also allowed.

## Examples

```html title="Example"
<!-- Fails: only shape and position -->
<p>To order, press the green arrow at the bottom right.</p>

<!-- Passes: the instruction also names the visible label -->
<p>To order, press <strong>Next</strong> (the green arrow at the bottom right).</p>
<button type="submit" class="arrow-button">Next</button>
```

The second instruction keeps the helpful visual hint but adds the word "Next", which sighted users see on the button and screen reader users hear as its name.

**Do:** Do

Name the control in every instruction, use the exact visible label, keep shape or position as an extra hint, and make sure the content order in the code matches the reading order.

**Don't:** Don't

Write "click the icon on the left", "the star marks optional items" without a text equivalent, "use the big blue button", or rely on a sound alone to signal that a step is complete.

## How to check sensory characteristics



## Questions

Q: What are sensory characteristics in WCAG?
A: They are properties people perceive with their senses: shape, color, size, visual location, orientation and sound. WCAG 1.3.3 requires that instructions do not depend on these properties alone.

Q: Is "click the button below" allowed?
A: Usually yes. W3C accepts "above" and "below" when they refer to content before or after in the reading order and the reference is unambiguous. "On the right" is riskier, because the position changes on small screens.

Q: Is it enough to use icons with a tooltip?
A: Only if the instruction itself also names the item. Telling people to "click the gear icon" fails if the icon has no visible or programmatic name; "open Settings (gear icon)" passes when the button is named Settings.

Q: Does 1.3.3 cover color?
A: Color is mentioned in the criterion, but instructions that rely only on color are mainly covered by 1.4.1 Use of Color. In practice, fix both together: add text wherever color, shape or position carries meaning.

Q: How do I find these problems across a website?
A: Sensory wording in text needs a human read-through. The [free WCAG scanner](https://allyway.ai/free-wcag-accessibility-scanner-for-websites) helps with the related code issues, such as buttons and links without a name, which often come with "click the icon" instructions.
