Web Content Accessibility Guidelines 2.0, at http://www.w3.org/TR/2008/REC-WCAG20-20081211/

Level A - Yes

Level AA - Yes

Level AAA - No

Section 508 as published in 2017, at http://www.Section508.gov

Yes

EN 301 549 Accessibility requirements suitable for public procurement of ICT products and services in Europe, at http://mandate376.standards.eu/standard

Yes

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

• 9.2.1 (Web)
• 10.2.1 (non-web document)
• 11.2.1.1 (Software)
• 11.2.2.1 (Closed Functionality Software)
• 11.6.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

Authored Content (HTML): Does Not Support

Authored Content (Video): Supports

Web: Text alternatives are provided for many instances of non-text content, with the following exceptions:

• In Post editing palettes, the product provides controls as background images without text equivalents.
• In Manage Brand, the Template, Theme, and Branded Surfaces image elements do not have alt attributes.

Authored Content (HTML): The product does not allow an author to provide alternative text for most non-text content in authored HTML. For example, when an author adds a photo in a Page project, the product does not allow the author to provide alternative text for the photo.

Authored Content (Video): This requirement is not applicable to an authored MP4 video file.

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

• 9.2.3 (Web)
• 10.2.3 (non-web document)
• 11.2.1.3 (Software)
• 11.2.2.3 (Closed Software) – Does not apply
• 11.6.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

2017 Section 508

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

Web: Does Not Support

Authored Content (HTML): Does Not Support

Authored Content (Video): Does Not Support

Authored Content (HTML): The product allows the author to create an HTML video player, which does not provide a mechanism for displaying closed captions.

Authored Content (Video): The product does not enable an author to provide captions for authored content.

1.2.3 Audio Description or Media Alternative(Prerecorded) (Level A)

Also applies to:
EN 301 549 Criteria

• 9.2.4 (Web)
• 10.2.4 (non-web document)
• 11.2.1.4 (Software)
• 11.2.2.4 (Closed Software)
• 11.6.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

Authored Content (HTML): Supports with Exceptions

Authored Content (Video): Supports with Exceptions

Web: Exceptions include:

• The Jeremiah Pitch demo video, the end of the video contains an image of text that is not conveyed through a nonvisual alternative.

Authored Content (HTML): Exceptions include:

• The product does not allow the author to embed a video player where users can switch to an alternate audio track with audio description.

Authored Content (Video): Exceptions include:

• The product does not allow the author to add a second, alternate audio track with audio description.

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

• 9.2.8 (Web)
• 10.2.8 (non-web document)
• 11.2.1.8 (Software)
• 11.2.2.8 (Closed Software) – Does not apply
• 11.6.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

Authored Content (HTML): Supports

Authored Content (Video): Supports

Web: Exceptions include:

• In the Share function for a new video, the reading order of the Create Link, Download, and on-off switch controls does not follow the logical visual order.
• In the Post and Video editing screens, the drawing canvas and related controls fall in between the tab items (“Design”, “Layout”, etc.) and the palette that they control.

Authored Content (HTML): The product allows authors the ability to present content in a meaningful sequence.

Authored Content (Video): The product allows authors the ability to present content, such as a textual captioning track, in a meaningful sequence.

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

• 9.2.9 (Web)
• 10.2.9 (non-web document)
• 11.2.1.9 (Software)
• 11.2.2.9 (Closed Software) – Does not apply
• 11.6.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

Authored Content (HTML): Supports

Authored Content (Video): Supports

Authored Content (HTML): Authors can ensure that content meets this criterion.

Authored Content (Video): Authors can ensure that content meets this criterion.

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

• 9.2.11 (Web)
• 10.2.11 (non-web document)
• 11.2.1.11 (Software)
• 11.2.2.11 (Closed Software) – Does not apply
• 11.6.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

Authored Content (HTML): Supports

Authored Content (Video): Supports

Web: The product does not include audio that plays automatically.

Authored Content (HTML): Authored content does not contain audio that plays automatically.

Authored Content (Video): Authored content does not contain audio that plays automatically.

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

