Conversation
|
📚 Branch Preview Links🔍 First Generation Visual Regression Test ResultsWhen a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:
Deployed to Azure Blob Storage: If the changes are expected, update the |
| @@ -30,7 +30,7 @@ | |||
| - [Phase 3: API migration](#phase-3-api-migration) | |||
| - [What to do](#what-to-do) | |||
| - [Property migration scenarios](#property-migration-scenarios) | |||
| - [API patterns (statics, warnings, and 1st-gen exports)](#api-patterns-statics-warnings-and-1st-gen-exports) | |||
| - [API patterns (statics and warnings)](#api-patterns-statics-and-warnings) | |||
There was a problem hiding this comment.
TOC automatic update
| - [Factor rendering out of 1st-gen component](02_step-by-step/02_factor-rendering-out-of-1st-gen-component.md) | ||
| - [Move base class to 2nd-gen core](02_step-by-step/03_move-base-class-to-2nd-gen-core.md) | ||
| - [Understand the 1st-gen component structure](02_step-by-step/02_factor-rendering-out-of-1st-gen-component.md) | ||
| - [Create base class in 2nd-gen core](02_step-by-step/03_move-base-class-to-2nd-gen-core.md) |
There was a problem hiding this comment.
TOC automatic update
| - [Strategy](#strategy) | ||
| - [Disruptive vs. non-disruptive change](#disruptive-vs-non-disruptive-change) | ||
| - [Side-by-side development of 1st-gen and 2nd-gen](#side-by-side-development-of-1st-gen-and-2nd-gen) | ||
| - [Independent development of 1st-gen and 2nd-gen](#independent-development-of-1st-gen-and-2nd-gen) |
There was a problem hiding this comment.
TOC automatic update
| - [S1-only suffixing rule](#s1-only-suffixing-rule) | ||
| - [Naming rule](#naming-rule) | ||
| - [File structure](#file-structure) | ||
| - [Section order](#section-order) | ||
| - [Section separators](#section-separators) | ||
| - [Constant patterns](#constant-patterns) | ||
| - [Sizes](#sizes) | ||
| - [Variants with S1/S2 split](#variants-with-s1s2-split) | ||
| - [Variants without S1/S2 split](#variants-without-s1s2-split) | ||
| - [Simple variant arrays](#simple-variant-arrays) |
There was a problem hiding this comment.
TOC automatic update
| - [Cross-root ARIA delegation (explainer)](https://leobalter.github.io/cross-root-aria-delegation/) and [repository](https://github.com/leobalter/cross-root-aria-delegation). | ||
| - [Reference target for cross-root ARIA (WICG explainer)](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/reference-target-explainer.md); [Can I use… `shadowrootreferencetarget`](https://caniuse.com/mdn-html_elements_template_shadowrootreferencetarget) for current support. | ||
| - [How shadow DOM and accessibility are in conflict](https://blogs.igalia.com/alice/how-shadow-dom-and-accessibility-are-in-conflict/) — Alice Boxhall. | ||
| - [Shadow DOM and accessibility: the trouble with ARIA](https://nolanlawson.com/2022/11/28/shadow-dom-and-accessibility-the-trouble-with-aria/) — Nolan Lawson. |
There was a problem hiding this comment.
**STOP:
All other changes past this point were automatic navigation updates to the CONTRIBUTOR GUIDES**
Description
In contributor docs directory (CONTRIBUTOR-DOCS/04_accessibility_guides/01_semantic_html_aria.md):
Motivation and context
Create a comprehensive documentation page in the accessibility section that covers HTML semantics, ARIA best practices, and the challenges of cross-root ARIA in web components. This page should educate developers on proper semantic HTML usage, when to use ARIA, and current limitations with shadow DOM implementations.
Related issue(s)
Screenshots (if appropriate)
Author's checklist
Reviewer's checklist
patch,minor, ormajorfeaturesManual review test cases
Go to https://swcpreviews.z13.web.core.windows.net/pr-6142/docs/second-gen-storybook/?path=/docs/guides-accessibility-guides-semantic-html-and-aria--readme:
Device review
Accessibility testing checklist
Required: Complete each applicable item and document your testing steps (replace the placeholders with your component-specific instructions).
Keyboard (required — document steps below) — What to test for: Focus order is logical; Tab reaches the component and all interactive descendants; Enter/Space activate where appropriate; arrow keys work for tabs, menus, sliders, etc.; no focus traps; Escape dismisses when applicable; focus indicator is visible.
Screen reader (required — document steps below) — What to test for: Role and name are announced correctly; state changes (e.g. expanded, selected) are announced; labels and relationships are clear; no unnecessary or duplicate announcements.