Adobe Accessibility Conformance Report International Edition

1.1.1 Non-text Content (Level A)
Also applies to:
EN 301 549 Criteria

• 9.1.1.1 (Web)
• 10.1.1.1 (Non-web document)
• 11.1.1.1.1 (Open Functionality Software)
• 11.1.1.1.2 (Closed Functionality Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Software: The product provides sufficient text alternatives for most instances of functional and informative images. Exceptions include:

Informative Images are missing the text alternative in “Prepare for A11y: Properties”, “Protect a PDF: Manage security policies”, “Adobe Sign: Request E-Signatures” screens.

1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria

• 9.1.2.1 (Web)
• 10.1.2.1 (Non-web document)
• 11.1.2.1.1 (Open Functionality Software)
• 11.1.2.1.2.1 and 11.1.2.1.2.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

1.2.2 Captions (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria

• 9.1.2.2 (Web)
• 10.1.2.2 (Non-web document)
• 11.1.2.2 (Open Functionality Software)
• 11.1.2.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria

• 9.1.2.3 (Web)
• 10.1.2.3 (Non-web document)
• 11.1.2.3.1 (Open Functionality Software)
• 11.1.2.3.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

1.2.4 Captions (Live) (Level AA)
Also applies to:
EN 301 549 Criteria

• 9.1.2.4 (Web)
• 10.1.2.4 (Non-web document)
• 11.1.2.4 (Open Functionality Software)
• 11.1.2.4 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

1.2.5 Audio Description (Prerecorded) (Level AA)
Also applies to:
EN 301 549 Criteria

• 9.1.2.5 (Web)
• 10.1.2.5 (Non-web document)
• 11.1.2.5 (Open Functionality Software)
• 11.1.2.5 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

1.3.1 Info and Relationships (Level A)
Also applies to:
EN 301 549 Criteria

• 9.1.3.1 (Web)
• 10.1.3.1 (Non-web document)
• 11.1.3.1.1 (Open Functionality Software)
• 11.1.3.1.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Software: Most visual structure and relationship information is provided through element semantics or object information or are available in text. Exceptions include:

The content visually appears to be a data table but is not marked up as a table in “Prepare Form: General Properties”, “Protect a PDF: Create a Security Envelope”, “Protect a PDF: Encrypt with certificate - Select Recipients”, “Protect a PDF: Set security properties”, “View PDF: Attachments” screens.

The checkboxes group label is not associated with the checkboxes in “Prepare Form: General Properties”, “Protect a PDF: Set security properties”, “Prepare Form: Text field properties” screens.

Group of form controls are not associated with its group label in “Compress a PDF: Advanced Optimization”, “Compress a PDF: Optimize Scanned Pages”, “Edit: Links”, “Prepare Form: button properties”, “Prepare Form: date field properties”, “Prepare Form: Drop-down list properties”, “Prepare Form: E-signature field properties”, “Prepare Form: General”, “Prepare Form: General Properties”, “Prepare Form: list box properties”, “Prepare Form: Radio button properties”, “Protect a PDF: Create a Security Envelope”, “Protect a PDF: Encrypt with a password”, “Protect a PDF: Set security properties”, “Prepare Form: Barcode properties”, “Prepare Form: Checkbox properties”, “Prepare Form: Image field properties”, “Prepare Form: Text field properties”, “Redact a PDF: Set Properties” screens.

The radio buttons group label is not associated with the radio buttons in “Compress a PDF: Reduce File Size”, “Edit: Links”, “Export PDF”, “Protect a PDF: Create a Security Envelope”, “Protect a PDF: Protect with a Password & Remove Security”, “Redact a PDF: Find Text and Redact”, “Redact a PDF: Set Properties” screens.

1.3.2 Meaningful Sequence (Level A)
Also applies to:
EN 301 549 Criteria

• 9.1.3.2 (Web)
• 10.1.3.2 (Non-web document)
• 11.1.3.2.1 (Open Functionality Software)
• 11.1.3.2.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Software: The product does not present most content in a meaningful sequence. Examples include:

Hidden content is readable with a screen reader in “Redact a PDF: Sanitize Document” screen.

Informative static content is not readable by a screen reader in “Add a Stamp”, “Comment on PDF”, “Compress a PDF: Advanced Optimization”, “Compress a PDF: Optimize Scanned Pages”, “Compress a PDF: Reduce File Size”, “Create PDF”, “Edit PDF”, “Edit: Links”, “Enhance Scan”, “Prepare for A11y: Auto tag”, “Prepare for A11y: Properties”, “Prepare Form: button properties”, “Prepare Form: Drop-down list properties”, “Prepare Form: E-signature field properties”, “Prepare Form: General”, “Prepare Form: General Properties”, “Prepare Form: list box properties”, “Prepare Form: Radio button properties”, “Protect a PDF: Create a Security Envelope”, “Protect a PDF: Encrypt with a password”, “Protect a PDF: Encrypt with certificate - Certificate Details”, “Protect a PDF: Encrypt with certificate - General”, “Protect a PDF: Encrypt with certificate - Select Recipients”, “Protect a PDF: Encrypt with certificate - Summary”, “Protect a PDF: Manage security policies”, “Protect a PDF: Protect with a Password & Remove Security”, “Protect a PDF: Remove hidden information”, “Protect a PDF: Set security properties”, “Send for Comment”, “Share”, “Use a Certificate: Digitally Sign”, “Adobe Sign: Add”, “Adobe Sign: Prepare”, “Adobe Sign: Request e-Signatures”, “Combine Files & Organize”, “Edit: Organize PDF”, “Fill and Sign”, “Prepare Form: Barcode properties”, “Prepare Form: Checkbox properties”, “Prepare Form: date field properties”, “Prepare Form: Image field properties”, “Prepare Form: Text field properties”, “Quick Tools in Document”, “Redact a PDF: Sanitize Document”, “Use a Certificate: Certify (invisible signature)”, “Use a Certificate: Certify (visible signatures)” screens.

1.3.3 Sensory Characteristics (Level A)
Also applies to:
EN 301 549 Criteria

• 9.1.3.3 (Web)
• 10.1.3.3 (Non-web document)
• 11.1.3.3 (Open Functionality Software)
• 11.1.3.3 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

1.3.4 Orientation (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

• 9.1.3.4 (Web)
• 10.1.3.4 (Non-web document)
• 11.1.3.4 (Open Functionality Software)
• 11.1.3.4 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

1.3.5 Identify Input Purpose (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

• 9.1.3.5 (Web)
• 10.1.3.5 (Non-web document)
• 11.1.3.5.1 (Open Functionality Software)
• 11.1.3.5.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

1.4.1 Use of Color (Level A)
Also applies to:
EN 301 549 Criteria

• 9.1.4.1 (Web)
• 10.1.4.1 (Non-web document)
• 11.1.4.1 (Open Functionality Software)
• 11.1.4.1 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Software: Most functions of the product do not convey information through color alone. Exceptions include:

Color alone is used to convey information in “Edit: Links”, “Prepare Form: button properties”, “Prepare Form: date field properties”, “Prepare Form: Drop-down list properties”, “Prepare Form: E-signature field properties”, “Prepare Form: list box properties”, “Prepare Form: Radio button properties” screens.

1.4.2 Audio Control (Level A)
Also applies to:
EN 301 549 Criteria

• 9.1.4.2 (Web)
• 10.1.4.2 (Non-web document)
• 11.1.4.2 (Open Functionality Software)
• 11.1.4.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

1.4.3 Contrast (Minimum) (Level AA)
Also applies to:
EN 301 549 Criteria

• 9.1.4.3 (Web)
• 10.1.4.3 (Non-web document)
• 11.1.4.3 (Open Functionality Software)
• 11.1.4.3 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Software: Most text meet minimum contrast requirements. Exceptions include:

Placeholder text lacks 4.5:1 contrast ratio in “Comment on PDF”, “Send for Comment”, “Use a Certificate: Certify (visible signatures)”, “Adobe Sign: Add”, “Adobe Sign: Request e-Signatures” screens.

Text content lacks 4.5:1 contrast ratio in “Comment on PDF”, “Create PDF”, “Protect a PDF: Protect with a Password & Remove Security”, “Send for Comment”, “Adobe Sign: Add”, “Adobe Sign: Request e-Signatures”, “Prepare Form: Text field properties” screens.

Most of the screens interactive controls text lack 4.5:1 contrast ratio on focus in the application.

1.4.4 Resize text (Level AA)
Also applies to:
EN 301 549 Criteria

• 9.1.4.4 (Web)
• 10.1.4.4 (Non-web document)
• 11.1.4.4.1 (Open Functionality Software)
• 11.1.4.4.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Software: Most text can be resized using zoom, but content and functionality is lost in some product functions. Exceptions include:

Functionality is lost at 200% zoom in “Adobe Sign: Prepare”, “Compress a PDF: Reduce File Size”, “Redact a PDF: Find Text and Redact”, “Send for Comment”, “View PDF: Navigate & View” screens.

1.4.5 Images of Text (Level AA)
Also applies to:
EN 301 549 Criteria

• 9.1.4.5 (Web)
• 10.1.4.5 (Non-web document)
• 11.1.4.5.1 (Open Functionality Software)
• 11.1.4.5.2 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

1.4.10 Reflow (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

• 9.1.4.10 (Web)
• 10.1.4.10 (Non-web document)
• 11.1.4.10.1 (Open Functionality Software)
• 11.1.4.10.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

1.4.11 Non-text Contrast (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

• 9.1.4.11 (Web)
• 10.1.4.11 (Non-web document)
• 11.1.4.11 (Open Functionality Software)
• 11.1.4.11 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Software: Most meaningful non-text content elements have sufficient contrast requirements. Exceptions include:

Active user interface component lacks 3 to 1 contrast ratio in “Protect a PDF: Protect with a Password & Remove Security”, “Send for Comment”, “Share”, “Use a Certificate: Certify (visible signatures)”, “Adobe Sign: Prepare”, “Adobe Sign: Request e-Signatures”, “Comment on PDF”, “Compress a PDF: Optimize Scanned Pages”, “Edit: Links”, “Prepare Form: button properties”, “Prepare Form: Drop-down list properties”, “Prepare Form: E-signature field properties”, “Prepare Form: list box properties”, “Prepare Form: Radio button properties”, “Thumbnails”, “Adobe Sign: Add” screens.

An icon lacks 3 to 1 contrast ratio in “Adobe Sign: Add”, “Adobe Sign: Prepare”, “Adobe Sign: Send”, “Comment on PDF”, “Protect a PDF: Create a Security Envelope”, “Protect a PDF: Encrypt with certificate - General”, “Protect a PDF: Manage security policies” screens.

State of active component lacks 3 to 1 contrast ratio in “Prepare Form: Checkbox properties”, “Prepare Form: Image field properties”, “Add a Stamp”, “Comment on PDF”, “Create PDF”, “Enhance Scan”, “Prepare for A11y: Accessibility Tags”, “Prepare for A11y: Auto tag”, “Prepare Form: button properties”, “Prepare Form: date field properties”, “Prepare Form: Drop-down list properties”, “Prepare Form: E-signature field properties”, “Prepare Form: list box properties”, “Prepare Form: Radio button properties”, “Protect a PDF: Remove hidden information”, “View PDF: Attachments”, “View PDF: Bookmarks”, “Adobe Sign: Prepare”, “Compress a PDF: Reduce File Size”, “Fill and Sign”, “Prepare Form: Barcode properties”, “Prepare Form: General”, “Prepare Form: General Properties”, “Prepare Form: Text field properties”, “Protect a PDF: Create a Security Envelope”, “Protect a PDF: Encrypt with certificate - Certificate Details”, “Protect a PDF: Encrypt with certificate - Select Recipients”, “Protect a PDF: Manage security policies”, “Protect a PDF: Set security properties”, “Redact a PDF: Set Properties”, “Send for Comment”, “Share”, “Thumbnails” screens.

Focus indicator lacks 3 to 1 contrast ratio in “Adobe Sign: Request E-Signatures”, “Combine Files & Organize” screens.

1.4.12 Text Spacing (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

• 9.1.4.12 (Web)
• 10.1.4.12 (Non-web document)
• 11.1.4.12 (Open Functionality Software)
• 11.1.4.12 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

1.4.13 Content on Hover or Focus (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

• 9.1.4.13 (Web)
• 10.1.4.13 (Non-web document)
• 11.1.4.13 (Open Functionality Software)
• 11.1.4.13 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Software: Most of the product’s functionality, the additional content that is displayed on hover or focus is dismissible, hoverable or persistent. Exceptions include:

Additional content not dismissible in “Prepare Form: General”, “Redact a PDF: Sanitize Document”, “Redact a PDF: Text. Images, PDF”, “View PDF: Navigate & View” screens.

Hover content disappearing in “Adobe Sign: Prepare”, “Prepare Form: General”, “Redact a PDF: Text. Images, PDF”, “View PDF: Navigate & View” screens.

2.1.1 Keyboard (Level A)
Also applies to:
EN 301 549 Criteria

• 9.2.1.1 (Web)
• 10.2.1.1 (Non-web document)
• 11.2.1.1.1 (Open Functionality Software)
• 11.2.1.1.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Software: Most product functionality can be operated through a keyboard interface. Exceptions include:

Action cannot be performed with a screen reader turned on in “Thumbnails” screen.

Device-dependent event handlers are used in “Comment on PDF”, “Quick Tools in Document”, “Thumbnails” screens.

Drag and drop feature is not keyboard accessible in “Adobe Sign: Prepare”, “Edit: Organize PDF” screens.

Function cannot be performed by keyboard alone in “Adobe Sign: Request e-Signatures”, “Comment on PDF”, “Edit: Links”, “Prepare for A11y: Auto tag”, “Prepare for A11y: Properties”, “Prepare Form: Barcode properties”, “Prepare Form: Component Menu”, “Prepare Form: General Properties”, “Protect a PDF: Create a Security Envelope”, “Protect a PDF: Encrypt with certificate - Select Recipients”, “Protect a PDF: Manage security policies”, “Protect a PDF: Set security properties”, “Use a Certificate: Certify (invisible signature)”, “Use a Certificate: Certify (visible signatures)”, “Use a Certificate: Digitally Sign”, “View PDF: Attachments”, “View PDF: Bookmarks” screens

2.1.2 No Keyboard Trap (Level A)
Also applies to:
EN 301 549 Criteria

• 9.2.1.2 (Web)
• 10.2.1.2 (Non-web document)
• 11.2.1.2 (Open Functionality Software)
• 11.2.1.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

2.1.4 Character Key Shortcuts (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria

• 9.2.1.4 (Web)
• 10.2.1.4 (Non-web document)
• 11.2.1.4.1 (Open Functionality Software)
• 11.2.1.4.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

2.2.1 Timing Adjustable (Level A)
Also applies to:
EN 301 549 Criteria

• 9.2.2.1 (Web)
• 10.2.2.1 (Non-web document)
• 11.2.2.1 (Open Functionality Software)
• 11.2.2.1 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

2.2.2 Pause, Stop, Hide (Level A)
Also applies to:
EN 301 549 Criteria

• 9.2.2.2 (Web)
• 10.2.2.2 (Non-web document)
• 11.2.2.2 (Open Functionality Software)
• 11.2.2.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

2.3.1 Three Flashes or Below Threshold (Level A)
Also applies to:
EN 301 549 Criteria

• 9.2.3.1 (Web)
• 10.2.3.1 (Non-web document)
• 11.2.3.1 (Open Functionality Software)
• 11.2.3.1(Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

2.4.1 Bypass Blocks (Level A)
Also applies to:
EN 301 549 Criteria

• 9.2.4.1 (Web)
• 10.2.4.1 (Non-web document) – Does not apply
• 11.2.4.1 (Open Functionality Software) – Does not apply
• 11.2.4.1 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software) – Does not apply to non-web software
• 504.2 (Authoring Tool)
• 602.3 (Support Docs) – Does not apply to non-web docs

2.4.2 Page Titled (Level A)
Also applies to:
EN 301 549 Criteria

• 9.2.4.2 (Web)
• 10.2.4.2 (Non-web document)
• 11.2.4.2 (Open Functionality Software) - Does not apply
• 11.2.4.2 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

2.4.3 Focus Order (Level A)
Also applies to:
EN 301 549 Criteria

• 9.2.4.3 (Web)
• 10.2.4.3 (Non-web document)
• 11.2.4.3 (Open Functionality Software)
• 11.2.4.3 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Software: Most components receive focus in a meaningful order. Exceptions include:

Hidden or empty element receives focus in “Adobe Sign: Add”, “Adobe Sign: Request e-Signatures” screens.

Keyboard focus is lost or misplaced due to user interaction or content update in “Prepare Form: Drop-down list properties”, “View PDF: Navigate & View” screens.

Modal is closed, focus is not returned to trigger in “Adobe Sign: Send” screen.

2.4.4 Link Purpose (In Context) (Level A)
Also applies to:
EN 301 549 Criteria

• 9.2.4.4 (Web)
• 10.2.4.4 (Non-web document)
• 11.2.4.4 (Open Functionality Software)
• 11.2.4.4 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Software: The purpose of links in the product can be determined from the link text alone or from the programmatic context of the link. Exceptions include:

Purpose of link is not clear in context in “Edit PDF”, “Send for Comment”, “Share” screens.

2.4.5 Multiple Ways (Level AA)
Also applies to:
EN 301 549 Criteria

• 9.2.4.5 (Web)
• 10.2.4.5 (Non-web document) – Does not apply
• 11.2.4.5 (Open Functionality Software) – Does not apply
• 11.2.4.5 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software) – Does not apply to non-web software
• 504.2 (Authoring Tool)
• 602.3 (Support Docs) – Does not apply to non-web docs

2.4.6 Headings and Labels (Level AA)
Also applies to:
EN 301 549 Criteria

• 9.2.4.6 (Web)
• 10.2.4.6 (Non-web document)
• 11.2.4.6 (Open Functionality Software)
• 11.2.4.6 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Software: Most of the Headings and labels are descriptive. Exceptions include:

Buttons have same name but different actions in “Compress a PDF: Optimize Scanned Pages” screen.

Programmatic label does not convey purpose of control in “Prepare Form: date field properties”, “Add a Stamp”, “Adobe Sign: Prepare”, “Compress a PDF: Advanced Optimization”, “Compress a PDF: Optimize Scanned Pages”, “Edit PDF”, “Edit: Links”, “Export PDF”, “Prepare Form: Barcode properties”, “Prepare Form: button properties”, “Prepare Form: Checkbox properties”, “Prepare Form: Drop-down list properties”, “Prepare Form: E-signature field properties”, “Prepare Form: Image field properties”, “Prepare Form: list box properties”, “Prepare Form: Radio button properties”, “Prepare Form: Text field properties”, “Protect a PDF: Remove hidden information”, “Redact a PDF: Set Properties”, “Redact a PDF: Text. Images, PDF”, “View PDF: Attachments”, “View PDF: Navigate & View” screens.

2.4.7 Focus Visible (Level AA)
Also applies to:
EN 301 549 Criteria

• 9.2.4.7 (Web)
• 10.2.4.7 (Non-web document)
• 11.2.4.7 (Open Functionality Software)
• 11.2.4.7 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Software: Most focusable elements have a visible keyboard focus indicator. Exceptions include:

The visual focus indicator is missing in “Protect a PDF: Remove hidden information”, “View PDF: Bookmarks”, “Adobe Sign: Prepare” screens.

2.5.1 Pointer Gestures (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria

• 9.2.5.1 (Web)
• 10.2.5.1 (Non-web document)
• 11.2.5.1 (Open Functionality Software)
• 11.2.5.1 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

2.5.2 Pointer Cancellation (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria

• 9.2.5.2 (Web)
• 10.2.5.2 (Non-web document)
• 11.2.5.2 (Open Functionality Software)
• 11.2.5.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

2.5.3 Label in Name (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria

• 9.2.5.3 (Web)
• 10.2.5.3 (Non-web document)
• 11.2.5.3.1 (Open Functionality Software)
• 11.2.5.3.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Software: In most product functions, accessible names of controls contain the text of their visible labels. Exceptions include:

Accessible name missing in “Prepare Form: Text field properties”, “Prepare Form: General Properties”, “Prepare Form: date field properties”, “Prepare Form: Drop-down list properties”, “View PDF: Bookmarks”, “Edit: Links”, “Redact a PDF: Set Properties”, “Protect a PDF: Set security properties”, “Prepare Form: Image field properties”, “Prepare Form: Checkbox properties”, “Edit: Organize PDF”, “Prepare Form: Barcode properties”, “Redact a PDF: Find Text and Redact” screens.

Accessible name has interspersed words in “Add a Stamp”, “Prepare for A11y: Prepare” screens.

Accessible name does not contain visible label in “Adobe Sign: Add”, “Prepare Form: button properties”, “Prepare Form: date field properties”, “Prepare Form: Drop-down list properties”, “Prepare Form: E-signature field properties”, “Prepare Form: Radio button properties”, “Prepare Form: Image field properties”, “Prepare Form: Checkbox properties”, “Prepare Form: Barcode properties”, “Prepare Form: list box properties” screens.

2.5.4 Motion Actuation (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria

• 9.2.5.4 (Web)
• 10.2.5.4 (Non-web document)
• 11.2.5.4 (Open Functionality Software)
• 11.2.5.4 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

3.1.1 Language of Page (Level A)
Also applies to:
EN 301 549 Criteria

• 9.3.1.1 (Web)
• 10.3.1.1 (Non-web document)
• 11.3.1.1.1 (Open Functionality Software)
• 11.3.1.1.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

3.1.2 Language of Parts (Level AA)
Also applies to:
EN 301 549 Criteria

• 9.3.1.2 (Web)
• 10.3.1.2 (Non-web document)
• 11.3.1.2 (Open Functionality Software) – Does not apply
• 11.3.1.2 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

3.2.1 On Focus (Level A)
Also applies to:
EN 301 549 Criteria

• 9.3.2.1 (Web)
• 10.3.2.1 (Non-web document)
• 11.3.2.1 (Open Functionality Software)
• 11.3.2.1 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

3.2.2 On Input (Level A)
Also applies to:
EN 301 549 Criteria

• 9.3.2.2 (Web)
• 10.3.2.2 (Non-web document)
• 11.3.2.2 (Open Functionality Software)
• 11.3.2.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Software: Changes of context do not occur automatically on user input.
Exceptions include:

Form field causes unexpected change in “Send for Comment”, “Share” screens.

3.2.3 Consistent Navigation (Level AA)
Also applies to:
EN 301 549 Criteria

• 9.3.2.3 (Web)
• 10.3.2.3 (Non-web document) – Does not apply
• 11.3.2.3 (Open Functionality Software) – Does not apply
• 11.3.2.3 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software) – Does not apply to non-web software
• 504.2 (Authoring Tool)
• 602.3 (Support Docs) – Does not apply to non-web docs

3.2.4 Consistent Identification (Level AA)
Also applies to:
EN 301 549 Criteria

• 9.3.2.4 (Web)
• 10.3.2.4 (Non-web document) – Does not apply
• 11.3.2.4 (Open Functionality Software) – Does not apply
• 11.3.2.4 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software) – Does not apply to non-web software
• 504.2 (Authoring Tool)
• 602.3 (Support Docs) – Does not apply to non-web docs

3.3.1 Error Identification (Level A)
Also applies to:
EN 301 549 Criteria

• 9.3.3.1 (Web)
• 10.3.3.1 (Non-web document)
• 11.3.3.1.1 (Open Functionality Software)
• 11.3.3.1.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

3.3.2 Labels or Instructions (Level A)
Also applies to:
EN 301 549 Criteria

• 9.3.3.2 (Web)
• 10.3.3.2 (Non-web document)
• 11.3.3.2 (Open Functionality Software)
• 11.3.3.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Software: Labels are provided for most input fields.

Exceptions include:

Label is not persistent in “Comment on PDF”, “Use a Certificate: Certify (visible signatures)”, “Adobe Sign: Add” screens.

Visible label missing in “Prepare Form: date field properties”, “Adobe Sign: Add”, “Protect a PDF: Create a Security Envelope”, “Redact a PDF: Find Text and Redact”, “View PDF: Navigate & View” screens.

3.3.3 Error Suggestion (Level AA)
Also applies to:
EN 301 549 Criteria

• 9.3.3.3 (Web)
• 10.3.3.3 (Non-web document)
• 11.3.3.3 (Open Functionality Software)
• 11.3.3.3 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Also applies to:
EN 301 549 Criteria

• 9.3.3.4 (Web)
• 10.3.3.4 (Non-web document)
• 11.3.3.4 (Open Functionality Software)
• 11.3.3.4 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

4.1.1 Parsing (Level A)
Also applies to:
EN 301 549 Criteria

• 9.4.1.1 (Web)
• 10.4.1.1 (Non-web document)
• 11.4.1.1.1 (Open Functionality Software)
• 11.4.1.1.2 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

4.1.2 Name, Role, Value (Level A)
Also applies to:
EN 301 549 Criteria

• 9.4.1.2 (Web)
• 10.4.1.2 (Non-web document)
• 11.4.1.2.1 (Open Functionality Software)
• 11.4.1.2.2 (Closed Software) – Not required
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Software: User interface components at most of the places do not provide programmatic name, role, state, or value information. Examples include:

Custom user interface component is not compatible with AT in “Fill and Sign” screen.

Button does not have an accessible name in “Edit: Links”, “Prepare Form: General”, “Redact a PDF: Set Properties” screens.

Button does not have a role in “Add a Stamp”, “Edit PDF”, “Edit: Links”, “Export PDF”, “Prepare for A11y: Prepare”, “Prepare Form: button properties”, “Prepare Form: Component Menu”, “Prepare Form: Drop-down list properties”, “Prepare Form: E-signature field properties”, “Prepare Form: General”, “Prepare Form: General Properties”, “Prepare Form: list box properties”, “Prepare Form: Radio button properties”, “Protect a PDF: Create a Security Envelope”, “Protect a PDF: Encrypt with certificate - Select Recipients”, “Protect a PDF: Manage security policies”, “Protect a PDF: Protect with a Password & Remove Security”, “Protect a PDF: Remove hidden information”, “Protect a PDF: Set security properties”, “Send for Comment”, “Share”, “View PDF: Attachments”, “Adobe Sign: Add”, “Adobe Sign: Prepare”, “Adobe Sign: Request e-Signatures”, “Adobe Sign: Send”, “Edit: Organize PDF”, “Fill and Sign”, “Redact a PDF: Sanitize Document”, “Redact a PDF: Text. Images, PDF”, “Use a Certificate: Certify (invisible signature)”, “Use a Certificate: Certify (visible signatures)” screens.

Button is missing both role and an accessible name in “View PDF: Bookmarks”, “Adobe Sign: Add”, “Adobe Sign: Request e-Signatures”, “Edit: Organize PDF”, “Redact a PDF: Sanitize Document”, “Thumbnails” screens.

Button pressed state is not conveyed in “Send for Comment”, “Share” screens.

Custom checkbox does not have a role and/or state in “Edit PDF”, “Adobe Sign: Prepare”, “Edit: Organize PDF” screens.

Combo box is missing appropriate roles and/or attributes in “Adobe Sign: Add”, “Adobe Sign: Request e-Signatures”, “Edit: Organize PDF”, “Use a Certificate: Certify (invisible signature)”, “Use a Certificate: Certify (visible signatures)” screens.

Dialog is missing appropriate role and/or attributes in “Adobe Sign: Request e-Signatures”, “Compress a PDF: Reduce File Size”, “Prepare for A11y: Auto tag”, “Protect a PDF: Protect with a Password & Remove Security”, “Redact a PDF: Sanitize Document”, “Use a Certificate: Certify (visible signatures)”, “Use a Certificate: Certify (invisible signature)” screens.

Form field is missing an accessible name in “Redact a PDF: Set Properties”, “Adobe Sign: Add”, “Edit: Links”, “Edit: Organize PDF”, “Prepare Form: Barcode properties”, “Prepare Form: button properties”, “Prepare Form: Checkbox properties”, “Prepare Form: date field properties”, “Prepare Form: Drop-down list properties”, “Prepare Form: E-signature field properties”, “Prepare Form: General Properties”, “Prepare Form: Image field properties”, “Prepare Form: list box properties”, “Prepare Form: Radio button properties”, “Prepare Form: Text field properties”, “Protect a PDF: Set security properties”, “Redact a PDF: Find Text and Redact”, “View PDF: Bookmarks” screens.

Link does not have a role in “Adobe Sign: Request E-Signatures”, “Export PDF”, “Fill and Sign” screens.

Link does not have discernable link text in “Prepare for A11y: Properties” screen.

List box is missing appropriate roles and/or attributes in “Protect a PDF: Protect with a Password & Remove Security”, “Prepare Form: button properties”, “Prepare Form: date field properties”, “Prepare Form: Drop-down list properties” screens.

Custom radio button does not have a role and/or state in “Export PDF”, “Protect a PDF: Protect with a Password & Remove Security” screens.

The element's role is incorrect in “Quick Tools in Document” screen.

Expand/collapse state of the element is missing or incorrect in “Prepare Form: date field properties”, “Add a Stamp”, “Adobe Sign: Add”, “Combine Files & Organize”, “Comment on PDF”, “Compress a PDF: Reduce File Size”, “Create PDF”, “Edit PDF”, “Edit: Links”, “Edit: Organize PDF”, “Enhance Scan”, “Prepare for A11y: Auto tag”, “Prepare Form: button properties”, “Prepare Form: Checkbox properties”, “Prepare Form: Drop-down list properties”, “Prepare Form: E-signature field properties”, “Prepare Form: General”, “Prepare Form: Image field properties”, “Prepare Form: list box properties”, “Prepare Form: Radio button properties”, “Protect a PDF: Protect with a Password & Remove Security”, “Protect a PDF: Remove hidden information”, “Quick Tools in Document”, “Redact a PDF: Sanitize Document”, “Redact a PDF: Set Properties”, “Thumbnails”, “Use a Certificate: Certify (invisible signature)”, “Use a Certificate: Certify (visible signatures)”, “View PDF: Attachments”, “View PDF: Bookmarks”, “View PDF: Navigate & View” screens.

Selected state of the element is missing or incorrect “Create PDF”, “Export PDF”, “Fill and Sign”, “Prepare Form: Component Menu”, “Protect a PDF: Create a Security Envelope”, “Protect a PDF: Encrypt with certificate - Certificate Details”, “Protect a PDF: Encrypt with certificate - General”, “Quick Tools in Document”, “Redact a PDF: Text. Images, PDF” screens.

Table sort state is missing or incorrect in “Prepare Form: General Properties”, “Protect a PDF: Create a Security Envelope”, “Protect a PDF: Encrypt with certificate - Select Recipients”, “Protect a PDF: Manage security policies”, “Protect a PDF: Set security properties”, “View PDF: Attachments” screens.

The element has missing or incorrect states or properties in “Protect a PDF: Protect with a Password & Remove Security”, “Adobe Sign: Add”, “Adobe Sign: Prepare”, “Adobe Sign: Request e-Signatures”, “Edit: Organize PDF”, “Redact a PDF: Find Text and Redact”, “Redact a PDF: Set Properties”, “View PDF: Navigate & View” screens.

The element has incorrect state in “Use a Certificate: Certify (visible signatures)” screen.

Tree view: File system navigator missing appropriate roles and/or attributes in “Prepare for A11y: Accessibility Tags”, “Protect a PDF: Remove hidden information”, “View PDF: Bookmarks” screens.

4.1.3 Status Messages (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

• 9.4.1.3 (Web)
• 10.4.1.3 (Non-web document)
• 11.4.1.3 (Open Functionality Software)
• 11.4.1.3 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Software: When status messages do not receive focus, the product does not provide the dynamic and automatic update to the assistive technology. Exceptions include:

Status message is not automatically announced in “Adobe Sign: Add”, “Adobe Sign: Prepare”, “Adobe Sign: Request e-Signatures”, “Prepare for A11y: Auto tag”, “Protect a PDF: Encrypt with a password”, “Protect a PDF: Encrypt with certificate - General”, “Protect a PDF: Protect with a Password & Remove Security”, “Protect a PDF: Remove hidden information”, “Send for Comment”, “Share” screens.

Software: Most functions of the product are usable without vision. Exceptions include:

As noted in 1.1.1 Non-text Content, informative Images are missing the text alternative.

As noted in 1.3.1 Info and Relationships, the content visually appears to be a data table but is not marked up as a table, the checkboxes group label is not associated with the checkboxes, group of form controls are not associated with its group label, the radio buttons group label is not associated with the radio buttons.

As noted in 1.3.2 Meaningful sequence, hidden content is readable with a screen reader, informative static content is not readable by a screen reader.

As noted in 1.4.1 Use of Color, color alone is used to convey information.

As noted in 2.1.1 Keyboard, action cannot be performed with a screen reader turned on, device-dependent event handlers are used, drag and drop feature is not keyboard accessible, function cannot be performed by keyboard alone.

As noted in 2.4.3 Focus Order, hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, modal is closed, focus is not returned to trigger.

As noted in 2.4.4 Link Purpose, Purpose of link is not clear in context.

As noted in 2.4.6 Headings and labels, buttons have same name but different actions, Programmatic label does not convey purpose of control.

As noted in 3.2.2 On Input, form field causes unexpected change.

As noted in 3.3.2 Labels or Instructions, visible label missing, Label is not persistent.

As noted in 4.1.2 Name, Role, Value, custom user interface component is not compatible with AT, button does not have an accessible name, button does not have a role, button is missing both role and an accessible name, button pressed state is not conveyed, custom checkbox does not have a role and/or state, combo box is missing appropriate roles and/or attributes, dialog is missing appropriate role and/or attributes, form field is missing an accessible name, link does not have a role, link does not have discernable link text, list box is missing appropriate roles and/or attributes, custom radio button does not have a role and/or state, the element's role is incorrect, expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, table sort state is missing or incorrect, the element has missing or incorrect states or properties, the element has incorrect state, tree view: File system navigator missing appropriate roles and/or attributes.

Software: Most functions of the product are usable with limited vision. Exceptions include:

As noted in 1.1.1 Non-text Content, informative Images are missing the text alternative.

As noted in 1.3.1 Info and Relationships, the content visually appears to be a data table but is not marked up as a table, the checkboxes group label is not associated with the checkboxes, group of form controls are not associated with its group label, the radio buttons group label is not associated with the radio buttons.

As noted in 1.3.2 Meaningful sequence, hidden content is readable with a screen reader, informative static content is not readable by a screen reader.

As noted in 1.4.1 Use of Color, color alone is used to convey information.

As noted in 1.4.3 Contrast (Minimum), Placeholder text lacks 4.5:1 contrast ratio, text content lacks 4.5:1 contrast ratio, interactive controls text lack 4.5:1 contrast ratio on focus.

As noted in 1.4.4 Resize text, functionality is lost at 200% zoom.

As noted in 2.1.1 Keyboard, action cannot be performed with a screen reader turned on, device-dependent event handlers are used, drag and drop feature is not keyboard accessible, function cannot be performed by keyboard alone.

As noted in 2.4.3 Focus Order, hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, modal is closed, focus is not returned to trigger.

As noted in 2.4.4 Link Purpose, Purpose of link is not clear in context.

As noted in 2.4.6 Headings and labels, buttons have same name but different actions, Programmatic label does not convey purpose of control.

As noted in 2.4.7 Focus Visible, the visual focus indicator is missing.

As noted in 3.2.2 On Input, form field causes unexpected change.

As noted in 3.3.2 Labels or Instructions, visible label missing, Label is not persistent.

As noted in 4.1.2 Name, Role, Value, custom user interface component is not compatible with AT, button does not have an accessible name, button does not have a role, button is missing both role and an accessible name, button pressed state is not conveyed, custom checkbox does not have a role and/or state, combo box is missing appropriate roles and/or attributes, dialog is missing appropriate role and/or attributes, form field is missing an accessible name, link does not have a role, link does not have discernable link text, list box is missing appropriate roles and/or attributes, custom radio button does not have a role and/or state, the element's role is incorrect, expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, table sort state is missing or incorrect, the element has missing or incorrect states or properties, the element has incorrect state, tree view: File system navigator missing appropriate roles and/or attributes.

Software: Most functions of the product are usable without perception of color. Exceptions include:

As noted in 1.4.3 Contrast (Minimum), placeholder text lacks 4.5:1 contrast ratio, text content lacks 4.5:1 contrast ratio, interactive controls text lack 4.5:1 contrast ratio on focus.

As noted in 1.4.1 Use of Color, color alone is used to convey information.

Software: Users with limited manipulation who use speech recognition or switch control software will not have difficulty navigating to most of the controls.
Exceptions include:

As noted in 2.1.1 Keyboard, action cannot be performed with a screen reader turned on, device-dependent event handlers are used, drag and drop feature is not keyboard accessible, function cannot be performed by keyboard alone.

As noted in 2.4.3 Focus Order, hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, modal is closed, focus is not returned to trigger.

As noted in 2.4.4 Link Purpose, Purpose of link is not clear in context.

As noted in 2.4.6 Headings and labels, buttons have same name but different actions, Programmatic label does not convey purpose of control.

As noted in 2.4.7 Focus Visible, the visual focus indicator is missing.

As noted in 3.3.2 Labels or Instructions, visible label missing, Label is not persistent.

As noted in 4.1.2 Name, Role, Value, custom user interface component is not compatible with AT, button does not have an accessible name, button does not have a role, button is missing both role and an accessible name, button pressed state is not conveyed, custom checkbox does not have a role and/or state, combo box is missing appropriate roles and/or attributes, dialog is missing appropriate role and/or attributes, form field is missing an accessible name, link does not have a role, link does not have discernable link text, list box is missing appropriate roles and/or attributes, custom radio button does not have a role and/or state, the element's role is incorrect, expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, table sort state is missing or incorrect, the element has missing or incorrect states or properties, the element has incorrect state, tree view: File system navigator missing appropriate roles and/or attributes.

Software: Users with limited reach and strength will not have difficulty navigating to most of the controls.
Exceptions include:

As noted in 2.1.1 Keyboard, action cannot be performed with a screen reader turned on, device-dependent event handlers are used, drag and drop feature is not keyboard accessible, function cannot be performed by keyboard alone.

As noted in 2.4.3 Focus Order, hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, modal is closed, focus is not returned to trigger.

As noted in 2.4.4 Link Purpose, Purpose of link is not clear in context.

As noted in 2.4.6 Headings and labels, buttons have same name but different actions, programmatic label does not convey purpose of control.

As noted in 2.4.7 Focus Visible, the visual focus indicator is missing.

As noted in 3.3.2 Labels or Instructions, visible label missing, Label is not persistent.

As noted in 4.1.2 Name, Role, Value, custom user interface component is not compatible with AT, button does not have an accessible name, button does not have a role, button is missing both role and an accessible name, button pressed state is not conveyed, custom checkbox does not have a role and/or state, combo box is missing appropriate roles and/or attributes, dialog is missing appropriate role and/or attributes, form field is missing an accessible name, link does not have a role, link does not have discernable link text, list box is missing appropriate roles and/or attributes, custom radio button does not have a role and/or state, the element's role is incorrect, expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, table sort state is missing or incorrect, the element has missing or incorrect states or properties, the element has incorrect state, tree view: File system navigator missing appropriate roles and/or attributes.

Software: The product is functional for users with limited language, cognitive, and learning abilities. Users with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology. The product provides labeling for most controls.
Exceptions include:

As noted in 1.3.2 Meaningful sequence, hidden content is readable with a screen reader, informative static content is not readable by a screen reader.

As noted in 2.4.3 Focus Order, hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, modal is closed, focus is not returned to trigger.

As noted in 2.4.4 Link Purpose, Purpose of link is not clear in context.

As noted in 2.4.6 Headings and labels, buttons have same name but different actions, Programmatic label does not convey purpose of control.

As noted in 2.4.7 Focus Visible, the visual focus indicator is missing.

As noted in 3.2.2 On Input, form field causes unexpected change.

As noted in 3.3.2 Labels or Instructions, visible label missing, Label is not persistent.

As noted in 4.1.2 Name, Role, Value, custom user interface component is not compatible with AT, button does not have an accessible name, button does not have a role, button is missing both role and an accessible name, button pressed state is not conveyed, custom checkbox does not have a role and/or state, combo box is missing appropriate roles and/or attributes, dialog is missing appropriate role and/or attributes, form field is missing an accessible name, link does not have a role, link does not have discernable link text, list box is missing appropriate roles and/or attributes, custom radio button does not have a role and/or state, the element's role is incorrect, expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, table sort state is missing or incorrect, the element has missing or incorrect states or properties, the element has incorrect state, tree view: File system navigator missing appropriate roles and/or attributes.

501.1 Scope – Incorporation of WCAG 2.0 AA
The requirements of Chapter 5 shall apply to software where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.

EXCEPTION: Where Web applications do not have access to platform accessibility services and do not include components that have access to platform accessibility services, they shall not be required to conform to 502 or 503 provided that they conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0.

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.

502.2.2 No Disruption of Accessibility Features

Software shall not disrupt platform features that are defined in the platform documentation as accessibility features.

502.3 Accessibility Services

Platform software and software tools that are provided by the platform developer shall provide a documented set of accessibility services that support applications running on the platform to interoperate with assistive technology and shall conform to 502.3. Applications that are also platforms shall expose the underlying platform accessibility services or implement other documented accessibility services.

502.3.1 Object Information

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

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.

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.

502.3.4 Values

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

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.

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.

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.

502.3.8 Text

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

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.

502.3.10 List of Actions

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

502.3.11 Actions on Objects

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

The product allows assistive technology to perform all available actions on objects.

Exceptions are noted in 2.1.1 Keyboard.

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.

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.

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 technology.

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:

A. Section 9.3.3 Enable sequential entry of multiple (chorded) keystrokes;

B. Section 9.3.4 Provide adjustment of delay before key acceptance;

C. Section 9.3.5 Provide adjustment of same-key double-strike acceptance;

D. Section 10.6.7 Allow users to choose visual alternative for audio output;

E. Section 10.6.8 Synchronize audio equivalents for visual events;

F. Section 10.6.9 Provide speech output services; and
Section 10.7.1 Display any captions provided.

503 Applications

503.1 General

Applications shall conform to 503.

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.

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.

503.4 User Controls for Captions and Audio Description

Where ICT displays video with synchronized audio, ICT shall provide user controls for closed captions and audio descriptions conforming to 503.4.

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.

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.

504 Authoring Tools

504.1 General

Where an application is an authoring tool, the application shall conform to 504 to the extent that information required for accessibility is supported by the destination format.

504.2 Content Creation or Editing
(if not authoring tool, enter “not applicable”)

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.

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.

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).

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.

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.

Software: Most functions of the product are usable without vision.

Exceptions include:

As noted in 1.1.1 Non-text Content, informative Images are missing the text alternative.

As noted in 1.3.1 Info and Relationships, the content visually appears to be a data table but is not marked up as a table, the checkboxes group label is not associated with the checkboxes, group of form controls are not associated with its group label, the radio buttons group label is not associated with the radio buttons.

As noted in 1.3.2 Meaningful sequence, hidden content is readable with a screen reader, informative static content is not readable by a screen reader.

As noted in 1.4.1 Use of Color, color alone is used to convey information.

As noted in 1.4.13 Content on Hover or Focus, hover content disappearing, additional content not dismissible.

As noted in 2.1.1 Keyboard, action cannot be performed with a screen reader turned on, device-dependent event handlers are used, drag and drop feature is not keyboard accessible, function cannot be performed by keyboard alone.

As noted in 2.4.3 Focus Order, hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, modal is closed, focus is not returned to trigger.

As noted in 2.4.4 Link Purpose, Purpose of link is not clear in context.

As noted in 2.4.6 Headings and labels, buttons have same name but different actions, programmatic label does not convey purpose of control.

As noted in 3.2.2 On Input, form field causes unexpected change.

As noted in 3.3.2 Labels or Instructions, visible label missing, Label is not persistent.

As noted in 4.1.2 Name, Role, Value, custom user interface component is not compatible with AT, button does not have an accessible name, button does not have a role, button is missing both role and an accessible name, button pressed state is not conveyed, custom checkbox does not have a role and/or state, combo box is missing appropriate roles and/or attributes, dialog is missing appropriate role and/or attributes, form field is missing an accessible name, link does not have a role, link does not have discernable link text, list box is missing appropriate roles and/or attributes, custom radio button does not have a role and/or state, the element's role is incorrect, expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, table sort state is missing or incorrect, the element has missing or incorrect states or properties, the element has incorrect state, tree view: File system navigator missing appropriate roles and/or attributes.

As noted in 4.1.3 Status Messages, status messages are not automatically announced.

Software: Most functions of the product are usable with limited vision. Exceptions include:

Exceptions include:

As noted in 1.1.1 Non-text Content, informative Images are missing the text alternative.

As noted in 1.3.1 Info and Relationships, the content visually appears to be a data table but is not marked up as a table, the checkboxes group label is not associated with the checkboxes, group of form controls are not associated with its group label, the radio buttons group label is not associated with the radio buttons.

As noted in 1.3.2 Meaningful sequence, hidden content is readable with a screen reader, informative static content is not readable by a screen reader.

As noted in 1.4.1 Use of Color, color alone is used to convey information.

As noted in 1.4.3 Contrast (Minimum), Placeholder text lacks 4.5:1 contrast ratio, text content lacks 4.5:1 contrast ratio, interactive controls text lack 4.5:1 contrast ratio on focus.

As noted in 1.4.4 Resize text, functionality is lost at 200% zoom.

As noted in 1.4.11 Non-text Contrast, active user interface component lacks 3 to 1 contrast ratio, an icon lacks 3 to 1 contrast ratio, state of active component lacks 3 to 1 contrast ratio, focus indicator lacks 3 to 1 contrast ratio.

As noted in 1.4.13 Content on Hover or Focus, hover content disappearing, additional content not dismissible.

As noted in 2.1.1 Keyboard, action cannot be performed with a screen reader turned on, device-dependent event handlers are used, drag and drop feature is not keyboard accessible, function cannot be performed by keyboard alone.

As noted in 2.4.3 Focus Order, hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, modal is closed, focus is not returned to trigger.

As noted in 2.4.4 Link Purpose, Purpose of link is not clear in context.

As noted in 2.4.6 Headings and labels, buttons have same name but different actions, programmatic label does not convey purpose of control.

As noted in 2.4.7 Focus Visible, the visual focus indicator is missing.

As noted in 3.2.2 On Input, form field causes unexpected change.

As noted in 3.3.2 Labels or Instructions, visible label missing, Label is not persistent.

As noted in 4.1.2 Name, Role, Value, custom user interface component is not compatible with AT, button does not have an accessible name, button does not have a role, button is missing both role and an accessible name, button pressed state is not conveyed, custom checkbox does not have a role and/or state, combo box is missing appropriate roles and/or attributes, dialog is missing appropriate role and/or attributes, form field is missing an accessible name, link does not have a role, link does not have discernable link text, list box is missing appropriate roles and/or attributes, custom radio button does not have a role and/or state, the element's role is incorrect, expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, table sort state is missing or incorrect, the element has missing or incorrect states or properties, the element has incorrect state, tree view: File system navigator missing appropriate roles and/or attributes

As noted in 4.1.3 Status Messages, status messages are not automatically announced.

Software: Most functions of the product are usable without perception of color.

Exceptions include:

As noted in 1.4.1 Use of Color, color alone is used to convey information.

As noted in 1.4.3 Contrast (Minimum), placeholder text lacks 4.5:1 contrast ratio, text content lacks 4.5:1 contrast ratio, interactive controls text lack 4.5:1 contrast ratio on focus.

As noted in 1.4.11 Non-text Contrast, active user interface component lacks 3 to 1 contrast ratio, an icon lacks 3 to 1 contrast ratio, state of active component lacks 3 to 1 contrast ratio, focus indicator lacks 3 to 1 contrast ratio.

Software: Users with limited manipulation who use speech recognition or switch control software will not have difficulty navigating to most of the controls.

Exceptions include:

As noted in 1.4.13 Content on Hover or Focus, hover content disappearing, additional content not dismissible.

As noted in 2.1.1 Keyboard, action cannot be performed with a screen reader turned on, device-dependent event handlers are used, drag and drop feature is not keyboard accessible, function cannot be performed by keyboard alone.

As noted in 2.4.3 Focus Order, hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, modal is closed, focus is not returned to trigger.

As noted in 2.4.4 Link Purpose, Purpose of link is not clear in context.

As noted in 2.4.6 Headings and labels, buttons have same name but different actions, programmatic label does not convey purpose of control.

As noted in 2.4.7 Focus Visible, the visual focus indicator is missing.

As noted in 2.5.3 Label in Name, accessible name missing, accessible name has interspersed words, accessible name does not contain visible label.

As noted in 3.3.2 Labels or Instructions visible label missing, Label is not persistent.

As noted in 4.1.2 Name, Role, Value, custom user interface component is not compatible with AT, button does not have an accessible name, button does not have a role, button is missing both role and an accessible name, button pressed state is not conveyed, custom checkbox does not have a role and/or state, combo box is missing appropriate roles and/or attributes, dialog is missing appropriate role and/or attributes, form field is missing an accessible name, link does not have a role, link does not have discernable link text, list box is missing appropriate roles and/or attributes, custom radio button does not have a role and/or state, the element's role is incorrect, expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, table sort state is missing or incorrect, the element has missing or incorrect states or properties, the element has incorrect state, tree view: File system navigator missing appropriate roles and/or attributes.

Software: Users with limited reach and strength will not have difficulty navigating to most of the controls.

Exceptions include:

As noted in 1.4.13 Content on Hover or Focus, hover content disappearing, additional content not dismissible.

As noted in 2.1.1 Keyboard, action cannot be performed with a screen reader turned on, device-dependent event handlers are used, drag and drop feature is not keyboard accessible, function cannot be performed by keyboard alone.

As noted in 2.4.3 Focus Order, hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, modal is closed, focus is not returned to trigger.

As noted in 2.4.4 Link Purpose, Purpose of link is not clear in context.

As noted in 2.4.6 Headings and labels, buttons have same name but different actions, programmatic label does not convey purpose of control.

As noted in 2.4.7 Focus Visible, the visual focus indicator is missing.

As noted in 2.5.3 Label in Name, accessible name missing, accessible name has interspersed words, accessible name does not contain visible label.

As noted in 3.3.2 Labels or Instructions, visible label missing, Label is not persistent.

As noted in 4.1.2 Name, Role, Value, custom user interface component is not compatible with AT, button does not have an accessible name, button does not have a role, button is missing both role and an accessible name, button pressed state is not conveyed, custom checkbox does not have a role and/or state, combo box is missing appropriate roles and/or attributes, dialog is missing appropriate role and/or attributes, form field is missing an accessible name, link does not have a role, link does not have discernable link text, list box is missing appropriate roles and/or attributes, custom radio button does not have a role and/or state, the element's role is incorrect, expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, table sort state is missing or incorrect, the element has missing or incorrect states or properties, the element has incorrect state, tree view: File system navigator missing appropriate roles and/or attributes

Software: The product is functional for users with limited language, cognitive, and learning abilities. Users with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology. The product provides labeling for most controls.

Exceptions include:

As noted in 1.3.2 Meaningful sequence, hidden content is readable with a screen reader, informative static content is not readable by a screen reader.

As noted in 2.4.3 Focus Order, hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, modal is closed, focus is not returned to trigger.

As noted in 2.4.4 Link Purpose, Purpose of link is not clear in context.

As noted in 2.4.6 Headings and labels, buttons have same name but different actions, programmatic label does not convey purpose of control.

As noted in 2.4.7 Focus Visible, the visual focus indicator is missing.

As noted in 3.2.2 On Input, form field causes unexpected change.

As noted in 3.3.2 Labels or Instructions, visible label missing, Label is not persistent.

As noted in 4.1.2 Name, Role, Value, custom user interface component is not compatible with AT, button does not have an accessible name, button does not have a role, button is missing both role and an accessible name, button pressed state is not conveyed, custom checkbox does not have a role and/or state, combo box is missing appropriate roles and/or attributes, dialog is missing appropriate role and/or attributes, form field is missing an accessible name, link does not have a role, link does not have discernable link text, list box is missing appropriate roles and/or attributes, custom radio button does not have a role and/or state, the element's role is incorrect, expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, table sort state is missing or incorrect, the element has missing or incorrect states or properties, the element has incorrect state, tree view: File system navigator missing appropriate roles and/or attributes.

As noted in 4.1.3 Status Messages, status messages are not automatically announced.

11.5.1 Closed functionality

Where the closed functionality of software conforms to clause 5.1 (Closed functionality) it shall not be required to conform with clause 11.5.2 to clause 11.5.2.17.

11.5.2.1 Platform accessibility service support for software that provides a user interface

Platform software shall provide a set of documented platform services that enable software that provides a user interface running on the platform software to interoperate with assistive technology.

Platform software should support requirements 11.5.2.5 to 11.5.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.5.2.5 to 11.5.2.17 is not supported within the software environment, these requirements are not applicable. For example, selection attributes from 11.5.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.

11.5.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.5.2.5 to 11.5.2.17, then software that provides a user interface shall use other documented services to interoperate with assistive technology.

Note: The term "documented platform accessibility services" refers to the set of services provided by the platform according to clauses 11.5.2.1 and 11.5.2.2.

It is best practice to develop software using toolkits that automatically implement the underlying platform accessibility services.

11.5.2.4 Assistive technology

Where the ICT is assistive technology it shall use the documented platform accessibility services.

Note 1: The term "documented platform accessibility services" refers to the set of services provided by the platform according to clauses 11.5.2.1 and 11.5.2.2.

Note 2: Assistive technology can also use other documented accessibility services.

11.5.2.5 Object information

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the user interface elements' role, state(s), boundary, name, and description programmatically determinable by assistive technologies.

11.5.2.6 Row, column, and headers

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the row and column of each cell in a data table, including headers of the row and column if present, programmatically determinable by assistive technologies.

11.5.2.7 Values

Where the software provides a user interface, it shall, by using the services as described in clause 11.5.2.3, make the current value of a user interface element and any minimum or maximum values of the range, if the user interface element conveys information about a range of values, programmatically determinable by assistive technologies.

11.5.2.8 Label relationships

Where the software provides a user interface it shall expose the relationship that a user interface element has as a label for another element, or of being labelled by another element, using the services as described in clause 11.5.2.3, so that this information is programmatically determinable by assistive technologies.

11.5.2.9 Parent-child relationships

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the relationship between a user interface element and any parent or children elements programmatically determinable by assistive technologies.

11.5.2.10 Text

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the text contents, text attributes, and the boundary of text rendered to the screen programmatically determinable by assistive technologies.

11.5.2.11 List of available actions

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make a list of available actions that can be executed on a user interface element, programmatically determinable by assistive technologies.

11.5.2.12 Execution of available actions

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow the programmatic execution of the actions exposed according to clause 11.5.2.11 by assistive technologies.

Note 1: In some cases, the security requirements imposed on a software product may forbid external software from interfering with the ICT product. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

Note 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

11.5.2.13 Tracking of focus and selection attributes

Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface elements programmatically determinable by assistive technologies.

11.5.2.14 Modification of focus and selection attributes

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify focus, text insertion point, and selection attributes of user interface elements where the user can modify these items.

Note 1: In some cases, the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

Note 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

11.5.2.15 Change notification

Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, notify assistive technologies about changes in those programmatically determinable attributes of user interface elements that are referenced in requirements 11.5.2.5 to 11.5.2.11 and 11.5.2.13.

11.5.2.16 Modifications of states and properties

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify states and properties of user interface elements, where the user can modify these items.

Note 1: In some cases, the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

Note 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

11.5.2.17 Modifications of values and text

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.

Note 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

Note 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

11.6.1 User control of accessibility features

Where software is a platform, it shall provide sufficient modes of operation for user control over those platform accessibility features documented as intended for users.

11.6.2 No disruption of accessibility features

Where software provides a user interface it shall not disrupt those documented accessibility features that are defined in platform documentation except when requested to do so by the user during the operation of the software.

11.7 User preferences

Where software provides a user interface it shall provide sufficient modes of operation that use user preferences for platform settings for color, contrast, font type, font size, and focus cursor except for software that is designed to be isolated from its underlying platforms.

11.8.2 Accessible content creation

(if not authoring tool, enter “not applicable”)

Authoring tools shall enable and guide the production of content that conforms to clauses 9 (Web content) or 10 (Non-Web content) as applicable.

Note: Authoring tools may rely on additional tools where conformance with specific requirements is not achievable by a single tool. For example, a video editing tool may enable the creation of video files for distribution via broadcast television and the web, but authoring of caption files for multiple formats may be provided by a different tool.

11.8.3 Preservation of accessibility information in transformations

If the authoring tool provides restructuring transformations or re-coding transformations, then accessibility information shall be preserved in the output if equivalent mechanisms exist in the content technology of the output.

Note 1: Restructuring transformations are transformations in which the content technology stays the same, but the structural features of the content are changed (e.g. linearizing tables, splitting a document into pages).

Note 2: Re-coding transformations are transformations in which the technology used to encode the content is changed.

11.8.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) or 10 (Non-web documents) as applicable, then the authoring tool shall provide repair suggestion(s).

11.8.5 Templates

When an authoring tool provides templates, at least one template that supports the creation of content that conforms to the requirements of clauses 9 (Web) or 10 (Non-web documents) as applicable shall be available and identified as such.