The following table lists the legacy checkpoints incorporated from the previous version of the Software checklist. The primary reason these checkpoints were retained was to maintain accuracy of Voluntary Product Accessibility Templates (VPATs) for legacy US Section 508 compliance requirements.

Because the ICT Refresh of Section 508 contains many new requirements (most based on the Web Content Accessibility Guidelines 2.0), some of which do not have a perfect 1:1 mapping with the prior version of the Software checklist, these seven checkpoints have been renumbered and brought forward during this transitional phase while the ICT Refresh is still in draft. Most of these seven are highly specific requirements, either not mentioned in the ICT Refresh due to technological changes, or covered by a new checkpoint that encompasses a great deal more than just this specific requirement. Conversely, three of them – 5.2 Object information, 5.3 Labels and 5.4 Forms – are all much broader than any single checkpoint in the new ICT Refresh checklist.

Because of this variety of scenarios the seven checkpoints cover, this table has been created to indicate the simplest method of completing each checkpoint for software teams.

Legacy Checkpoint Description Relevant checkpoints Explanation

6.0 to 3.6.1 checkpoint mappings

5.1 Non-audio cues for audio alerts.

Provide an option to display a visual cue for audio alerts.

On SW checklist 3.6.1, this was listed as checkpoint 3.1.

1.1.1 Non-Text Content (Situation G)

Non-audio cues are completely covered under Situation G of checkpoint 1.1.1 Non-Text Content.

Since 1.1.1 covers additional situations, legacy checkpoint 5.1 was left in place to ensure accurate reporting on legacy Section 508 VPATs for 1194.31(c)

If 1.1.1 passes without errors, 5.1 can be marked as passing as well. Otherwise, teams need to ensure 1.1.1 failures do not involve Situation G before marking 5.1 as passed.

5.2 Object information.

Provide semantic information about user interface objects. When an image represents a program element, the information conveyed by the image must also be available in text.

On SW checklist 3.6.1, this was listed as checkpoint 2.2.

1.1.1 Non-text Content (Situation C); 502.3.1 Object Information; 502.3.3 Values

Meeting the required development techniques of checkpoints 502.3.1 Object Information and 502.3.3 Values achieves the bulk of this requirement.

However, the language about requirements for images is covered by Situation C in 1.1.1 Non-text Content.

Since multiple checkpoints apply, checkpoint 5.2 has been created to ensure accurate legacy VPAT reporting,. Teams can follow the requirements and tests covered in 5.2. Alternatively, if the three checkpoints in the Relevant Checkpoints column pass, then 5.2 can be marked as passed without further testing.

5.3 Labels.

Associate labels with controls, objects, icons and images. If an image is used to identify programmatic elements, the meaning of the image must be consistent throughout the application.

On SW checklist 3.6.1 this was listed as checkpoint 2.3

1.1.1 Non-text Content; 1.3.1 Info and Relationships; 3.2.4 Consistent Identification (where applicable); 502.3.4 Label Relationships

Meeting the required development techniques of checkpoint 502.3.4 Label Relationships achieves the bulk of this requirement.

However, the legacy checkpoint also references the labelling of images. Associating labels with images is covered under 1.1.1 Non-text Content.

As well, consistently using the same meaning for an image throughout an application is covered partially by 1.1.1. Non-Text Content, Situation C, as well as by 3.2.4 Consistent Identification. Since 3.2.4 is Not Applicable to Most Software, checkpoint 5.3 was retained to capture a specific legacy 508 requirement, 1194.21(e).

Teams may find it simplest to pass 502.3.4, and then carry out an independent check on the image requirements of 5.3.

Note: 2.4.6 Headings and Labels, and 3.3.2 Labels or Instructions may seem to be related to 5.3, but these two WCAG checkpoints are concerned with proper use of language not programmatic association, so are not directly related.

5.4 Forms.

When electronic forms are used, the form shall allow people using assistive technology to access the information, field elements and functionality required for completion and submission of the form, including all directions and cues.

On SW checklist 3.6.1 this was listed as checkpoint 2.4.

2.1.1 Keyboard;1.3.1 Info and Relationships; 3.3.2 Labels or Instructions; 502.3.1 Object Information; 502.3.3 Values; 502.3.4 Label Relationships

5.4 maps directly to a Legacy 508 requirement, 1194.21(l).

Teams are recommended to follow requirements and tests covered in 5.4.

However, if all checkpoints in the Relevant Checkpoints column pass, then 5.4 can be marked as passed as well, without further testing.

5.5 Variety of color selections.

When color customization is supported, provide a variety of color selections capable of producing a range of contrast levels.

On SW checklist 3.6.1 this was listed as checkpoint 4.4.

No equivalent

5.5 maps directly to Legacy 508 requirement 1194.21(j).

Teams must follow requirements and tests covered in 5.5, since there is no equivalent in 508 Refresh.

5.6 Animation.

Provide an option to display animation in a non-animated presentation mode.

On SW checklist 3.6.1 this was listed as checkpoint 4.6.

1.1.1 Non-text Content; 2.2.2 Pause, Stop, Hide

5.6 maps directly to Legacy 508 requirement 1194.21(h).

Although animation is partially addressed in two WCAG checkpoints, the requirements are not identical. 2.2.2 Pause, Stop, Hide only applies when content automatically plays for more than 5 seconds.

To ensure proper reporting for 508, teams should follow requirements and tests covered in 5.6.

5.7 Volume control.

Provide an option to enable the user to adjust the volume.

On SW checklist 3.6.1 this was listed as checkpoint 3.3.

1.4.2 Audio Control

5.7 maps to Legacy 508 requirement 1194.31(d).

Although a WCAG checkpoint covers audio control, it is specifically directed at audio that plays automatically for more than 3 seconds.

Meeting 5.7 ensures that all important audio can be enhanced through volume control.