• 9.2.16 (Web)
• 10.2.16 (non-web document)
• 11.2.1.16 (Software)
• 11.2.2.16 (Closed Software) – Does not apply
• 11.6.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

Authored Content (HTML): Supports

Authored Content (Video): Supports

Web: Exceptions include:

• In Page editing, focus is trapped on a document container.

Authored Content (HTML): Authored content does not include keyboard traps.

Authored Content (Video): Authored content does not have focusable elements.

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

• 9.2.18 (Web)
• 10.2.18 (non-web document)
• 11.2.1.18 (Software)
• 11.2.2.18 (Closed Software) – Does not apply
• 11.6.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

Authored Content (HTML): Supports

Authored Content (Video): Supports

Web: Exceptions include:

• The Glideshow explanation video appears in parallel with other content, starts automatically, plays for more than five seconds, and does not provide a mechanism for the user to halt it.

Authored Content (HTML): Authors can ensure that content meets this criterion.

Authored Content (Video): Authored content does not include elements which automatically move, blink, scroll, or auto-update.

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

• 9.2.21 (Web)
• 10.2.21 (non-web document)
• 11.2.1.21 (Software) - Does not apply
• 11.2.2.21 (Closed Software) – Does not apply
• 11.6.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

2017 Section 508

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

Web: Does Not Support

Authored Content (HTML): Supports

Authored Content (Video): Supports

Authored Content (HTML): The product allows the author to provide title text for each Post, Page, and Video.

Authored Content (Video): Authored content is not capable of containing a page title.

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

• 9.2.22 (Web)
• 10.2.22 (non-web document)
• 11.2.1.22 (Software)
• 11.2.2.22 (Closed Software) – Does not apply
• 11.6.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

Authored Content (HTML): Supports with Exceptions

Authored Content (Video): Supports

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

• In project editing screens, some dialogs do not receive focus automatically nor do they follow next in the tab order.

Authored Content (HTML): Authors can ensure that most content meets this criterion. Exceptions include:

• When authors choose to display their branded header and footer on an authored Page, the header and footer both fall at the bottom of the page in focus order.

Authored Content (Video): Authored content does not have focusable elements.

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

• 9.2.23 (Web)
• 10.2.23 (non-web document)
• 11.2.1.23 (Software)
• 11.2.2.23 (Closed Software) – Does not apply
• 11.6.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

Authored Content (HTML): Supports with Exceptions

Authored Content (Video): Supports

Web: Exceptions include:

• In Manage Brand, two “See all” links contain the same text with different purposes, and these links are not inside programmatic context that conveys the purpose.

Authored Content (HTML): Exceptions include:

• The link with accessible name “Share” does not convey that this is a Facebook sharing link, and the product does not allow the user to override this text.

Authored Content (Video): Authored content does not contain links.

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

• 9.2.30 (Web)
• 10.2.30 (non-web document)
• 11.2.1.30 (Software)
• 11.2.2.30 (Closed Software) – Does not apply
• 11.6.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

Authored Content (HTML): Supports

Authored Content (Video): Supports

Authored Content (Video): Authored content is not capable of containing user interface components.

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

• 9.2.34 (Web)
• 10.2.34 (non-web document)
• 11.2.1.34 (Software)
• 11.2.2.34 (Closed Software) – Does not apply
• 11.6.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

Authored Content (HTML): Supports

Authored Content (Video): Supports

Web: Exceptions include:

• When adding text to a Post, a dialog contains a single text field with no visible label.
• In Publish, labels and instructions for “Pick a category*” do not explain that the asterisk signifies a required field.

Authored Content (HTML): Authored content does not contain input controls that would require labels and instructions.

Authored Content (Video): Authored content is not capable of containing user interface components that would require labels or instructions.

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

• 9.2.38 (Web)
• 10.2.38 (non-web document)
• 11.2.1.38 (Software)
• 11.2.2.38 (Closed Software) – Does not apply
• 11.6.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

2017 Section 508

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

Web: Does Not Support

Authored Content (HTML): Supports with Exceptions

Authored Content (Video): Supports

Authored Content (HTML): Exceptions include:

• The user’s branding logo link does not have an accessible name.
• In the video page, the Appreciate control does not have a role.

Authored Content (Video): Authored content is not capable of containing user interface components.

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

• 9.2.6 (Web)
• 10.2.6 (non-web document)
• 11.2.1.6 (Software)
• 11.2.2.6 (Closed Software) – Does not apply
• 11.6.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

Authored Content (HTML): Does Not Support

Authored Content (Video): Does Not Support

Web: Exceptions include:

In the Jeremiah Pitch demo video, the default audio track conveys most of the visual information, but the end of the video contains an image of text that is not conveyed through audio description.

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

• 9.2.13 (Web)
• 10.2.13 (non-web document)
• 11.2.1.13 (Software)
• 11.2.2.13 (Closed Software)
• 11.6.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

2017 Section 508

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

Web: Does Not Support

Authored Content (HTML): Supports with Exceptions

Authored Content (Video): Supports

Authored Content (HTML): Exceptions include:

• When an author creates a title and subtitle that each occupy two lines at default zoom level, and the user zooms their browser until text is 200% of default size, then the subtitle is cut off.
• When a video page is enlarged to 200%, the Embed function is not available.

Authored Content (Video): Authored content only contains text exempted by the criterion.

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

• 9.2.14 (Web)
• 10.2.14 (non-web document)
• 11.2.1.14 (Software)
• 11.2.2.14 (Closed Software) – Does not apply
• 11.6.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

Authored Content (HTML): Supports

Authored Content (Video): Supports

Web: The product provides pre-rendered images of text as examples of content optimized for social media posts. These third-party social media platforms are not capable of presenting plain text overlaid on post images, so an “essential function” exception is allowed.

Authored Content (HTML): The product creates HTML pages which do not contain images of text. The product also creates standalone JPEG images of text optimized for social media posts, and the JPEG format is not capable of encoding a plain text layer.

Authored Content (Video): Authored content is not capable of presenting text in a wide variety of styles.

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

• 9.2.25 (Web)
• 10.2.25 (non-web document)
• 11.2.1.25 (Software)
• 11.2.2.25 (Closed Software) – Does not apply
• 11.6.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

Authored Content (HTML): Supports

Authored Content (Video): Supports

Web: Headings and labels are descriptive.

Authored Content (HTML): Authors can ensure that content meets this criterion.

Authored Content (Video): Authors can ensure that content meets this criterion.

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

• 9.2.26 (Web)
• 10.2.26 (non-web document)
• 11.2.1.26 (Software)
• 11.2.2.26 (Closed Software) – Does not apply
• 11.6.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

Authored Content (HTML): Supports with Exceptions

Authored Content (Video): Supports

Web: The keyboard focus indicator is generally visible. Exceptions include:

• After activating the “What can I make with Spark?” link, all homepage content remains tab focusable although it is visually hidden behind a takeover.
• In the homepage, when the edit control of a Post project gains focus.

Authored Content (HTML): The keyboard focus indicator is generally visible. Exceptions include:

• When a user tabs to the video player frame or player controls while the video content is not playing.

Authored Content (Video): Authored content does not have focusable elements.

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

• 9.2.32 (Web)
• 10.2.32 (non-web document) – Does not apply
• 11.2.1.32 (Software) – Does not apply
• 11.2.2.32 (Closed Software) – Does not apply
• 11.6.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

2017 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

Web: Supports with Exceptions

Authored Content (HTML): Supports

Authored Content (Video): Supports

Web: Exceptions include:

• In the Start from Scratch dialog for a Post project, the X icon has accessible name “Ok”, elsewhere it has accessible name “Close”.

Authored Content (Video): This criterion does not apply to non-web documents.

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

• 9.2.36 (Web)
• 10.2.36 (non-web document)
• 11.2.1.36 (Software)
• 11.2.2.36 (Closed Software) – Does not apply
• 11.6.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

Authored Content (HTML): Supports

Authored Content (Video): Supports

Web: The product does not process legal commitments or financial transactions. Changes to user-controllable data are reversible.

Authored Content (Video): Authored content does not process legal commitments or financial transactions, or modify user-controllable data.

302.2 With Limited Vision

