Skip to content

Commit 40736fd

Browse files
committed
fix
1 parent b60b658 commit 40736fd

File tree

1 file changed

+28
-3
lines changed

1 file changed

+28
-3
lines changed

ko-KR/src/guide/best-practices/accessibility.md

Lines changed: 28 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -206,7 +206,7 @@ ID와 일치하는 label을 명시적으로 설정하는 것이, 보조 기술
206206

207207
<!-- <common-codepen-snippet title="Form ARIA label" slug="NWdvvYQ" :height="265" tab="js,result" theme="light" :preview="false" :editable="false" /> -->
208208

209-
크롬 개발자도구에서 이 요소를 검사하여, 접근성 이름(accessible name)이 어떻게 바뀌는지 확인하여 자유를 느껴라:
209+
크롬 개발자도구에서 이 요소를 검사하여, 접근성 이름(accessible name)이 어떻게 바뀌는지 확인해도 좋다:
210210

211211
![Chrome Developer Tools showing input accessible name from aria-label](./images/AccessibleARIAlabelDevTools.png)
212212

@@ -284,7 +284,15 @@ You can see the description by inspecting Chrome DevTools:
284284

285285
Avoid using placeholders as they can confuse many users.
286286

287-
One of the issues with placeholders is that they don't meet the [color contrast criteria](https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html) by default; fixing the color contrast makes the placeholder look like pre-populated data in the input fields. Looking at the following example, you can see that the Last Name placeholder which meets the color contrast criteria looks like pre-populated data:
287+
유저들을 혼란스럽게 할 수 있으므로 placeholders 사용을 피하세요.
288+
289+
One of the issues with placeholders is that they don't meet the [color contrast criteria](https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html) by default;
290+
291+
placeholders의 이슈 중 하나는, 기본적으로 [색상 대비 기준](https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html)을 충족하지 않는 다는 것입니다.
292+
293+
fixing the color contrast makes the placeholder look like pre-populated data in the input fields. Looking at the following example, you can see that the Last Name placeholder which meets the color contrast criteria looks like pre-populated data:
294+
295+
색상 대비를 수정하면 placeholder가 input 영역에 미리 채워진 데이터처럼 보입니다. 다음 예를 보면, 미리 데이터가 채워진것처럼 보이며, 색상 대비 기준을 충족하는 Last Name placeholder를 볼 수 있습니다.
288296

289297
```vue-html
290298
<form
@@ -311,11 +319,18 @@ One of the issues with placeholders is that they don't meet the [color contrast
311319

312320
It is best to provide all the information the user needs to fill out forms outside any inputs.
313321

322+
입력의 외부에 유저가 양식을 채우기 위한 모든 정보를 제공하는 것이 가장 좋습니다.
323+
314324
### Instructions
315325

316326
When adding instructions for your input fields, make sure to link it correctly to the input.
327+
328+
입력 영역에 대해 지시자를 추가할 때, 입력에 올바르게 연결해야 합니다.
329+
317330
You can provide additional instructions and bind multiple ids inside an [`aria-labelledby`](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-labelledby_attribute). This allows for more flexible design.
318331

332+
추가 지침을 제공하고, [`aria-labelledby`](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-labelledby_attribute)에 여러 id를 바인딩 할 수 있습니다. 이를 통해 보다 유연한 설계가 가능합니다.
333+
319334
```vue-html
320335
<fieldset>
321336
<legend>Using aria-labelledby</legend>
@@ -332,6 +347,8 @@ You can provide additional instructions and bind multiple ids inside an [`aria-l
332347

333348
Alternatively, you can attach the instructions to the input with [`aria-describedby`](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-describedby_attribute):
334349

350+
또는 [`aria-describedby`](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-describedby_attribute)를 사용하여 입력에 지침을 첨부할 수 있습니다.
351+
335352
```vue-html
336353
<fieldset>
337354
<legend>Using aria-describedby</legend>
@@ -345,10 +362,18 @@ Alternatively, you can attach the instructions to the input with [`aria-describe
345362

346363
### Hiding Content
347364

348-
Usually it is not recommended to visually hide labels, even if the input has an accessible name. However, if the functionality of the input can be understood with surrounding content, then we can hide the visual label.
365+
Usually it is not recommended to visually hide labels, even if the input has an accessible name.
366+
367+
입력에 접근가능한 이름(accessible name)이 있더라도, 시각적으로 label을 숨기는 것은 일반적으로 권장되지 않습니다.
368+
369+
However, if the functionality of the input can be understood with surrounding content, then we can hide the visual label.
370+
371+
그러나, 입력의 기능을 주변 콘텐츠로 이해할 수 있다면, label을 시각적으로 숨길 수 있습니다.
349372

350373
Let's look at this search field:
351374

375+
아래 검색 영역을 살펴보자.
376+
352377
```vue-html
353378
<form role="search">
354379
<label for="search" class="hidden-visually">Search: </label>

0 commit comments

Comments
 (0)