Skip to content

Translate Invalid Aria Prop#57

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
simsim0709 merged 6 commits into from
Mar 8, 2019
Merged

Translate Invalid Aria Prop #57

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
1d79654
Translate Invalid Aria Prop
simsim0709 Mar 2, 2019
5a3f827
Apply a review
simsim0709 Mar 3, 2019
72b6c97
Fix typo
simsim0709 Mar 3, 2019
a050e8e
Merge branch 'master' into translate-invalid-aria-prop
simsim0709 Mar 3, 2019
fd7ab03
Fix translation
simsim0709 Mar 5, 2019
c0e4900
Merge branch 'master' into translate-invalid-aria-prop
simsim0709 Mar 8, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions content/warnings/invalid-aria-prop.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -4,8 +4,8 @@ layout: single
permalink: warnings/invalid-aria-prop.html
---

The invalid-aria-prop warning will fire if you attempt to render a DOM element with an aria-* prop that does not exist in the Web Accessibility Initiative (WAI) Accessible Rich Internet Application (ARIA) [specification](https://www.w3.org/TR/wai-aria-1.1/#states_and_properties).
웹 접근성 이니셔티브(WAI) 접근 가능한 리치 인터넷 애플리케이션(Rich Internet Application)의 [명세](https://www.w3.org/TR/wai-aria-1.1/#states_and_properties)에 없는 aria-* 프로퍼티로 DOM 요소를 렌더링하려고 하면 invalid-aria-prop 경고가 발생합니다.

@taggontaggonMar 6, 2019

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

접근성에서는 명세 제목을 원문으로 사용했던 데 어느 쪽으로 통일하는 게 좋을까요?

@simsim0709simsim0709Mar 7, 2019

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

음.. 저도 이 부분은 위키를 보고 번역 한거라 번역하는게 맞는지 원문 그대로 쓰는게 좋은지 정확히 잘 모르겠습니다. 하지만, 번역된 단어 웹 접근성 이니셔티브도 어색해 보이진 않는거 같습니다. 😄

@simsim0709simsim0709Mar 8, 2019

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@taggon 님. 우선 이 부분 원문 사용할지 번역할지는 translate glossary에서 논의하는 걸로 하고, 이 pr은 머지 하겠습니다. 😄


1. If you feel that you are using a valid prop, check the spelling carefully. `aria-labelledby` and `aria-activedescendant` are often misspelled.
1. 유효한 프로퍼티를 사용했는데도 이 문제가 발생했다면 철자를 확인하십시오. `aria-labelledby`와 `aria-activedescendant`의 철자를 틀리는 경우가 종종 있습니다.

2. React does not yet recognize the attribute you specified. This will likely be fixed in a future version of React. However, React currently strips all unknown attributes, so specifying them in your React app will not cause them to be rendered
2. React는 알 수 없는 속성을 아직 인식하지 못합니다. 이것은 React의 다음 버전에서 수정될 가능성이 있습니다. 하지만 React는 현재 알 수 없는 속성을 모두 제거하므로 React 애플리케이션에 설정된 알 수 없는 속성은 렌더링 되지 않습니다.