• Home
• About GAWDS
• Member Profiles
• Contact
• Join GAWDS
• RSS

Self-study Training Course: WCAG Priority 1 Checkpoints

Training: WCAG 1 Priority 1

WCAG 1 Priority 1 Training Course Index.

• 1.1 Provide a text equivalent for every non-text element
  
  • Article: How to make non-text elements accessible
    
  • Exercise: Compare graphic and text browser versions of tutorial site
    
  • Exercise: Add an alt attribute to the image based heading
    
• 5.1 For data tables, identify row and column headers.
  
  • Exercise: Adding a longdesc attribute to the Customer Satisfaction Survey Pie Chart
    
  • Exercise: Add text equivalent to applets and programmatic objects.
    
• 1.2 Provide redundant text links for each active region of a server-side image map.
  
  • Exercise: Adding an alt attribute to a client-side image map
    
• 1.3 Until user agents can automatically read aloud the text equivalent of a visual track, provide auditory description of the important information
  
  • Exercise: View an example of accessible media
    
• 2.1 Ensure that all information conveyed with colour is also available without color, for example from context or markup.
  
  • Exercise: alter the tutorial website so that access is not dependent on the use of colour
    
• 4.1 Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions).
  
  • Exercise: indicate a change in language
    
  • Article: Making Data Tables Accessible
    
  • Exercise: Use appropriate markup for tables
    
  • Exercise: Making more complex tables accessible
    
    
• 6.1 Organise documents so that they may be read without style sheets.
  
  • Article: CSS accessibility problems: is markup dead?
    
  • Exercise: Turn off style sheets and check accessiblity of the website
    
    
• 6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes.
  
  • Exercise: Suggest how alternatives could be provided for dynamic content
    
    
• 6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported.
  
  • Article: Accessibility issues with Javascript
    
  • Exercise: Ensure links still work when Javascript is not supported or turned off
    
    
• 7.1. Until users agents allow users to control flickering, avoid causing the screen to flicker.
  
• 9.1: Provide client-side image maps instead of server side image maps where the region cannot be defined with an available geometric shape.
  
• 12.1 Title each frame to facilitate frame identification and navigation.
  
  
  • Article: Frames and accessibility
    
  • Exercise: Making a websites that uses frames accessible
    
  • Exercise: Use the noframes element on the tutorial website
    
    
• 14.1 Use the clearest and simplest language appropriate for a site's content.
  
  • Exercise: Improve clarity and organisation of content
    
    

Contributed by Jim Byrne