Tabs

ArrangeTabs

Tabs is part of the Basic Catalog in Google's A2UI v1.0 protocol. This page shows how it behaves so you can build with it. Unofficial, and not affiliated with Google.

Live preview

What you try is exactly what we tested
Recorded snapshot · React 0.15.0 with web_core 0.15.0 · 2026-11-14Live · rendered in your browser by @a2ui/react 0.15.0
Recorded render of Tabs (two tabs; then click second)

What it is

A set of tabs, each with a title and child component.

In the trip planner

The trip planner does not use Tabs. Open the explorer.

Properties

Schema properties for Tabs
PropertyTypeRequiredAllowed valuesNew in 1.0
tabsarray of objectyes–

Evidence

FINDING React 0.15.0 with web_core 0.15.0, v1.0 module · headless Chromium, Linux · 2026-11-14 · 1 run

What is not claimed

  • Other renderers (Lit, Angular, community) were not rerun; the 8 November 2026 matrix stands.
  • Gemini Enterprise was not tested in this run (14 November 2026).
  • Remote media was not loaded, so media records element creation and attributes, not playback.
  • Layout and visual quality are not judged.

Media and links in the examples use example.invalid placeholders. Navigation is intercepted and media is not played.

Findings

Findings

  • The renderer draws no tablist role and no aria-selected, so assistive technology is not told these are tabs.
  • In React 0.15.0 the renderer draws Tabs without role="tablist", role="tab" or aria-selected. Fixed on the project's main branch, unreleased (checked 14 Nov 2026 at commit 3ed960186): the tablist and aria-selected are present there. Published 0.15.0 is what a developer installs today.

Recorded cases

Recorded cases for Tabs
CaseExpectedObservedVerdict
click tab 2,3,1 -> only active panel in DOMonly the active panel showsPASS
tab semantics: role/aria-selected after switchtab semantics (role tablist, aria-selected) so assistive tech announces tabsthe renderer drew no tablist role: hasTablist=0FINDING