Name of Product/Version: VoiceThread Version 2.4) Report ...

VoiceThread Accessibility ConformanceReport

International Edition(Based on VPAT® Version 2.4)

Name of Product/Version: VoiceThread

Report Date: March 2021

Product Description: Asynchronous conversations arounddigital media using voice, video, and/or text.

Contact Information: [email protected]

Evaluation Methods Used:Primary: NVDA in Chrome, Keyboard onlySecondary: Jaws in Chrome, NVDA in Firefox, VoiceOver inSafari

Applicable Standards/GuidelinesThis report covers the degree of conformance for the following accessibility standard/guidelines:

Standard/Guideline Included In Report

Web Content Accessibility Guidelines 2.1 Level A - Yes

Level AA - Yes

Level AAA - No

Revised Section 508 standards published January 18, 2017 andcorrected January 22, 2018 Yes

EN 301 549 Accessibility requirements suitable for public

procurement of ICT products and services in Europe, - V3.1.1

(2019-11)

Yes

Page 1 of 32

https://www.w3.org/TR/WCAG21

https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines

https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines

https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.01.01_60/en_301549v030101p.pdf

https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.01.01_60/en_301549v030101p.pdf

TermsThe terms used in the Conformance Level information are defined as follows:

● Supports: The functionality of the product has at least one method that meetsthe criterion without known defects or meets with equivalent facilitation.

● Partially Supports: Some functionality of the product does not meet thecriterion.

● Does Not Support: The majority of product functionality does not meet thecriterion.

● Not Applicable: The criterion is not relevant to the product.● Not Evaluated: The product has not been evaluated against the criterion.

WCAG 2.1 ReportTables 1 and 2 also document conformance with:

● EN 301 549: Chapter 9 - Web, Sections 10.1-10.4 of Chapter 10 - Non-Webdocuments, and Sections 11.1-11.4 and 11.8.2 of Chapter 11 - Non-WebSoftware (open and closed functionality), and Sections 12.1.2 and 12.2.4 ofChapter 12 – Documentation

● Revised Section 508: Chapter 5 – 501.1 Scope, 504.2 Content Creation orEditing, and Chapter 6 – 602.3 Electronic Support Documentation.

Note: When reporting on conformance with the WCAG 2.1 Success Criteria, they arescoped for full pages, complete processes, and accessibility-supported ways of usingtechnology as documented in the WCAG 2.0 Conformance Requirements.

Page 2 of 32

https://www.w3.org/TR/WCAG20/#conformance-reqs

Table 1: Success Criteria, Level ANotes:

Different from 2018 VPAT

New to this VPAT version

Question/Uncertain

Criteria Conformance Level Remarks andExplanations

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

● 9.1.1.1 (Web)● 10.1.1.1 (Non-web document)● 11.1.1.1.1 (Open Functionality

Software)● 11.1.1.1.2 (Closed Functionality

Software)● 11.8.2 (Authoring Tool)● 12.1.2 (Product Docs)● 12.2.4 (Support Docs)

Revised Section 508● 501 (Web)(Software)● 504.2 (Authoring Tool)● 602.3 (Support Docs)

Standard app: PartiallySupports

Universal app: PartiallySupports

Mobile app: Partiallysupports

Standard and mobileapplications are missingclear labels for someinformational and buttonicons.

Screen reader users are

encouraged to use the

Universal interface. Slide

titles and descriptions can

provide some context,

however alt text options

are not yet available in

authoring tools

1.2.1 Audio-only and Video-only (Prerecorded)(Level A)

Also applies to:EN 301 549 Criteria


Software)● 11.1.2.1.2.1 and 11.1.2.1.2.2 (Closed

Software)● 11.8.2 (Authoring Tool)● 12.1.2 (Product Docs)● 12.2.4 (Support Docs)


Standard app: Supports

Universal app: Supports

Mobile app: Supports

1.2.2 Captions (Prerecorded) (Level A)Also applies to:

Standard app: Supports VoiceThread provides

captioning as an orderable

Page 3 of 32

http://www.w3.org/TR/WCAG20/#text-equiv-all

http://www.w3.org/TR/WCAG20/#media-equiv-av-only-alt

http://www.w3.org/TR/WCAG20/#media-equiv-captions

EN 301 549 Criteria● 9.1.2.2 (Web)● 10.1.2.2 (Non-web document)● 11.1.2.2 (Open Functionality

Software)● 11.1.2.2 (Closed Software)● 11.8.2 (Authoring Tool)● 12.1.2 (Product Docs)● 12.2.4 (Support Docs)


Universal app: Partiallysupports


option (both free and paid

options). Once service is

requested, captions are

available in the standard

site and transcripts are

available in Universal

where applicable.

The standard application is

more suited for Deaf and

hard-of-hearing users.

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



Software)● 11.1.2.3.2 (Closed Software)● 11.8.2 (Authoring Tool)● 12.1.2 (Product Docs)● 12.2.4 (Support Docs)





Universal: Users canupload videos that containaudio description providedfile size meetsVoiceThread capacity. Ifusers need to synchronizepreexisting media they willneed to utilize externalediting software.

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




Standard app: Partiallysupports


Mobile app: PartiallySupports

Standard: Some dialogs

may require more context,

and the Manager interface

has minor exceptions in

sub-tab navigation.

Mobile: Not all user

actions are labelled

appropriately for screen

readers.

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



Mobile: The majority of

content is in an

appropriate sequence but

Page 4 of 32

http://www.w3.org/TR/WCAG20/#media-equiv-audio-desc

http://www.w3.org/TR/WCAG20/#media-equiv-audio-desc

http://www.w3.org/TR/WCAG20/#content-structure-separation-programmatic

http://www.w3.org/TR/WCAG20/#content-structure-separation-sequence





work on the sequence is

needed in the player.

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

● 9.1.3.3 (Web)● 10.1.3.3 (Non-web document)● 11.1.3.3 (Open Functionality






Standard and mobile: Not

all buttons and links

identified solely by an icon

have appropriate labels to

be identified meaningfully

by screen readers.

The universal application

is more suited for blind

and visually impaired

users.

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







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

● 9.1.4.2 (Web)● 10.1.4.2 (Non-web document)


Universal app: N/A


In Universal contentplayback does notautomatically begin uponpage load.

Page 5 of 32

http://www.w3.org/TR/WCAG20/#content-structure-separation-understanding

http://www.w3.org/TR/WCAG20/#visual-audio-contrast-without-color

http://www.w3.org/TR/WCAG20/#visual-audio-contrast-dis-audio

● 11.1.4.2 (Open FunctionalitySoftware)

● 11.1.4.2 (Closed Software)● 11.8.2 (Authoring Tool)● 12.1.2 (Product Docs)● 12.2.4 (Support Docs)


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







Standard: The standardapplication providescustom keyboardshortcuts to interact withthe player, but not allsurrounding content canbe accessed using akeyboard.

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







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


Software)

Standard app: Does notsupport

Universal app: Notapplicable

Standard and Mobile: Wecurrently do not provide away for users to customizeor disable customkeyboard shortcuts.

Page 6 of 32

http://www.w3.org/TR/WCAG20/#keyboard-operation-keyboard-operable

http://www.w3.org/TR/WCAG20/#keyboard-operation-trapping

https://www.w3.org/TR/WCAG21/#character-key-shortcuts

● 11.2.1.4.2 (Closed Software)● 11.8.2 (Authoring Tool)● 12.1.2 (Product Docs)● 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Mobile app: Does notsupport

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




Standard app: Notapplicable


Mobile app: Notapplicable

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




Standard app:

Partially supports

Universal app:

Partially supports

Mobile app:

Partially supports

In the standard and

mobile applications,

someone saving a

comment while a user has

a VoiceThread open

results in that comment

appearing on the page

automatically.

Screen reader users are

encouraged to use the

Universal interface.

Universal: Only exception

is GIF files

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






Page 7 of 32

http://www.w3.org/TR/WCAG20/#time-limits-required-behaviors

http://www.w3.org/TR/WCAG20/#time-limits-pause

http://www.w3.org/TR/WCAG20/#seizure-does-not-violate


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

● 9.2.4.1 (Web)● 10.2.4.1 (Non-web document) – Does

