Elements must only use permitted ARIA attributes
Accessibility testing for dev teams - No experience required
Compliance Data & Impact
Disabilities Affected
- 視覚障害
- 視聴覚障害
- 運動障害
Standard(s)
- WCAG 2.1 (A)
- WCAG 2.0 (A)
- WCAG 2.2 (A)
- EN 301 549
WCAG 達成基準 [WCAG 2.1 (A)]
- 4.1.2: 必須: Name, Role, Value
WCAG 達成基準 [WCAG 2.0 (A)]
- 4.1.2: 必須: Name, Role, Value
WCAG 達成基準 [WCAG 2.2 (A)]
- 4.1.2: 必須: Name, Role, Value
EN 301 549 Guidelines
- 9.4.1.2: 必須: Name, Role, Value
修正方法
Prohibited attributes are often used in an attempt to communicate information that then ends up ignored by screen readers and other assistive technologies. If the information conveyed is not important, the attribute can be ignored. More commonly though the information will need to be communicated, so instead of removing the prohibited attribute, consider one of the following:
- Change the role to one on which the attribute is not prohibited
- Provide the information as text in the page.
- Move the attribute to a different element that does support it.
なぜ重要なのか
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. assistive technologies may also attempt to compensate for the issue, resulting in inconsistent and confusing behavior of these tools.
ルールの説明
Not all ARIA role-attribute combinations are valid. This Rule checks that noe of the attributes used with a particular role are listed as "prohibited" for that role in the latest version of WAI-ARIA.
The aria-label and
aria-labelledby attributes are prohibited on
presentation and none roles, as well as on text-like
roles such as code, insertion, strong,
etc.
仕組みについて (簡単に言うと)
Check that each ARIA attribute used is not described as prohibited for that element's role in the WAI-ARIA specification .
リソース
axe 4.10 ルールの一覧 を参照する
この情報は役に立ちましたか?
あなたの回答は次のとおりです。
フィードバックが提出された日付/時刻: