CoursesCompose Multiplatform, one screen from state to pixels

Puzzle 3 · 4 of 4

Can VoiceOver understand the bookmark?

A custom bookmark icon looks right. Make its action understandable without seeing the screen.

All puzzles in this course

The problem

A custom icon toggles a bookmark and changes from outline to solid. A sighted person can see the difference. What information can a person using VoiceOver get?

See it

Can VoiceOver understand the bookmark? Icon changes Name and state Native mapping VoiceOver

Scroll sideways to see the full diagram.

  1. The icon changes shape when the item is saved.

    Step 1 of 4
  2. The control also exposes its name and its current state.

    Step 2 of 4
  3. Compose maps the description to iOS accessibility information.

    Step 3 of 4
  4. VoiceOver can use that information as the person focuses and activates the control.

    Step 4 of 4

The building block

Accessibility semantics are UI descriptions that a device's assistive technology can use, such as a label, a role, a current state or an action. On iOS, the screen reader is VoiceOver. Compose Multiplatform maps its semantics data to native accessibility services.

For this bookmark, expose what the control does and whether the item is currently saved. Prefer a control that already represents a toggle, then give it a meaningful label and expose the checked state. Keep the icon decorative if the surrounding control already provides the complete description.

SituationWhat the user should be able to learn
Focus before savingWhich item the action applies to and whether it is saved
Activate the controlThat bookmarking can be toggled
Focus after savingThat the item is now saved

A visual check proves part of the behavior. On an iPhone, verify focus order, spoken meaning and whether activating the item changes the state. Test a native field embedded in the same screen independently as well. At the hosting boundary, its view and interaction differ from the surrounding shared UI.

Go deeperDesign a two-platform check
What would a useful check record if the same icon works on iOS and Android?

Record the focused control, distinguish its saved and unsaved states, activate it with the platform screen reader, and verify the result. Keep platform-specific wording separate from the intended meaning.

Back to the main puzzle

Check yourself

The icon is solid after saving, but the action has no label or state. What is the missing signal?

Not quite. Changing pixels does not expose a saved state to the screen reader. Re-read that part ↑

Right. Provide the meaning of the control along with its pixels.

Not quite. The navigation bar does not describe an unlabeled bookmark. Re-read that part ↑

The button already provides the full label. What can duplicate text on the icon cause?

Not quite. Duplicating the name does not remove the state. Re-read that part ↑

Right. Describe one logical control coherently.

Not quite. This concerns focus and labels on the bookmark. Re-read that part ↑

An automated check finds the icon. Which additional check best verifies the intended interaction?

Right. Check focus, spoken meaning and a changed state.

Not quite. Successful navigation does not verify the label or toggle. Re-read that part ↑

Not quite. A screenshot checks pixels instead of the screen reader interaction. Re-read that part ↑

Sources

What you now know

Compose semantics describe meaning and actions independently from pixels. On iOS the mapping to native accessibility information makes those semantics available to VoiceOver.

That's everything published so far

You've reached the last puzzle of Compose Multiplatform, one screen from state to pixels.

New puzzles are announced on LinkedIn and in the learning log feed.

All courses →