not apply● 11.2.4.1 (Open Functionality

Software) – Does not apply● 11.2.4.1 (Closed Software) – Does not

apply● 11.8.2 (Authoring Tool)● 12.1.2 (Product Docs)● 12.2.4 (Support Docs)

Revised Section 508● 501 (Web)(Software) – Does not apply

to non-web software● 504.2 (Authoring Tool)● 602.3 (Support Docs) – Does not apply

to non-web docs




Standard: Users canbypass blocks of contentto access the main contentof the application using ascreen reader, but notwhen using keyboard-onlynavigation.

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


Software) - Does not apply● 11.2.4.2 (Closed Software) – Does not




Universal: Partiallysupports


Standard and universalapplications provide pagetitles but do not alwaysprovide meaningful titlesto distinguish betweenpages within eachapplication.

The mobile applicationprovides visible page titlesbut these are notrecognized by screenreaders.

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


Software)● 11.2.4.3 (Closed Software)


Universal: Supports

Mobile: Partially supports

In the standard andmobile applications thefocus order when usingkeyboard navigation maynot always follow a logicalorder.

Page 8 of 32

http://www.w3.org/TR/WCAG20/#navigation-mechanisms-skip

http://www.w3.org/TR/WCAG20/#navigation-mechanisms-title

http://www.w3.org/TR/WCAG20/#navigation-mechanisms-focus-order

● 11.8.2 (Authoring Tool)● 12.1.2 (Product Docs)● 12.2.4 (Support Docs)


Screen reader andkeyboard users areencouraged to use theUniversal interface. Note:Browser/screen readerand OS combination caninfluence focusfunctionality..

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


Software)● 11.2.4.4 (Closed Software● 11.8.2 (Authoring Tool)● 12.1.2 (Product Docs)● 12.2.4 (Support Docs)





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




Standard app: Partiallysupports.


Mobile app: Does notsupport.

Standard: Panning on aslide while zoomedrequires mouse dragging.

Mobile: You can zoom inand out with fingergestures but there are no+ and - buttons toreplicate this behavior.

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


Software)● 11.2.5.2 (Closed Software)● 11.8.2 (Authoring Tool)● 12.1.2 (Product Docs)




Page 9 of 32

http://www.w3.org/TR/WCAG20/#navigation-mechanisms-refs

https://www.w3.org/TR/WCAG21/#pointer-gestures

https://www.w3.org/TR/WCAG21/#pointer-cancellation

● 12.2.4 (Support Docs)Revised Section 508 – Does not apply

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






Mobile: Partially supports

In the standard andmobile applications not allvisual labels are includedin the accessible name.

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




Standard app: Notapplicable.

Universal app: Notapplicable.


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




Standard app: Partiallysupports.



Standard: Marketing and

support pages are not

internationalized, but user

interfaces and tools are.

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

● 9.3.2.1 (Web)● 10.3.2.1 (Non-web document)




Page 10 of 32

https://www.w3.org/TR/WCAG21/#label-in-name

https://www.w3.org/TR/WCAG21/#motion-actuation

http://www.w3.org/TR/WCAG20/#meaning-doc-lang-id

http://www.w3.org/TR/WCAG20/#consistent-behavior-receive-focus

● 11.3.2.1 (Open FunctionalitySoftware)



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







Selecting a new language

in license default settings

automatically refreshes

the page. Changing default

setting from Standard to

Universal results in

automatic forwarding to

Universal interface.

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







Standard and mobileapplications provide visualmessaging of errors butthese are not alwaysannounced by screenreaders.

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


Software)




Page 11 of 32

http://www.w3.org/TR/WCAG20/#consistent-behavior-unpredictable-change

http://www.w3.org/TR/WCAG20/#minimize-error-identified

http://www.w3.org/TR/WCAG20/#minimize-error-cues



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


Software)● 11.4.1.1.2 (Closed Software) – Does

not apply● 11.8.2 (Authoring Tool)● 12.1.2 (Product Docs)● 12.2.4 (Support Docs)





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


Software)● 11.4.1.2.2 (Closed Software) – Not

required● 11.8.2 (Authoring Tool)● 12.1.2 (Product Docs)● 12.2.4 (Support Docs)





