Release Notes
Catalog and per-pattern versions use semver (MAJOR.MINOR.PATCH). Catalog revisions are dated. Each release lists changes by pattern.
0.11.0 — 2026-11-10
Lessons from TalkBack testing in a production Compose app. No pattern changed.
Foundations changes in this release:
- Merged Semantics — Two new Must Haves. A
contentDescriptionset on a merged parent adds a name without removing its children's text, so replacing what the children say takesclearAndSetSemanticson the parent, after itsclickableortoggleable. A merged node reports itsRoleas a class name, such asandroid.widget.Button, only when it has no merged children, so a tile that must announce its role is made childless the same way. - Collection Semantics — New Don't: do not replace a lazy list's
LazyListStatewhile the list is on screen. The accessibility delegate stays bound to the old state, stops reporting scrolls, and TalkBack's heading navigation reports "No next heading." Platform defect: https://issuetracker.google.com/issues/538084338 - Announcements — The
paneTitleMust Have now says that on content that loads asynchronously, the pane title can race the first focus announcement and be cut off or doubled, so the context goes in the first focused element's label instead. New Don't: do not keep a hidden live-region node to carry announcements, since once it holds text it is a permanent extra focus stop. The ban onannounceForAccessibilityandTYPE_ANNOUNCEMENTis unchanged. - Screen Announcement — New Must Have: after a window change (cold start, deep link, new activity), request focus after the window's first accessibility-focus event rather than on first composition, because TalkBack can drop an early request and land on the first focusable node, usually Back.
- Traversal Order — Tightened without banning
traversalIndex: fix composition order or useisTraversalGroupfirst, and use the index only when neither works. It reorders accessibility traversal only, not keyboard, D-pad, or switch access focus, so keyboard focus is made to follow the same order (WCAG 2.4.3 Focus Order, 1.3.2 Meaningful Sequence). - Icons and Images — New Must Have: an image that stands in for text, such as a title logo, is named with
Modifier.semantics { contentDescription = "..." }andcontentDescription = nullon theImage, so it reads as text rather than as an image. The decorative-image rules are unchanged.
0.10.1 — 2026-10-23
The stack now states its scope wherever retrieval reads it. No pattern changed.
Foundations change in this release:
- Scope — The Foundations summary and introduction, and the Components page, say the patterns cover Android phones and tablets and that Android TV, Google TV, and Fire TV are out of scope. Code that runs only on a TV does not apply them. Code in a module that the TV build also uses follows them, unchecked against TV behavior. The summary carries the statement because the MCP server's
get_foundationsreturns the frontmatter and the rules but not the introduction. The skills have run the same check before every task since October 7.
0.10.0 — 2026-10-06
The app's chrome: three wave-2 patterns for the bars and the drawer around a screen, checked against the stable Material 3 1.4.0 and Compose UI and Foundation 1.12.1 sources.
- Top App Bar → 0.1.0 — All four of Material's top app bars read the navigation control, the title, and the actions in order as one group, and none marks the title as a heading, so the pattern does. The navigation control is named for what it does ("Navigate up", "Open navigation menu"), and the content is padded clear of the bar so it never covers a focused item. All four bars are stable; only their scroll behaviors are still experimental.
- Bottom App Bar → 0.1.0 — A traversal group of actions with the floating action button read last, and nothing else from Material, so each action is named as
button.basicdescribes and the content is padded clear of the bar. Actions stay actions: an item that marks the current screen belongs in a navigation bar. - Navigation Drawer (Modal) → 0.1.0 —
ModalNavigationDrawernames its panel "Navigation menu", gives it a dismiss action, and makes the scrim a "Close navigation menu" control, but leaves the screen behind in the accessibility tree and does nothing with focus or keys. The pattern hides the covered screen while the drawer is open, keeps keyboard focus inside the drawer, moves focus in on opening and back on closing, and closes on Escape. Turning off gestures also turns off the scrim's tap to close.
Foundations change in the same release:
- Headings — A title passed to a
TopAppBar's title slot is marked as a heading. The rule had exempted titles supplied through a component's title slot, which assumed Material marks them; none of its top app bars does. AnAlertDialog's title stays unmarked, since TalkBack lands on it when the dialog opens.
0.9.0 — 2026-10-06
Five more wave-2 patterns: the small surfaces that carry state or meaning, and the select. Checked against the stable Material 3 1.4.0 and Compose UI and Foundation 1.12.1 sources. CVS has no technique for the chips, badge, or card; the device checks all five rely on are on the validation list.
- Filter Chip → 0.1.0 —
FilterChipreportsRole.Checkboxwith a selected state and drops its border when selected, which carries the state without color. The set of chips is named for what it filters, and a change to the results is announced once as a short count rather than by moving focus. - Input Chip → 0.1.0 —
InputChipis a single click target, and its trailing icon is content rather than a button: a close icon placed there joins the chip's name and removes nothing. Removal is a remove button inside the chip, its own TalkBack stop named for what it removes, the way Android's View-based Material chip exposes its close icon, plus a "Remove" custom action on the chip itself. Focus moves deliberately after a removal. - Badge → 0.1.0 —
BadgeandBadgedBoxset no semantics, so a count merges into its host's name as a bare number and a dot badge says nothing. The badge replaces its own content with words ("3 unread"), whichBadgedBoxplaces after the host's name; a status beside a person's name goes on the row asstateDescriptioninstead. - Card → 0.1.0 — The static card is a traversal group; the clickable overload merges its content into one stop and sets no role. A clickable card puts its name first, carries a click label, and exposes any secondary control as a custom action with the control itself hidden.
- Select → 0.1.0 —
ExposedDropdownMenuBoxwith a read-only field:menuAnchorreports the field as a dropdown list and opens it from touch, TalkBack, and the keyboard, butDropdownMenuItemreports no selection, so the current option is marked by hand. The component is still marked experimental, so the call site opts in. It ships anyway, by exception: the 1.5.0 previews drop the marker with the same parameters, so only the opt-in line changes when it is stabilized.
0.8.0 — 2026-10-06
The first wave-2 patterns: four selection patterns that report checked or selected state, checked against the stable Compose Foundation and UI 1.12.1 and Material 3 1.4.0 sources.
- Toggle Button → 0.1.0 — Material's icon toggle buttons report
Role.Checkboxand a checked state, so the name says what the control turns on and stays the same in both states; a name that changes to the next action belongs tobutton.basic. The standardIconToggleButtonshows its checked state by color alone, so its icon changes with the state as well. - Checkbox Group → 0.1.0 — Several checkboxes answering one question. Nothing on Android ties a label to a set of controls, so the container is named for the question, and
selectableGroup()derives position only from selectable children, so a checkbox set declares its collection properties by hand. A requirement on the whole set gets one error, announced once, rather than an error on every option. - Tri-State Checkbox → 0.1.0 —
TriStateCheckboxandtriStateToggleable, with Compose supplying "Partially checked" as the third state's description. The parent's state is derived from its children every time it is read, and activating it checks or clears them all; a cycle that restores the user's last mix is allowed as a variant. The same row-hoisting rule ascheckbox.basic, sinceTriStateCheckboxapplies its 48dp minimum only while it owns its callback. - Segmented Button → 0.1.0 — One pattern for single and multiple choice. The single-choice row gives each segment
Role.RadioButtonand its position in the set. Material's multiple-choice segment reports a checked state but no role, and its row reports no set, so the caller addsRole.Checkboxand the collection properties. A selected segment keeps its check mark, without which it differs only by container color. Planned as two patterns; written out, six of eight Must Haves were shared, so it ships as one. - Button → 0.3.0 — An icon-only button is named on its
Icon, which the button merges into its own name, matching Android's documentation and the CVS techniques; the pattern's own example already did this. A control that turns a feature on or off and keeps its name now routes tobutton.toggle, and a button whose name changes to the next action, such as "Play" and "Pause", stays here. - Checkbox → 0.1.2, Radio Group → 0.1.2, Tabs → 0.1.1 — Redirects now name
checkbox.groupandsegmented-button.basic.
Foundations change in the same release:
- Icons and Images — An icon that is the only content of a control is named on the
Icon, not on the control. The control keeps its role and merges the description into its name, so TalkBack hears the same thing either way, and this is the form Android's documentation and Material's samples use. The control is named instead only when its content changes on screen, such as anExtendedFloatingActionButtonthat collapses to its icon. Naming both still announces the name twice.
0.7.0 — 2026-10-06
The last wave-1 patterns, which completes the first wave: eighteen patterns. Checked against the stable Compose Foundation and UI 1.12.1 and Material 3 1.4.0 sources.
- Link → 0.1.0 — Compose has no link role and no Link composable. A
LinkAnnotationis announced as a link but its tap area is clipped to the outline of its characters, so a standalone link is aTextButtonwhose text names the destination, with a click label when it leaves the app. Namedlink.basicto match web and iOS; it waslink.standalonein the taxonomy, with no recorded reason to diverge. - Inline Link → 0.1.0 — Compose exposes each
LinkAnnotationas aURLSpanorClickableSpanon its text, not as a node, so TalkBack reaches it through its Links menu and the link text has to stand on its own. The link node sets no indication and Material's default link style sets nofocusedStyle, so keyboard focus is invisible until the caller supplies one. - Progress Indicator → 0.1.0 — One pattern for measured and unmeasured progress. The
progresslambda overloads reportProgressBarRangeInfowith a value and the others an indeterminate range, both on a merged node with no name, so a standalone indicator is named for its work and one inside a control hands its meaning to that control. A control showing its own progress stays focusable: a clickable set toenabled = falsedrops its focusable node, which throws away a keyboard user's focus the moment "Save" becomes "Saving". The taxonomy had planned this as two patterns, split on determinacy; written out, they shared most of their rules, so they ship as one. - Button → 0.2.2 — Its redirect for a control that opens a URL now names
link.basic. - Image → 0.1.1 — Its redirect for a graphic showing work in progress now names
progress-indicator.basic.
0.6.0 — 2026-10-06
Four wave-1 patterns in two pairs, each pair sharing a mechanism, checked against the stable Material 3 1.4.0 source.
- Navigation Bar → 0.1.0 — Items report
Role.Tab, selected state, and position throughselectableandselectableGroup.NavigationBarItemwraps its icon inclearAndSetSemantics {}whenever the label shows, which is right for the icon's description and silently drops aBadgedBoxcount drawn in the same slot. The badge's meaning goes in the item's name, and each icon still carries a description, because it is the item's only name when labels are hidden. - Tabs → 0.1.0 — The same
Role.Tabcontract, with the opposite icon rule:Tabdoes not clear its icon, so an icon beside a tab's text takescontentDescription = null. Only the selected tab's content is composed, and a swipeable pager keeps the selected tab in step. - Snackbar → 0.1.0 — Everything accessible lives in
SnackbarHost, notSnackbar: a polite live region, adismissaction, and a duration run through the system's recommended timeout. ASnackbardrawn by hand behind a timer gets none of it.showSnackbarqueues messages rather than replacing them. - Snackbar with Action → 0.1.0 — Focus never moves to the message, so its action is also available elsewhere on the screen.
showSnackbaralready defaults an action snackbar toSnackbarDuration.Indefinite; the pattern keeps that default and adds a visible dismiss control.
0.5.1 — 2026-10-06
- Foundations — The
Rule:prefix is gone from every rule heading, so the list reads as rule names ("Focus States", "Native First") instead of the same word repeated down the page. No rule changed.@a11y-context/mcp-serverreads both forms, soget_foundationsreturns the same rules either way.
0.5.0 — 2026-10-05
Three wave-1 patterns, and four corrections that came from checking their mechanisms against the stable Material 3 1.4.0 and Compose UI 1.12.1 sources.
- Image → 0.1.0 — Informative, decorative, and functional images.
contentDescriptionis a required parameter onImageandIcon, so the decision is explicit at every call site, and""is not decorative: it still appliesRole.Image. Onlynullremoves an image from the tree. - Menu → 0.1.0 —
DropdownMenuis a focusable popup that closes on back, Escape, and a tap outside it with no extra code. Its items carry no role, so each label has to stand on its own as a command. An overflow trigger is named "More options", the label Android uses for its own overflow control. - Dialog (Alert) → 0.1.0 —
AlertDialogblocks the screen and closes on back and Escape, but sets its pane title to the generic word "Dialog". The title is the first content the user lands on, so it carries the question; the icon before it is decorative. The dialog's own window takes focus, so no button is focused on open. - List Item → 0.2.0 — Replaced a Don't that warned against omitting
contentDescription, which cannot be omitted on Compose. The real trap is passing""to a decorative thumbnail. - Content Shelf → 0.2.0 — The same correction for tile artwork.
- Bottom Sheet (Modal) → 0.3.0 — The focus request moves inside the sheet's content, because the sheet composes in its own window and an effect in the parent can run before its target exists. The Escape Must Have now says the sheet is the exception:
AlertDialogandDropdownMenuhandle Escape themselves. The Escape handler now restores focus to the trigger, as back press already did.
Every Golden Pattern in the stack drops its explanatory comments. Each one restated a Must Have or argued a choice for a human reviewer; the agent retrieves the sections with the code, so they cost tokens and said nothing new.
- Button → 0.2.1 — Golden Pattern comments removed; no requirements change.
- Checkbox → 0.1.1 — Golden Pattern comments removed; no requirements change.
- Radio Group → 0.1.1 — Golden Pattern comments removed; no requirements change.
- Switch → 0.1.1 — Golden Pattern comments removed; no requirements change.
- Text Field → 0.2.1 — Golden Pattern comments removed; no requirements change.
Foundations change in the same release:
global.iconreplaces a Don't about an "unset"contentDescriptionwith the two Compose traps that are real: passing""instead ofnull, and drawing a meaningful graphic withModifier.paint,Canvas, or a background, none of which applies semantics.
0.4.0 — 2026-09-23
Two gaps found by auditing formula coverage across all eight patterns.
- Text Field → 0.2.0 — Adds the disabled-control Must Have, which every other form-control pattern carried and this one did not, plus the
readOnlydistinction: read-only keeps the value focusable and copyable, disabled removes it from the interaction flow. Touch-target Must Have also reworded to match the style guide's formula verbatim. - Bottom Sheet (Modal) → 0.2.0 — Adds the focus-states Must Have. The pattern makes its content container focusable in order to move focus into the sheet on open, and never said that a container which can hold focus has to show it.
0.3.0 — 2026-09-23
- Button → 0.2.0 — Fixed the
IconButtonexample in the Golden Pattern.onClick(label = ...) { false }passed a real action lambda that overrode the button's click handler in the accessibility tree, so a TalkBack double-tap did nothing while touch still worked.action = nullattaches the label without overriding the handler. Must Haves and Don'ts now cover components, likeIconButton, that take noonClickLabelparameter directly.
0.2.0 — 2026-09-22
First component release. Eight patterns, all at 0.1.0.
- Bottom Sheet (Modal) → 0.1.0 — Modal sheet. Material supplies more of the dismissal contract than expected, and each part of it disappears under a configuration the caller controls: the drag handle's expand, collapse, and dismiss actions are conditional, and Escape is never handled.
- Button → 0.1.0 — Text, icon-only, floating, and action-chip presentations, which share one role and differ in where the accessible name comes from.
- Checkbox → 0.1.0 — Independent yes-or-no choice submitted with a form. The row that owns
toggleableowns the role and the touch target. - Content Shelf → 0.1.0 — Horizontally scrolling strip of tiles. A
LazyRowis one row of many columns, and reversing the collection axes reports position against the wrong one. - List Item → 0.1.0 — A row in a vertical list, as one accessibility node. A secondary control inside it becomes a custom action rather than a nested target.
- Radio Group → 0.1.0 — Exactly one choice from a mutually exclusive set.
selectableGroupon the container is what makes each option announce its position, and the group ships with one option already selected. - Switch → 0.1.0 — Persistent on-or-off setting that takes effect immediately.
- Text Field → 0.1.0 — Single-line entry.
isErrorannounces a generic default string rather than the supporting text, and supporting text is laid out without being attached to the field, so both have to be handled deliberately.
Foundations changes in the same release:
global.collection-semanticsnow requires naming the collection container outright. The rule previously asked for a name only when the heading was not adjacent in traversal order, a condition that did no work, since nothing on Android associates a heading with the list below it.global.native-firstno longer namesandroidx.compose.material3as the thing to prefer over foundation primitives. It says not to hand-assemble a control when a component that meets the contract is available, whether that is the Material composable or the design system's own.
Every component pattern states its contract first — the role, state, and actions the control must expose — and names Material 3 as the reference implementation rather than as the instruction. A design system's own component satisfies the same contract by forwarding to the same semantics.
0.1.0
Stack scaffolding and Foundations. No component patterns yet.
- Foundations established with 18 baseline rules.
- Component taxonomy settled in
schema/android-component-taxonomy.md.