Web: Does Not Support

Authored Content (HTML): Does Not Support

Authored Content (Video): Supports

Web: For users with limited vision who rely on platform accessibility features, most core functions of the product are not functional. For example, when a user who relies on 200% browser zoom edits a Post project, several controls are offscreen and scrolling is not available. As another example, when a user who relies on certain browser high contrast settings edits a Page project, the controls for adding content are not visible.

Authored Content (HTML): When an author uses the product to create HTML, most content of the HTML is not available for users who rely on certain browser high contrast settings. For example, the HTML page scrollbar, the video player controls, and most images are not visible.

Authored Content (Video): Using the product, authors can create an MP4 video file which allows users to make use of limited vision.

302.3 Without Perception of Color

Web: Supports with Exceptions

Authored Content (HTML): Supports

Authored Content (Video): Supports

Web: Most functions of the product are functional without perception of color; however, some functions require color perception. For example, most error messages, such as the error message for the link field in Add an Embedded Video, require color perception to recognize that they are errors.

Authored Content (HTML): Using the product, authors can create HTML which does not require user perception of color.

Authored Content (Video): Using the product, authors can create an MP4 video file which does not require user perception of color.

302.4 Without Hearing

Web: Supports with Exceptions

Authored Content (HTML): Supports with Exceptions

Authored Content (Video): Does Not Support

Web: Most functions of the product are functional without hearing. However, in most prerecorded video content with synchronized audio, there is important audio-only content not conveyed through captions. For example, in the Jeremiah Pitch demo video, there is a spoken audio track but no means of displaying captions.

Authored Content (HTML): Using the product, authors can create HTML where most content is functional without hearing. However, the HTML video player does not enable playback of closed captions.

Authored Content (Video): The product does not allow authors to create an MP4 video file with embedded closed captions.

302.5 With Limited Hearing

Web: Supports with Exceptions

Authored Content (HTML): Supports with Exceptions

Authored Content (Video): Does Not Support

Web: Most functions of the product are functional with limited hearing. However, in most prerecorded video content with synchronized audio, there is important audio-only content not conveyed through captions. For example, in the Jeremiah Pitch demo video, there is a spoken audio track, but no means of displaying captions.

Authored Content (HTML): Using the product, authors can create HTML where most content is functional with limited hearing. However, the HTML video player does not enable playback of closed captions.

Authored Content (Video): The product does not allow authors to create an MP4 video file with embedded closed captions.

302.6 Without Speech

Web: Supports

Authored Content (HTML): Supports

Authored Content (Video): Supports

Web: The product allows a user to record sound, including speech, for the audio track of a video. Adapting this feature for use without speech would be a fundamental alteration. Otherwise, the product does not require speech input.

Authored Content (HTML): Using the product, authors can create HTML which does not require speech input.

Authored Content (Video): Using the product, authors can create an MP4 video file which does not require speech input.

302.7 With Limited Manipulation

Web: Does Not Support

Authored Content (HTML): Supports with Exceptions

Authored Content (Video): Supports

Web: Most functions of the product are not functional for users with limited manipulation who rely on keyboard access, because actionable controls either do not receive keyboard focus or do not display a visual indication of keyboard focus. For example, on the homepage, the Create New menu does not receive keyboard focus when tabbing, and the edit control of a Post project does not have a visual indication of focus.

Authored Content (HTML): Using the product, authors can create HTML where most of the actionable controls are functional for users with limited manipulation who rely on keyboard access. To locate a control, a sighted keyboard-only user can use a standard keyboard function to scroll down, after which tabbing reaches any actionable controls that are visible in the browser viewport. However, tabbing skips past all controls that are not currently in the viewport; this is non-standard behavior without a clear mechanism for users to learn it, so it is not equivalent facilitation.

Authored Content (Video): Using the product, authors can create an MP4 video file which is functional with limited manipulation.

302.8 With Limited Reach and Strength

Web: Supports

Authored Content (HTML): Supports

Authored Content (Video): Supports

Web: The product is functional with limited reach and limited strength.

Authored Content (HTML): Using the product, authors can create HTML which is functional with limited reach and limited strength.

Authored Content (Video): Using the product, authors can create an MP4 video file which is functional with limited reach and limited strength.

302.9 With Limited Language, Cognitive, and Learning Abilities

Web: Supports with Exceptions

Authored Content (HTML): Supports with Exceptions

Authored Content (Video): Supports

Web: The product provides features for simpler, easier use by individuals with limited cognitive, language, and learning abilities. For example, the product offers reduced technical jargon; consistent use of language; and options to create content through examples, templates, or “from scratch” to support different learning styles. However, some features of the product place more demands than necessary on users’ reasoning, memory, or decision making. For example, when the user creates or edits a video and the tutorial dialog appears, neither the browser title nor heading text helps the user understand that they are now in the video editing function. As another example, most error messages in the product do not identify the item that is in error, and do not clearly describe the error.

Authored Content (HTML): Using the product, authors can create HTML in which most features are functional for users with limited language, cognitive, and learning abilities. However, the product does not provide programmatic indication of the language of the page or parts of the page, which impedes speech synthesis for users with limited language abilities.

Authored Content (Video): Using the product, authors can create an MP4 video file which is functional for users with limited language, cognitive, and learning abilities.

502.2.2 No Disruption of Accessibility Features

Supports

The product does not disrupt platform accessibility features.

502.3 Accessibility Services

See 502.3.1-502.3.14

502.3.1 Object Information

Does Not Support

Most core functions of the product contain functional components which lack role, state, or accessible name information. For example, in content editing pages the product’s logo behaves as a navigation component which exits the page, but this component has no role and no accessible name. As another example, the on-off state of switch controls is not announced in Share screens and in Settings.

502.3.2 Modification of Object Information

Supports with Exceptions

When states and properties of an object in the product can be modified by users in general, in most cases these states and properties can be modified by assistive technology; however, some cannot be modified. For example, in a Post editing screen, users in general can mark a text layer as selected, but the text layer cannot be marked as selected by assistive technology.

502.3.3 Row, Column, and Headers

Not Applicable

The product does not contain data tables.

502.3.4 Values

Supports with Exceptions

The values of most input controls in the product are programmatically determinable, but some values are not. For example, in a Post editing screen, users in general can observe the modifiable x-y locations of the corners of a text layer, but these values are not announced by assistive technology.

502.3.5 Modification of Values

Supports with Exceptions

When the value of an input control in the product can be modified by users in general, in most cases the value can be modified by assistive technology; however, some values cannot be modified. For example, in a Post editing screen, users in general can modify the x-y locations of the corners of a text layer, but these values cannot be modified by assistive technology.

502.3.6 Label Relationships

Does Not Support

Most form fields in the product do not have a programmatic label. For example, when creating a Post from scratch, the “What do you want to say?” field has no programmatic label.

502.3.7 Hierarchical Relationships

Supports with Exceptions

Some containers are not programmatically determinable. For example, in Video editing, the “Drag and drop text” instructional dialog lacks semantics to indicate its boundaries.

502.3.8 Text

Supports

Text content, text attributes, and text boundaries are programmatically determinable.

502.3.9 Modification of Text

Supports

The text content of text input controls in the product can be modified by assistive technology.

502.3.10 List of Actions

Supports with Exceptions

Most actionable controls provide a common role, such as “button”, which informs the user what actions are available; however, some actionable controls do not provide a programmatic role nor a list of actions. For example, Post layout options do not provide a role nor a list of actions.

502.3.11 Actions on Objects

Supports with Exceptions

Most actionable controls can be activated by assistive technology; however, some controls, such as Video layout options, are hidden from assistive technology and cannot be activated.

502.3.12 Focus Cursor

Supports with Exceptions

Some controls in the product can gain focus, but do not indicate the focus location visually. For example, in the homepage, when the edit control of a Post project gains focus, the control does not have a visual indication of focus.

502.3.13 Modification of Focus Cursor

Supports

When a user can focus or change selection state of a control in the product via keyboard, then the focus or selection state can also be changed programmatically.

502.3.14 Event Notification

Supports

When components in the product change their programmatic states and values, the changes are available to assistive technology.

502.4 Platform Accessibility Features

Not Applicable

The product is not platform software.

503.3 Alternative User Interfaces

Not Applicable

The product does not provide an alternative user interface that functions as assistive technology.

503.4 User Controls for Captions and Audio Description

See 503.4.1-503.4.2

503.4.1 Caption Controls

Does Not Support

In most video with synchronized audio in the product, no captions or caption controls are provided.

503.4.2 Audio Description Controls

Does Not Support

In most video with synchronized audio in the product, no audio descriptions or audio description controls are provided.

4.2.2 Usage with limited vision

Web: Does Not Support

Authored Content (HTML): Does Not Support

Authored Content (Video): Supports

Web: For users with limited vision who rely on platform accessibility features, most core functions of the product are not functional. For example, when a user who relies on 200% browser zoom edits a Post project, several controls are offscreen and scrolling is not available. As another example, when a user who relies on certain browser high contrast settings edits a Page project, the controls for adding content are not visible.

Authored Content (HTML): When an author uses the product to create HTML, most content of the HTML is not available for users who rely on certain browser high contrast settings. For example, the HTML page scrollbar, the video player controls, and most images are not visible.

Authored Content (Video): Using the product, authors can create an MP4 video file which allows users to make use of limited vision.

4.2.3 Usage without perception of colour

Web: Supports with Exceptions

Authored Content (HTML): Supports

Authored Content (Video): Supports

Web: Most functions of the product are functional without perception of color; however, some functions require color perception. For example, most error messages, such as the error message for the link field in Add an Embedded Video, require color perception to recognize that they are errors.

Authored Content (HTML): Using the product, authors can create HTML which does not require user perception of color.

Authored Content (Video): Using the product, authors can create an MP4 video file which does not require user perception of color.

4.2.4 Usage without hearing

Web: Supports with Exceptions

Authored Content (HTML): Supports with Exceptions

Authored Content (Video): Does Not Support

Web: Most functions of the product are functional without hearing. However, in most prerecorded video content with synchronized audio, there is important audio-only content not conveyed through captions. For example, in the Jeremiah Pitch demo video, there is a spoken audio track but no means of displaying captions.

Authored Content (HTML): Using the product, authors can create HTML where most content is functional without hearing. However, the HTML video player does not enable playback of closed captions.

Authored Content (Video): The product does not allow authors to create video with closed captions.

4.2.5 Usage with limited hearing

Web: Supports with Exceptions

Authored Content (HTML): Supports with Exceptions

Authored Content (Video): Does Not Support

Web: Most functions of the product are functional with limited hearing. However, in most prerecorded video content with synchronized audio, there is important audio-only content not conveyed through captions. For example, in the Jeremiah Pitch demo video, there is a spoken audio track but no means of displaying captions.

Authored Content (HTML): Using the product, authors can create HTML where most content is functional with limited hearing. However, the HTML video player does not enable playback of closed captions.

Authored Content (Video): The product does not allow authors to create an MP4 video file with embedded closed captions.

4.2.6 Usage without vocal capability

Web: Supports

Authored Content (HTML): Supports

Authored Content (Video): Supports

Web: The product allows a user to record sound, including speech, for the audio track of a video. Adapting this feature for use without speech would be a fundamental alteration. Otherwise, the product does not require speech input.

Authored Content (HTML): Using the product, authors can create HTML which does not require speech input.

Authored Content (Video): Using the product, authors can create an MP4 video file which does not require speech input

4.2.7 Usage with limited manipulation or strength

Web: Does Not Support

Authored Content (HTML): Supports with Exceptions

Authored Content (Video): Supports

Web: Most functions of the product are not functional for users with limited manipulation who rely on keyboard access, because actionable controls either do not receive keyboard focus or do not display a visual indication of keyboard focus. For example, on the homepage, the Create New menu does not receive keyboard focus when tabbing, and the edit control of a Post project does not have a visual indication of focus.

Authored Content (HTML): Using the product, authors can create HTML where most of the actionable controls are functional for users with limited manipulation who rely on keyboard access. To locate a control, a sighted keyboard-only user can use a standard keyboard function to scroll down, after which tabbing reaches any actionable controls that are visible in the browser viewport. However, tabbing skips past all controls that are not currently in the viewport; this is non-standard behavior without a clear mechanism for users to learn it, so it is not equivalent facilitation.

Authored Content (Video): Using the product, authors can create an MP4 video file which is functional with limited manipulation or limited strength.

4.2.8 Usage with limited reach

Web: Supports

Authored Content (HTML): Supports

Authored Content (Video): Supports

Web: The product is functional with limited reach.

Authored Content (HTML): Using the product, authors can create HTML which is functional with limited reach.

Authored Content (Video): Using the product, authors can create an MP4 video file which is functional with limited reach

4.2.9 Minimize photosensitive seizure

Web: Supports

Authored Content (HTML): Supports

Authored Content (Video): Supports

Web: Visual functions and content of the product minimize the potential for triggering photosensitive seizures.

Authored Content (HTML): Using the product, authors can create HTML which minimizes the potential for triggering photosensitive seizures.

Authored Content (Video): Using the product, authors can create an MP4 video file which minimizes the potential for triggering photosensitive seizures.

4.2.10 Usage with limited cognition

Web: Supports with Exceptions

Authored Content (HTML): Supports with Exceptions

Authored Content (Video): Supports

Web: The product provides features for simpler, easier use by individuals with limited cognitive abilities. For example, the product offers reduced technical jargon; consistent use of language; and options to create content through examples, templates, or “from scratch” to support different learning styles. However, some features of the product place more demands than necessary on users’ reasoning, memory, or decision making. For example, when the user creates or edits a video and the tutorial dialog appears, neither the browser title nor heading text helps the user understand that they are now in the video editing function. As another example, most error messages in the product do not identify the item that is in error, and do not clearly describe the error.

Authored Content (HTML): Using the product, authors can create HTML in which most features are functional for users with limited cognitive abilities. However, the product does not provide programmatic indication of the language of the page or parts of the page, which impedes speech synthesis for users with limited language abilities.

Authored Content (Video): Using the product, authors can create an MP4 video file which is functional for users with limited cognitive abilities.

4.2.11 Privacy

Web: Supports

Authored Content (HTML): Supports

Authored Content (Video): Supports

Web: When using product features that are provided for accessibility, users can maintain privacy of information in the product.

Authored Content (HTML): Using the product, authors can create HTML which conforms to this requirement.

Authored Content (Video): Using the product, authors can create an MP4 video file which conforms to this requirement.

5.2 Activation of accessibility features

Not Applicable

The product does not have accessibility features requiring activation.

5.3 Biometrics

Not Applicable

The product does not rely on biological characteristics.

5.4 Preservation of accessibility information during conversion

Not Applicable

The product does not convert information or communication.

5.5.1 Means of operation

Not Applicable

The product does not have operable parts.

5.5.2 Operable parts discernibility

Not Applicable

The product does not have operable parts.

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.

5.7 Key repeat

Not Applicable

The product relies on platform software to supply key repeat functionality.

5.8 Double-strike key acceptance

Not Applicable

The product does not, by itself, supply a keyboard or keypad.

5.9 Simultaneous user actions

Supports

Simultaneous user actions are not required to operate the product.

7.1.2 Captioning synchronization

Supports

When a third-party hosted video is embedded in the Page editing screen of the product and displays captions, the video player preserves synchronization between the audio and the corresponding captions.

7.1.3 Preservation of captioning

Does Not Support

When using the product to upload an MP4 video segment with a caption track, the product does not preserve the caption track in the downloadable video.

7.2.1 Audio description playback

Does Not Support

In most video with synchronized audio in the product, no audio descriptions or audio description controls are provided.

7.2.2 Audio description synchronization

Not Applicable

The product does not provide audio descriptions, so the synchronization requirement is not applicable.

7.2.3 Preservation of audio description

Does Not Support

When using the product to upload an MP4 video segment with two audio tracks, the product does not preserve both audio tracks in the downloadable video.

7.3 User controls for captions and audio description

Does Not Support

In most video with synchronized audio in the product, no captions, audio descriptions, or controls for captions and audio description are provided.

