الدلالات ووسوم الاختبار

Compose builds a semantics tree next to the visual one. It describes what each element means, and it is exactly what both tests and screen readers read.

If a node carries no meaning in the tree, finders cannot reach it and TalkBack cannot announce it. Good semantics make your app both testable and accessible. ♿

Icons and images carry no text, so give them a contentDescription. It feeds the semantics tree, letting tests find them and screen readers describe them.

Sometimes many nodes share the same text and a text finder gets confused. You need a stable handle that does not depend on the visible label.

A testTag is an invisible identifier you attach with a Modifier. It gives a node a unique name for tests without affecting how it looks.

Once tagged, locate the node with onNodeWithTag. This is rock-solid even when text changes across languages or states.

Several buttons share the label Done, so a text finder is ambiguous. What gives one button a unique, invisible handle for tests?

Keep them separate: contentDescription serves real users, while testTag exists only for tests. Do not overload one to do the other's job.

For full control, the semantics modifier lets you set custom properties, like marking a node as a heading for accessibility tools.

Compose can merge a parent and its children into one node with mergeDescendants. That makes a whole row announce as a single, friendly unit.

Stuck on a missing node? Call printToLog on the root to dump the full semantics tree, then read exactly what is available to match.

Adding clear descriptions and tags as you build means your tests almost write themselves. Accessible apps and testable apps grow from the same habits.

The semantics tree powers both testing and accessibility. Use contentDescription for users and testTag for tests to keep your UI easy to verify. 🌳