The following are guidelines that, when adhered to will make the site accessible to the various types of screen readers. CleverCherry will always provide a Text only version of the website’s content. There are occasions when the guidelines below cannot be followed (e.g. the website is built mainly using Flash Technology), on these occasions, the text only version will ensure that the content is still available to screen readers.

Further reference to the items below can also be clarified by researching the w3c’s website (www.w3.org) , under the heading “Web Accessibility Initiative”

General

• Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video.
• Organize documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document.
• Ensure that equivalents for dynamic content are updated when the dynamic content changes
• Use the clearest and simplest language appropriate for a site's content.

ACRONYM And ABBR Tags

• Encourage the use of Acronym and ABBR tags. These can greatly enhance the usability of the data. They can be useful in giving links a clear description.

Image Maps

• Provide redundant text links for each active region of a server-side image map.
• Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape.

Tables

• For data tables, identify row and column headers.
• For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells.

Applets and scripts

• Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page.