Skip to content

Commit 2b5ee06

Browse files
Update tutorial.md
Included the suggested changes to update the accessibility section
1 parent 7c66120 commit 2b5ee06

File tree

1 file changed

+20
-16
lines changed

1 file changed

+20
-16
lines changed

html/lesson6/tutorial.md

Lines changed: 20 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -147,19 +147,23 @@ Now that you are familiar with HTML & CSS, how about you create your own portfol
147147
## Further Reading:
148148
### Accessibility
149149

150-
Some of your users might be using screenreaders or keyboards to navigate across your page.
151-
How do you ensure your website is available to them? By following a few guidelines and integrating techniques.
152-
153-
#### A few names acronyms to know:
154-
- (ARIA) Accessible Rich Internet Applications are set of techniques and additions to HTML to allow additional markup to be interpreted by accessibility devices
155-
- (WCAG) Website Content Accessibility Guidelines contain different compliance levels (A, AA and AAA) and lay down the “rules”to make a website or application accessible.
156-
- (WAI) Web Accessibility Initiative of W3 cover standard, guidelines, rules and techniques.
157-
158-
#### There is a growing amount of information about accessibilty, here are few articles to get you started!
159-
- (Introduction to Accessibility)[https://www.w3.org/standards/webdesign/accessibility]
160-
- (WAI Getting started)[https://www.w3.org/WAI/gettingstarted/]
161-
- (How People with disabilities use the web)[https://www.w3.org/WAI/intro/people-use-web]
162-
- (Tutorials)[https://www.w3.org/WAI/tutorials/]
163-
- (Mozilla have created their own Accessibility page)[https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA]
164-
- (ARIA Techniques for WCAG 2.0)[https://www.w3.org/TR/WCAG20-TECHS/aria]
165-
- The (A11Y Project)[http://a11yproject.com/] is an open source project on aiming to provide up to date and easy to access information regarding accessibility.
150+
Some of your users might be using screenreaders or keyboards to navigate across your page. How do you ensure your website is available to them? By following a few guidelines and integrating particular techniques.
151+
152+
#### Acronyms to know:
153+
- (ARIA) Accessible Rich Internet Applications are set of techniques and additions to HTML to allow additional markup to be interpreted by accessibility devices.
154+
- (WCAG) Website Content Accessibility Guidelines contain different compliance levels (A, AA and AAA) and lay down the “rules” to make a website or application accessible.
155+
- (WAI) The Web Accessibility Initiative is a part of the W3 consortium that works on accessibility standards, guidelines, rules and techniques.
156+
- (a11y or A11Y) is an abbreviation/numeronym for accessibility. The number 11 refers to the number of letters omitted.
157+
158+
#### Articles for getting started with accessibility:
159+
- [Introduction to Accessibility](https://www.w3.org/standards/webdesign/accessibility)
160+
- [WAI Getting started](https://www.w3.org/WAI/gettingstarted/)
161+
- [How People with disabilities use the web](https://www.w3.org/WAI/intro/people-use-web)
162+
- [Tutorials](https://www.w3.org/WAI/tutorials/)
163+
- [Mozilla have created their own Accessibility page](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA)
164+
- [ARIA Techniques for WCAG 2.0](https://www.w3.org/TR/WCAG20-TECHS/aria)
165+
- The [A11Y Project](http://a11yproject.com/) is an open source project on providing the most up to date and easy to access information regarding accessibility.
166+
167+
#### These extensions are handy if you wish to check if your website meets the criteria and areas to improve:
168+
- Chrome: WAVE Evaluation Tool
169+
- Firefox:[AInspector](https://addons.mozilla.org/en-US/firefox/addon/ainspector-sidebar/)

0 commit comments

Comments
 (0)