Standard and Mobile:Cannot navigate or accessall content using a screenreader in the mobile app.

Table 2: Success Criteria, Level AANotes:

Page 12 of 32

http://www.w3.org/TR/WCAG20/#ensure-compat-parses

http://www.w3.org/TR/WCAG20/#ensure-compat-rsv


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




Not applicable

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







Universal does not

support captions for all

user-generated content,

but does for video

content.

The standard application

is more suited for Deaf

and hard-of-hearing users.

Users can add audio track

to describe any video they

upload. Note: Utilizing

this method is considered

non-traditional and users

may be familiar. Users will

likely need to use external

editing software to create

synchronization between

existing captions with

existing media content.

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


Software)● 11.1.3.4 (Closed Software)




Page 13 of 32

http://www.w3.org/TR/WCAG20/#media-equiv-real-time-captions

http://www.w3.org/TR/WCAG20/#media-equiv-audio-desc-only

https://www.w3.org/TR/WCAG21/#orientation


Revised Section 508 – Does not apply1.3.5 Identify Input Purpose (Level AA 2.1 only)





Not applicable

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







Standard: The majority ofcontent does adhere tothis criteria with the fewexceptions of the footerlinks. Any other items thatdo not pass contrast havealternative elements thatdo adhere to this criterionthat achieve that sameaction.

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







Page 14 of 32

https://www.w3.org/TR/WCAG21/#identify-input-purpose

http://www.w3.org/TR/WCAG20/#visual-audio-contrast-contrast

http://www.w3.org/TR/WCAG20/#visual-audio-contrast-scale

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


Software)● 11.1.4.5.2 (Closed Software) – Does

not apply● 11.8.2 (Authoring Tool)● 12.1.2 (Product Docs)● 12.2.4 (Support Docs)





Authoring tools do notprovide a way to includealternative text. Usersmay utilize slidedescriptions and textcomments to describeimage. These methodsare not a truereplacement for ALT textattribute.

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




Standard app: Does notsupport



The standard app does notrequire horizontal scrollingwhen zoomed to 400%;however, the majority ofthe content is notaccessible when zoomedto this extent.

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







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


Software)

Standard: Supports

Universal: Supports

Mobile: Supports

Page 15 of 32

http://www.w3.org/TR/WCAG20/#visual-audio-contrast-text-presentation

https://www.w3.org/TR/WCAG21/#reflow

https://www.w3.org/TR/WCAG21/#non-text-contrast

https://www.w3.org/TR/WCAG21/#text-spacing


Revised Section 508 – Does not apply1.4.13 Content on Hover or Focus (Level AA 2.1only)








The standard applicationdoes adhere to thiscriteria when hoveringwith a mouse, but whenremoving focus on thiscontent using a keyboardthe additional contentremains visible.

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





Revised Section 508● 501 (Web)(Software) – Does not

apply to non-web software● 504.2 (Authoring Tool)● 602.3 (Support Docs) – Does not

apply to non-web docs




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


Software)● 11.2.4.6 (Closed Software)● 11.8.2 (Authoring Tool)● 12.1.2 (Product Docs)




Standard: Headings areprovided on the maincontent page making iteasier for users tonavigate to content, butadditional headings aremissing to provide easieraccess to supplementarycontent.

Page 16 of 32

https://www.w3.org/TR/WCAG21/#content-on-hover-or-focus

http://www.w3.org/TR/WCAG20/#navigation-mechanisms-mult-loc

http://www.w3.org/TR/WCAG20/#navigation-mechanisms-descriptive

● 12.2.4 (Support Docs)Revised Section 508

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

Universal: Authoring toolsprovided to create titlesand labels, however ifusers do not createheadings or labels thencontent may be unclear.

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







Standard: Visual focusmissing on mainnavigation and in player.

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








Standard: Marketing and

support pages are not

internationalized, but user

interfaces and tools are.

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



Software) – Does not apply




Page 17 of 32

http://www.w3.org/TR/WCAG20/#navigation-mechanisms-focus-visible

http://www.w3.org/TR/WCAG20/#meaning-other-lang-id

http://www.w3.org/TR/WCAG20/#consistent-behavior-consistent-locations

