After reading the WCAG recomondation for Lavel A and AA, and reading serveral contributions to serveral forums I still have to admit that the whole issue of accesibility needs more time and attention to really get to a full understanding. Time which I doubt is worth spending at this point.
To my understanding the very basic points for Accesibility are:
Checklist on Design
- always offer a text alternative to nontext content
- only use text for the navigation (topnavigation and sidenavigation)
- try not to use Java, Javascript or anythink alike
- only use the latest HTML which the correct sytax
- not flickering or blinking elements (animated GIFs, Flash)
Checklist on fonts
- allways use relative font-size (100%) never absolut or fixed font-size (e.g. 12pt)
- fontsize 1em= 100%
- do not use the<Font>, <Blink> or <Marque>- Tag
- Use only sans serif fonts like Arial, Verdana
- do not use more than three different fonts
Checklist on colours
- best to use is anything with highcontrast text/background (e.g. black text on white background)
- no red/brown or red/green, some people will not see the difference
- All information has to stay understandable when displayed using no colours. (e.g. how it should not be done: "the names below, which are highlited in green are the responsible..." - for viewing this without colour there will be no difference between the name)
Checklist on images
- Another option is aTextlink below the image pointing to a page with further discription of the image
- if we use nonvisiable grafik leave ALT-Tag empty. Screenreader than do not read anything
- do not put image numbers etc. in the alt tag. Its anoing when the screen reader reads them all
- As ALT-Tags are visible to all user (on mouse over/MSIE) we might consider a link bellow the picture if we have a longer discription to an image (the usage of the ALT-Tags are also an SEO issue)
- try to aviod using background images
- charts (images only) be offered also as text chart or with an alternative text description
Checklist on Video
- possiblity to stop, pause and play
- no flickering in the array of 4-59 Hertz (flashing stuff)
- no subtitels, playing in the video - text alternative
Checklist on Audio
- deaf people need a text alternative (link bello the audio to a text description page)
Checklist on Applets and Scripts
- only use if the information retain the same if the user cannot use the applet or offer a textalternative to it
Checklist on Links
- use short textlinks which describes it function
- do not use "klick here"-Links as some people jump from link to link and will not have the information in the text before. Link the whole sentence (e.g.: "for further information on the International Association click here")
- all links reachaable with the Tab-key
- Links not to close to each other (think of the displaying of the taxonomy)
- skip links option on the beginning of the site (not only readable for screen readers as keybord user who can read might whant to use this as well-- I have no idear how we can achieve this)
Of course there are more recomondations related f.e. to using/not using frames or tables etc. etc. but so far I think they do not affect us. We will see.
Please leave any comment on "is it possible for us to achieve this?"
Linked project:
Accessibility