Skip to content

Commit fb3433b

Browse files
authored
Merge pull request andreasbm#33 from yso009/master
3학년 상세내용 수정(andreasbm#32)
2 parents 0bd3434 + 8271043 commit fb3433b

File tree

4 files changed

+236
-1363
lines changed

4 files changed

+236
-1363
lines changed

src/data/accessibility.js

Lines changed: 91 additions & 103 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,11 @@
11
export const accessibilityCollection = {
2-
name: "Accessibility",
2+
name: "2학년",
33
areas: [
44
{
5+
name: "1학기",
56
skills: [
67
{
7-
name: "The why",
8+
name: "자료구조",
89
description: {
910
text: "Learn what accessibility is and why it is important.",
1011
links: [
@@ -19,7 +20,7 @@ export const accessibilityCollection = {
1920
}
2021
},
2122
{
22-
name: "Screen Readers",
23+
name: "컴퓨터구조",
2324
description: {
2425
text: "Learn about assistive technology such as screen readers that reads sections of the page aloud based on the current focus.",
2526
links: [
@@ -31,65 +32,17 @@ export const accessibilityCollection = {
3132
}
3233
},
3334
{
34-
name: "Accessibility tree",
35+
name: "소프트웨어실전영어",
3536
description: {
3637
text: "Learn about the accessibility tree and how assistive technology uses it.",
3738
links: [
3839
["Google Devs - The Accessibility Tree", "https://developers.google.com/web/fundamentals/accessibility/semantics-builtin/the-accessibility-tree"]
3940
]
4041
},
41-
skills: [
42-
{
43-
name: "ARIA",
44-
description: {
45-
text: "Learn how to use ARIA descriptions an labels to help assistive technology understanding your website.",
46-
links: [
47-
["Google Devs - ARIA Labels", "https://developers.google.com/web/fundamentals/accessibility/semantics-aria/aria-labels-and-relationships"],
48-
["Google Devs - Hiding and updating content", "https://developers.google.com/web/fundamentals/accessibility/semantics-aria/hiding-and-updating-content"],
49-
["The A11Y Project - ARIA States", "https://a11yproject.com/posts/ARIA-states/"],
50-
["The A11Y Project - ARIA Properties", "https://a11yproject.com/posts/ARIA-properties/"],
51-
]
52-
}
53-
},
54-
{
55-
name: "Accessible HTML",
56-
description: {
57-
text: "Learn how to write HTML in such as way that assistive technology better understands it.",
58-
links: [
59-
["Google Devs - Introduction to Semantics", "https://developers.google.com/web/fundamentals/accessibility/semantics-builtin/"],
60-
["MDN - Accessibility HTML", "https://developer.mozilla.org/en-US/docs/Learn/Accessibility/HTML"],
61-
["Webaim - Skip navigation", "https://webaim.org/techniques/skipnav/"],
62-
["w3c - Headings", "https://www.w3.org/WAI/tutorials/page-structure/headings/"],
63-
["Freecodecamp - Semantic Elements", "https://guide.freecodecamp.org/html/html5-semantic-elements/"]
64-
]
65-
},
66-
skills: [
67-
{
68-
name: "Alt text",
69-
description: {
70-
text: "Learn how to use the alt attribute to provide a useful text alternative to this image.",
71-
links: [
72-
["Google Devs - Text Alternatives for Images", "https://developers.google.com/web/fundamentals/accessibility/semantics-builtin/text-alternatives-for-images"],
73-
["Webaim - Accessible Images", "https://webaim.org/techniques/images/"],
74-
["Webaim - Alternative text", "https://webaim.org/techniques/alttext/"],
75-
]
76-
}
77-
}
78-
]
79-
},
80-
{
81-
name: "Accessible CSS",
82-
description: {
83-
text: "Learn how to write CSS in such as way that assistive technology better understands it.",
84-
links: [
85-
["Webaim - CSS", "https://webaim.org/techniques/css/"]
86-
]
87-
}
88-
},
89-
]
42+
9043
},
9144
{
92-
name: "Accessible forms",
45+
name: "객체지향 프로그래밍",
9346
description: {
9447
text: "Learn how to build accessible forms that makes it usable to as many people as possible.",
9548
links: [
@@ -99,7 +52,7 @@ export const accessibilityCollection = {
9952
}
10053
},
10154
{
102-
name: "UI States",
55+
name: "선형대수학",
10356
description: {
10457
text: "Learn how to make the state of each UI element clear.",
10558
links: [
@@ -108,34 +61,18 @@ export const accessibilityCollection = {
10861
}
10962
},
11063
{
111-
name: "Keyboard Accessibility",
64+
name: "미래설계구현",
11265
description: {
11366
text: "Learn how to make it easy for keyboard users to navigate your site.",
11467
links: [
11568
["Webaim - Keyboard", "https://webaim.org/techniques/keyboard/"],
11669
["Smashing Magazine - Web with just a keyboard", "https://www.smashingmagazine.com/2018/07/web-with-just-a-keyboard/"]
11770
]
11871
},
119-
skills: [
120-
{
121-
name: "Focus",
122-
description: {
123-
text: "Learn how to create a sensible tab order and how to make it easy for the users to locate the currently focused element.",
124-
links: [
125-
["web.dev - Control focus with tabindex", "https://web.dev/control-focus-with-tabindex/"],
126-
["Google Devs - Focus", "https://developers.google.com/web/fundamentals/accessibility/focus/"],
127-
["Google Devs - Dom Order Matters", "https://developers.google.com/web/fundamentals/accessibility/focus/dom-order-matters"],
128-
["Google Devs - Using Tabindex", "https://developers.google.com/web/fundamentals/accessibility/focus/using-tabindex"],
129-
["Google Devs - Track Focus", "https://developers.google.com/web/tools/chrome-devtools/accessibility/focus"],
130-
["MDN - :focus-visible", "https://developer.mozilla.org/en-US/docs/Web/CSS/:focus-visible"],
131-
["MDN - :focus-within", "https://developer.mozilla.org/en-US/docs/Web/CSS/:focus-within"]
132-
]
133-
}
134-
}
135-
]
72+
13673
},
13774
{
138-
name: "Accessible Colors",
75+
name: "오픈소스 기초프로젝트",
13976
description: {
14077
text: "Learn how to select colors in such a way that users, including those with visual disabilities, can perceive the content on the page.",
14178
links: [
@@ -145,41 +82,92 @@ export const accessibilityCollection = {
14582
["Designing accessible color systems", "https://stripe.com/en-dk/blog/accessible-color-systems"],
14683
]
14784
}
85+
}
86+
],
87+
},
88+
{
89+
name: "2학기",
90+
skills: [
91+
{
92+
name: "알고리즘",
93+
description: {
94+
text: "Learn what accessibility is and why it is important.",
95+
links: [
96+
["Google Devs - Accessibility Fundamentals", "https://developers.google.com/web/fundamentals/accessibility/"],
97+
["A11ycasts with Rob Dodson", "https://www.youtube.com/playlist?list=PLNYkxOF6rcICWx0C9LVWWVqvHlYJyqw7g"],
98+
["Udacity - Chromevox Lite", "http://udacity.github.io/ud891/lesson3-semantics-built-in/02-chromevox-lite/"],
99+
["Dev.to - Why Accessibility Matters", "https://dev.to/lhoffmanwg1/why-accessibility-matters-39nl"],
100+
["Abilitynet - Why Accessibility Matters", "https://www.abilitynet.org.uk/why-accessibility-matters"],
101+
["Udacity - Web Accessibility", "https://www.udacity.com/course/web-accessibility--ud891"],
102+
["Youtube - Headings, Landmarks, and Tabs", "https://www.youtube.com/watch?v=HE2R86EZPMA"],
103+
]
104+
}
105+
},
106+
{
107+
name: "프로그래밍언어이론",
108+
description: {
109+
text: "Learn about assistive technology such as screen readers that reads sections of the page aloud based on the current focus.",
110+
links: [
111+
["The A11Y Project - Screen Reader Myths", "https://a11yproject.com/posts/people-who-use-screen-readers-dont-use-javascript/"],
112+
["The A11Y Project - NVDA Screen Reader", "https://a11yproject.com/posts/getting-started-with-nvda/"],
113+
["The A11Y Project - OS X Voiceover", "https://a11yproject.com/posts/getting-started-with-voiceover/"],
114+
["Webaim - Screen Reader Survey", "https://webaim.org/projects/screenreadersurvey7/"]
115+
]
116+
}
117+
},
118+
{
119+
name: "시스템프로그래밍",
120+
description: {
121+
text: "Learn about the accessibility tree and how assistive technology uses it.",
122+
links: [
123+
["Google Devs - The Accessibility Tree", "https://developers.google.com/web/fundamentals/accessibility/semantics-builtin/the-accessibility-tree"]
124+
]
125+
},
126+
148127
},
149128
{
150-
name: "Laws & Policies",
129+
name: "창업탐색",
151130
description: {
152-
text: "Learn about the governmental policies related to web accessibility.",
131+
text: "Learn how to build accessible forms that makes it usable to as many people as possible.",
153132
links: [
154-
["W3C - Laws & Policies", "https://www.w3.org/WAI/policies/"],
155-
["Webaim - Laws around the world", "https://webaim.org/articles/laws/world/"],
156-
["Webaim - Section 508", "https://webaim.org/standards/508/checklist"],
157-
["Webaim - WCAG 2 Checklist", "https://webaim.org/standards/wcag/checklist"],
158-
["A11Y.dev - Lawsuits", "https://a11y.dev/470-digital-accessibility-cases-were-filed-in-q3-2018/"],
133+
["Webaim - Forms", "https://webaim.org/techniques/forms/"],
134+
["Itnext - Form Accessibility Gudie", "https://itnext.io/form-accessibility-a-practical-guide-4062b7e2dd14"]
135+
]
136+
}
137+
},
138+
{
139+
name: "오픈소스개발프로젝트",
140+
description: {
141+
text: "Learn how to make the state of each UI element clear.",
142+
links: [
143+
["Google Devs - Accessible Styles", "https://developers.google.com/web/fundamentals/accessibility/accessible-styles"]
144+
]
145+
}
146+
},
147+
{
148+
name: "확률및통계",
149+
description: {
150+
text: "Learn how to make it easy for keyboard users to navigate your site.",
151+
links: [
152+
["Webaim - Keyboard", "https://webaim.org/techniques/keyboard/"],
153+
["Smashing Magazine - Web with just a keyboard", "https://www.smashingmagazine.com/2018/07/web-with-just-a-keyboard/"]
159154
]
160155
},
161-
skills: [
162-
{
163-
name: "Audits",
164-
description: {
165-
text: "Learn how to conduct an accessibility review to improve the overall experience of using your site. Remember, good accessibility equals good UX!",
166-
links: [
167-
["web.dev - Accessibility audits", "https://web.dev/lighthouse-accessibility"],
168-
["Google Devs - How to review", "https://developers.google.com/web/fundamentals/accessibility/how-to-review"],
169-
["Webaim - Accessibility Tools", "https://webaim.org/articles/tools/"],
170-
["Google Devs - Accessibility Reference", "https://developers.google.com/web/tools/chrome-devtools/accessibility/reference"],
171-
["Webaim - Wave", "http://wave.webaim.org/"],
172-
["Google Chrome - NoCoffee Extension", "https://chrome.google.com/webstore/detail/nocoffee/jjeeggmbnhckmgdhmgdckeigabjfbddl"],
173-
["Digital A11Y - Accessibility Plugins", "https://www.digitala11y.com/accessibility-plug-ins-ie-chrome-firefox-browsers/"],
174-
["Google Devs - Accessibility for teams", "https://developers.google.com/web/fundamentals/accessibility/a11y-for-teams"],
175-
["WCAG 2.0 checklists", "https://www.wuhcag.com/wcag-checklist/"],
176-
["How to Meet WCAG (Quick Reference)", "https://www.w3.org/WAI/WCAG21/quickref/"],
177-
]
178-
}
179-
}
180-
]
156+
157+
},
158+
{
159+
name: "컴퓨터그래픽스",
160+
description: {
161+
text: "Learn how to select colors in such a way that users, including those with visual disabilities, can perceive the content on the page.",
162+
links: [
163+
["Webaim - Contrast and Color", "https://webaim.org/articles/contrast/"],
164+
["The A11Y Project - Check contrast", "https://a11yproject.com/posts/check-contrast-with-mobile-device/"],
165+
["The A11Y Project - What is color contrast?", "https://a11yproject.com/posts/what-is-color-contrast/"],
166+
["Designing accessible color systems", "https://stripe.com/en-dk/blog/accessible-color-systems"],
167+
]
168+
}
181169
}
182-
]
170+
],
183171
}
184172
]
185-
};
173+
}

0 commit comments

Comments
 (0)