● 11.3.2.3 (Closed Software) – Does notapply




apply to non-web docs3.2.4 Consistent Identification (Level AA)








apply to non-web docs




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







3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)


Page 18 of 32

http://www.w3.org/TR/WCAG20/#consistent-behavior-consistent-functionality

http://www.w3.org/TR/WCAG20/#minimize-error-suggestions

http://www.w3.org/TR/WCAG20/#minimize-error-reversible







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


Software)● 11.4.1.3 (Closed Software) – Does not






In the standard andmobile apps we providevisual alerts but these arenot announced by screenreaders.

Table 3: Success Criteria, Level AAANotes: Not evaluated.

Page 19 of 32

https://www.w3.org/TR/WCAG21/#status-messages

Revised Section 508 Report

Notes:

Chapter 3: Functional Performance Criteria (FPC)Notes:


302.1 Without Vision




Standard and mobile:Not all content isaccessible using akeyboard or screenreader. Screen readerand keyboard users areencouraged to use theUniversal interface.

302.2 With Limited Vision




Standard and mobile:Not all content isaccessible using akeyboard or screenreader. Screen readerand keyboard users areencouraged to use theUniversal interface.

302.3 Without Perception of Color




302.4 Without Hearing




302.5 With Limited Hearing




302.6 Without Speech



Mobile app: Supports302.7 With Limited Manipulation Standard app: Supports

Page 20 of 32

https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines#302-functional-performance-criteria


Mobile app: Supports302.8 With Limited Reach and Strength Not applicable

302.9 With Limited Language, Cognitive, andLearning Abilities




Chapter 4: HardwareNotes: VoiceThread does not provide hardware, so this section does not apply.

Chapter 5: SoftwareNotes:

Criteria ConformanceLevel

Remarks andExplanations

501.1 Scope – Incorporation of WCAG 2.0 AA See WCAG 2.1 sectionSee information in WCAG 2.1section

502 Interoperability with Assistive TechnologyHeading cell – noresponse required

Heading cell – no responserequired

502.2.1 User Control of Accessibility Features


Universal app:Supports


502.2.2 No Disruption of Accessibility Features




502.3 Accessibility ServicesHeading cell – noresponse required


502.3.1 Object Information




Standard and mobile: Not allcontent is accessible using akeyboard and/or screenreader. Screen reader andkeyboard users areencouraged to use theUniversal interface.

Page 21 of 32

https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines#401-general


https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines#502-interoperability-assistive-technology

502.3.2 Modification of Object Information



Mobile app: Supports502.3.3 Row, Column, and Headers Not applicable

502.3.4 Values




502.3.5 Modification of Values




502.3.6 Label Relationships




Standard and mobile: Not allelements incorporate therequired accessible names tomake them accessible orclear to screen readers.

Screen reader and keyboardusers are encouraged to usethe Universal interface. SeeWCAG 2.4.6

502.3.7 Hierarchical Relationships




502.3.8 Text




502.3.9 Modification of Text



Page 22 of 32


502.3.10 List of Actions




Standard and mobile: Not allactions incorporate therequired accessible names tomake them clearlyunderstood to users usingscreen readers.

Screen reader and keyboardusers are encouraged to usethe Universal interface.

502.3.11 Actions on Objects




502.3.12 Focus Cursor




Standard: Visual focusmissing on main navigationand in player.

Keyboard users areencouraged to use theUniversal interface.

502.3.13 Modification of Focus Cursor




502.3.14 Event Notification




In the standard and mobileapps we provide visual alertsbut these are not announcedby screen readers.

Universal: The majority ofstatus messages can bepresented to users usingassistive technologies, withthe few exceptions of whenslides are added to a threadand when a slide’s details areedited.

502.4 Platform Accessibility FeaturesStandard app: Supports

Page 23 of 32



503 ApplicationsHeading cell – noresponse required


503.2 User Preferences Not applicable

503.3 Alternative User Interfaces Not applicableThis VPAT covers allVoiceThread interfaces withineach item.

503.4 User Controls for Captions and AudioDescription

Heading cell – noresponse required


503.4.1 Caption Controls




See WCAG 1.2.2/WCAG 1.2.5

503.4.2 Audio Description Controls Not applicable

504 Authoring ToolsHeading cell – noresponse required


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

See WCAG 2.1 sectionSee information in WCAG 2.1section

504.2.1 Preservation of Information Providedfor Accessibility in Format Conversion

Not applicable

VoiceThreads pages and tools

are not converted.

VoiceThread artifacts may be

exported to offline videos

and used with assistive

technologies as needed.

504.2.2 PDF Export Not applicableVoiceThreads include audioand video content, and arenot suitable for PDF.

504.3 Prompts Does not support

We do not prompt users tocreate content that conformsto Level A and Level AASuccess Criteria andConformance Requirementsin WCAG 2.0

504.4 Templates Not applicable

Chapter 6: Support Documentation and ServicesNotes:


Page 24 of 32

https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines#503-applications

https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines#504-authoring-tools


601.1 ScopeHeading cell – no responserequired


602 Support DocumentationHeading cell – no responserequired


602.2 Accessibility and CompatibilityFeatures




602.3 Electronic Support Documentation See WCAG 2.1 sectionSee information inWCAG 2.1 section

602.4 Alternate Formats forNon-Electronic Support Documentation

Not applicable.VoiceThread does notprovide non-electronicsupport documentation.

603 Support ServicesHeading cell – no responserequired


603.2 Information on Accessibility andCompatibility Features




603.3 Accommodation ofCommunication Needs




EN 301 549 ReportNotes:

Chapter 4: Functional Performance Statements (FPS)Notes:

Criteria ConformanceLevel Remarks and Explanations

4.2.1 Usage without vision




Standard and mobile: Not all content isaccessible using a keyboard or screenreader. Screen reader and keyboardusers are encouraged to use theUniversal interface.

Page 25 of 32

https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines#602-support-documentation

https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines#603-support-services

https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.01.01_60/en_301549v030101p.pdf#%5B%7B%22num%22%3A38%2C%22gen%22%3A0%7D%2C%7B%22name%22%3A%22XYZ%22%7D%2C54%2C747%2C0%5D

4.2.2 Usage with limited vision




Standard and mobile: Not all content isaccessible using a keyboard or screenreader. Screen reader and keyboardusers are encouraged to use theUniversal interface.

4.2.3 Usage without perception of colour

Standard app:Supports



4.2.4 Usage without hearing




4.2.5 Usage with limited hearing




4.2.6 Usage with no or limited vocalcapability




4.2.7 Usage with limited manipulation orstrength




4.2.8 Usage with limited reach Not applicable

4.2.9 Minimize photosensitive seizuretriggers


Page 26 of 32



4.2.10 Usage with limited cognition,language or learning




4.2.11 Privacy




Chapter 5: Generic RequirementsNotes: VoiceThread supports standard assistive technologies; this section is not applicable

Chapter 6: ICT with Two-Way Voice CommunicationNotes: VoiceThread does not offer two-way synchronous voice communication; this section is not

applicable

Chapter 7: ICT with Video CapabilitiesNotes:

Criteria Conformance Level Remarks and Explanations7.1 Caption processing technology Heading cell – no

response requiredHeading cell – no response required

7.1.1 Captioning playback Standard app: Supports



The standard application is more

suited for Deaf and hard-of-hearing

users.

7.1.2 Captioning synchronization Standard app: Supports





users.

Page 27 of 32




7.1.3 Preservation of captioning Standard app: Supports





users.

7.1.4 Captions characteristics Standard app: Does notsupport

Universal app: Does notsupport


7.1.5 Spoken subtitles Standard app: Does notsupport

Universal app: Does notsupport


7.2.1 Audio description playback Not applicable

7.2.2 Audio description synchronization Not applicable

7.2.3 Preservation of audio description Not applicable

7.3 User controls for captions and audiodescription




Chapter 8: HardwareNotes: VoiceThread does not provide hardware; this section is not applicable

Chapter 9: Web (see WCAG 2.1 section)

Chapter 10: Non-Web SoftwareNotes: VoiceThread does not provide non-web documents; this section is not applicable

Chapter 11: SoftwareNotes:

Page 28 of 32






11.0 General (informative) Heading cell – no responserequired


11.1.1.1 through 11.4.1.3 See WCAG 2.1 section See information in WCAG 2.xsection

11.5 Interoperability with assistivetechnology



11.5.1 Closed functionality Heading cell – no responserequired


11.5.2 Accessibility services Heading cell – no responserequired


11.5.2.1 Platform accessibility servicesupport for software that provides auser interface

See 11.5.2.5 through 11.5.2.17 See information in 11.5.2.5through 11.5.2.17

11.5.2.2 Platform accessibility servicesupport for assistive technologies

See 11.5.2.5 through 11.5.2.17 See information in 11.5.2.5through 11.5.2.17

11.5.2.3 Use of accessibility services Standard app: Partially supports

Universal app: Partially supports

Mobile app: Partially supports

The applications do not fullysupport criterion 11.5.2.5 to11.5.2.17. See criterion 11.5.2.5to 11.5.2.17 in this table formore information.

11.5.2.4 Assistive technology Not applicable

11.5.2.5 Object information Standard app: Partially supports

Universal app: Partially supports


Not all elements incorporate therequired accessible names tomake them accessible or clearto screen readers.

11.5.2.6 Row, column, and headers Not applicable

11.5.2.7 Values Standard app: Supports


Mobile app: Supports11.5.2.8 Label relationships Standard app: Partially supports



Not all content in the standardand mobile applications areappropriately labeled for screenreaders.

Screen reader users areencouraged to use the Universalinterface.

11.5.2.9 Parent-child relationships Standard app: Supports


Page 29 of 32

Mobile app: Supports11.5.2.10 Text Standard app: Does not support


Mobile app:Does not support11.5.2.11 List of available actions Standard app: Partially supports



Standard and mobile: Not allactions are appropriatelylabeled for screen readers.

Screen reader users areencouraged to use the Universalinterface.

11.5.2.12 Execution of availableactions



Mobile app: Supports11.5.2.13 Tracking of focus andselection attributes



Mobile app: Supports11.5.2.14 Modification of focus andselection attributes



Mobile app: Supports11.5.2.15 Change notification Standard app: Partially supports



In the standard and mobile appswe provide visual alerts butthese are not announced byscreen readers.

11.5.2.16 Modifications of states andproperties



Mobile app: Supports11.5.2.17 Modifications of values andtext



Mobile app: Supports11.6 Documented accessibility usage Heading cell – no response

requiredHeading cell – no responserequired

11.6.1 User control of accessibilityfeatures


Page 30 of 32


Mobile app: Supports11.6.2 No disruption of accessibilityfeatures



Mobile app: Supports11.7 User preferences Standard app: Supports


Mobile app: Supports11.8 Authoring tools Heading cell – no response

requiredHeading cell – no responserequired

11.8.1 Content technology Heading cell – no responserequired


11.8.2 Accessible content creation See WCAG 2.1 section(If not authoring tool, enter “NotApplicable”)

See information in WCAG 2.1section

11.8.3 Preservation of accessibilityinformation in transformations



Mobile app: Supports11.8.4 Repair assistance Not applicable

11.8.5 Templates Not applicable

Chapter 12: Documentation and Support ServicesNotes:

Criteria Conformance Level Remarks and Explanations12.1 Product documentation Heading cell – no response

requiredHeading cell – no response required

12.1.1 Accessibility andcompatibility features



Mobile app: Supports12.1.2 Accessible documentation See WCAG 2.1 section See information in WCAG 2.1 section

12.2 Support Services Heading cell – no responserequired

Heading cell – no response required

12.2.2 Information onaccessibility and compatibilityfeatures



Page 31 of 32


Mobile app: Supports12.2.3 Effective communication Standard app: Supports


Mobile app: Supports12.2.4 Accessible documentation See WCAG 2.1 section See information in WCAG 2.1 section

Chapter 13: ICT Providing Relay or Emergency Service AccessNotes: VoiceThread does not provide relay or emergency services; this section is not applicable.

Page 32 of 32


Date post:	13-Nov-2021
Category:	Documents
Upload:	others
View:	4 times
Download:	0 times

Name of Product/Version: VoiceThread Version 2.4) Report ...

Documents