11.2.2 Software success criteria (closed functionality)

Not Applicable

11.3.2.3 Use of accessibility services

Supports

The product uses accessibility services of the browser platform.

11.3.2.4 Assistive technology

Not Applicable

The product is not assistive technology.

11.3.2.5 Object information

Does Not Support

Most core functions of the product contain functional components which lack role, state, or accessible name information. For example, in content editing pages the product’s logo behaves as a navigation component which exits the page, but this component has no role and no accessible name. As another example, the on-off state of switch controls is not announced in Share screens and in Settings.

11.3.2.6 Row, column, and headers

Not Applicable

The product does not contain data tables.

11.3.2.7 Values

Supports with Exceptions

The values of most input controls in the product are programmatically determinable, but some values are not. For example, in a Post editing screen, users in general can observe the modifiable x-y locations of the corners of a text layer, but these values are not announced by assistive technology.

11.3.2.8 Label relationships

Does Not Support

Most form fields in the product do not have a programmatic label. For example, when creating a Post from scratch, the “What do you want to say?” field has no programmatic label.

11.3.2.9 Parent-child relationships

Supports with Exceptions

Some containers are not programmatically determinable. For example, in Video editing, the “Drag and drop text” instructional dialog lacks semantics to indicate its boundaries.

11.3.2.10 Text

Supports

Text content, text attributes, and text boundaries are programmatically determinable.

11.3.2.11 List of available actions

Supports with Exceptions

Most actionable controls provide a common role, such as “button”, which informs the user what actions are available; however, some actionable controls do not provide a programmatic role nor a list of actions. For example, Post layout options do not provide a role nor a list of actions.

11.3.2.12 Execution of available actions

Supports with Exceptions

Most actionable controls can be activated by assistive technology; however, some controls, such as Video layout options, are hidden from assistive technology and cannot be activated.

11.3.2.13 Tracking of focus and selection attributes

Supports with Exceptions

Some controls in the product can gain focus, but do not indicate the focus location visually. For example, in the homepage, when the edit control of a Post project gains focus, the control does not have a visual indication of focus.

11.3.2.14 Modification of focus and selection attributes

Supports

When a user can focus or change selection state of a control in the product via keyboard, then the focus or selection state can also be changed programmatically.

11.3.2.15 Change notification

Supports

When components in the product change their programmatic states and values, the changes are available to assistive technology.

11.3.2.16 Modifications of states and properties

Supports with exceptions

When states and properties of an object in the product can be modified by users in general, in most cases these states and properties can be modified by assistive technology; however, some cannot be modified. For example, in a Post editing screen, users in general can mark a text layer as selected, but the text layer cannot be marked as selected by assistive technology.

11.3.2.17 Modifications of values and text

Supports with exceptions

When the value or text of an input control in the product can be modified by users in general, in most cases the value or text can be modified by assistive technology; however, some cannot be modified. For example, in a Post editing screen, users in general can modify the x-y locations of the corners of a text layer, but these values cannot be modified by assistive technology.

11.4.1 User control of accessibility features

Not Applicable

The product is not platform software.

11.4.2 No disruption of accessibility features

Supports

The product does not disrupt platform accessibility features.

11.5 User preferences

Not Applicable

The product is a web application, which is isolated from its underlying platforms.

11.6.2 Accessible content creation (if not authoring tool, enter “not applicable”)

See WCAG 2.0 section.

See information in WCAG section

11.6.3 Preservation of accessibility information in transformations

Does Not Support

When using the product to upload an MP4 video segment with a caption track or two audio tracks, the product does not preserve the caption track or two audio tracks in the downloadable video.

11.6.4 Repair assistance

Not Applicable

The product does not provide accessibility checking functions, so the Repair Assistance requirement is not applicable.

11.6.5 Templates

Does Not Support

Most templates in the product do not allow content creation that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0. For example, the Page editor provides a single template in which most controls are not keyboard operable in a typical vertical scrolling page. As another example, in the Post editor, the product does not identify which Style Suggestions are conformant to WCAG success criterion 1.4.3 Contrast (Minimum).