Website accessibility Hints and Tips

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.
Ensure that all information conveyed with colour is also available without colour, for example from context or markup
Clearly identify changes in the natural language of a document's text and any text equivalents (e.g. captions)
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
Until user agents allow users to control flickering, avoid causing the screen to flicker
Use the clearest and simplest language appropriate for a site's content

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

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

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

Checklist of Checkpoints for Web Content Accessibility Guidelines 1.0
Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation
For any time-based multimedia presentation (e.g. a movie or animation), synchronize equivalent alternatives (e.g. captions or auditory descriptions of the visual track) with the presentation

If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies; is accessible; has equivalent information (or functionality); and is updated as often as the inaccessible (original) page

W3C checkpoints which are less relevant to e-recruitment sites have been omitted

Ensure that foreground and background colour combinations provide sufficient contrast when viewed by someone having colour deficits or when viewed on a black and white screen [Priority 2 for images, Priority 3 for text] Note: It is highly recommend that you use relative font sizes on your site if at all possible to assist applicants who need to enlarge screen text size
Ensure that dynamic content is accessible or provide an alternative presentation or page
Until user agents allow users to control blinking, avoid causing content to blink (i.e. change presentation at a regular rate, such as turning on and off)
Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages
Until user agents allow users to turn off spawned (pop up) windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user
Clearly identify the target of each link
Use navigation mechanisms in a consistent manner

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)

Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone

Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure the label is properly positioned
Associate labels explicitly with their controls

For scripts and applets, ensure event handlers are input device-independent
Until user agents allow users to freeze moving content, avoid movement in pages
Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies
[Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2.]
Ensure any element that has its own interface can be operated in a device-independent manner
For scripts, specify logical event handlers rather than device-dependent event handlers