-
Notifications
You must be signed in to change notification settings - Fork 2.8k
A11Y testing using AI #34924
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
Anush2303
wants to merge
5
commits into
microsoft:master
Choose a base branch
from
Anush2303:usr/agupta/a11y/ai
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
A11Y testing using AI #34924
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
## Repository Structure | ||
|
||
Fluent UI is a **monorepo** managed with Yarn workspace. | ||
It contains multiple packages, each with its own purpose and versioning strategy. The main packages of interest for charting components are: | ||
|
||
Key structure: | ||
|
||
- **`react-charting` (v8)** → Legacy charting components built on Fluent UI v8 styling & patterns. | ||
- **`react-charts` (v9)** → Next-generation chart components based on Fluent UI v9, focusing on modern React patterns, hooks, and convergence goals. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,55 @@ | ||
# Accessibility Issue Fixing Prompt (Generic) | ||
|
||
**Context:** | ||
You are tasked with fixing an accessibility issue in the given project and validating it thoroughly. | ||
|
||
--- | ||
|
||
## Steps | ||
|
||
### Step 1: Bug Context Gathering | ||
|
||
- Take the concerned project name and bug id from the user. | ||
|
||
- Use the ADO MCP Server to gather all relevant context for the bug/work item with the given ID. | ||
|
||
--- | ||
|
||
### Step 2: FIX IMPLEMENTATION | ||
|
||
1. Explain the root cause and target component of the bug to the user. | ||
2. Implement the fix in the **target package or module** (provided by the user or derived from context). | ||
3. Don't validate the issue at this stage; focus solely on implementing the fix. | ||
4. Focus only on fixing the given bug: | ||
- Do not introduce unrelated changes. | ||
- Ensure no new bugs or syntax errors are introduced. | ||
- Ensure the fix adheres to **accessibility standards** (e.g., ARIA roles, aria-labels, keyboard navigation, screen reader support). | ||
|
||
--- | ||
|
||
### Step 3: VALIDATION USING PLAYWRIGHT MCP AND A11Y-ACCESSIBILITY MCP | ||
|
||
1. Take repo specific context of development commands from `fluent_charts.prompt.md` file to build and run the storybook server. | ||
2. **Wait for the server to start**. Only after the server is up and running, use the localhost server running in terminal to validate the bug using Playwright MCP. | ||
3. **Use the same terminal session** to: | ||
- Launch Playwright MCP. | ||
- Perform interactive accessibility validation. | ||
- Use A11Y-accessibility MCP for ARIA compliance. | ||
|
||
--- | ||
|
||
### Step 4: SCREENSHOT CAPTURE AND ACCESSIBILITY SNAPSHOT | ||
|
||
1. Capture **screenshots of the entire interactive component area**. | ||
2. Ensure focus reaches the **interactive elements** (e.g., pressing Tab until focus reaches chart/controls). | ||
3. Enumerate test cases before execution: | ||
- Include actions (e.g., tab navigation, screen reader attribute check). | ||
- Include validation steps (e.g., expected aria-label values). | ||
4. Capture screenshots of: | ||
- Every tab stop within the interactive area. | ||
- Accessibility snapshots of ARIA attributes and labels. | ||
5. Confirm no new accessibility regressions are introduced. | ||
|
||
--- | ||
|
||
**Goal:** Fix and validate accessibility issues reliably across any repository or package. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
# Fluent UI Charts Accessibility Prompt Add-on | ||
|
||
This file provides **Fluent UI charts-specific context** to be used in conjunction with `accessibility_fix.prompt.md`. | ||
|
||
--- | ||
|
||
### Repository Structure | ||
|
||
- **Monorepo Structure:** | ||
Fluent UI is a monorepo. | ||
- **Charts Packages:** | ||
- `packages/charts/react-charting` → v8 charts implementation (reference only). | ||
- `packages/charts/react-charts/library` → v9 charts implementation (fixes should be made here). | ||
|
||
--- | ||
|
||
### Development Commands | ||
|
||
**Don't use && as it runs on yarn workspace in powershell** | ||
|
||
- Build package - | ||
|
||
```bash | ||
yarn --cwd packages/charts/react-charts/library nx run react-charts:build | ||
``` | ||
|
||
- Start Storybook server for development - | ||
```bash | ||
yarn --cwd packages/charts/react-charts/library nx run react-charts:start | ||
``` |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🕵🏾♀️ visual changes to review in the Visual Change Report
vr-tests-react-components/Avatar Converged 2 screenshots
vr-tests-react-components/Charts-DonutChart 2 screenshots
vr-tests-react-components/Charts-HorizontalBarChart 2 screenshots
vr-tests-react-components/Drawer 2 screenshots
vr-tests-react-components/Positioning 2 screenshots
vr-tests-react-components/Skeleton converged 1 screenshots
vr-tests-react-components/TagPicker 1 screenshots
There were 1 duplicate changes discarded. Check the build logs for more information.