The following tables show the impact of the new 7.0 checklist on new and existing checkpoints from the 6.1 checklists.

For products transitioning from earlier checklists, see the prior analyses: Web Checklist 6.1 to 5.2 Comparison and Impact Analysis and SW Checklist 6.x to 3.6.1 Comparison and Impact Analysis. An IBM-internal-only recording of the 2016 Impact Analysis seminar is also available.

Overall Impact

WCAG 2.0 A and AA. No impact to web products.

502 - Interoperability with Assistive Technology. Low impact to non-web products.

503 - Applications. No to moderate impact to non-web products.

504 - Authoring Tools. Medium to high impact to web, hybrid and non-web products which offer authoring tool capabilities.

602 - Documentation. No impact web documentation; medium impact to non-web documentation.

EN 301 549 Additional Requirements. Low impact except for applications with authoring tool or media player capabilities

 

WCAG 2.0 A and AA

Checkpoint Impact Comments
All checkpoints (1.1.1 through 4.1.3) No impact All WCAG checkpoints are pre-existing for teams transitioning from 6.1.

502 - Interoperability with Assistive Technology

Checkpoint Impact Comments

502.2.1 User Control of Accessibility Features. Platform software shall provide user control over platform features that are defined in the platform documentation as accessibility features.

None New for 7.0. Applies only to platform software (i.e., desktop operating systems, web browsers) so almost all products are N/A. Platform software should likely meet already.

502.2.2 No Disruption of Accessibility Features. Applications shall not disrupt platform features that are defined in the platform documentation as accessibility features.

None No change to requirements.

502.3.1 Object Information. The object role, state(s), properties, boundary, name, and description shall be programmatically determinable.

Trivial Version 6.1 content for Object Information split into two separate checkpoints for 7.0 (502.3.1 and 502.3.2) but requirements are largely the same. Properties is a new requirement which was already covered by 502.3.4 Values.

502.3.2 Modification of Object Information. States and properties that can be set by the user shall be capable of being set programmatically, including through assistive technology.

Trivial Version 6.1 content for Object Information split into two separate checkpoints for 7.0 (502.3.1 and 502.3.2) but requirements are largely the same.

502.3.3 Row, Column, and Headers. If an object is in a data table, the occupied rows and columns, and any headers associated with those rows or columns, shall be programmatically determinable.

None Renumbered from 6.1 (502.3.2). No change to requirements.

502.3.4 Values. Any current value(s), and any set or range of allowable values associated with an object, shall be programmatically determinable.

Trivial Version 6.1 content for Values is split into two separate checkpoints for 7.0 (502.3.4, 502.3.5). No new requirements.

502.3.5 Modification of Values. Values that can be set by the user shall be capable of being set programmatically, including through assistive technology.

Trivial Version 6.1 content for Values is split into two separate checkpoints for 7.0 (502.3.4, 502.3.5). No new requirements.

502.3.6 Label Relationships. Any relationship that a component has as a label for another component, or of being labeled by another component, shall be programmatically determinable.

None Renumbered from 6.1 (502.3.4). No change to requirements.

502.3.7 Hierarchical Relationships. Any hierarchical (parent-child) relationship that a component has as a container for, or being contained by, another component shall be programmatically determinable.

None Renumbered from 6.1 (502.3.5). No change to requirements.

502.3.8 Text. The content of text objects, text attributes, and the boundary of text rendered to the screen, shall be programmatically determinable.

Trivial Version 6.1 content for Text split into two separate checkpoints for 7.0 (502.3.8, 502.3.9). No new requirements.

502.3.9 Modification of Text. Text that can be set by the user shall be capable of being set programmatically, including through assistive technology.

Trivial Version 6.1 content for Text split into two separate checkpoints for 7.0 (502.3.8, 502.3.9). No new requirements.

502.3.10 List of Actions. A list of all actions that can be executed on an object shall be programmatically determinable.

 Trivial Version 6.1 content for Actions split into two separate checkpoints for 7.0 (502.3.10, 502.3.11). No new requirements.

502.3.11 Actions on Objects. Applications shall allow assistive technology to programmatically execute available actions on objects.

 Trivial Version 6.1 content for Actions split into two separate checkpoints for 7.0 (502.3.10, 502.3.11). No new requirements.

502.3.12 Focus Cursor. Applications shall expose information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface components.

 None  Renumbered from 6.1 (502.3.8). No new requirements.

502.3.13 Modification of Focus Cursor. Focus, text insertion point, and selection attributes that can be set by the user shall be capable of being set programmatically, including through the use of assistive technology.

 Low to moderate New for 7.0. Native controls and many standard programming elements already support programmatic access for focus, insertion point and selection.

502.3.14 Event Notification. Notification of events relevant to user interactions, including but not limited to changes in the component’s state(s), value, name, description, or boundary, shall be available to assistive technologies.

 None  Renumbered from 6.1 (502.3.9). No new requirements.

502.4 Platform Accessibility Features. Platforms and platform software shall conform to the requirements in ANSI/HFES 200.2, Human Factors Engineering of Software User Interfaces — Part 2: Accessibility (2008) listed below:

  1. Section 9.3.3 Enable sequential entry of multiple (chorded) keystrokes;
  2. Section 9.3.4 Provide adjustment of delay before key acceptance;
  3. Section 9.3.5 Provide adjustment of same-key double-strike acceptance;
  4. Section 10.6.7 Allow users to choose visual alternative for audio output;
  5. Section 10.6.8 Synchronize audio equivalents for visual events;
  6. Section 10.6.9 Provide speech output services; and
  7. Section 10.7.1 Display any captions provided.
 None New for 7.0. Applies only to platform software (i.e., desktop operating systems, web browsers), so almost all products are N/A. Platform software likely already meets.

503 - Applications

Checkpoint Impact Comments

503.2 User Preferences. Applications shall permit user preferences from platform settings for color, contrast, font type, font size, and focus cursor.

EXCEPTION: Applications that are designed to be isolated from their underlying platform software, including Web applications, shall not be required to conform to 503.2.

None No change to requirements.

503.3 Alternative User Interfaces. Where an application provides an alternative user interface that functions as assistive technology, the application shall use platform and other industry standard accessibility services.

None New for 7.0. Aimed specifically at a product which creates an alternative user interface to support users with disabilities. Almost all products will mark this as N/A.

503.4.1 Caption Controls. Where user controls are provided for volume adjustment, ICT shall provide user controls for the selection of captions at the same menu level as the user controls for volume or program selection.

None to moderate New for 7.0. Only applies  to applications with media player functionality. Where it does apply, the effort to meet the requirement is not significant.

503.4.2 Audio Description Controls. Where user controls are provided for program selection, ICT shall provide user controls for the selection of audio descriptions at the same menu level as the user controls for volume or program selection.

None to moderate New for 7.0. Only applies  to applications with media player functionality. Where it does apply, the effort to meet the requirement is not significant.

504 - Authoring Tools

Checkpoint Impact Comments

504.2 Content Creation or Editing. Authoring tools shall provide a mode of operation to create or edit content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 for all supported features and, as applicable, to file formats supported by the authoring tool. Authoring tools shall permit authors the option of overriding information required for accessibility.

EXCEPTION: Authoring tools shall not be required to conform to 504.2 when used to directly edit plain text source code.

Medium to high New requirement to provide capability to support the generation of accessible output in compliance with all WCAG A and AA checkpoints. Impacts design, development and test. Applies to any product which includes the ability to author content.

504.2.1 Preservation of Information Provided for Accessibility in Format Conversion. Authoring tools shall, when converting content from one format to another or saving content in multiple formats, preserve the information required for accessibility to the extent that the information is supported by the destination format.

None to high Only applies to products that have mechanism for converting authoring tool output to different formats.

504.2.2 PDF Export. Authoring tools capable of exporting PDF files that conform to ISO 32000-1:2008 (PDF 1.7) shall also be capable of exporting PDF files that conform to ANSI/AIIM/ISO 14289-1:2016 (PDF/UA-1).

None to medium Only applies to products that generate PDF 1.7-compliant output from authored content.

504.3 Prompts. Authoring tools shall provide a mode of operation that prompts authors to create content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 for supported features and, as applicable, to file formats supported by the authoring tool.

Medium to high New requirement to provide capability to prompt for the creation of accessible output for authoring tools.  Impacts design, development and test. May need to add in features to prompt for accessibility.

504.4 Templates. Where templates are provided, templates allowing content creation that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 shall be provided for a range of template uses for supported features and, as applicable, to file formats supported by the authoring tool.

None to high New requirement to provide support for the generation of accessible output from authoring tool templates, where templates are offered. Impacts development and test.

602 - Documentation

Checklist Impact Comments

602.2 Accessibility and Compatibility Features.  Documentation lists and explains accessibility and compatibility features, including keyboard access.

None to medium Existed in 6.1 for web products, and an equivalent requirement existed for v2.1 Documentation checklist. No impact to products without authoring tools. Applications that contain authoring tools need to promote the production of accessible content.

602.3 Electronic Support Documentation. Documentation in electronic format, including Web-based self-service support, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0.

None to medium For web-based documentation, no to low impact. For other electronic formats, such as MS Word, PDF and other formats, effort will vary based on tooling capabilities and vendor guidance.

EN 301 549 Additional Requirements

Checkpoint Impact Comments

7.1.1 Captioning Playback. Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

None to low Applies to media players; feature should already be in place.

7.1.2 Captioning Synchronization. Where ICT displays captions, the mechanism to display captions shall preserve synchronization between the audio and the corresponding captions.

None to low Applies to media players; feature should already be in place.

7.1.3 Preservation of Captioning. Where ICT transmits, converts or records video with synchronized audio, it shall preserve caption data such that it can be displayed in a manner consistent with clauses 7.1.1 and 7.1.2.

None to low Applies to media players; feature should already be in place.

7.2.1 Audio Description Playback. Where ICT displays video with synchronized audio, it shall provide a mechanism to select and play available audio description to the default audio channel.

None to moderate Applies to media players

7.2.2 Audio Description Synchronization. Where ICT has a mechanism to play audio description, it shall preserve the synchronization between the audio/visual content and the corresponding audio description.

None to moderate Applies to media players.

7.2.3 Preservation of Audio Description. Where ICT transmits, converts, or records video with synchronized audio, it shall preserve audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

None to moderate Applies to media players.

7.3 User Controls for Captions and Audio Description. Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

None to moderate Applies to media players.

10.2.39 Caption Positioning. Where ICT is a non-web document that contains synchronized media with captions, the captions should not obscure relevant information in the synchronized media.

None to low Unlikely to affect most non-web documents. If captioning tool supports positioning, this requirement is easily achieved.

10.2.40 Audio Description Timing. Where ICT is a non-web document that contains synchronized media with audio description, the audio description should not interfere with relevant audio information in the synchronized media.

None to low Unlikely to affect most non-web documents. WCAG techniques already address this timing issue.

11.3.2.3 Use of Accessibility Services. Where the software provides a user interface it shall use the applicable documented platform accessibility services. If the documented platform accessibility services do not allow the software to meet the applicable requirements of clauses 11.3.2.5 to 11.3.2.17, then software that provides a user interface shall use other documented services to interoperate with assistive technology.

None to low 508 doesn't specify to use accessibility services. This is an EU requirement, most impactful to native windows software using retro MSAA or other APIs to provide a11y. If the interoperability requirements are met, this checkpoint is satisfied.

11.6.4 Repair Assistance. If the accessibility checking functionality of an authoring tool can detect that content does not meet a requirement of clauses 9 (Web content) or 10 (Documents) as applicable, then the authoring tool shall provide repair suggestion(s).

None to high Where an authoring tool provides the capability to detect accessibility issues in the authored content, the tool must provide repair suggestions. If product does not have the ability to automatically detect issues with authoring tool-generated content, it is Not Applicable.