Delayed refresh must not be used

ルールID: meta-refresh-no-exceptions
ルールセット: axe-core 4.10
ユーザーへの影響: 軽微
ガイドライン: WCAG 2.1 (AAA), WCAG 2.0 (AAA)
 

Learn Web Accessibility

Subscribe to our extensive curriculum of online self-paced courses

Compliance Data & Impact

User Impact

軽微
Minor
Critical

Disabilities Affected

  • 視覚障害
  • 視聴覚障害
  • 運動障害

Standard(s)

  • WCAG 2.1 (AAA)
  • WCAG 2.0 (AAA)

WCAG 達成基準 [WCAG 2.1 (AAA)]

  • 2.2.4: 必須: Interruptions
  • 3.2.5: 必須: Change on Request

WCAG 達成基準 [WCAG 2.0 (AAA)]

  • 2.2.4: 必須: Interruptions
  • 3.2.5: 必須: Change on Request

修正方法

Remove the http-equiv="refresh" attribute from each meta element in which it is present.

To modify this example and make it accessible, remove the http-equiv="refresh" attribute from the meta element.

Bad Example

<meta http-equiv="refresh" content="40" url="http://www.yourdomain.com/index.html">

If the purpose of the <meta> element is to refresh the page, this should be handled through JavaScript. Furthermore, additional scripting should be used to provide users the ability to pause the refresh, extend the time between refreshes, or to turn the refresh off entirely.

For more information, see Timed Content in the Dynamic Content section of the HTML and CSS Accessibility course.

なぜ重要なのか

Since users do not expect a page to refresh automatically, such refreshing can be disorienting. Refreshing also moves the programmatic focus back to the top of the page, away from where the user had it. Such resetting is frustrating for users.

Redirection and page refresh through the use of the <meta> element is problematic for users with disabilities in many ways. The primary reason why redirects and refreshes are problematic is that the user has no control over when the redirect or refresh occurs. If the purpose of the <meta> element is to redirect the user to a new location, server-side means should be employed instead of client-side. Content that moves or auto-updates can be a barrier to anyone who has trouble reading the stationary text as quickly as well as to anyone who has trouble tracking moving objects. It can also cause problems for screen readers.

ルールの説明

The document must not use <meta http-equiv="refresh"> because it can prevent control over when the refresh occurs for users with disabilities.

仕組みについて (簡単に言うと)

Checks for the presence of the http-equiv="refresh" attribute on the meta elements.

リソース

axe 4.10 ルールの一覧 を参照する

この情報は役に立ちましたか?

すでにフィードバックをいただきました、ありがとうございます。.

あなたの回答は次のとおりです。

この情報は役に立ちましたか?
フィードバックが提出された日付/時刻: