the intelligent content company

Voluntary Product Accessibility Template (VPAT)

Version 2.5

Name of Product: Intelligent Content Tools

Effective Date: January 2024

Product Description: Intelligent Content Software is the single software solution for document creation, formatting, compliance, automation, XML, and more. icTools is our flagship product with Microsoft Word and Office 365.

Table 1: Success Criteria, Level A

Criteria Conformance Level Remarks and Explanations
1.1.1 Non-text Content (Level A) All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below.
  • Controls, Input: If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Guideline 4.1 for additional requirements for controls and content that accepts user input.)
  • Time-Based Media: If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to Guideline 1.2 for additional requirements for media.)
  • Test: If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content.
  • Sensory: If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content.
  • CAPTCHA: If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities.
  • Decoration, Formatting, Invisible: If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology.
Supported Alternative text description has been provided for all the non-text content.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A) For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such:
  • Prerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.
  • Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.
Not Applicable
1.2.2 Captions (Prerecorded) (Level A) Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such. Not Applicable
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such. Not Applicable
1.3.1 Info and Relationships (Level A) Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. Not Applicable
1.3.2 Meaningful Sequence (Level A) When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. Supported The content is presented in a meaningful sequence.
1.3.3 Sensory Characteristics (Level A) Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. Supported Instructions do not rely solely on sensory characteristics.
1.4.1 Use of Color (Level A) Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. Supported Color is used only for the visual presentation and not for conveying information.
1.4.2 Audio Control (Level A) If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. Not Applicable
2.1.1 Keyboard (Level A) All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. Supported With Exceptions All functionality of the content is operable through a keyboard interface except for instances such as image resizing, data within images or charts, etc.
2.1.2 No Keyboard Trap (Level A) If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. Supported With Exceptions Depending on the view mode of Word some navigation may result in keyboard focus traps. Using the "Accessibility Mode" option is recommended.
2.2.1 Timing Adjustable (Level A) For each time limit that is set by the content, at least one of the following is true: (Level A)
  • Turn off: The user is allowed to turn off the time limit before encountering it; or
  • Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
  • Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or
  • Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
  • Essential Exception: The time limit is essential and extending it would invalidate the activity; or
  • 20 Hour Exception: The time limit is longer than 20 hours.
Not Applicable
2.2.2 Pause, Stop, Hide (Level A) For moving, blinking, scrolling, or auto-updating information, all of the following are true: (Level A)
  • Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and
  • Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.
Not Applicable
2.3.1 Three Flashes or Below Threshold (Level A) Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. Not Applicable
2.4.1 Bypass Blocks (Level A) A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. Not Applicable
2.4.2 Page Titled (Level A) Web pages have titles that describe topic or purpose. Supported Titles are provided for web pages.
2.4.3 Focus Order (Level A) If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. Supported The components receive focus in a meaningful order.
2.4.4 Link Purpose (In Context) (Level A) The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. Supported Link texts are semantic to determine the meaning of the link.
3.1.1 Language of Page (Level A) The default human language of each Web page can be programmatically determined. Supported Language of the page can be determined using attribute.
3.2.1 On Focus (Level A) When any component receives focus, it does not initiate a change of context. Supported User interface component does not initiate a change of context on receiving focus.
3.2.2 On Input (Level A) Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. Supported User interface component does not automatically cause a change of context on user input.
3.3.1 Error Identification (Level A) If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. Supported When an input error is automatically detected, the erro is identified and a text message is displayed describing the error.
3.3.2 Labels or Instructions (Level A) Labels or instructions are provided when content requires user input. Supported Labels are provided for user input fields.
4.1.1 Parsing (Level A) In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. Supported Semantically correct markup is provided for all the elements.
4.1.2 Name, Role, Value (Level A) For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. Supported User interface components can be determined programmatically.

Table 2: Success Criteria, Level AA

Criteria Conformance Level Remarks and Explanations
1.2.4 Captions (Live) (Level AA) Captions are provided for all live audio content in synchronized media. Not Applicable
1.2.5 Audio Description (Prerecorded) (Level AA) Audio description is provided for all prerecorded video content in synchronized media. Not Applicable
1.4.3 Contrast (Minimum) (Level AA) The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following:
  • Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1;
  • Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.
  • Logotypes: Text that is part of a logo or brand name has no minimum contrast requirement.
