ITS Services and Applications
Page tree

The following is a list of the most used checkpoint groups with descriptions on when it is suitable to use them and what to expect from the results.

For additional descriptions of the individual checkpoints please reference the digested WCAG Checkpoint list curated by WebAIM.

 

The groups are listed in a ascending format from least results to most. It is recommended to start at the top of this list and work your way down to the next checkpoint once issues have been remediated from your current checkpoint.

Just for count pages (Recommend start checkpoint)

Description: This checkpoint group contains zero checkpoints, so that you can receive a logical number of pages 

Use: This is used to get an exact number of pages that Compliance Sheriff is scanning. This will give you an optimized number of pages for the amount of levels you are scanning (and this will take into affect the excludes/includes you have added). Once you set your Max Pages from this number, it will give you a better timeline of when the scan will be finished, because the scan calculations is based on Pages Scanned over Max Pages.

Results: You will not receive a score number or any results from this, only the pages scanned number is of importance. If you adjust your levels you will want to run this checkpoint again to get a new count.

OCR Contrast Ratio

Description: Contrast checking only for 3:1 on large text and 4.5:1 on small text.  Removed requirement for need to specify both text and background color.

Use: This is used to flush out two main Contrast issues on pages using accessibility checkpoints Accessibility 20 G145 and Accessibility 20 G18.

  • Accessibility 20 G145 - Ensure that a contrast ratio of at least 3:1 exists between text (and images of text) and background behind the text
  • Accessibility 20 G18 - Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text

Results: The results received should show you any instance in which either of these cases needs to be corrected.

OCR Prioritizing Checkpoints

Description: This checkpoint group contains 10 of the most important accessibility issues that should be addressed.

Use: Use this checkpoint to gauge overall issues that would drastically impact accessible users.

  • WCAG 2.0 - Criterion 1.1.1 [Non-text Content]
  • WCAG 2.0 - Criterion 1.2.2 [Captions (Prerecorded)] 
  • WCAG 2.0 - Criterion 1.3.1 [Info and Relationships]
  • WCAG 2.0 - Criterion 1.4.1 [Use of Color]
  • WCAG 2.0 - Criterion 2.4.1 [Bypass Blocks]
  • WCAG 2.0 - Criterion 2.4.2 [Page Titled]
  • WCAG 2.0 - Criterion 2.4.4 [Link Purpose (In Context)]
  • WCAG 2.0 - Criterion 3.1.1 [Language of Page]
  • Contains OCR Contrast ratio Checkpoint Group

Results: The results received should give you a good starting point for remediation, as these checkpoints impact the usability of the webpage.

WCAG 2.0 w/o Contrast & Font Sizing

Description: This was the original checkpoint created in order to limit the results of a couple most common errors, this will allow the results to better determine other most common issues on pages. 

Use: This checkpoint group is used primarily with sites already incorporated with rem font sizes, as they are deemed unworthy by Compliance Sheriff at this time. This group contains 24 checkpoints:

  • WCAG 2.0 - Criterion 1.1.1 [Non-text Content]
  • WCAG 2.0 - Criterion 1.2.1 [Audio-only and Video-only (Prerecorded)]
  • WCAG 2.0 - Criterion 1.2.2 [Captions (Prerecorded)] 
  • WCAG 2.0 - Criterion 1.2.3 [Audio Description or Full Text Alternative] 
  • WCAG 2.0 - Criterion 1.2.4 [Captions (Live)] 
  • WCAG 2.0 - Criterion 1.3.1 [Info and Relationships]
  • WCAG 2.0 - Criterion 1.3.2 [Meaningful Sequence] 
  • WCAG 2.0 - Criterion 1.3.3 [Sensory Characterisitics] 
  • WCAG 2.0 - Criterion 1.4.2 [Audio Control] 
  • WCAG 2.0 - Criterion 2.1.1 [Keyboard] 
  • WCAG 2.0 - Criterion 2.2.1 [Timing Adjustable] 
  • WCAG 2.0 - Criterion 2.2.2 [Pause, Stop, Hide] 
  • WCAG 2.0 - Criterion 2.3.1 [Three Flashes or Below Threshold] 
  • WCAG 2.0 - Criterion 2.4.1 [Bypass Blocks]
  • WCAG 2.0 - Criterion 2.4.2 [Page Titled] 
  • WCAG 2.0 - Criterion 2.4.4 [Link Purpose (In Context)]
  • WCAG 2.0 - Criterion 3.1.1 [Language of Page]
  • WCAG 2.0 - Criterion 3.1.2 [Language of Parts] 
  • WCAG 2.0 - Criterion 3.2.1 [On Focus] 
  • WCAG 2.0 - Criterion 3.2.2 [On Input] 
  • WCAG 2.0 - Criterion 3.2.3 [Consistent Navigation] 
  • WCAG 2.0 - Criterion 3.2.4 [Consistent Identification] 
  • WCAG 2.0 - Criterion 4.1.1 [Parsing] 
  • WCAG 2.0 - Criterion 4.1.2 [Name, Role, Value] 

Results: The results received will outline many issues to insure: Web content is made available to the senses - sight, hearing, and/or touch; Interface forms, controls, and navigation are operable; Content and interface are understandable; and Content can be used reliably by a wide variety of user agents, including assistive technologies.

WCAG 2.0 - Compliance Level A

Description: This is the unedited WCAG 2.0 A Checkpoints which are maintained by Compliance Sheriff.

Use: Use this group if you wish to see the full gambit of issues that may need to be adjusted.

WCAG 2.0 - Compliance Level AA

Description: This is the unedited WCAG 2.0 AA Checkpoints which are maintained by Compliance Sheriff.

Use: Use this group in conjunction with WCAG 2.0 - Compliance Level A if you wish to see the full gambit of issues that may need to be adjusted.

WCAG 2.0 - Compliance Level AAA

Description: This is the unedited WCAG 2.0 AAA Checkpoints which are maintained by Compliance Sheriff.

Use: Use this group in conjunction with WCAG 2.0 - Compliance Level A and WCAG 2.0 - Compliance Level AA if you wish to see all the results that are required to meet the WCAG AAA standard.

  • No labels