Adobe FrameMaker 2019
Accessibility Conformance Report published by Adobe
Partial extraction. We read 30 of 31 Level A and 20 of 24 Level AA criteria from this document (91% coverage). The remainder are missing from our extraction, not necessarily from Adobe's report — their table layout defeated our parser. Treat the figures below as incomplete and read the source document for the full picture.
Conformance by level
Reported by the vendor. WCAG Level AA is the benchmark referenced by ADA Title II, Section 508 and the European Accessibility Act; Level AAA is optional and often left unevaluated.
Level A — 30 criteria
- Supports
- 20
- Partially supports
- 9
- Does not support
- 1
- Not applicable
- 0
- Not evaluated
- 0
Level AA — 20 criteria
- Supports
- 13
- Partially supports
- 6
- Does not support
- 1
- Not applicable
- 0
- Not evaluated
- 0
Source: View the original report published by Adobe.
These figures are extracted from that document. They are the vendor's own statements, not an independent assessment, and automated extraction can misread a table.
All reported criteria (96)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Partially Supports | Software: Most product functions do not contain images which would require a text alternative. Exceptions include: In the document editor, embedded image objects lack a text alternative. In the QR Code Builder dialog, the QR code graphic does not provide a text alternative. Authored Content (HTML): Authors can provide text alternatives for most images. Exceptions include: Some image buttons in the navigation controls, such as Previous and Next, lack text alternatives. Authored Content (PDF): Authors can provide text alternatives for images. |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Supports | Software: The product does not contain prerecorded audio-only or video-only media. Authored Content (HTML): Authors can provide audio description for what would otherwise be video-only media embedded in a document. Authors can also provide transcripts for video-only media. Authored Content (PDF): Authors can provide audio description for what would otherwise be video-only media embedded in a document. Authors can also provide transcripts for video-only media. |
| 1.2.2 | Captions (Prerecorded) | A | Supports | Software: The product does not contain prerecorded synchronized media. Authored Content (HTML): Authors can provide open captions for audio content in embedded video, but the product does not allow authors to provide closed captions. Authored Content (PDF): Authors can provide open captions for audio content in embedded video, but the product does not allow authors to provide closed captions. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Supports | Software: The product does not contain prerecorded video content that would require audio description or a media alternative. Authored Content (HTML): Authors can provide transcripts for video. Authored Content (PDF): Authors can provide transcripts for video. |
| 1.2.4 | Captions (Live) | AA | Supports | Software: The product does not contain live synchronized media. Authored Content (HTML): Authored content does not contain live synchronized media. Authored Content (PDF): Authored content does not contain live synchronized media. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Supports | Software: The product does not contain prerecorded video content that would require audio description. Authored Content (HTML): Authors can embed video with audio description in the main narration track, but the product does not allow authors to provide separate audio description tracks. Authored Content (PDF): Authors can embed video with audio description in the main narration track, but the product does not allow authors to provide separate audio description tracks. |
| 1.3.1 | Info and Relationships | A | Partially Supports | Software: Most structure and relationship information, such as grouping of form fields, is provided through object information. However, some information is provided visually but is not provided to assistive technology. Examples include: In a document window, the XML hierarchy text is not provided to assistive technology. In the Spell Checker dialog, the radio buttons lack programmatic grouping. In the Standard Templates window, the text content is not provided to assistive technology. Authored Content (HTML): Most visual structure and relationship information is provided through element seman |
| 1.3.2 | Meaningful Sequence | A | Partially Supports | Software: The product presents most content in a meaningful sequence. However, in some cases text in the document editor is announced out of sequence in assistive technology. Examples include: When two pages appear side by side, alternating lines of text from the two pages are announced. When a pod appears in front of a document, pod text is announced between lines of document text. Authored Content (HTML): Content is presented in a meaningful sequence. Authored Content (PDF): Content is presented in a meaningful sequence. |
| 1.3.3 | Sensory Characteristics | A | Partially Supports | Software: Most instructions do not rely solely on sensory characteristics. Exceptions include: In the Standard Templates window, an instruction relies on visual position information. Authored Content (HTML): Authors can ensure that content meets this criterion. Authored Content (PDF): Authors can ensure that content meets this criterion. |
| 1.3.4 | Orientation | AA | Supports | Software: Content does not restrict its view and operation to a single display orientation. Authored Content (HTML): Authored content does not restrict its view and operation to a single display orientation. Authored Content (PDF): Authored content does not restrict its view and operation to a single display orientation. |
| 1.3.5 | Identify Input Purpose | AA | Supports | Software: The product does not contain input fields that collect information about the user. Authored Content (HTML): Authored content does not include input fields that collect information about the user. Authored Content (PDF): Authored content does not include input fields that collect information about the user. |
| 1.4.1 | Use of Color | A | Partially Supports | Software: Most functions of the product do not convey information through color alone. Exceptions include: In some tab lists, the currently selected tab is indicated solely by a color difference. Authored Content (HTML): Authors can ensure that content meets this criterion. Authored Content (PDF): Authors can ensure that content meets this criterion. |
| 1.4.2 | Audio Control | A | Supports | Software: The product does not contain audio that plays automatically. Authored Content (HTML): Authored content does not contain audio that plays automatically. Authored Content (PDF): Authored content does not contain audio that plays automatically. |
| 1.4.3 | Contrast (Minimum) | AA | Partially Supports | Software: Most text meets minimum contrast requirements. Exceptions include: In the Welcome screen, the DITA version number has insufficient color contrast. In the Standard Templates window, green text elements have insufficient color contrast. Authored Content (HTML): Authors can ensure that text meets contrast requirements. Authored Content (PDF): Authors can ensure that text meets contrast requirements. |
| 1.4.4 | Resize text | AA | Partially Supports | Software: The product does not provide its own text resizing function. When text is resized using operating system display scaling, some content is unavailable. Examples include: In the Welcome screen, some content under “Resources” and “Learn” extends off-screen and cannot be scrolled into view. In the QR Code Builder dialog, some form controls extend off-screen and cannot be scrolled into view. Authored Content (HTML): Using browser zoom, text can be resized up to 200 percent without loss of content or functionality. Authored Content (PDF): Using the zoom function of a PDF reader application |
| 1.4.5 | Images of Text | AA | Supports | Software: The product uses text instead of images of text, except for branding elements that are considered essential. Authored Content (HTML): Authors can ensure that most content meets this criterion. Exceptions include: When text is grouped with a non-text object, it is published as an image of text. Authored Content (PDF): Authored content does not contain images of text. |
| 1.4.10 | Reflow | AA | Does Not Support | Software: At the required width of 320 CSS pixels, content or functionality extends off-screen in most product functions and cannot be scrolled into view. Examples include: In most pods and dialogs, form controls and content extend off-screen. In the Welcome screen, most sections of content are cut off. In the status bar of the Document window, content is cut off. Authored Content (HTML): At the required width equivalent of 320 CSS pixels, content is presented without loss of information or functionality, and without requiring scrolling in two dimensions. Authored Content (PDF): At the require |
| 1.4.11 | Non-text Contrast | AA | Partially Supports | Software: Most meaningful non-text content elements, such as form controls and graphical buttons, have sufficient contrast. Exceptions include: Borders of text entry fields lack sufficient color contrast. The selected state indicator of some toolbar buttons lacks sufficient color contrast. Authored Content (HTML): Authors can ensure that most content meets this criterion. Exceptions include: Some Search form controls lack sufficient contrast. Some navigation controls use a low-contrast color to indicate selection. Authored Content (PDF): Authors can ensure that content meets this criterion. |
| 1.4.12 | Text Spacing | AA | Supports | Software: The product’s Welcome screen has markup content but no mechanism for applying text style properties to the content. Authored Content (HTML): Authors can ensure that content meets this criterion. Authored Content (PDF): Authors can ensure that content meets this criterion. |
| 1.4.13 | Content on Hover or Focus | AA | Partially Supports | Software: In most product functions, content does not become visible and then hidden in response to pointer hover or keyboard focus. Exceptions include: Tooltip text disappears when hovered with a mouse pointer. Authored Content (HTML): Authored content does not contain content elements triggered by hover or focus. Authored Content (PDF): Authored content does not contain content elements triggered by hover or focus. |
| 2.1.1 | Keyboard | A | Partially Supports | Software: Some product functionality, such as the functions of most dialogs and pods, can be operated directly through a keyboard interface. Some controls do not receive keyboard focus, such as editor toolbars and Welcome screen controls, yet the same functions are available through standard keystrokes in application menus or through documented product-specific keyboard shortcuts. However, some functions are not keyboard accessible. Exceptions include: Some functions of the Welcome screen Functions of the Drawing toolbar. Insertion of symbols from the Equations pod. Selection of objects previo |
| 2.1.2 | No Keyboard Trap | A | Supports | Software: Some actions, such as closing a dialog or inserting a non-text object in a document, cause a momentary keyboard trap. However, users can continue to other product functions by performing menu commands with the keyboard. Authored Content (HTML): Authored content does not include keyboard traps. Authored Content (PDF): Authored content does not include keyboard traps. |
| 2.1.4 | Character Key Shortcuts | A | Supports | Software: The product does not provide character key shortcuts. Authored Content (HTML): Authored content does not provide character key shortcuts. Authored Content (PDF): Authored content does not provide character key shortcuts. |
| 2.2.1 | Timing Adjustable | A | Supports | Software: The product does not include time limits. Authored Content (HTML): Authored content does not include time limits. Authored Content (PDF): Authored content does not include time limits. |
| 2.2.2 | Pause, Stop, Hide | A | Supports | Software: The product does not include elements which move, blink, scroll, or auto-update. Authored Content (HTML): Authors can ensure that content meets this criterion. Authored Content (PDF): Authors can ensure that content meets this criterion. |
| 2.3.1 | Three Flashes or Below Threshold | A | Supports | Software: The product does not contain flashing content. Authored Content (HTML): Authors can ensure that content does not flash. Authored Content (PDF): Authors can ensure that content does not flash. |
| 2.4.1 | Bypass Blocks | A | Supports | Software: This criterion does not apply to non-web software. Authored Content (HTML): The authored content provides an inline frame, which allows assistive technology users to bypass a repeated navigation block. However, for users without assistive technology, a bypass mechanism is not provided. Authored Content (PDF): This criterion does not apply to non-web documents. |
| 2.4.2 | Page Titled | A | Partially Supports | Software: Most windows have titles which describe their purpose. Exceptions include: The Spell Checker pod is presented as a window, but does not provide a title to assistive technology. Authored Content (HTML): The product allows authors to customize the page title. Authored Content (PDF): The product does not allow authors to customize the document title or display it in the window title. |
| 2.4.3 | Focus Order | A | Supports | Software: Components receive focus in a meaningful order. Authored Content (HTML): Most components receive focus in a meaningful order. Exceptions include: Some content, such as the Previous and Next controls, gains focus in the reverse order as its intended visual focus order. Some content, such as the Search form focus order, does not match the visual order. Authored Content (PDF): Components receive focus in a meaningful order. |
| 2.4.4 | Link Purpose (In Context) | A | Supports | Software: The purpose of links in the product can be determined from the link text alone or from the programmatic context of the link. Authored Content (HTML): Authored content provides the purpose of links through link text alone or through programmatic context. Authored Content (PDF): Authored content provides the purpose of links through link text alone or through programmatic context. |
| 2.4.5 | Multiple Ways | AA | Supports | Software: This criterion does not apply to non-web software. Authored Content (HTML): Authors can provide more than one way to locate a page in a set of pages, such as Search and navigation. Authored Content (PDF): This criterion does not apply to non-web documents. |
| 2.4.6 | Headings and Labels | AA | Supports | Software: Headings and labels are descriptive. Authored Content (HTML): Authors can ensure that content meets this criterion. Authored Content (PDF): Authors can ensure that content meets this criterion. |
| 2.4.7 | Focus Visible | AA | Partially Supports | Software: Most focusable elements have a visible keyboard focus indicator. Exceptions include: In the Welcome screen, two elements in the tab sequence lack a visible focus indicator. Authored Content (HTML): Most focusable elements have a visible keyboard focus indicator. Exceptions include: Some off-screen inactive navigation elements receive keyboard focus. Authored Content (PDF): Authors can ensure that content meets this criterion. |
| 2.5.1 | Pointer Gestures | A | Supports | Software: The product does not rely on multipoint or path-based gestures. Authored Content (HTML): Authored content does not rely on multipoint or path-based gestures. Authored Content (PDF): Authored content does not rely on multipoint or path-based gestures. |
| 2.5.2 | Pointer Cancellation | A | Supports | Software: Product functions that use a single pointer are completed when the user releases the pointer. Authored Content (HTML): Authored content functions that use a single pointer are completed when the user releases the pointer. Authored Content (PDF): Authored content functions that use a single pointer are completed when the user releases the pointer. |
| 2.5.3 | Label in Name | A | Supports | Software: The accessible names of controls contain the text of their visible labels. Authored Content (HTML): The accessible names of controls contain the text of their visible labels. Authored Content (PDF): The accessible names of controls contain the text of their visible labels. |
| 2.5.4 | Motion Actuation | A | Supports | Software: The product does not have functionality operated by device motion or user motion. Authored Content (HTML): Authored content does not have functionality operated by device motion or user motion. Authored Content (PDF): Authored content does not have functionality operated by device motion or user motion. |
| 3.1.1 | Language of Page | A | Supports | Software: The language is programmatically determinable within the product. The language of the product is set based on the version installed by the user. Authored Content (HTML): The product does not allow authors to set the language of the page. Authored Content (PDF): The product does not allow authors to set the language of the document. |
| 3.1.2 | Language of Parts | AA | Supports | Software: Content is only presented in one language at a time. Authored Content (HTML): Authored content is only presented in one language at a time. Authored Content (PDF): Authored content is only presented in one language at a time. |
| 3.2.1 | On Focus | A | Supports | Software: Most components do not initiate a change of context when focused. Exceptions include: In the Character Catalog pod, a focus change occurs when the user focuses items in the list. Authored Content (HTML): Authored content components do not initiate a change of context when focused. Authored Content (PDF): Authored content components do not initiate a change of context when focused. |
| 3.2.2 | On Input | A | Supports | Software: Changes of context do not occur automatically on user input. Authored Content (HTML): Changes of context do not occur automatically on user input. Authored Content (PDF): Authored content does not contain user input controls. |
| 3.2.3 | Consistent Navigation | AA | Supports | Software: This criterion does not apply to non-web software. Authored Content (HTML): Navigational mechanisms are repeated in the same relative order in a set of pages. Authored Content (PDF): This criterion does not apply to non-web documents. |
| 3.2.4 | Consistent Identification | AA | Supports | Software: This criterion does not apply to non-web software. Authored Content (HTML): Authors can ensure that components with the same functionality are identified consistently in a set of pages. Authored Content (PDF): This criterion does not apply to non-web documents. |
| 3.3.1 | Error Identification | A | Partially Supports | Software: Most input errors are identified and described to the users in text. Exceptions include: In the Create CMS Connection dialog, the error message for an invalid server format does not indicate which field is in error. Authored Content (HTML): Authored content does not detect input errors. Authored Content (PDF): Authored content does not detect input errors. |
| 3.3.2 | Labels or Instructions | A | Partially Supports | Software: Labels are provided for most input fields. Exceptions include: In the Create CMS Connection dialog, labels and instructions do not indicate which fields are required. Authored Content (HTML): Labels or instructions are provided when content requires user input. Authored Content (PDF): Authored content does not contain user input controls that would require labels or instructions. |
| 3.3.3 | Error Suggestion | AA | Partially Supports | Software: Where input errors are automatically detected, suggestions for correction are provided to the user in most cases. Exceptions include: In the Publish dialog, an error message for Output Location does not say which characters are allowed or disallowed. In the Code Builder dialog, an error message for Telephone does not say what format is required. Authored Content (HTML): Authored content does not detect input errors that are displayed to users. Authored Content (PDF): Authored content does not detect input errors that are displayed to users. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Supports | Software: The product does not process legal commitments or financial transactions. Changes to user-controllable data are reversible or can be confirmed before finalizing. Authored Content (HTML): Authored content does not contain legal or financial data and does not modify user-controllable data. Authored Content (PDF): Authored content does not contain legal or financial data and does not modify user-controllable data. |
| 4.1.1 | Parsing | A | Supports | Software: Embedded markup, such as Welcome screen content, meets parsing requirements. Authored Content (HTML): 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. Authored Content (PDF): The authored content is not implemented using markup languages. |
| 4.1.2 | Name, Role, Value | A | Does Not Support | Software: The product’s main menus convey name, role, and state information to assistive technology. However, user interface components in most product functions lack programmatic name, role, state, or value information. Examples include: In most pods and dialogs, form input fields lack accessible names. In the document editor, the accessible text values of some content, such as headings, equations, and line endings, do not match the visual presentation of the content. In the document editor, non-text objects, such as images and frames, lack accessible role and property information. In the doc |
| 4.1.3 | Status Messages | AA | Supports | Software: This criterion does not apply to non-web software. Authored Content (HTML): Authored content does not include status messages. Authored Content (PDF): This criterion does not apply to non-web documents. |
| 502.2.1 | User Control of Accessibility Features | - | Not Applicable | The product is not platform software. |
| 502.2.2 | No Disruption of Accessibility Features | - | Supports | The product does not disrupt platform accessibility features. |
| 502.3.1 | Object Information | - | Partially Supports | As noted in 4.1.2 Name, Role, Value , some objects in the product do not expose name, role, state, or description information to assistive technology. |
| 502.3.2 | Modification of Object Information | - | Supports | The product allows assistive technology to modify states and properties of controls. |
| 502.3.3 | Row, Column, and Headers | - | Does Not Support | The product does not expose the row, column, and headers of most table cells to assistive technology. |
| 502.3.4 | Values | - | Partially Supports | The product exposes the values of most input controls to assistive technology. Exceptions include: As noted in 4.1.2 Name, Role, Value , some user-entered content objects in the document editor are not exposed to assistive technology. |
| 502.3.5 | Modification of Values | - | Supports | The product allows assistive technology to modify the values of input controls. |
| 502.3.6 | Label Relationships | - | Does Not Support | As noted in 4.1.2 Name, Role, Value , the product does not expose the label relationships of input fields to assistive technology in most pods and dialogs. |
| 502.3.7 | Hierarchical Relationships | - | Partially Supports | The product exposes most hierarchical parent-child relationships to assistive technology. Exceptions include: As noted in 1.3.1 Info and Relationships , radio buttons in the Spell Checker dialog lack programmatic grouping. |
| 502.3.8 | Text | - | Partially Supports | The product exposes most text content and text values to assistive technology. Exceptions include: As noted in 1.3.1 Info and Relationships , XML hierarchy text is not exposed to assistive technology. As noted in 1.3.1 Info and Relationships , text in the Standard Templates window is not exposed to assistive technology. As noted in 4.1.2 Name, Role, Value , some user-entered text in the document editor is exposed incorrectly to assistive technology. |
| 502.3.9 | Modification of Text | - | Supports | The product allows assistive technology to modify the text of input controls. |
| 502.3.10 | List of Actions | - | Partially Supports | Most controls in the product expose programmatic role information, which conveys available actions to assistive technology. As noted in 4.1.2 Name, Role, Value , exceptions include: The Workspace menu lacks an accessible role. Controls in the Standard Templates window lack accessible roles. |
| 502.3.11 | Actions on Objects | - | Partially Supports | The product allows assistive technology to perform most actions on objects. As noted in 2.1.1 Keyboard , exceptions include: Some functions of the Welcome screen. Functions of the Drawing toolbar. Insertion of symbols from the Equations pod. The workspace switcher function. |
| 502.3.12 | Focus Cursor | - | Partially Supports | The product exposes most focus, text insertion point, and selection attributes to assistive technology. Exceptions include: The selection attribute of some objects in documents, such as frames and images, are not exposed to assistive technology. |
| 502.3.13 | Modification of Focus Cursor | - | Partially Supports | The product allows assistive technology to move focus and modify most selection attributes. Exceptions include: The product does not allow assistive technology to select some objects in documents, such as frames and images. |
| 502.3.14 | Event Notification | - | Supports | The product notifies assistive technology about attribute changes in user interface elements. |
| 503.4.1 | Caption Controls | - | Not Applicable | The product does not display video. |
| 503.4.2 | Audio Description Controls | - | Not Applicable | The product does not display video. |
| 504.2.1 | Preservation of Information Provided for Accessibility in Format Conversion | - | Partially Supports | When publishing to HTML or PDF, the product preserves most information for accessibility that is available in source documents. Exceptions include: As noted in 1.3.1 Info and Relationships , some visual structure and relationship information is not provided through element semantics. The product does not preserve captions and audio description data when publishing a document with imported video. |
| 504.2.2 | PDF Export | - | Does Not Support | When publishing to a PDF 1.7 file, the product does not enable PDF/UA-1 conformance for most content. Examples include: Most path objects and text objects are not tagged. Link elements lack alternative text values. Figure elements lack bounding boxes. |
| 4.2.1 | Usage without vision | - | Does Not Support | Software: Most functions of the product are not usable without vision. Examples include: As noted in 1.1.1 Non-text Content , some images lack a text alternative. As noted in 1.3.1 Info and Relationships , some structure and relationship information is provided visually, but is not provided to assistive technology. As noted in 1.3.2 Meaningful Sequence , in some cases text in the document editor is announced out of sequence. As noted in 2.1.1 Keyboard , some product functions are not keyboard accessible. As noted in 4.1.2 Name, Role, Value , user interface components in most product functions |
| 4.2.2 | Usage with limited vision | - | Partially Supports | Software: Most functions of the product are usable with limited vision. Exceptions include: As noted in 1.4.3 Contrast (Minimum) , some text does not meet minimum contrast requirements. As noted in 1.4.4 Resize Text , some content is unavailable when text is resized using operating system display scaling. As noted in 1.4.10 Reflow , at the required width of 320 CSS pixels, content or functionality extends off-screen in most product functions and cannot be scrolled into view. As noted in 1.4.11 Non-text Contrast , some meaningful non-text content elements do not have sufficient contrast. As not |
| 4.2.3 | Usage without perception of colour | - | Partially Supports | Software: Most functions of the product are usable without perception of color. Exceptions include: As noted in 1.4.1 Use of Color , some tab selections are indicated solely by a color difference. Authored Content (HTML): Authors can create content which is functional for users without perception of color. Authored Content (PDF): Authors can create content which is functional for users without perception of color. |
| 4.2.4 | Usage without hearing | - | Supports | Software: The product does not require the use of hearing. Authored Content (HTML): Authors can create content in which most functions can be used without hearing. Exceptions include: As noted in 1.2.2 Captions (Prerecorded) , closed captions are not preserved in embedded video. Authored Content (PDF): Authors can create content in which most functions can be used without hearing. Exceptions include: As noted in 1.2.2 Captions (Prerecorded) , closed captions are not preserved in embedded video. |
| 4.2.5 | Usage with limited hearing | - | Supports | Software: The product does not require the use of hearing. Authored Content (HTML): Authors can create content in which most functions can be used with limited hearing. Exceptions include: As noted in 1.2.2 Captions (Prerecorded) , closed captions are not preserved in embedded video. Authored Content (PDF): Authors can create content in which most functions can be used with limited hearing. Exceptions include: As noted in 1.2.2 Captions (Prerecorded) , closed captions are not preserved in embedded video. |
| 4.2.6 | Usage without vocal capability | - | Supports | Software: The product does not require the use of speech. Authored Content (HTML): Authors can create content which is functional for users without speech. Authored Content (PDF): Authors can create content which is functional for users without speech. |
| 4.2.7 | Usage with limited manipulation or strength | - | Partially Supports | Software: Most functions of the product are usable with limited manipulation or strength. Exceptions include: As noted in 2.1.1 Keyboard , some product functions are not keyboard accessible. As noted in 2.4.7 Focus Visible , two elements in the Welcome screen lack a visible focus indicator. As noted in 3.2.1 On Focus , a component in the Character Catalog pod initiates a change of context when focused. Authored Content (HTML): Authors can create content in which most functions can be used with limited manipulation or strength. Exceptions include: As noted in 2.1.1 Keyboard , some controls are |
| 4.2.8 | Usage with limited reach | - | Supports | Software: The product is functional with limited reach. Authored Content (HTML): Authors can create content which is functional with limited reach. Authored Content (PDF): Authors can create content which is functional with limited reach. |
| 4.2.9 | Minimize photosensitive seizure triggers | - | Supports | Software: As noted in 2.3.1 Three Flashes or Below Threshold , the product does not contain flashing content. Authored Content (HTML): Authors can create content which does not flash, or flashes within an acceptable threshold, in order to minimize the potential for triggering photosensitive seizures. Authored Content (PDF): Authors can create content which does not flash, or flashes within an acceptable threshold, in order to minimize the potential for triggering photosensitive seizures. |
| 4.2.10 | Usage with limited cognition | - | Partially Supports | Software: Most functions of the product are usable 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 or accessibility features of the platform. The product provides descriptive labels, instructions, and error identification and suggestions for most user input. Exceptions include: As noted in 3.3.1 Error Identification , an error message in the Create CMS Connection dialog does not indicate which field is in error. As noted in 3.3.2 Labels or Instructions |
| 4.2.11 | Privacy | - | Supports | Software: The product does not ask for or display legal, financial, or personal data. Authored Content (HTML): Authored content does not contain legal or financial data and does not modify user-controllable data. Authored Content (PDF): Authored content does not contain legal or financial data and does not modify user-controllable data. |
| 5.5.1 | Means of operation | - | Not Applicable | The product has only non-mechanical operable parts, such as on-screen buttons, which do not require grasping, pinching, or twisting of the wrist to operate. |
| 5.5.2 | Operable parts discernibility | - | Partially Supports | The product has only non-mechanical operable parts, such as on-screen buttons. Most operable parts have an accessible name which enables them to be discernible without user vision. Exceptions include: Some graphical on-screen buttons do not have an accessible name. |
| 5.6.1 | Tactile or auditory status | - | Not Applicable | The product does not have locking or toggle controls. |
| 5.6.2 | Visual status | - | Not Applicable | The product does not have locking or toggle controls. |
| 7.1.1 | Captioning playback | - | Not Applicable | The product does not require a caption playback function for imported video because the document window does not have a video player. |
| 7.1.2 | Captioning synchronization | - | Not Applicable | The product does not display captions. |
| 7.1.3 | Preservation of captioning | - | Does Not Support | The product does not preserve caption data when converting a document with imported video to HTML or PDF. |
| 7.2.1 | Audio description playback | - | Not Applicable | The product does not require a function to play back a separate audio description track in imported video because the document window does not have a video player. |
| 7.2.2 | Audio description synchronization | - | Not Applicable | The product does not have a mechanism to play audio description. |
| 7.2.3 | Preservation of audio description | - | Does Not Support | The product does not preserve audio description data when converting a document with imported video to HTML or PDF. |
| 11.6.1 | User control of accessibility features | - | Not Applicable | The product is not platform software. |
| 11.6.2 | No disruption of accessibility features | - | Supports | The product does not disrupt platform accessibility features. |
| 11.8.3 | Preservation of accessibility information in transformations | - | Partially Supports | When publishing to HTML or PDF, the product preserves most information for accessibility that is available in source documents. Exceptions include: As noted in 1.3.1 Info and Relationships , some visual structure and relationship information is not provided through element semantics. The product does not preserve captions and audio description data when publishing a document with imported video. |
| 11.8.4 | Repair assistance | - | Not Applicable | The product does not have accessibility checking functionality. |
| 11.8.5 | Templates | - | Partially Supports | Templates in the product enable authors to create a range of content, such as book chapters and reports. As noted in the WCAG 2.x section, the product does not enable authors to create content which conforms to WCAG 2.1 Levels A and AA. |
Is this your product? If this report is out of date or misrepresented, we will correct or remove it. Contact us to claim this listing.
Get told when this changes
This report is dated August 2019. An ACR can be quietly replaced at any time, and the published date is the only signal a buyer gets. We will email you when this one is updated.
Double opt-in — we email you once to confirm, and send nothing until you do. One-click unsubscribe on every message. We store your address and what you are watching, nothing else. Privacy.