[a11y] Assess the next set of components #49260

Context

The conformance page says the coverage is partial. These widely used components are not assessed: Select, Autocomplete, Dialog, Menu, Table, Tabs, Slider, Tooltip, Snackbar, Drawer.

Scope

For each component, follow the existing pattern:

1. Add axe tests and fixtures in test/regressions/a11y/fixtures/.
2. Write <Component>/accessibility.md.
3. Enroll it in the CSS-dependent suite (1.4.10, 1.4.4, 1.4.12).
4. Run pnpm a11y:scorecard.

Each component has its own sub-issue. The sub-issues are grouped into four projects (waves) in the initiative "Accessibility conformance: component coverage". Each wave groups components that share a primitive, so findings and tests carry over. In each wave, assess the high-risk components first.

1. Wave 1: Siblings of covered components (Q4 2026). IconButton, Fab, ButtonGroup, CircularProgress, FormControlLabel, FormLabel, FormHelperText, FormGroup, Link, Chip.
2. Wave 2: Overlays (Q4 2026). Dialog, Drawer, Popover, Menu, MenuItem, MenuList, Tooltip, Snackbar. Includes a screen-reader pass.
3. Wave 3: Composite ARIA widgets (Q1 2027). Select, NativeSelect, Autocomplete, Tabs, Slider.
4. Wave 4: Data, navigation and display (later). Table, TablePagination, TableSortLabel, Pagination, Breadcrumbs, Stepper, List, ListItemButton, BottomNavigation, Rating, Alert, Badge, Skeleton, Card, CardActionArea, AppBar, SpeedDial, ImageList.

Do not change the wave order. Each wave reuses evidence from the previous one. Use procurement and support data to reorder components inside a wave.

Done when

• Each listed component has a report and is in the scorecard.
• The conformance page coverage statement is updated.

Search keywords: