You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/guide/a11y-basics.md
+31-31Lines changed: 31 additions & 31 deletions
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,16 @@
1
-
# Basics
1
+
# 基礎
2
2
3
-
Web accessibility (also known as a11y) refers to the practice of creating websites that can be used by anyone — be that a person with a disability, a slow connection, outdated or broken hardware or simply someone in an unfavorable environment. For example, adding subtitles to a video would help both your deaf and hard-of-hearing users and your users who are in a loud environment and can't hear their phone. Similarly, making sure your text isn't too low contrast will help both your low-vision users and your users who are trying to use their phone in bright sunlight.
3
+
Web アクセシビリティ(a11y とも呼ばれる)とは、障害のある人、回線速度が遅い人、古かったり壊れたハードウェアを使用している人、単に芳しくない環境にいる人など、誰もが利用できる Web サイトを作ることを指します。たとえば、ビデオに字幕を追加すると、聴覚障害のあるユーザと、大きな音がして電話の音が聞こえないユーザの両方に役立ちます。同様に、テキストのコントラストを低くしないようにすることで、目の見えないユーザと、明るい日光の下で携帯電話を使おうとしているユーザの両方に役立ちます。
4
4
5
-
Ready start but aren’t sure where?
5
+
アクセシビリティを始めたいけど、どこを参照すれば良いかわかりませんか?
6
6
7
-
Checkout the [Planning and managing web accessibility guide](https://www.w3.org/WAI/planning-and-managing/) provided by [World Wide Web Consortium (W3C)](https://www.w3.org/)
7
+
[World Wide Web Consortium (W3C)](https://www.w3.org/) が提供する [Planning and Managing Web Accessibility](https://www.w3.org/WAI/planning-and-managing/) を参照してください。
8
8
9
-
## Skip link
9
+
## スキップリンク
10
10
11
-
You should add a link at the top of each page that goes directly to the main content area so users can skip content that is repeated on multiple Web pages.
11
+
ユーザが複数の Web ページで繰り返されるコンテンツをスキップできるように、各ページの上部にメインコンテンツエリアに直接行くリンクを追加する必要があります。
12
12
13
-
Typically this is done on the top of `App.vue`as it will be the first focusable element on all your pages:
One of the most important pieces of accessibility is making sure that design can support accessible implementation. Design should consider not only color contrast, font selection, text sizing, and language, but also how the content is structured in the application.
Users can navigate an application through headings. Having descriptive headings for every section of your application makes it easier for users to predict the content of each section. When it comes to headings, there are a couple of recommended accessibility practices:
@@ -95,23 +95,23 @@ Users can navigate an application through headings. Having descriptive headings
95
95
</main>
96
96
```
97
97
98
-
### Landmarks
98
+
### ランドマーク
99
99
100
-
Landmarks provide programmatic access to sections within an application. Users who rely on assistive technology can navigate to each section of the application and skip over content. You can use [ARIA roles](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles) to help you achieve this.
It is recommended to use landmark HTML elements with redundant landmark role attributes in order to maximize compatibility with legacy [browsers that don’t support HTML5 semantic elements](https://caniuse.com/#feat=html5semantic).
114
+
レガシーな [HTML5 のセマンティック要素をサポートしていないブラウザ](https://caniuse.com/#feat=html5semantic)との互換性を最大限に高めるために、冗長なランドマークロール属性を持つランドマーク HTML 要素を使用することをお勧めします。
115
115
:::
116
116
117
-
[Read more about landmarks](https://www.w3.org/TR/wai-aria-1.2/#landmark_roles)
0 commit comments