In the recent times when we developed web properties, it has become standard for us to adhere to "Privacy and Accessibility" guidelines. In some cases, the customers have their own set of privacy and accessibility guidelines, and in other cases the customers expect the implementation agencies to follow the latest standard. In either case the core of these guidelines are laid out of by the World Wide Web Consortium (W3C).
Let us explore the accessibility guidelines a little more, and ask, why and how it is relevant?
It is essential that the Web be accessible in order to provide equal access and equal opportunity to people with diverse abilities
Accessibility supports social inclusion for people with disabilities as well as others, such as older people, people in rural areas, and people in developing countries. (Source: W3C)
There is also a strong business case for accessibility. Accessibility overlaps with other best practices such as mobile web design, device independence, multi-modal interaction, usability, design for older users, and search engine optimization (SEO). Case studies show that accessible websites have better search results, reduced maintenance costs, and increased audience reach, among other benefits. (Source: W3C)
Some of these following examples will probably give much better view on the practical usage of these Accessibility guidelines.
1) Alternative Text for Images
Images should include equivalent alternative text in the markup example
This Alt text is useful in following scenarios,
2) Transcripts for Pod Casts
Just as images aren't available to people who can't see, audio files aren't available to people who can't hear. Providing a text transcript makes the audio information accessible to people who are deaf or hard of hearing, as well as to search engines and other technologies that can't hear.
It's easy and relatively inexpensive for website developers to provide transcripts for podcasts and audio files.
Making a Web site accessible can be simple or complex, depending on many factors such as the type of content, the size and complexity of the site, and the development tools and environment.
Many accessibility features are easily implemented if they are planned from the beginning of Web site development. Fixing inaccessible Web sites can require significant effort, especially sites that were not originally "coded" properly with standard XHTML markup, and sites with certain types of content such as multimedia.
The detailed list of guidelines to be followed can be found here http://www.w3.org/TR/WCAG20/
When developing or redesigning a site, evaluating accessibility early and throughout the development process can identify accessibility problems early when it is easier to address them. Some of these can be tested in the browser itself. For example turn-off image download and verify Alt Text has been applied on all images
Other than this there is an exhaustive list of free and commercial version of evaluation tools are available. HiSoftware is one of leading organization in this, and in one of our leading Customer HiSoftware tools are used to evaluate the Accessibility checks.
During some of our implementation, the most commonly failed accessibility checks are on the visual side like font color, background color etc. rather than the markup issues like ALT Text which is more under the developer control. Best way to handle these visual issues will be to scan the Visual Design (PSD files) itself for accessibility issues before the start of the technical development and ensure that all visual issues are resolved during the Visual Design Phase. This will avoid significant remediation effort that might be required to perform these visual fixes during the later stage of the development.
Protecting customer privacy is critically important. In many areas of the world, privacy is considered a fundamental human right. Additionally, protecting customer privacy can increase loyalty and be a market differentiator
Like accessibility, there are tools available to you to check on the privacy guidelines.
Following are some key Privacy Guidelines:
Other than this there will also be country and region specific privacy regulations that would need to be followed. For example:
Hence the customer privacy guidelines should be constantly modified / keep up-to-date to comply with new privacy laws in various regions.
In Summary it is essential to follow good privacy and accessibility guidelines such as those found in this article. A lack of follow-up of these could lead to usability issues as well as risk in terms of legal compliance, with potential for costly fines (potential for multi-millions) and regulatory orders.
Deepak Bhat currently working as Principal Consultant in MindTree Ltd, has been working in CMS space over last 10 years. Initially started working on the Enterprise Products like Interwoven TeamSite, BroadVision One-to-One CMS Systems, and with evolvement of Industry have been exposed to more Mid-stream to Open Soruce products like SharePoint, Alfresco and Drupal.