You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Include Toolbar. Focus on the banner landmark (1.3.1), the contrast of the color variants (1.4.3), 2.4.11 Focus Not Obscured (fixed and sticky AppBar over focused content) and 1.4.10 Reflow.
Scope
Add axe tests and fixtures in test/regressions/a11y/fixtures/.
Write AppBar/accessibility.md.
Enroll it in the CSS-dependent suite (1.4.10, 1.4.4, 1.4.12).
Run pnpm a11y:scorecard.
Manual tests
Write each check in the report as numbered Manual testing steps, as in Button/accessibility.md. pnpm a11y:scorecard then adds them to manual-testing.md. For screen-reader steps, use NVDA with Chrome and VoiceOver with Safari.
1.3.1 — With a screen reader, list the landmarks. The AppBar shows as the banner landmark. A page with more than one AppBar has more than one banner. Record this.
2.4.11 — With position="fixed" and "sticky", press Tab through the page while it scrolls. The AppBar does not fully hide a focused element. Record if the author must set scroll-padding-top.
1.4.3 — With a contrast checker, measure the title and the icons for each color, in light and dark mode, and with enableColorOnDark. The text is at least 4.5:1.
1.4.10 — At 320 CSS px width, the Toolbar content stays usable, and the page does not scroll horizontally.
1.4.4 — At 200% zoom, the title and the actions are fully visible.
Done when
AppBar has a report and is in the scorecard.
Each manual test in this issue has steps and a result in the report.
I'd like to take this on and work on the AppBar WCAG 2.2 conformance assessment. I'll review the existing accessibility reports and follow the outlined scope for tests, manual checks, and documentation. Please let me know if anyone is already working on it.
Activity
rohits2501 commentedon Oct 26, 2026
I'd like to take this on and work on the AppBar WCAG 2.2 conformance assessment. I'll review the existing accessibility reports and follow the outlined scope for tests, manual checks, and documentation. Please let me know if anyone is already working on it.