13
edits
Drumbeat/p2pu/courses/accessibility: Difference between revisions
no edit summary
(First draft) |
No edit summary |
||
| Line 1: | Line 1: | ||
= | = Accessibility (Working Draft) = | ||
== | == Short description == | ||
*Martin Kliehm* | |||
This could be an introduction to web accessibility, but you you never stop learning. So even if you're an accessibility veteran, together we will find a challenging task for you. Please let me know in advance what your job requires, and if you're into design, programming, or consultancy. | |||
You will become aware of the top ten barriers in websites, you will learn that accessibility reaches beyond blind people as there are many aspects and perspectives to keep in mind. Yes, checklists and add-ons help, but you will also get some insights in using (open source) screen reader software. | |||
== Can you lead this course in September 2010 or is this a general concept? == | == Can you lead this course in September 2010 or is this a general concept? == | ||
Course typically run over 6 weeks with a weekly | Course typically run over 6 weeks with a weekly telcon. | ||
== What's The Major Project? == | == What's The Major Project? == | ||
I'm open for suggestions. Building a WordPress website for a non-profit would be cool. | |||
== What you should know == | == What you should know == | ||
* | *Good understanding of the web | ||
**Why: We won't explain what web pages are, so you should know the basics of your profession. | |||
** | **How: If you're a frontend engineer, you should have a thorough understanding of web standards and semantic markup. If you are a designer, you certainly know a few things about color, typography, whitespace, and usability. As a consultant you should have a general idea about usability, information architecture, project goals, and target groups; perhaps you won't be knee deep into code, but you should recognize a bad page and why it is so. | ||
**... | |||
== What you can expect to learn == | == What you can expect to learn == | ||