Website Accessibility in SharePoint

As part of my work I had to build accessible Web sites
This article explains what is accessible and why we need it.
The following articles explain how accessibility can be applied in practice in SharePoint

What is Website Accessibility?

Accessibility is defined as a need to increase the use of people with disabilities (blind, color blind, deaf, have problems with motor or cognitive) sites and computer systems.
Accessible websites are websites that allow people with disabilities and older people to browse at the same level of efficiency and fun as surfing the Internet. Accessible Web Development is not just a matter of social responsibility and compliance with laws and regulations.
December 2008 announced a new version with accessibility guidelines (version 2.0) - This version is the binding version.
Differences of the three access levels:
• Priority 1 - A basic level of accessibility
• Priority 2 - AA basic level of accessibility
• Priority 3 - highly accessible AAA
Accessible Web site must meet at least Priority 1 guidelines.
Government sites are committed to follow instructions priority level A and AA.

Priorities examples:

Priority	Description	Section	Class
1	Until user agents allow users to control flickering, avoid causing the screen to flicker	7.1	General
1	Provide redundant text links for each active region of a server-side image map.	1.2	Images
2	Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user	10.1	General
2	Do not use tables for layout unless the table makes sense when linearized. Otherwise, if the table does not make sense, provide an alternative equivalent (which may be a linearized version).	5.3	Tables
3	Until user agents render text equivalents for client-side image map links, provide redundant text links for each active region of a client-side image map.	1.5	Images
3	Provide summaries for tables	5.5	Tables

Rules for writing accessible:

Web sites serve the entire population. Therefore, site content writing should be clear and simple, to the result to be understandable to people from all sectors of the population, including people with reading difficulties for various reasons.
Reading difficulties may be due to the following problems:
• lower level of education or language skills are limited.
• difficulties in understanding the language of the content of the site, if it is not language of the user.
• Learning Disabilities
When writing content to the site, be sure to visualize the range of users. Think of a - store received only an elementary education, the child still attends - elementary school, think of a new immigrant, a person with dyslexia and other people like that. Give these people names and faces and ask yourself each time whether they will be able to easily understand the content you write.

Bar Accessories - Accessibility

Icons or Tags arranged together and appear on all or most, pages (Master-Page). Components listed on the aids are often technical aids and tags linked to specific text on the site.
Usually positioned at the top of the screen above the main navigation menu.
The bar should appear on all pages of the site. Only a few cases can give the ruler, for example, windows open (Pop-Up Window).
Information should include the ALT component for each ruler related tags. The information will describe in more detail where the user tag will be leading graphic replacement for restricted users
It has a
Zoom in / out of fonts
Contrast the page
Orientation bar / breadcrumb navigation

In the following articles:

• Prevention design is not good for Accessibility in SharePoint
• Construction of correct design patterns in SharePoint
• Preventing copy-paste all the rich text editor in SharePoint
• Font growing and reduction in SharePoint
• Change the site colors (mostly black background and yellow font and vice versa) in SharePoint

Online you will find many more rules accessible sites.
Roi