Infrastructure: Complete portable Storybook accessibility coverage and reporting
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
调研方向
Start with the native assertion/test integration reference and packages/agentic/storybook-desktop/src/testing/runWdioTests.ts, then review packages/agentic/components/WIN32-FOCUS-PLAN.md and the linked prerequisite work. Run the existing WDIO cohort to understand its current cases and result data. Done means the documented cohort has deterministic native accessibility assertions, authoritative endpoint results, versioned reports, compatibility tests, documentation, and explicit exclusions or diagnostics.
由索引模型根据 Issue 内容生成。
描述
Goal
Complete the portable native accessibility cohort, qualification, and reporting above the assertion foundation delivered by #4255. Parent: #4275.
Status - 2026-10-01
Open; assertion support and a broader behavioral suite are implemented, full conformance is not.
Native providers normalize role/name/state/text/value; catalog tests now use top-level named WDIO callbacks, not the obsolete parameters.desktopTest proposal. Merged PRs #4306, #4313, and #4314 provide real native role/state/focus and interaction assertions.
Current main discovers 29 cases across 17 stories and ten component/primitive families on each endpoint. That is not 29 accessibility-conformance cases: some test motion/layout, many require unavailable hosted input, and Radio/Tag/Accordion/standalone Tab plus the negative Divider case are not a complete authored accessibility cohort.
The active WDIO run.json contains per-case status/error/skip data, but no dedicated role/name/reachability counters or observed-primary-element summary.
Remaining scope and acceptance criteria
- Complete the initial Button, Checkbox, Radio, Switch, Tag, Tab, and Accordion cohort, plus Divider or another documented noninteractive negative fixture.
- Each applicable case asserts a deterministic accessible name, normalized role, relevant native state/value, and positive or negative keyboard reachability.
- Reachability proves bounded real Tab navigation where required; an enabled flag, programmatic focus, or component-owned state is not substituted for actual keyboard/native accessibility evidence.
- Test both label-prop names and deterministic visible-label fallback; intentional name/role mismatches fail clearly in portable contract tests.
- Verify and document the Switch role mapping against the actual native Windows/Win32/macOS control representations. Keep normalization in the provider boundary rather than platform-native literals in shared assertions.
- Add versioned accessibility reporting with passed/failed/skipped role/name/reachability counts, observed native attributes, and actionable unsupported-state diagnostics.
- Run the complete cohort on authoritative interactive Windows and managed macOS endpoints, publishing exact runtime/helper/manifest identities and results. Qualify Win32 separately where its provider/control behavior differs.
- Resolve or explicitly track native disabled/selected/enabled-state projection gaps; behavioral callbacks and focus exclusion must not be claimed as AX/UIA state passes.
- Required coverage excludes quarantine and capability skips. Preserve explicit reasoned exclusions until the native catalog crashes are fixed.
- Public type/report changes have compatibility tests, documentation, appropriate changesets, and the owning package/root validation.
Scope boundary
This issue owns native-tree assertions, their cohort, and reports. Component prop-propagation/unit coverage and the package-wide conformance registry remain with #4216/#4214. Manual VoiceOver/NVDA validation is separate; do not claim it from UIA/AX assertions.
Evidence
- Native assertion/test integration
- Current WDIO result implementation
- Merged focus and accessibility evidence/limits
- Focus qualification and renderer gaps
- Delivered milestone: #4255. Coordinate #4349 for authoritative required CI, #4346 for native state projection, #4344 for catalog crashes, and #4347 for historical focus parity.
- 主要语言
- TypeScript
- 星标
- 1.4k
- 派生
- 179
- 平均合并
- 2 天 9 小时
- 30 天内合并 PR
- 30
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
microsoft/fluentui-react-native 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
microsoft/fluentui-react-native#4174 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
microsoft/fluentui-react-native#4344 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 20/100
microsoft/fluentui-react-native#4345 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 30/100
microsoft/fluentui-react-native#4346 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
microsoft/fluentui-react-native#4347 ·
维护者通常 1 天内回复
查看 microsoft/fluentui-react-native 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 85/100
wardian-app/Wardian#1603 ·
维护者通常 1 天内回复
-
Sign the pledge未关闭
难度 1/5 1 小时以内 新手友好度 85/100
input-output-hk/devx-updates#168 ·
维护者通常 1 天内回复
-
triage
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
agent-ready area: config area: skills type: chore upstream: brain-kit
难度 1/5 1 小时以内 新手友好度 95/100
-
dev experience frontend good first issue
难度 2/5 1-3 小时 新手友好度 78/100
cuttle-cards/cuttle#1403 ·
维护者通常 1 天内回复