Supported With Exceptions Elements meet minimum contrast requirements. Except:
  • Changed areas for co-authoring don’t meet contrast ratio vs. the white background by default, color can be customized via the track changes UI.
  • Colors for tracked change insertion/deletion of table rows/cells do not meet 3:1 contrast ratio.
1.4.4 Resize text (Level AA) Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. Supported Text supports standard Zoom-in and Zoom-out capabilities.
1.4.5 Images of Text (Level AA) If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: (Level AA)
  • Customizable: The image of text can be visually customized to the user's requirements;
  • Essential: A particular presentation of text is essential to the information being conveyed.
Supported Text is used vs image of text.
2.4.5 Multiple Ways (Level AA) More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. Not Applicable
2.4.6 Headings and Labels (Level AA) Headings and labels describe topic or purpose. Supported Headings and labels in the site are descriptive.
2.4.7 Focus Visible (Level AA) Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. Supported All focusable elements on site have a visible keyboard focus indicator.
3.1.2 Language of Parts (Level AA) The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. Supported The language of each passage or phrase can be programmatically determined.
3.2.3 Consistent Navigation (Level AA) Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. Supported Navigation is consistent.
3.2.4 Consistent Identification (Level AA) Components that have the same functionality within a set of Web pages are identified consistently. Supported Components with same functionality are identified consistently.
3.3.3 Error Suggestion (Level AA) If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. Supported A suggestion for correction is provided when an input error is automatically detected.
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true:
  • Reversible: Submissions are reversible.
  • Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
  • Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
Not Applicable

Table 3: Success Criteria, Level AAA

Not Applicable

Chapter 3: Functional Performance Criteria (FPC)

Not Applicable

Chapter 4: Hardware

Not Applicable

Chapter 5: Software

Criteria Conformance Level Remarks and Explanations
501.1 Scope ‐ Incorporation of WCAG 2.0 AA See WCAG 2.x section See information in WCAG 2.x section
502 Interoperability with Assistive Technology
502.2.1 User Control of Accessibility Features Not Applicable
502.2.2 No Disruption of Accessibility Features Supported With Exceptions
  • Ctrl key is used to expand some on object UI (ex. paste recovery, object skittle), but will also silence a screen reader. You can use alt + shift + F10 to open that UI instead.
  • Read Aloud (also part of Learning Tools) is difficult to use at the same time as a screen reader. If using a screen reader, it is recommended to pause Read Aloud immediately when launching, but the Read Aloud UI is accessible.
  • Screen reader users have to have headphones or something that diverts screen reader announcements from the microphone in order to use the Dictate feature, otherwise Dictate will pick up the screen reader announcements.
502.3 Accessibility Services
502.3.1 Object Information Supported Product has been developed in compliance to this standard.
502.3.2 Modification of Object Information Supported Product has been developed in compliance to this standard.
502.3.3 Row, Column, and Headers Supported Product has been developed in compliance to this standard.
502.3.4 Values Supported Product has been developed in compliance to this standard.
502.3.5 Modification of Values Supported Product has been developed in compliance to this standard.
502.3.6 Label Relationships Supported Product has been developed in compliance to this standard.
502.3.7 Hierarchical Relationships Supported With Exceptions
  • The navigation pane represents headings as a flat list. Headings and list within the main document accurately reflect parent/child relationships, list level, list position, or selection information.
  • In certain dialog boxes Office may not fully expose the parent/child relationships between all containers and their controls programmatically. For example, in the Word Format Font dialog, the parent/child relationship between the group of checkboxes and the individual checkboxes is not exposed to accessibility APIs.
  • When a user navigates to a “blank document” on the New & Start pages, a user is not informed that this control is part of a grid. A user will miss out on the fact that there are many templates to choose from other than blank file and will not receive information relevant to the template’s location within the grid.
502.3.8 Text Supported With Exceptions Assistive technologies cannot access equations, textboxes, charts, or smart art since they are renders as images.
502.3.9 Modification of Text Supported Product has been developed in compliance to this standard.
502.3.10 List of Actions Supported Product has been developed in compliance to this standard.
502.3.11 Actions on Objects Supported Product has been developed in compliance to this standard.
502.3.12 Focus Cursor Supported With Exceptions Tooltips that display from items in the status bar in Office applications are not exposed to AT. They generally do not offer additional information compared to the label on the item from which they're triggered.
502.3.13 Modification of Focus Cursor Supported Product has been developed in compliance to this standard.
502.3.14 Event Notification Supported With Exceptions
  • Screen readers may not confirm the success or failure of all user actions. For example, Narrator does not announce notifications for AutoCorrect (ex. Automatically correcting common misspellings) and AutoFormat (ex. Automatically creating a list). You can enable the “Provide feedback with sound” option in Word under “Ease of Access” to mitigate this issue. You can verify an action was successfully applied by inspecting Undo or inspecting the changed area of the document.
  • When a user uses the search box to search for a template on the New & Start pages, an AT does not read the text to announce the search action is underway and is currently searching. User will be confused after hitting enter to search why focus is no longer on anything and why there’s nothing being read. This is particularly an issue for slow internet connectivity.
  • After a user successfully shares another user to a file, the user is not informed that the share was successful.
  • Narrator users may hear repetitive announcements while coauthoring simultaneously with other users. The root cause for the issue has been identified, but a schedule for providing a solution has not yet been published. Users can minimize this by turning-off AutoSave or eliminate this by editing in another copy and pasting back into the original document. Users can also avoid the problem by using JAWS or NVDA.
  • Office web apps generally do not provide change notification for user initiated action. Today there is no browser support or sufficient web standards to provide confirmation of action information to AT users without creating an overwhelming experience. If a user makes a change to a setting, the user can navigate back to that setting to read the current state. For non-user actions, for example other collaborators entering a document and status changes, we provide AT with a notification.
502.4 Platform Accessibility Features Not Applicable
503 Applications
503.2 User Preferences Supported With Exceptions
  • Ctrl key is used to expand some on object UI (ex. paste recovery, object skittle), but will also silence a screen reader. You can use alt + shift + F10 to open that UI instead.
  • Read Aloud (also part of Learning Tools) is difficult to use at the same time as a screen reader. If using a screen reader, it is recommended to pause Read Aloud immediately when launching, but the Read Aloud UI is accessible.
  • Screen reader users have to have headphones or something that diverts screen reader announcements from the microphone in order to use the Dictate feature, otherwise Dictate will pick up the screen reader announcements.
  • The Text Cursor Indicator in Windows 10 version 2004 and later needs consistent rendering.
503.3 Alternative User Interfaces Not Applicable
503.4 User Controls for Captions and Audio Description
503.4.1 Caption Controls Not Applicable
503.4.2 Audio Description Controls Not Applicable
504 Authoring Tools
504.2 Content Creation or Editing (if not authoring tool, enter “not applicable”) Supported See information in WCAG 2.x section
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion Supported With Exceptions Publish to blog post does not convert accessible Word documents to accessible HTML.
504.2.2 PDF Export Supported With Exceptions Accessible documents can be exported as accessible PDFs with some exceptions.
504.3 Prompts Supported With Exceptions The Accessibility checker cannot be run when publishing a Word document to blog post.
504.4 Templates Supported Product has been developed in compliance to this standard.

Chapter 6: Support Documentation and Services

Criteria Conformance Level Remarks and Explanations
601.1 Scope
602 Support Documentation
602.2 Accessibility and Compatibility Features Supported Product has been developed in compliance to this standard.
602.3 Electronic Support Documentation Supported See information in WCAG 2.x section
602.4 Alternate Formats for Non-Electronic Support Documentation Supported Product has been developed in compliance to this standard.
603 Support Services
603.2 Information on Accessibility and Compatibility Features Supported Product has been developed in compliance to this standard.
603.3 Accommodation of Communication Needs Supported Product has been developed in compliance to this standard.