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

Self-study Training Course: WCAG 1 Priority 2 Checkpoints

Training: Web Content Accessibility Guidelines Version 1 Priority 2 Checkpoints

WCAG 1 Priority 2 Training Course Index.

• 2.2 Ensure that foreground and background color combinations provide sufficient contrast
  
  • Article: Accessible Web design: Colour
    
  • Exercise: Check colour contrast
    
• 3.1 When an appropriate markup language exists, use markup rather than images to convey information.
  
  • Article: Why not use images instead of text?
    
  • Exercise for Checkpoint 3.1
    
• 3.2 Create documents that validate to published formal grammars
  
  • Article: HTML - looking down at it from a very great height
    
  • Article: An introduction to standard HTML and accessibility
    
  • Article: Use Valid Markup in your documents
    
  • Exercise: Use the W3C valdiator to check that the validity of markup
    
• 3.3 Use style sheets to control layout and presentation.
  
  • Article: Definitions: Document Content, Structure, and Presentation
    
  • Exercise: use CSS to set text colour
    
• 3.4 Use relative rather than absolute units in markup language attribute values and style sheet property values
  
  • Exercise: use a relative unit to set font sizes
    
  • Exercise: use a relative unit to set font sizes
    
  • Exercise: Mark up headings appropriately
    
• 3.6 Mark up lists and list items properly.
  
  • Exercise; markup a list on the tutorial website
    
• 3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation
  
• 5.3 Do not use tables for layout unless the table makes sense when linearized
  
  • Article: Table Manners: Creating accessible layout tables
    
  • Exercise: view table in WAVE accessibility tool
    
• 6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page
  
  • Article: Making Dynamic Content Accessible
    
• 7.2 Until user agents allow users to control blinking, avoid causing content to blink
  
  • Notes: Allow user control of blinking
    
• 7.4 and 7.5 Until user agents provide the ability to stop the refresh and redirect
  
• Article; autodirecting or refreshing pages
  
• 8.1 Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies
  
  • Article: Accessibility issues with Javascript
    
• 9.3 For scripts, specify logical event handlers rather than device-dependent event handlers
  
  • Article: Javascript event handlers and accessibility
    
• 10.1 Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear
  
  • Article: problems with opening new windows
    
• 11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported
  
  • Article: Use latest W3C technologies when appropriate
    
• 11.2 Avoid deprecated features of W3C technologies.
  
  • Article: deprecated (X)HTML features
    
• 12.3 Divide large blocks of information into more manageable groups where natural and appropriate
  
  • Article: Creating accessible forms on the Web
    
  • Exercise: Creating accessible forms
    
• 13.1 Clearly identify the target of each link
  
  • Exercise: check link text in a text browser
    
• 13.2 Provide metadata to add semantic information to pages and sites
  
  • Article: Adding metadata to web pages
    
• 13.3 Provide information about the general layout of a site (e.g., a site map or table of contents)
  
• 12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone
  

Contributed by Jim Byrne