Template:Notes: Difference between revisions
From TCU Wiki
| Line 14: | Line 14: | ||
</noinclude><includeonly> | </noinclude><includeonly> | ||
==Session Outputs== | ==Session Outputs== | ||
- Accessibility principles | |||
- Usability versus accessibility. Definitions. | |||
- Statistics. 15% of people are disabled, Internet is also for them. | |||
- Some tips: | |||
1 - Keep the website simple | |||
2 - Scale responsive design to achieve accessibility | |||
3 - Use semantic tags while programming | |||
4 - Use of stylesheets | |||
5 - Use of section markup (header, body, footer... all semantically organised) | |||
6 - Hovering, over effects for those people who use only keyboards | |||
7 - Put the alerts in an invalid form below not above the element | |||
8 - Play with pixels size for those using only mouse | |||
9 - Color is not only the way to differentiate information | |||
10 - Write accessible content (sentence - header, paragraphs - body...) | |||
Conclusion: Accessibility happens when people don't need to think. Accessibility allows your platform to get more users (don't forget the 15%!) | |||
Example of good accessible website -> Dropbox | |||
Discussions: | |||
1 - Are carrousels accessible enough? | |||
2 - Do all websites look like the same? Is this okay? | |||
3 - When translating websites, how do we deal with components getting too big because of the longer content in another language? | |||
==Next Steps== | ==Next Steps== | ||
Revision as of 21:58, 6 March 2017
This is the "Notes" template. It should be called in the following format:
{{Notes
|Session Outputs=
|Next Steps=
|Additional Notes=
|Relevant Resources=
|Contributors=
}}
Edit the page to see the template text.
test
