Difference between revisions of "Accessibility legislation"
(Created page with "As of January 1st 2012, the AODA Act legally requires all organizations providing goods or services to the public or to other organizations in Ontario to provide accessible cu...") |
Mark Bridger (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | + | Web Content Accessibility Guidelines (WCAG) is a set of recommendations for making web content more accessible. | |
| − | + | The Accessibility for Ontarians with Disabilities Act, 2005 (AODA) legally requires all organizations providing goods or services to the public in Ontario to provide accessible customer service to all people, including those with disabilities. | |
| − | + | '''You can learn more about these:''' | |
| − | + | *Web Content Accessibility Guidelines (WCAG) 2.0 http://www.w3.org/TR/WCAG20/ | |
| − | + | *The Accessibility for Ontarians with Disabilities Act (AODA) http://www.ontario.ca/laws/statute/05a11 | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | '''How SmartSimple adheres to these:''' | |
| + | Below is a list of some of these accessibility guidelines and how SmartSimple meets them. | ||
| − | + | Inputs need a label | |
| − | + | Example: On the login page the password input has a label called password. On the signup page each input has a label. For custom fields the label name will be the same as the caption; if there is no caption the label will take the name of the field. Labels are automatically added for inputs by SmartSimple. | |
| − | + | ||
| − | + | Images need alternate text | |
| − | + | Example: Your logo is given an alternate text tag. The custom field “Display Only – Image” will give an image uploaded an alternate text tag. The tag will take the name of the caption and if no caption is present it will take the field name. Alt tags are added automatically for logos and display only images. | |
| − | + | ||
| + | Language needs to be declared | ||
| + | Example: Language is declared in pages (lang="fr" for French , lang="en" for English ). This is automatically added to pages and it changes dynamically when the user changes their language. | ||
| + | |||
| + | Use descriptive names for links | ||
| + | Example: When including links in your content, use text that properly describes where the link will go. Using "click here" is not considered descriptive, and is ineffective for a screen reader user. Link names are customizable in SmartSimple. | ||
Revision as of 13:04, 3 September 2015
Web Content Accessibility Guidelines (WCAG) is a set of recommendations for making web content more accessible.
The Accessibility for Ontarians with Disabilities Act, 2005 (AODA) legally requires all organizations providing goods or services to the public in Ontario to provide accessible customer service to all people, including those with disabilities.
You can learn more about these:
- Web Content Accessibility Guidelines (WCAG) 2.0 http://www.w3.org/TR/WCAG20/
- The Accessibility for Ontarians with Disabilities Act (AODA) http://www.ontario.ca/laws/statute/05a11
How SmartSimple adheres to these: Below is a list of some of these accessibility guidelines and how SmartSimple meets them.
Inputs need a label Example: On the login page the password input has a label called password. On the signup page each input has a label. For custom fields the label name will be the same as the caption; if there is no caption the label will take the name of the field. Labels are automatically added for inputs by SmartSimple.
Images need alternate text Example: Your logo is given an alternate text tag. The custom field “Display Only – Image” will give an image uploaded an alternate text tag. The tag will take the name of the caption and if no caption is present it will take the field name. Alt tags are added automatically for logos and display only images.
Language needs to be declared Example: Language is declared in pages (lang="fr" for French , lang="en" for English ). This is automatically added to pages and it changes dynamically when the user changes their language.
Use descriptive names for links Example: When including links in your content, use text that properly describes where the link will go. Using "click here" is not considered descriptive, and is ineffective for a screen reader user. Link names are customizable in SmartSimple.
