angular / angular/components

docs-bug(Accessibility): Clarifying Accessibility target in documentation

未关闭
#29,492 0 条评论 2 个 reaction 已指派 0 人 在 GitHub 查看
Accessibility docs P3
主要语言
TypeScript
星标
25k
派生
6.8k
平均合并
1 天 8 小时
30 天内合并 PR
91

描述

### Documentation Feedback

I'm evaluating component libraries to use in an enterprise app, and accessibility is a key consideration. Having looked through the documentation, I'm not able to find a specific target for Angular Material's accessibility. Would you all consider specifying which WCAG level you are targeting? PrimeNG specifically calls out that they meet the WCAG 2.1 AA standard. While Angular Material seems to put a lot of work into accessibility, it would be helpful to be able to state that the component library we use targets a specific WCAG level.

### Affected documentation page

material.angular.io

贡献指南

打开贡献指南

调研方向

打开 material.angular.io 并查看现有的无障碍指南,找出库的目标在哪里有描述,或哪里缺少描述。与维护者确认预期的 WCAG 级别,然后在相关页面记录该目标;当用户能够清楚地识别所声明的无障碍目标时,即视为完成。

由索引模型根据 Issue 内容生成。

评估

技术栈
angular
领域
accessibility, documentation
Issue 类型
文档
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
基本清楚
新手友好度
35/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。