Atlassian Accessibility VPAT: Jira Cloud (Mobile)(Based on VPAT® Version 2.4)
Name of
Product/Version

Jira cloud (mobile app) – Android & iOS

Report Date

June 2020

Product Description

Jira enables software teams to create user stories and issues, plan sprints, distribute tasks, track releases and teamperformance metrics.

Contact Information

https://www.atlassian.com/company/contact or email a11y@atlassian.com
App versions tested:
Android - Jira Cloud by Atlassian: v46.0.406, downloaded 8 April 2020
iOS - Jira Cloud by Atlassian: v46.0.406, downloaded 8 April 2020
The following tested pages are a representative sample of layouts, states, content types, and user interactions acrossthe app. They are collectively reported as Software throughout this document.

Notes

•
•
•
•
•
•
•
•
•
•
•
•

Login
Enter email & password
Onboarding (Welcome, etc.)
Choose a site
Projects list
Project > Board
Project > Backlog
Project > Roadmap
Project > Releases
Project > Reports
Project > Settings
Project > Settings > Features__________________________________“Voluntary Product Accessibility Template” and “VPAT” are registeredservice marks of the Information Technology Industry Council (ITI)

•
•
•
•
•
•
•
•
•
•

Issues home
Issues > All list
Issues > Search
Create issue
Account
Account > Invite people
Account > Notifications
Account > Give feedback
Account > Settings
Notifications

Page 1 of 59••

Projects > Search
Projects > Create project

The following page is assessed separately as an Authoring Tool due to its rich text editor functionality:• View / edit issue

Evaluation Methods
Used

The app pages were tested against WCAG 2.1 Level A and AA success criteria. The testing methodology used is based on
the Website Accessibility Conformance Evaluation Methodology (WCAG-EM) 1.0 (W3C Working Group Note 10 July2014).
These assistive technologies, settings, operating systems and devices were used for testing:Android - Voice Access 3.1, TalkBack 8.1, Invert Colours, Font Size, Android 10, Google Pixel 3A, Logitech K380 keyboard
iOS - Voice Control, VoiceOver, Smart Invert, Text Size, iOS 13.4, iPhone XS, Logitech K380 keyboard

Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
Standard/Guideline
Included In Report
Web Content Accessibility Guidelines 2.0
Level A (Yes)
Level AA (Yes)
Level AAA (No)Web Content Accessibility Guidelines 2.1
Level A (Yes)
Level AA (Yes)
Level AAA (No)Revised Section 508 standards published January 18, 2017 and corrected(Yes)
January 22, 2018
EN 301 549 Accessibility requirements suitable for public procurement of ICT(Yes)
products and services in Europe, - V3.1.1 (2019-11)

Terms
The terms used in the Conformance Level information are defined as follows:• Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets withequivalent facilitation.
Page 2 of 59

•
•
•
•

Partially Supports: Some functionality of the product does not meet the criterion.
Does Not Support: The majority of product functionality does not meet the criterion.
Not Applicable: The criterion is not relevant to the product.
Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.0 Level AAA.

WCAG 2.1 Report
Tables 1 and 2 also document conformance with:• EN 301 549: Chapter 9 - Web, Sections 10.1-10.4 of Chapter 10 - Non-Web documents, and Sections 11.1-11.4 and 11.8.2 of Chapter 11 Non-Web Software (open and closed functionality), and Sections 12.1.2 and 12.2.4 of Chapter 12 – Documentation• Revised Section 508: Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 – 602.3 Electronic Support Documentation.
Note: When reporting on conformance with the WCAG 2.x Success Criteria, they are scoped for full pages, complete processes, and accessibilitysupported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.

Page 3 of 59

Table 1: Success Criteria, Level A
Criteria
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)
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria• 9.1.2.1 (Web)• 10.1.2.1 (Non-web document)• 11.1.2.1.1 (Open Functionality Software)• 11.1.2.1.2.1 and 11.1.2.1.2.2 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
1.2.2 Captions (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria

Conformance Level

Remarks and Explanations

Software:• iOS: Some non-text elements (icons, status
Software:bars, charts) do not have meaningful labels.
• iOS: Partially supports
Some decorative and layout elements are not• Android: Partiallyhidden from assistive technologies.
supports• Android: Some non-text elements (icons, logo,
issues) do not have meaningful labels.
Authoring Tool:
Some decorative elements are not hidden• iOS: Partially Supports
from assistive technologies.
• Android: Partially
Authoring Tool (iOS and Android): Some non-text
Supports
elements (icons, images, issues) do not havemeaningful labels.

Software:• iOS: Not Applicable• Android: Not
Applicable

Authoring Tool (iOS and Android):• Authors cannot add/manage a transcript for
pre-recorded audio-only or video-only media.
Authoring Tool:• Authors cannot add/manage an audio track for• iOS: Does Not Support
pre-recorded video-only media• Android: Does Not
SupportSoftware:• iOS: Not Applicable• Android: Not
Page 4 of 59

Authoring Tool (iOS and Android):• Authors cannot add/manage captions for prerecorded audio-video media.

Criteria

Conformance Level
Applicable

Remarks and Explanations• 9.1.2.2 (Web)• 10.1.2.2 (Non-web document)
Authoring Tool:• 11.1.2.2 (Open Functionality Software)• iOS: Does Not Support• 11.1.2.2 (Closed Software)• Android: Does Not• 11.8.2 (Authoring Tool)
Support• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level
A)
Also applies to:
EN 301 549 Criteria
Software:• 9.1.2.3 (Web)• iOS: Not Applicable• 10.1.2.3 (Non-web document)
Authoring Tool (iOS and Android):• Android: Not• 11.1.2.3.1 (Open Functionality Software)
Applicable• Authors cannot add/manage a transcript for• 11.1.2.3.2 (Closed Software)
pre-recorded audio-video media.
• 11.8.2 (Authoring Tool)
Authoring Tool:• Authors cannot add/manage an audio track for• 12.1.2 (Product Docs)• iOS: Does Not Support
pre-recorded audio-video media• 12.2.4 (Support Docs)• Android: Does Not
Revised Section 508
Support• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
1.3.1 Info and Relationships (Level A)
Software:
Software:
Also applies to:• iOS: Does Not Support • iOS:
EN 301 549 Criteria• Android: Does Not
o Content exposed to assistive technologies is• 9.1.3.1 (Web)Supportoften a subset of what is shown on most• 10.1.3.1 (Non-web document)
Project pages.
Authoring Tool:o Text used as headings on screen is not• 11.1.3.1.1 (Open Functionality Software)
described as such by assistive technologies.
• iOS: Does Not Support• 11.1.3.1.2 (Closed Software)
Page 5 of 59

Criteria• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)

1.3.2 Meaningful Sequence (Level A)
Also applies to:
EN 301 549 Criteria• 9.1.3.2 (Web)• 10.1.3.2 (Non-web document)• 11.1.3.2.1 (Open Functionality Software)• 11.1.3.2.2 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
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)

Conformance Level• Android: Does Not
SupportRemarks and Explanations• Android:o Content exposed to assistive technologies isoften a subset of what is shown on most
Project pages.
o Text used as headings on screen is notdescribed as such by assistive technologies.
o Charts are not described meaningfully orcompletely

Authoring Tool (iOS and Android):• Content exposed to assistive technologies isoften a subset of what is shown on screen.
• Text used as headings on screen is notdescribed as such by assistive technologies.
Software:• iOS:o Occasionally the VoiceOver linear sequence
does not match the layout
Software:o Several adjacent related items are• iOS: Partially Supports
presented separately instead of combined• Android: Partiallyo A couple of elements have been hidden
Supports
from view but are still presented to assistive
technologies.
Authoring Tool:• Android:• iOS: Supportso Occasionally the TalkBack linear sequence
does not match the layout• Android: Supportso A couple of elements have been hiddenfrom view but are still presented to assistive
technologies.
Software:• iOS: Supports• Android: Supports
Page 6 of 59

Criteria• 11.1.3.3 (Open Functionality Software)• 11.1.3.3 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
1.4.1 Use of Color (Level A)
Also applies to:
EN 301 549 Criteria• 9.1.4.1 (Web)• 10.1.4.1 (Non-web document)• 11.1.4.1 (Open Functionality Software)• 11.1.4.1 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
1.4.2 Audio Control (Level A)
Also applies to:
EN 301 549 Criteria• 9.1.4.2 (Web)• 10.1.4.2 (Non-web document)• 11.1.4.2 (Open Functionality Software)• 11.1.4.2 (Closed Software)

Conformance Level
Authoring Tool:• iOS: Supports• Android: Supports

Remarks and Explanations

Software:• iOS: Many instances of colour used as the only
method of communicating information or
status (status bars, chart data, current
Software:navigation tab, issue priority icons, filter• iOS: Does Not Support
selection)• Android: Partially• Android: Several instances of colour used as
Supports
the only method of communicating
information or status (status bars, chart data,
Authoring Tool:
issue priority icons, filters)• iOS: Supports
Authoring Tool:• Android: Partially• iOS: One instance of colour alone used to
Supports
differentiate button from static text
• Android: Several instances of colour alone
used to indicate role (button vs text) or state(focus, selected)
Software:• iOS: Not Applicable• Android: Not
Applicable
Authoring Tool:• iOS: Supports
Page 7 of 59

Criteria• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
2.1.1 Keyboard (Level A)
Also applies to:
EN 301 549 Criteria• 9.2.1.1 (Web)• 10.2.1.1 (Non-web document)• 11.2.1.1.1 (Open Functionality Software)• 11.2.1.1.2 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
2.1.2 No Keyboard Trap (Level A)
Also applies to:
EN 301 549 Criteria• 9.2.1.2 (Web)• 10.2.1.2 (Non-web document)• 11.2.1.2 (Open Functionality Software)• 11.2.1.2 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)

Conformance Level• Android: Supports

Remarks and Explanations

Software:• iOS: External keyboard can’t access some dragand drop reordering functions, can’t trigger
Software:chart data display.
• iOS: Partially Supports• Android: External keyboard can’t use several• Android: Does Not
buttons, menus, and other components on
Supportcore path.
Authoring Tool:
Authoring Tool:• iOS: Does Not Support• iOS: Many of the authoring tool features are• Android: Partially
not accessible with an external keyboard,
Supports
including the core issue description field.
• Android: A few of the authoring tool features
are not accessible with a keyboard.

Software:• iOS: Partially Supports
Software:• Android: Supports• iOS: Two screen reader traps, one external
Authoring Tool:
keyboard trap
• iOS: Supports• Android: Supports

Page 8 of 59

Criteria• 504.2 (Authoring Tool)• 602.3 (Support Docs)
2.1.4 Character Key Shortcuts (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria• 9.2.1.4 (Web)• 10.2.1.4 (Non-web document)• 11.2.1.4.1 (Open Functionality Software)• 11.2.1.4.2 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
2.2.1 Timing Adjustable (Level A)
Also applies to:
EN 301 549 Criteria• 9.2.2.1 (Web)• 10.2.2.1 (Non-web document)• 11.2.2.1 (Open Functionality Software)• 11.2.2.1 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
2.2.2 Pause, Stop, Hide (Level A)
Also applies to:
EN 301 549 Criteria• 9.2.2.2 (Web)• 10.2.2.2 (Non-web document)• 11.2.2.2 (Open Functionality Software)

Conformance Level

Remarks and Explanations

Software:• iOS: Not Applicable• Android: Not
Applicable
Authoring Tool:• iOS: Not Applicable• Android: Not
Applicable

Software:• iOS: Supports• Android: PartiallySupports
Authoring Tool:• iOS: Supports• Android: Supports

Software:• iOS: Not Applicable• Android: Not
Applicable
Authoring Tool:
Page 9 of 59

Software:• Android: A couple of errors auto-dismiss
without user acknowledgement

Authoring Tool (iOS and Android): Animated GIF
images auto-play and cannot be stopped or paused.
Other media types do not auto-play.

Criteria
Conformance Level• 11.2.2.2 (Closed Software)• iOS: Partially Supports• 11.8.2 (Authoring Tool)• Android: PartiallySupports• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
2.3.1 Three Flashes or Below Threshold (Level A)
Also applies to:
EN 301 549 Criteria• 9.2.3.1 (Web)Software:• 10.2.3.1 (Non-web document)• iOS: Supports• 11.2.3.1 (Open Functionality Software)• Android: Supports• 11.2.3.1 (Closed Software)• 11.8.2 (Authoring Tool)
Authoring Tool:• 12.1.2 (Product Docs)• iOS: Supports• 12.2.4 (Support Docs)• Android: Supports
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
2.4.1 Bypass Blocks (Level A)
Also applies to:
Software:EN 301 549 Criteria• iOS: Not Applicable• 9.2.4.1 (Web)• Android: Not• 10.2.4.1 (Non-web document) – Does not apply
Applicable• 11.2.4.1 (Open Functionality Software) – Does not apply
Authoring Tool:• 11.2.4.1 (Closed Software) – Does not apply• iOS: Not Applicable• 11.8.2 (Authoring Tool)• Android: Not• 12.1.2 (Product Docs)
Applicable• 12.2.4 (Support Docs)
Revised Section 508
Page 10 of 59

Remarks and Explanations

Criteria
Conformance Level• 501 (Web)(Software) – Does not apply to non-web
software• 504.2 (Authoring Tool)• 602.3 (Support Docs) – Does not apply to non-web docs
2.4.2 Page Titled (Level A)
Also applies to:
EN 301 549 Criteria
Software:• 9.2.4.2 (Web)• iOS: Not Applicable• 10.2.4.2 (Non-web document)• 11.2.4.2 (Open Functionality Software) - Does not apply • Android: Not
Applicable• 11.2.4.2 (Closed Software) – Does not apply• 11.8.2 (Authoring Tool)
Authoring Tool:• 12.1.2 (Product Docs)• iOS: Not Applicable• 12.2.4 (Support Docs)• Android: Not
Revised Section 508
Applicable• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
2.4.3 Focus Order (Level A)
Also applies to:
EN 301 549 Criteria• 9.2.4.3 (Web)• 10.2.4.3 (Non-web document)• 11.2.4.3 (Open Functionality Software)• 11.2.4.3 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)

Remarks and Explanations

Software:• iOS:o VoiceOver focus occasionally not managed
Software:after page transitions or layout / content• iOS: Partially Supports
updates• Android: Partiallyo A couple of empty / visually hidden
Supports
elements receive VoiceOver focus• Android:
Authoring Tool:o TalkBack focus occasionally not managed• iOS: Partially Supports
after page transitions or layout / content
updates• Android: Partiallyo Two inefficient TalkBack focus paths
Supports
Authoring Tool (iOS and Android): Focus is not
managed for several features
Page 11 of 59

Criteria
2.4.4 Link Purpose (In Context) (Level A)
Also applies to:
EN 301 549 Criteria• 9.2.4.4 (Web)• 10.2.4.4 (Non-web document)• 11.2.4.4 (Open Functionality Software)• 11.2.4.4 (Closed Software• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
2.5.1 Pointer Gestures (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria• 9.2.5.1 (Web)• 10.2.5.1 (Non-web document)• 11.2.5.1 (Open Functionality Software)• 11.2.5.1 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
2.5.2 Pointer Cancellation (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria• 9.2.5.2 (Web)• 10.2.5.2 (Non-web document)• 11.2.5.2 (Open Functionality Software)• 11.2.5.2 (Closed Software)

Conformance Level

Remarks and Explanations

Software:• iOS: Supports• Android: Supports
Authoring Tool:• iOS: Supports• Android: Supports

Software:• iOS: Some data refresh (swipe) and content
Software:reorder (drag and drop) functions only use• iOS: Partially Supports
complex gestures, no simple gesture• Android: Partiallyalternatives provided.
Supports• Android: Carousel slides (swipe) and data
refresh (swipe) functions only use complex
Authoring Tool:
gestures, no simple gesture alternatives• iOS: Partially Supports
provided.
• Android: PartiallySupports
Authoring Tool (iOS and Android): Issue refresh(swipe) is only triggered by a complex gesture.
Software:• iOS: Supports• Android: Supports
Authoring Tool:• iOS: Supports• Android: Supports
Page 12 of 59

Criteria• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
2.5.3 Label in Name (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria• 9.2.5.3 (Web)• 10.2.5.3 (Non-web document)• 11.2.5.3.1 (Open Functionality Software)• 11.2.5.3.2 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
2.5.4 Motion Actuation (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria• 9.2.5.4 (Web)• 10.2.5.4 (Non-web document)• 11.2.5.4 (Open Functionality Software)• 11.2.5.4 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
3.1.1 Language of Page (Level A)
Also applies to:
EN 301 549 Criteria• 9.3.1.1 (Web)• 10.3.1.1 (Non-web document)• 11.3.1.1.1 (Open Functionality Software)• 11.3.1.1.2 (Closed Software)

Conformance Level

Remarks and Explanations

Software:• iOS: Partially Supports
Software:• Android: Supports• iOS: A couple of Voice Control element labels
Authoring Tool:
don’t match on-screen content.
• iOS: Supports• Android: Supports

Software:• iOS: Supports• Android: Supports
Authoring Tool:• iOS: Supports• Android: Supports

Software:• iOS: Supports• Android: Supports
Authoring Tool:• iOS: Supports• Android: Supports
Page 13 of 59

Criteria• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
3.2.1 On Focus (Level A)
Also applies to:
EN 301 549 Criteria• 9.3.2.1 (Web)• 10.3.2.1 (Non-web document)• 11.3.2.1 (Open Functionality Software)• 11.3.2.1 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
3.2.2 On Input (Level A)
Also applies to:
EN 301 549 Criteria• 9.3.2.2 (Web)• 10.3.2.2 (Non-web document)• 11.3.2.2 (Open Functionality Software)• 11.3.2.2 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)

Conformance Level

Software:• iOS: Supports• Android: Supports
Authoring Tool:• iOS: Supports• Android: Supports

Software:• iOS: Supports• Android: Supports
Authoring Tool:• iOS: Supports• Android: Supports

Page 14 of 59

Remarks and Explanations

Criteria• 504.2 (Authoring Tool)• 602.3 (Support Docs)
3.3.1 Error Identification (Level A)
Also applies to:
EN 301 549 Criteria• 9.3.3.1 (Web)• 10.3.3.1 (Non-web document)• 11.3.3.1.1 (Open Functionality Software)• 11.3.3.1.2 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
3.3.2 Labels or Instructions (Level A)
Also applies to:
EN 301 549 Criteria• 9.3.3.2 (Web)• 10.3.3.2 (Non-web document)• 11.3.3.2 (Open Functionality Software)• 11.3.3.2 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
4.1.1 Parsing (Level A)
Also applies to:
EN 301 549 Criteria

Conformance Level

Remarks and Explanations

Software:• iOS: Partially Supports
Software:• Android: Partially• iOS: 1 instance where error not linked to form
Supports
field in code
• Android: 1 instance where error not linked to
Authoring Tool:
form field in code
• iOS: Supports• Android: Supports

Software:• iOS: Several instances of placeholder text
Software:acting as a text field label, which can have
• iOS: Partially supports
flow-on activation issues for speech interfaces• Android: Partially• Android: Several instances of placeholder text
supports
acting as a text field label, which can haveflow-on activation issues for speech interfaces,
Authoring Tool:
incorrect TalkBack interpretation of symbols in• iOS: Does Not Support
instructions.
• Android: Does Not
Authoring Tool (iOS and Android): Many editor
Supportfields have placeholder text acting as a label.
(Android) A couple of button labels aren’t clear.
Software:• iOS: Supports• Android: Supports
Page 15 of 59

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

4.1.2 Name, Role, Value (Level A)
Also applies to:
EN 301 549 Criteria• 9.4.1.2 (Web)• 10.4.1.2 (Non-web document)• 11.4.1.2.1 (Open Functionality Software)• 11.4.1.2.2 (Closed Software) – Not required• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)

Conformance Level

Remarks and Explanations

Authoring Tool:• iOS: Supports• Android: Supports

Software:• iOS: Lots of interactive element notannouncing role/type, lots of stateful elements
not reporting state, some form field labellingissues.
Software:• Android: Some interactive element not• iOS: Does Not Support
announcing role/type, some stateful elements• Android: Does Not
not reporting state, lots of element labelling
Supportissues.
Authoring Tool:
Authoring Tool:• iOS: Does Not Support • iOS: Lots of interactive element notannouncing role/type, lots of stateful elements• Android: Does Not
not reporting state, some form field labelling
Supportissues.
• Android: Some interactive element notannouncing role/type, some stateful elements
not reporting state, lots of element labellingissues.

Page 16 of 59

Table 2: Success Criteria, Level AA
Criteria
1.2.4 Captions (Live) (Level AA)
Also applies to:
EN 301 549 Criteria• 9.1.2.4 (Web)• 10.1.2.4 (Non-web document)• 11.1.2.4 (Open Functionality Software)• 11.1.2.4 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
1.2.5 Audio Description (Prerecorded) (Level AA)
Also applies to:
EN 301 549 Criteria• 9.1.2.5 (Web)• 10.1.2.5 (Non-web document)• 11.1.2.5 (Open Functionality Software)• 11.1.2.5 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
1.3.4 Orientation (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria• 9.1.3.4 (Web)

Conformance Level

Remarks and Explanations

Software:• iOS: Not Applicable• Android: Not
Applicable
Authoring Tool:• iOS: Not Applicable• Android: Not
Applicable

Software:• iOS: Not Applicable• Android: Not
Applicable
Authoring Tool:• iOS: Does Not Support• Android: Does Not
SupportSoftware:• iOS: Supports• Android: Supports
Page 17 of 59

Authoring Tool (iOS and Android): Authors cannot
add/manage an audio track for pre-recorded audiovideo media

Criteria• 10.1.3.4 (Non-web document)• 11.1.3.4 (Open Functionality Software)• 11.1.3.4 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
1.3.5 Identify Input Purpose (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria• 9.1.3.5 (Web)• 10.1.3.5 (Non-web document)• 11.1.3.5.1 (Open Functionality Software)• 11.1.3.5.2 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
1.4.3 Contrast (Minimum) (Level AA)
Also applies to:
EN 301 549 Criteria• 9.1.4.3 (Web)• 10.1.4.3 (Non-web document)• 11.1.4.3 (Open Functionality Software)• 11.1.4.3 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
1.4.4 Resize text (Level AA)

Conformance Level
Authoring Tool:• iOS: Supports• Android: Supports

Remarks and Explanations

Software:• iOS: Supports• Android: Supports
Authoring Tool:• iOS: Supports• Android: Supports

Software:• iOS: Does Not Support Software:• iOS: Many instances of low contrast text
• Android: Partially• Android: Some instances of low contrast text
Supports
Authoring Tool:
Authoring Tool:• iOS: Partially Supports • iOS: Some instances of low contrast text
• Android: Does Not• Android: Many instances of low contrast text
SupportSoftware:Page 18 of 59

Software:Criteria
Also applies to:
EN 301 549 Criteria• 9.1.4.4 (Web)• 10.1.4.4 (Non-web document)• 11.1.4.4.1 (Open Functionality Software)• 11.1.4.4.2 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
1.4.5 Images of Text (Level AA)
Also applies to:
EN 301 549 Criteria• 9.1.4.5 (Web)• 10.1.4.5 (Non-web document)• 11.1.4.5.1 (Open Functionality Software)• 11.1.4.5.2 (Closed Software) – Does not apply• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
1.4.10 Reflow (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria• 9.1.4.10 (Web)• 10.1.4.10 (Non-web document)• 11.1.4.10 (Open Functionality Software)

Conformance Level
Remarks and Explanations• iOS: Does Not Support • iOS: Some instances of text that doesn’t
respond to system text size settings. Some
• Android: Partiallyinstances of text that truncates at larger text
Supports
sizes.
Authoring Tool:• Android: Several instances of text thattruncates at larger text sizes.
• iOS: Partially Supports• Android: Partially
Authoring Tool (iOS and Android): Some instances
Supportsof text that truncates at larger text sizes.

Software:• iOS: Not Applicable• Android: Not
Applicable
Authoring Tool:• iOS: Not Applicable• Android: Not
Applicable

Software:• iOS: Supports• Android: PartiallySupports
Authoring Tool:
Page 19 of 59

Software:• Android: Several instances of text truncating atlarger display size settings
Authoring Tool:• Android: Several instances of text truncating at

Criteria• 11.1.4.10 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
1.4.11 Non-text Contrast (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria• 9.1.4.11 (Web)• 10.1.4.11 (Non-web document)• 11.1.4.11 (Open Functionality Software)• 11.1.4.11 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
1.4.12 Text Spacing (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria• 9.1.4.12 (Web)• 10.1.4.12 (Non-web document)• 11.1.4.12 (Open Functionality Software)• 11.1.4.12 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
1.4.13 Content on Hover or Focus (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria• 9.1.4.13 (Web)• 10.1.4.13 (Non-web document)• 11.1.4.13 (Open Functionality Software)

Conformance Level• iOS: Supports• Android: PartiallySupports

Remarks and Explanations
larger display size settings

Software:
Software:• iOS: Many instances of low-contrast icons,• iOS: Does Not Support
element outlines and state styling, particularly• Android: Does Not
for external keyboard focus.
Support• Android: Many instances of low-contrast icons,element outlines and state styling, particularly
Authoring Tool:for external keyboard focus.
• iOS: Does Not Support
Authoring Tool (iOS and Android): Many instances• Android: Does Notof low-contrast icons, element outlines and state
Supportstyling, particularly for external keyboard focus.
Software:• iOS: Not Applicable• Android: Not
Applicable
Authoring Tool:• iOS: Not Applicable• Android: Not
Applicable
Software:• iOS: Not Applicable• Android: Not
Applicable
Authoring Tool:
Page 20 of 59

Criteria
Conformance Level
Remarks and Explanations• 11.1.4.13 (Closed Software)• iOS: Not Applicable• 11.8.2 (Authoring Tool)• Android: Not
Applicable• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
2.4.5 Multiple Ways (Level AA)
Also applies to:
EN 301 549 Criteria• 9.2.4.5 (Web)• 10.2.4.5 (Non-web document) – Does not apply• 11.2.4.5 (Open Functionality Software) – Does not apply• 11.2.4.5 (Closed Software) – Does not apply
Authoring Tool:• 11.8.2 (Authoring Tool)• iOS: Supports• 12.1.2 (Product Docs)• Android: Supports• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software) – Does not apply to non-web
software• 504.2 (Authoring Tool)• 602.3 (Support Docs) – Does not apply to non-web docs
2.4.6 Headings and Labels (Level AA)
Also applies to:
EN 301 549 Criteria
Software:• 9.2.4.6 (Web)• iOS: Does Not Support Software:• 10.2.4.6 (Non-web document)• Android: Partially• iOS: Generic button labels are used for• 11.2.4.6 (Open Functionality Software)
Supports
different functions on the same page, other• 11.2.4.6 (Closed Software)labels only describe state, not button action.
• 11.8.2 (Authoring Tool)
Authoring Tool:• Android: Several button labels aren’t• 12.1.2 (Product Docs)• iOS: Supports
descriptive enough.
• 12.2.4 (Support Docs)• Android: Supports
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)
Page 21 of 59

Criteria
Conformance Level
Remarks and Explanations• 602.3 (Support Docs)
2.4.7 Focus Visible (Level AA)
Also applies to:
EN 301 549 Criteria
Software:• 9.2.4.7 (Web)• iOS: Supports
Software:• 10.2.4.7 (Non-web document)• Android: Partially• Android: 1 instance where focus isn’t visible• 11.2.4.7 (Open Functionality Software)
Supports
for 6 Tab key presses (off-screen content)• 11.2.4.7 (Closed Software)• 11.8.2 (Authoring Tool)
Authoring Tool:
Authoring Tool:• 12.1.2 (Product Docs)• iOS: Supports• Android: 1 instance where focus isn’t visible• 12.2.4 (Support Docs)for an element• Android: Partially
Revised Section 508
Supports• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
3.1.2 Language of Parts (Level AA)
Also applies to:
EN 301 549 Criteria• 9.3.1.2 (Web)Software:• 10.3.1.2 (Non-web document)• iOS: Supports• 11.3.1.2 (Open Functionality Software) – Does not apply• Android: Supports• 11.3.1.2 (Closed Software) – Does not apply• 11.8.2 (Authoring Tool)
Authoring Tool:• 12.1.2 (Product Docs)• iOS: Supports• 12.2.4 (Support Docs)• Android: Supports
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
3.2.3 Consistent Navigation (Level AA)
Authoring Tool:
Also applies to:• iOS: Supports
EN 301 549 Criteria• Android: Supports• 9.3.2.3 (Web)Page 22 of 59

Criteria
Conformance Level
Remarks and Explanations• 10.3.2.3 (Non-web document) – Does not apply• 11.3.2.3 (Open Functionality Software) – Does not apply• 11.3.2.3 (Closed Software) – Does not apply• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software) – Does not apply to non-web
software• 504.2 (Authoring Tool)• 602.3 (Support Docs) – Does not apply to non-web docs
3.2.4 Consistent Identification (Level AA)
Also applies to:
EN 301 549 Criteria• 9.3.2.4 (Web)• 10.3.2.4 (Non-web document) – Does not apply• 11.3.2.4 (Open Functionality Software) – Does not apply• 11.3.2.4 (Closed Software) – Does not apply
Authoring Tool:• 11.8.2 (Authoring Tool)• iOS: Supports• 12.1.2 (Product Docs)• Android: Supports• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software) – Does not apply to non-web
software• 504.2 (Authoring Tool)• 602.3 (Support Docs) – Does not apply to non-web docs
3.3.3 Error Suggestion (Level AA)
Software:
Also applies to:• iOS: Supports
Software:EN 301 549 Criteria• Android: Supports• iOS: One instance where a disabled button is• 9.3.3.3 (Web)used to indicate an incomplete form instead of• 10.3.3.3 (Non-web document)
Authoring Tool:
validation and errors.
• 11.3.3.3 (Open Functionality Software)• iOS: Supports• 11.3.3.3 (Closed Software)• Android: Supports
Page 23 of 59

Criteria• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Also applies to:
EN 301 549 Criteria• 9.3.3.4 (Web)• 10.3.3.4 (Non-web document)• 11.3.3.4 (Open Functionality Software)• 11.3.3.4 (Closed Software)• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508• 501 (Web)(Software)• 504.2 (Authoring Tool)• 602.3 (Support Docs)
4.1.3 Status Messages (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria• 9.4.1.3 (Web)• 10.4.1.3 (Non-web document)• 11.4.1.3 (Open Functionality Software)• 11.4.1.3 (Closed Software) – Does not apply• 11.8.2 (Authoring Tool)• 12.1.2 (Product Docs)• 12.2.4 (Support Docs)
Revised Section 508 – Does not apply

Conformance Level

Software:• iOS: Supports• Android: Supports
Authoring Tool:• iOS: Supports• Android: Supports

Software:• iOS: Supports• Android: Supports
Authoring Tool:• iOS: Supports• Android: Supports

Page 24 of 59

Remarks and Explanations

Table 3: Success Criteria, Level AAA
Notes: WCAG 2.1 AAA criteria were not assessed

Page 25 of 59

Section 508 Report
Chapter 3: Functional Performance Criteria (FPC)
Criteria

302.1 Without Vision

Conformance Level

Remarks and Explanations
Software (iOS and Android):• As described in 1.1.1 Non-Text Content, some meaningful elements are
unlabelled and some decorative elements aren’t hidden from assistive
technologies• As described in 1.3.1 Info and Relationships, content and relationships
equivalent to the visual experience are not always available
programmatically• As described in 1.3.2 Meaningful Sequence, the linear content sequence
travelled by screen readers doesn’t always match the visual layout• As described in 2.1.1 Keyboard, some functions are not accessible via
external keyboard
Software:• (iOS only) As described in 2.1.2 No Keyboard Trap, there are several• iOS: Does Not Support
traps for screen readers and external keyboard• Android: Does Not Support • (Android only) As described in 2.2.1 Timing Adjustable, some errors
auto-dismiss without user acknowledgement
Authoring Tool:• As described in 2.4.3 Focus Order, screen reader location is not always• iOS: Does Not Support
managed and the content path is not always efficient• Android: Does Not Support • As described in 2.4.6 Headings and Labels, some labels are too genericto understand or differentiate.
• As described in 3.3.1 Error Identification, one error is not linked to its
related form field in code
• As described in 3.3.2 Labels or Instructions, some form fields use
placeholders as labels which aren’t always reliably communicated byscreen readers• As described in 4.1.2 Name, Role, Value, many elements do not reportat least one of name, role, or value to assistive technologies
Authoring Tool (iOS and Android):• As described in 1.1.1 Non-Text Content, some meaningful elements are
Page 26 of 59

Criteria

302.2 With Limited Vision

Conformance Level

Remarks and Explanations

unlabelled• As described in 1.2.1 Prerecorded Audio-only and Video-only, authors
cannot add/manage transcripts for pre-recorded audio-only media or
audio tracks for pre-recorded audio-only media• As described in 1.2.3 Audio Description or Media Alternative(Prerecorded), authors cannot add/manage transcripts or audio tracks
for pre-recorded audio-video media• As described in 1.2.5 Audio Description (Prerecorded), authors cannot
add/manage audio tracks for pre-recorded audio-video media• As described in 1.3.1 Info and Relationships, content and relationships
equivalent to the visual experience are not always available
programmatically• As described in 2.1.1 Keyboard, some functions are not accessible via
external keyboard• As described in 2.2.2 Pause, Stop, Hide, animated GIF images auto-playand cannot be stopped or paused.
• As described in 2.4.3 Focus Order, focus is not managed for several
features• As described in 3.3.2 Labels or Instructions, many editor fields haveplaceholder text acting as a label• As described in 4.1.2 Name, Role, Value, many elements do not reportat least one of name, role, or value to assistive technologies
Software (iOS and Android):• As described in 1.1.1 Non-Text Content, some meaningful elements are
unlabelled and some decorative elements aren’t hidden from assistive
Software:technologies• iOS: Does Not Support• As described in 1.3.1 Info and Relationships, content and relationships• Android: Does Not Support
equivalent to the visual experience are not always available
programmatically
Authoring Tool:• As described in 1.3.2 Meaningful Sequence, the linear content sequence• iOS: Does Not Support
travelled by screen readers doesn’t always match the visual layout• Android: Does Not Support• As described in 1.4.1 Use of Color, colour is relied on to communicate
information and status.
• As described in 1.4.3 Contrast (Minimum), there are many instances ofPage 27 of 59

Criteria

Conformance Level

Remarks and Explanations
low-contrast text.
• As described in 1.4.4 Resize Text, some text truncates at larger text size
settings and some text doesn’t respect system text size settings.
• (Android only) As described in 1.4.10 Reflow, some text truncates atlarger display size settings.
• As described in 1.4.11 Non-text Contrast, there are many instances of
low-contrast icons, element outlines and state styling.
• As described in 2.1.1 Keyboard, some functions are not accessible via
external keyboard• (iOS only) As described in 2.1.2 No Keyboard Trap, there are several
traps for screen readers and external keyboard• (Android only) As described in 2.2.1 Timing Adjustable, some errors
auto-dismiss without user acknowledgement• As described in 2.4.3 Focus Order, screen reader location is not always
managed and the content path is not always efficient• As described in 2.4.6 Headings and Labels, some labels are too genericto understand or differentiate.
• (Android only) As described in 2.4.7 Focus Visible, there is one screen
where focus is not always visible• As described in 3.3.1 Error Identification, one error is not linked to its
related form field in code
• As described in 3.3.2 Labels or Instructions, some form fields use
placeholders as labels which aren’t always reliably communicated byscreen readers• (iOS only) As described in 3.3.3 Error Suggestion, a disabled button isused to indicate an incomplete form instead of validation and feedback• As described in 4.1.2 Name, Role, Value, many elements do not reportat least one of name, role, or value to assistive technologies
Authoring Tool (iOS and Android):• As described in 1.1.1 Non-Text Content, some meaningful elements are
unlabelled• As described in 1.2.1 Prerecorded Audio-only and Video-only, authors
cannot add/manage transcripts for pre-recorded audio-only media orPage 28 of 59

Criteria

302.3 Without Perception of Color

Conformance Level

Software:Remarks and Explanations
audio tracks for pre-recorded audio-only media• As described in 1.2.3 Audio Description or Media Alternative(Prerecorded), authors cannot add/manage transcripts or audio tracks
for pre-recorded audio-video media• As described in 1.2.5 Audio Description (Prerecorded), authors cannot
add/manage audio tracks for pre-recorded audio-video media• As described in 1.3.1 Info and Relationships, content and relationships
equivalent to the visual experience are not always available
programmatically• As described in 1.4.1 Use of Color, colour is relied on to communicate
information and status• As described in 1.4.3 Contrast (Minimum), there are some instances of
low-contrast text.
• As described in 1.4.4 Resize Text, some text truncates at larger text size
settings and some text doesn’t respect system text size settings.
• (Android only) As described in 1.4.10 Reflow, some text truncates atlarger display size settings.
• As described in 1.4.11 Non-text Contrast, there are many instances of
low-contrast icons, element outlines and state styling.
• As described in 2.1.1 Keyboard, some functions are not accessible via
external keyboard• As described in 2.2.2 Pause, Stop, Hide, animated GIF images auto-playand cannot be stopped or paused.
• As described in 2.4.3 Focus Order, focus is not managed for several
features• (Android only) As described in 2.4.7 Focus Visible, there is one screen
where focus is not always visible• As described in 3.3.2 Labels or Instructions, many editor fields haveplaceholder text acting as a label• As described in 4.1.2 Name, Role, Value, many elements do not reportat least one of name, role, or value to assistive technologies
Software (iOS and Android):• As described in 1.4.1 Use of Color, colour is relied on to communicate
Page 29 of 59

Criteria

Conformance Level• iOS: Does Not Support• Android: Does Not Support
Authoring Tool:• iOS: Does Not Support• Android: Does Not Support

Remarks and Explanations
information and status.
• As described in 1.4.3 Contrast (Minimum), there are many instances of
low-contrast text.
• As described in 1.4.11 Non-text Contrast, there are many instances of
low-contrast icons, element outlines and state styling.
Authoring Tool (iOS and Android):• As described in 1.4.1 Use of Color, colour is relied on to communicate
information and status• As described in 1.4.3 Contrast (Minimum), there are some instances of
low-contrast text.
• As described in 1.4.11 Non-text Contrast, there are many instances of
low-contrast icons, element outlines and state styling.

Software:• iOS: Supports• Android: Supports
302.4 Without Hearing

302.5 With Limited Hearing

302.6 Without Speech

Authoring Tool (iOS and Android):• As described in 1.2.1 Prerecorded Audio-only and Video-only, authors
cannot add/manage transcripts for pre-recorded audio-only media or
audio tracks for pre-recorded audio-only media• As described in 1.2.2 Captions (Prerecorded), authors cannot
add/manage captions for pre-recorded audio-video media

Authoring Tool:• iOS: Does Not Support• Android: Does Not Support
Software:
Authoring Tool (iOS and Android):• iOS: Supports• As described in 1.2.1 Prerecorded Audio-only and Video-only, authors• Android: Supports
cannot add/manage transcripts for pre-recorded audio-only media or
audio tracks for pre-recorded audio-only media
Authoring Tool:• As described in 1.2.2 Captions (Prerecorded), authors cannot• iOS: Does Not Support
add/manage captions for pre-recorded audio-video media• Android: Does Not Support
Software (iOS and Android):
Software:• As described in 2.1.1 Keyboard, some functions are not accessible via• iOS: Partially Supports
external keyboard• Android: Partially Supports • (iOS only) As described in 2.1.2 No Keyboard Trap, there are several
traps for screen readers and external keyboard
Authoring Tool:
Page 30 of 59

Criteria

302.7 With Limited Manipulation

Conformance Level
Remarks and Explanations
Authoring Tool (iOS and Android):• iOS: Partially Supports• Android: Partially Supports • As described in 2.1.1 Keyboard, some functions are not accessible via
external keyboard• (Android only) As described in 2.4.7 Focus Visible, there is one screen
where focus is not always visible• As described in 3.3.2 Labels or Instructions, many editor fields haveplaceholder text acting as a label
Software (iOS and Android):• As described in 2.1.1 Keyboard, some functions are not accessible via
external keyboard• (iOS only) As described in 2.1.2 No Keyboard Trap, there are several
traps for screen readers and external keyboard• As described in 2.4.3 Focus Order, focus location is not always managed
and the content path is not always efficient• As described in 2.4.6 Headings and Labels, generic element labels may
make speech interfaces harder to use• (Android only) As described in 2.4.7 Focus Visible, there is one screen
Software:where focus is not always visible• iOS: Does Not Support• As described in 2.5.1 Pointer Gestures, several functions are triggered by• Android: Does Not Supportcomplex gestures only
• (iOS only) As described in 2.5.3 Label in Name, a couple of Voice Control
Authoring Tool:
element labels don’t match on-screen content• iOS: Does Not Support• As described in 3.3.2 Labels or Instructions, some form fields use• Android: Does Not Support
placeholder labels which aren’t reliable speech interface triggers• As described in 4.1.2 Name, Role, Value, many elements do not reportat least one of name, role, or value to assistive technologies
Authoring Tool (iOS and Android):• As described in 2.1.1 Keyboard, some functions are not accessible via
external keyboard• As described in 2.4.3 Focus Order, focus is not managed for several
features• (Android only) As described in 2.4.7 Focus Visible, there is one screen
Page 31 of 59

Criteria

302.8 With Limited Reach andStrength302.9 With Limited Language,
Cognitive, and Learning Abilities

Conformance Level

Remarks and Explanations
where focus is not always visible• As described in 2.5.1 Pointer Gestures, one feature is only triggered by acomplex gesture• As described in 3.3.2 Labels or Instructions, many editor fields haveplaceholder text acting as a label• As described in 4.1.2 Name, Role, Value, many elements do not reportat least one of name, role, or value to assistive technologies

Software:• iOS: Partially Supports• Android: Partially Supports
Authoring Tool:• iOS: Supports• Android: Supports

Software (iOS and Android):• As described in 2.5.1 Pointer Gestures, several functions are triggered bycomplex gestures only
• (iOS only) As described in 2.5.3 Label in Name, a couple of Voice Control
element labels don’t match on-screen content
Authoring Tool (iOS and Android):• As described in 2.5.1 Pointer Gestures, one feature is only triggered by acomplex gesture

Software (iOS and Android):• As described in 1.1.1 Non-Text Content, some meaningful elements are
unlabelled and some decorative elements aren’t hidden from assistive
technologies• As described in 1.3.1 Info and Relationships, content and relationships
Software:equivalent to the visual experience are not always available
programmatically• iOS: Does Not Support• Android: Does Not Support • As described in 1.3.2 Meaningful Sequence, the linear content sequence
travelled by assistive technologies doesn’t always match the visual layout
Authoring Tool:• As described in 1.4.1 Use of Color, colour is relied on to communicate
information and status.
• iOS: Does Not Support• Android: Does Not Support • As described in 1.4.3 Contrast (Minimum), there are many instances of
low-contrast text.
• As described in 1.4.11 Non-text Contrast, there are many instances of
low-contrast icons, element outlines and state styling.
• (Android only) As described in 2.2.1 Timing Adjustable, some errors
auto-dismiss without user acknowledgement
Page 32 of 59

Criteria

Conformance Level
•
•
•
•
•
•
•
•

Remarks and Explanations
As described in 2.4.3 Focus Order, focus location is not always managed
and the content path is not always efficient
As described in 2.4.6 Headings and Labels, generic element labels may
make speech interfaces harder to use(Android only) As described in 2.4.7 Focus Visible, there is one screen
where focus is not always visible
As described in 2.5.1 Pointer Gestures, several functions are triggered bycomplex gestures only
(iOS only) As described in 2.5.3 Label in Name, a couple of Voice Control
element labels don’t match on-screen content
As described in 3.3.1 Error Identification, one error is not linked to its
related form field in code
As described in 3.3.2 Labels or Instructions, some form fields use
placeholder labels which aren’t reliable speech interface triggers(iOS only) As described in 3.3.3 Error Suggestion, a disabled button isused to indicate an incomplete form instead of validation and feedback

Authoring Tool (iOS and Android):• As described in 1.1.1 Non-Text Content, some meaningful elements are
unlabelled• As described in 1.2.1 Prerecorded Audio-only and Video-only, authors
cannot add/manage transcripts for pre-recorded audio-only media or
audio tracks for pre-recorded audio-only media• As described in 1.2.2 Captions (Prerecorded), authors cannot
add/manage captions for pre-recorded audio-video media• As described in 1.2.3 Audio Description or Media Alternative(Prerecorded), authors cannot add/manage transcripts or audio tracks
for pre-recorded audio-video media• As described in 1.2.5 Audio Description (Prerecorded), authors cannot
add/manage audio tracks for pre-recorded audio-video media• As described in 1.3.1 Info and Relationships, content and relationships
equivalent to the visual experience are not always available
programmatically• As described in 1.4.1 Use of Color, colour is relied on to communicate
Page 33 of 59

Criteria

Conformance Level
•
•
•
•
•
•
•
•
•

Remarks and Explanations
information and status
As described in 1.4.3 Contrast (Minimum), there are some instances of
low-contrast text.
As described in 1.4.11 Non-text Contrast, there are many instances of
low-contrast icons, element outlines and state styling.
As described in 2.1.1 Keyboard, some functions are not accessible via
external keyboard
As described in 2.2.2 Pause, Stop, Hide, animated GIF images auto-playand cannot be stopped or paused.
As described in 2.4.3 Focus Order, focus is not managed for several
features(Android only) As described in 2.4.7 Focus Visible, there is one screen
where focus is not always visible
As described in 2.5.1 Pointer Gestures, one feature is only triggered by acomplex gesture
As described in 3.3.2 Labels or Instructions, many editor fields haveplaceholder text acting as a label
As described in 4.1.2 Name, Role, Value, many elements do not reportat least one of name, role, or value to assistive technologies

Chapter 4: Hardware
Notes: Jira cloud mobile apps are iOS and Android applications. They are not subject to the requirements of this section.

Chapter 5: Software
Notes:
Criteria
Conformance Level
501.1 Scope – Incorporation of
See WCAG 2.x section
WCAG 2.0 AA
502 Interoperability with Assistive Heading cell – no responseTechnology
required
Software:502.2.1 User Control of Accessibility• iOS: Not ApplicableFeatures• Android: Not Applicable

Remarks and Explanations
See information in WCAG 2.x section
Heading cell – no response required
Software and Authoring Tool do not act as a control proxy for platform-level
accessibility features.
Page 34 of 59

Criteria502.2.2 No Disruption ofAccessibility Features

502.3 Accessibility Services

Conformance Level

Remarks and Explanations

Authoring Tool:• iOS: Not Applicable• Android: Not Applicable
Software:• iOS: Supports• Android: Supports
No disruption to accessibility features provided at the platform level
Authoring Tool:• iOS: Supports• Android: Supports
Heading cell – no response
required
Software:• iOS: Does Not Support• Android: Does Not Support

Heading cell – no response required
Software (iOS and Android): As described in 4.1.2 Name, Role, Value, many
objects do not report one or more of role, state(s), properties, name, or
description to assistive technologies.

502.3.1 Object Information

502.3.2 Modification of Object
Information

502.3.3 Row, Column, and Headers

Authoring Tool:• iOS: Does Not Support• Android: Does Not Support
Software:• iOS: Supports• Android: Supports
Authoring Tool:• iOS: Supports• Android: Supports
Software:• iOS: Not Applicable• Android: Not Applicable

Authoring Tool (iOS and Android): As described in 4.1.2 Name, Role, Value,
many objects do not report one or more of role, state(s), properties, name,or description to assistive technologies.

No data tables

Authoring Tool:• iOS: Not Applicable
Page 35 of 59

Criteria

Conformance Level• Android: Not Applicable
Software:• iOS: Supports• Android: Supports

Remarks and Explanations

502.3.4 Values
Authoring Tool:• iOS: Supports• Android: Supports
Software:• iOS: Supports• Android: Supports
502.3.5 Modification of Values
Authoring Tool:• iOS: Does Not Support• Android: Partially Supports

Software:• iOS: Does Not Support• Android: Does Not Support

Authoring Tool:• iOS: As described in 2.1.1 Keyboard, many of the authoring toolfeatures are not accessible with an external keyboard• Android: As described in 2.1.1 Keyboard, a few authoring tool features
are not accessible with an external keyboard
Software (iOS and Android):• As described in 1.1.1 Non-Text Content, some meaningful elements are
unlabelled• As described in 3.3.2 Labels or Instructions, some form fields use
placeholder labels which aren’t reliable speech interface triggers• As described in 4.1.2 Name, Role, Value, many elements do not reportat least one of name, role, or value to assistive technologies

502.3.6 Label Relationships
Authoring Tool:• iOS: Does Not Support• Android: Does Not Support

502.3.7 Hierarchical Relationships

Software:• iOS: Partially Supports• Android: Partially Supports

Authoring Tool (iOS and Android):• As described in 1.1.1 Non-Text Content, some meaningful elements are
unlabelled• As described in 3.3.2 Labels or Instructions, many editor fields haveplaceholder text acting as a label• As described in 4.1.2 Name, Role, Value, many elements do not reportat least one of name, role, or value to assistive technologies
Software (iOS and Android): As described in 1.3.1 Info and Relationships,
some text used as headings on screen is not defined as suchprogrammatically.

Page 36 of 59

Criteria

Conformance Level

Remarks and Explanations

Authoring Tool:• iOS: Supports• Android: Supports
Software:• iOS: Supports• Android: Supports
502.3.8 Text
Authoring Tool:• iOS: Supports• Android: Supports
Software:• iOS: Supports• Android: Supports
502.3.9 Modification of Text
Authoring Tool:• iOS: Does Not Support• Android: Partially Supports
Software:• iOS: Partially Supports• Android: Partially Supports

Authoring Tool:• iOS: As described in 2.1.1 Keyboard, many of the authoring toolfeatures are not accessible with an external keyboard• Android: As described in 2.1.1 Keyboard, a few authoring tool features
are not accessible with an external keyboard
Software (iOS and Android): As described in 4.1.2 Name, Role, Value, someelements don’t have a programmatic role declared (which determines thelist of available actions).

502.3.10 List of Actions
Authoring Tool:• iOS: Partially Supports• Android: Partially Supports
Software:• iOS: Partially Supports• Android: Does Not Support
502.3.11 Actions on Objects
Authoring Tool:• iOS: Does Not Support• Android: Partially Supports

Authoring Tool (iOS and Android): As described in 4.1.2 Name, Role, Value,
some elements don’t have a programmatic role declared (which determines
the list of available actions).
Software:• iOS: As described in 2.1.1 Keyboard, an external keyboard can’t
execute some non-core functions.
• Android: As described in 2.1.1 Keyboard, an external keyboard can’t
use several buttons, menus, and other components on core path.
Authoring Tool:• iOS: As described in 2.1.1 Keyboard, many of the authoring tool

Page 37 of 59

Criteria

Conformance Level

Software:• iOS: Does Not Support• Android: Does Not Support

Remarks and Explanations
features are not accessible with an external keyboard• Android: As described in 2.1.1 Keyboard, a few authoring tool features
are not accessible with an external keyboard
Software (iOS and Android): The external keyboard focus cursor is almost
always visible, but as mentioned in 1.4.11 Non-text Contrast, the focus
cursor styling has very poor contrast.

502.3.12 Focus Cursor

502.3.13 Modification of Focus
CursorAuthoring Tool:• iOS: Does Not Support• Android: Does Not Support
Software:• iOS: Partially Supports• Android: Partially Supports
Authoring Tool:• iOS: Partially Supports• Android: Partially Supports
Software:• iOS: Partially Supports• Android: Partially Supports

Authoring Tool (iOS and Android): The external keyboard focus cursor isalmost always visible, but as mentioned in 1.4.11 Non-text Contrast, thefocus cursor styling has very poor contrast.
Software (iOS and Android): As described in 2.4.3 Focus Order, focus isoccasionally not managed after user actions or page transitions. Focus
sometimes goes to off-screen elements. Some focus pathing does not matchthe on-screen layout.
Authoring Tool (iOS and Android): As described in 2.4.3 Focus Order, focus
is occasionally not managed after user actions.
Software (iOS and Android): As described in 4.1.2 Name, Role, Value, someelements do not report their state or properties, let alone changes to those
attributes.

502.3.14 Event Notification

502.4 Platform Accessibility
Features

503 Applications

Authoring Tool:• iOS: Partially Supports• Android: Partially Supports
Software:• iOS: Not Applicable• Android: Not Applicable
Authoring Tool:• iOS: Not Applicable• Android: Not Applicable
Heading cell – no response
required

Authoring Tool (iOS and Android): As described in 4.1.2 Name, Role, Value,
some elements do not report their state or properties, let alone changes tothose attributes.

Heading cell – no response required
Page 38 of 59

Criteria

Conformance Level
Software:• iOS: Partially Supports• Android: Partially Supports

503.2 User Preferences
Authoring Tool:• iOS: Partially Supports• Android: Partially Supports
Software:• iOS: Not Applicable• Android: Not Applicable

Remarks and Explanations
Software (iOS and Android): As described in 1.4.4 Resize Text, some text
truncates at larger system text sizes. Some text ignores system text size
settings.
Authoring Tool (iOS and Android): As described in 1.4.4 Resize Text, some
text truncates at larger system text sizes.

503.3 Alternative User Interfaces

503.4 User Controls for Captions
and Audio Description

Authoring Tool:• iOS: Not Applicable• Android: Not Applicable
Heading cell – no response
required
Software:• iOS: Not Applicable• Android: Not Applicable

Heading cell – no response required

503.4.1 Caption Controls
Authoring Tool:• iOS: Does Not Support• Android: Does Not Support
Software:• iOS: Not Applicable• Android: Not Applicable
503.4.2 Audio Description Controls

504 Authoring Tools
504.2 Content Creation or Editing

Authoring Tool:• iOS: Does Not Support• Android: Does Not Support
Heading cell – no response
requiredSee WCAG 2.x section

Authoring Tool (iOS and Android): As described in 1.2.2 Captions(Prerecorded), authors can’t add/manage captions for pre-recorded audiovideo media. The media player does not have a captions button.

Authoring Tool (iOS and Android): As described in 1.2.3 Audio Description
or Media Alternative (Prerecorded) and 1.2.5 Audio Description(Prerecorded), authors can’t add/manage audio description for prerecorded audio-video media. The media player does not have an audio
description button.
Heading cell – no response required
See information in WCAG 2.x section

Page 39 of 59

Criteria
Conformance Level(if not authoring tool, enter “notapplicable”)
504.2.1 Preservation of Information Authoring Tool:
Provided for Accessibility in Format • iOS: Not Applicable
Conversion• Android: Not Applicable
Authoring Tool:
504.2.2 PDF Export• iOS: Not Applicable• Android: Not Applicable
Authoring Tool:
504.3 Prompts• iOS: Does Not Support• Android: Does Not Support
Authoring Tool:
504.4 Templates• iOS: Not Applicable• Android: Not Applicable

Remarks and Explanations

Authoring Tool (iOS and Android): No format conversion

Authoring Tool (iOS and Android): No PDF export feature
Authoring Tool (iOS and Android): No mode provided that prompts authors
to create accessible content
Authoring Tool (iOS and Android): No templates provided

Chapter 6: Support Documentation and Services
Notes: Jira cloud mobile apps are iOS and Android applications. They are not telecommunications equipment or customer premises equipment
required to provide support documentation and services as per section C206 or Chapter 6. They are not subject to the requirements of this section.

Page 40 of 59

EN 301 549 Report
Chapter 4: Functional Performance Statements (FPS)
Criteria

4.2.1 Usage without vision

Conformance Level

Remarks and Explanations
Software (iOS and Android):• As described in 1.1.1 Non-Text Content, some meaningful elements are
unlabelled and some decorative elements aren’t hidden from assistive
technologies• As described in 1.3.1 Info and Relationships, content and relationships
equivalent to the visual experience are not always available
programmatically• As described in 1.3.2 Meaningful Sequence, the linear content sequence
travelled by screen readers doesn’t always match the visual layout• As described in 2.1.1 Keyboard, some functions are not accessible via
external keyboard
Software:• (iOS only) As described in 2.1.2 No Keyboard Trap, there are several• iOS: Does Not Support
traps for screen readers and external keyboard• Android: Does Not Support • (Android only) As described in 2.2.1 Timing Adjustable, some errors
auto-dismiss without user acknowledgement
Authoring Tool:• As described in 2.4.3 Focus Order, screen reader location is not always• iOS: Does Not Support
managed and the content path is not always efficient• Android: Does Not Support • As described in 2.4.6 Headings and Labels, some labels are too genericto understand or differentiate.
• As described in 3.3.1 Error Identification, one error is not linked to its
related form field in code
• As described in 3.3.2 Labels or Instructions, some form fields use
placeholders as labels which aren’t always reliably communicated byscreen readers• As described in 4.1.2 Name, Role, Value, many elements do not reportat least one of name, role, or value to assistive technologies
Authoring Tool (iOS and Android):• As described in 1.1.1 Non-Text Content, some meaningful elements are
Page 41 of 59

Criteria

4.2.2 Usage with limited vision

Conformance Level

Remarks and Explanations

unlabelled• As described in 1.2.1 Prerecorded Audio-only and Video-only, authors
cannot add/manage transcripts for pre-recorded audio-only media or
audio tracks for pre-recorded audio-only media• As described in 1.2.3 Audio Description or Media Alternative(Prerecorded), authors cannot add/manage transcripts or audio tracks
for pre-recorded audio-video media• As described in 1.2.5 Audio Description (Prerecorded), authors cannot
add/manage audio tracks for pre-recorded audio-video media• As described in 1.3.1 Info and Relationships, content and relationships
equivalent to the visual experience are not always available
programmatically• As described in 2.1.1 Keyboard, some functions are not accessible via
external keyboard• As described in 2.2.2 Pause, Stop, Hide, animated GIF images auto-playand cannot be stopped or paused.
• As described in 2.4.3 Focus Order, focus is not managed for several
features• As described in 3.3.2 Labels or Instructions, many editor fields haveplaceholder text acting as a label• As described in 4.1.2 Name, Role, Value, many elements do not reportat least one of name, role, or value to assistive technologies
Software (iOS and Android):• As described in 1.1.1 Non-Text Content, some meaningful elements are
Software:unlabelled and some decorative elements aren’t hidden from assistive• iOS: Does Not Support
technologies• Android: Does Not Support • As described in 1.3.1 Info and Relationships, content and relationships
equivalent to the visual experience are not always available
Authoring Tool:
programmatically• iOS: Does Not Support• As described in 1.3.2 Meaningful Sequence, the linear content sequence
travelled by screen readers doesn’t always match the visual layout• Android: Does Not Support• As described in 1.4.1 Use of Color, colour is relied on to communicate
information and status.
Page 42 of 59

Criteria

Conformance Level
•
•
•
•
•
•
•
•
•
•
•
•

•
•

Remarks and Explanations
As described in 1.4.3 Contrast (Minimum), there are many instances of
low-contrast text.
As described in 1.4.4 Resize Text, some text truncates at larger text size
settings and some text doesn’t respect system text size settings.
(Android only) As described in 1.4.10 Reflow, some text truncates atlarger display size settings.
As described in 1.4.11 Non-text Contrast, there are many instances of
low-contrast icons, element outlines and state styling.
As described in 2.1.1 Keyboard, some functions are not accessible via
external keyboard(iOS only) As described in 2.1.2 No Keyboard Trap, there are several
traps for screen readers and external keyboard(Android only) As described in 2.2.1 Timing Adjustable, some errors
auto-dismiss without user acknowledgement
As described in 2.4.3 Focus Order, screen reader location is not always
managed and the content path is not always efficient
As described in 2.4.6 Headings and Labels, some labels are too genericto understand or differentiate.
(Android only) As described in 2.4.7 Focus Visible, there is one screen
where focus is not always visible
As described in 3.3.1 Error Identification, one error is not linked to its
related form field in code
As described in 3.3.2 Labels or Instructions, some form fields use
placeholders as labels which aren’t always reliably communicated byscreen readers(iOS only) As described in 3.3.3 Error Suggestion, a disabled button isused to indicate an incomplete form instead of validation and feedback
As described in 4.1.2 Name, Role, Value, many elements do not reportat least one of name, role, or value to assistive technologies

Authoring Tool (iOS and Android):• As described in 1.1.1 Non-Text Content, some meaningful elements are
unlabelled• As described in 1.2.1 Prerecorded Audio-only and Video-only, authors
Page 43 of 59

Criteria

4.2.3 Usage without perception ofConformance Level

Remarks and Explanations
cannot add/manage transcripts for pre-recorded audio-only media or
audio tracks for pre-recorded audio-only media• As described in 1.2.3 Audio Description or Media Alternative(Prerecorded), authors cannot add/manage transcripts or audio tracks
for pre-recorded audio-video media• As described in 1.2.5 Audio Description (Prerecorded), authors cannot
add/manage audio tracks for pre-recorded audio-video media• As described in 1.3.1 Info and Relationships, content and relationships
equivalent to the visual experience are not always available
programmatically• As described in 1.4.1 Use of Color, colour is relied on to communicate
information and status• As described in 1.4.3 Contrast (Minimum), there are some instances of
low-contrast text.
• As described in 1.4.4 Resize Text, some text truncates at larger text size
settings and some text doesn’t respect system text size settings.
• (Android only) As described in 1.4.10 Reflow, some text truncates atlarger display size settings.
• As described in 1.4.11 Non-text Contrast, there are many instances of
low-contrast icons, element outlines and state styling.
• As described in 2.1.1 Keyboard, some functions are not accessible via
external keyboard• As described in 2.2.2 Pause, Stop, Hide, animated GIF images auto-playand cannot be stopped or paused.
• As described in 2.4.3 Focus Order, focus is not managed for several
features• (Android only) As described in 2.4.7 Focus Visible, there is one screen
where focus is not always visible• As described in 3.3.2 Labels or Instructions, many editor fields haveplaceholder text acting as a label• As described in 4.1.2 Name, Role, Value, many elements do not reportat least one of name, role, or value to assistive technologies
Software (iOS and Android):
Page 44 of 59

Criteria
colour

Conformance Level
Software:• iOS: Does Not Support• Android: Does Not Support
Authoring Tool:• iOS: Does Not Support• Android: Does Not Support

Remarks and Explanations• As described in 1.4.1 Use of Color, colour is relied on to communicate
information and status.
• As described in 1.4.3 Contrast (Minimum), there are many instances of
low-contrast text.
• As described in 1.4.11 Non-text Contrast, there are many instances of
low-contrast icons, element outlines and state styling.
Authoring Tool (iOS and Android):• As described in 1.4.1 Use of Color, colour is relied on to communicate
information and status• As described in 1.4.3 Contrast (Minimum), there are some instances of
low-contrast text.
• As described in 1.4.11 Non-text Contrast, there are many instances of
low-contrast icons, element outlines and state styling.

Software:• iOS: Supports• Android: Supports
4.2.4 Usage without hearing

Authoring Tool (iOS and Android):• As described in 1.2.1 Prerecorded Audio-only and Video-only, authors
cannot add/manage transcripts for pre-recorded audio-only media or
audio tracks for pre-recorded audio-only media• As described in 1.2.2 Captions (Prerecorded), authors cannot
add/manage captions for pre-recorded audio-video media

Authoring Tool:• iOS: Does Not Support• Android: Does Not Support
Software:
Authoring Tool (iOS and Android):• iOS: Supports• As described in 1.2.1 Prerecorded Audio-only and Video-only, authors• Android: Supports
cannot add/manage transcripts for pre-recorded audio-only media or
4.2.5 Usage with limited hearing
audio tracks for pre-recorded audio-only media
Authoring Tool:• As described in 1.2.2 Captions (Prerecorded), authors cannot• iOS: Does Not Support
add/manage captions for pre-recorded audio-video media• Android: Does Not Support
Software:
Software (iOS and Android):• iOS: Partially Supports• As described in 2.1.1 Keyboard, some functions are not accessible via
4.2.6 Usage with no or limited vocal
external keyboard• Android: Partially Supports
capability• (iOS only) As described in 2.1.2 No Keyboard Trap, there are several
Authoring Tool:traps for screen readers and external keyboard
Page 45 of 59

Criteria

4.2.7 Usage with limited
manipulation or strength

Conformance Level
Remarks and Explanations• iOS: Partially Supports• Android: Partially Supports Authoring Tool (iOS and Android):• As described in 2.1.1 Keyboard, some functions are not accessible via
external keyboard• (Android only) As described in 2.4.7 Focus Visible, there is one screen
where focus is not always visible• As described in 3.3.2 Labels or Instructions, many editor fields haveplaceholder text acting as a label
Software (iOS and Android):• As described in 2.1.1 Keyboard, some functions are not accessible via
external keyboard• (iOS only) As described in 2.1.2 No Keyboard Trap, there are several
traps for screen readers and external keyboard• As described in 2.4.3 Focus Order, focus location is not always managed
and the content path is not always efficient• As described in 2.4.6 Headings and Labels, generic element labels may
make speech interfaces harder to use
Software:• (Android only) As described in 2.4.7 Focus Visible, there is one screen• iOS: Does Not Support
where focus is not always visible• Android: Does Not Support • As described in 2.5.1 Pointer Gestures, several functions are triggered bycomplex gestures only
Authoring Tool:• (iOS only) As described in 2.5.3 Label in Name, a couple of Voice Control• iOS: Does Not Support
element labels don’t match on-screen content• Android: Does Not Support • As described in 3.3.2 Labels or Instructions, some form fields use
placeholder labels which aren’t reliable speech interface triggers• As described in 4.1.2 Name, Role, Value, many elements do not reportat least one of name, role, or value to assistive technologies
Authoring Tool (iOS and Android):• As described in 2.1.1 Keyboard, some functions are not accessible via
external keyboard• As described in 2.4.3 Focus Order, focus is not managed for several
features
Page 46 of 59

Criteria

4.2.8 Usage with limited reach

4.2.9 Minimize photosensitive
seizure triggers

Conformance Level

Remarks and Explanations• (Android only) As described in 2.4.7 Focus Visible, there is one screen
where focus is not always visible• As described in 2.5.1 Pointer Gestures, one feature is only triggered by acomplex gesture• As described in 3.3.2 Labels or Instructions, many editor fields haveplaceholder text acting as a label• As described in 4.1.2 Name, Role, Value, many elements do not reportat least one of name, role, or value to assistive technologies
Software (iOS and Android):
Software:• As described in 2.5.1 Pointer Gestures, several functions are triggered by• iOS: Partially Supports
complex gestures only
• Android: Partially Supports • (iOS only) As described in 2.5.3 Label in Name, a couple of Voice Control
element labels don’t match on-screen content
Authoring Tool:
Authoring Tool (iOS and Android):• iOS: Supports• As described in 2.5.1 Pointer Gestures, one feature is only triggered by a
• Android: Supports
complex gesture
Software:• iOS: Supports• Android: Supports
Authoring Tool:• iOS: Supports• Android: Supports

Software (iOS and Android):
Software:• As described in 1.1.1 Non-Text Content, some meaningful elements are• iOS: Does Not Support
unlabelled and some decorative elements aren’t hidden from assistive
4.2.10 Usage with limited cognition,technologies• Android: Does Not Support
language or learning• As described in 1.3.1 Info and Relationships, content and relationships
Authoring Tool:
equivalent to the visual experience are not always available
programmatically• iOS: Does Not Support
Page 47 of 59

Criteria

Conformance Level• Android: Does Not Support

•
•
•
•
•
•
•
•
•
•
•
•
•

Remarks and Explanations
As described in 1.3.2 Meaningful Sequence, the linear content sequence
travelled by assistive technologies doesn’t always match the visual layout
As described in 1.4.1 Use of Color, colour is relied on to communicate
information and status.
As described in 1.4.3 Contrast (Minimum), there are many instances of
low-contrast text.
As described in 1.4.11 Non-text Contrast, there are many instances of
low-contrast icons, element outlines and state styling.
(Android only) As described in 2.2.1 Timing Adjustable, some errors
auto-dismiss without user acknowledgement
As described in 2.4.3 Focus Order, focus location is not always managed
and the content path is not always efficient
As described in 2.4.6 Headings and Labels, generic element labels may
make speech interfaces harder to use(Android only) As described in 2.4.7 Focus Visible, there is one screen
where focus is not always visible
As described in 2.5.1 Pointer Gestures, several functions are triggered bycomplex gestures only
(iOS only) As described in 2.5.3 Label in Name, a couple of Voice Control
element labels don’t match on-screen content
As described in 3.3.1 Error Identification, one error is not linked to its
related form field in code
As described in 3.3.2 Labels or Instructions, some form fields use
placeholder labels which aren’t reliable speech interface triggers(iOS only) As described in 3.3.3 Error Suggestion, a disabled button isused to indicate an incomplete form instead of validation and feedback

Authoring Tool (iOS and Android):• As described in 1.1.1 Non-Text Content, some meaningful elements are
unlabelled• As described in 1.2.1 Prerecorded Audio-only and Video-only, authors
cannot add/manage transcripts for pre-recorded audio-only media or
audio tracks for pre-recorded audio-only media• As described in 1.2.2 Captions (Prerecorded), authors cannot
Page 48 of 59

Criteria

Conformance Level
•
•
•
•
•
•
•
•
•
•
•
•
•

4.2.11 Privacy

Remarks and Explanations
add/manage captions for pre-recorded audio-video media
As described in 1.2.3 Audio Description or Media Alternative(Prerecorded), authors cannot add/manage transcripts or audio tracks
for pre-recorded audio-video media
As described in 1.2.5 Audio Description (Prerecorded), authors cannot
add/manage audio tracks for pre-recorded audio-video media
As described in 1.3.1 Info and Relationships, content and relationships
equivalent to the visual experience are not always available
programmaticallyAs described in 1.4.1 Use of Color, colour is relied on to communicate
information and status
As described in 1.4.3 Contrast (Minimum), there are some instances of
low-contrast text.
As described in 1.4.11 Non-text Contrast, there are many instances of
low-contrast icons, element outlines and state styling.
As described in 2.1.1 Keyboard, some functions are not accessible via
external keyboard
As described in 2.2.2 Pause, Stop, Hide, animated GIF images auto-playand cannot be stopped or paused.
As described in 2.4.3 Focus Order, focus is not managed for several
features(Android only) As described in 2.4.7 Focus Visible, there is one screen
where focus is not always visible
As described in 2.5.1 Pointer Gestures, one feature is only triggered by acomplex gesture
As described in 3.3.2 Labels or Instructions, many editor fields haveplaceholder text acting as a label
As described in 4.1.2 Name, Role, Value, many elements do not reportat least one of name, role, or value to assistive technologies

Software:• iOS: Supports• Android: Supports

Page 49 of 59

Criteria

Conformance Level
Authoring Tool:• iOS: Supports• Android: Supports

Remarks and Explanations

Chapter 5: Generic Requirements
Notes:
Criteria
5.1 Closed functionality
5.1.2 General
5.1.2.1 Closed functionality
5.1.2.2 Assistive technology
5.1.3 Non-visual access5.1.3.1 Audio output of visual information
5.1.3.2 Auditory output delivery including speech
5.1.3.3 Auditory output correlation
5.1.3.4 Speech output user control
5.1.3.5 Speech output automatic interruption
5.1.3.6 Speech output for non-text content
5.1.3.7 Speech output for video information
5.1.3.8 Masked entry
5.1.3.9 Private access to personal data
5.1.3.10 Non-interfering audio output
5.1.3.11 Private listening volume
5.1.3.12 Speaker volume
5.1.3.13 Volume reset
5.1.3.14 Spoken languages
5.1.3.15 Non-visual error identification
5.1.3.16 Receipts, tickets, and transactional outputs
5.1.4 Functionality closed to text enlargement
5.1.5 Visual output for auditory information

Conformance Level
Heading cell – no response required
Heading cell – no response required
See 5.2 through 13
See 5.1.3 through 5.1.6
Heading cell – no response required
Not Applicable
Not Applicable
Not Applicable
Not Applicable
Not Applicable
Not Applicable
Not Applicable
Not Applicable
Not Applicable
Not Applicable
Not Applicable
Not Applicable
Not Applicable
Not Applicable
Not Applicable
Not Applicable
Not Applicable
Not Applicable
Page 50 of 59

Remarks and Explanations
Heading cell – no response required
Heading cell – no response required
See information in 5.2 through 13
See information in 5.1.3 through 5.1.6
Heading cell – no response required

Criteria
5.1.6 Operation without keyboard interface

Conformance Level
Heading cell – no response required

5.1.6.1 Closed functionality

See 5.1.3.1 through 5.1.3.16

5.1.6.2 Input focus
5.1.7 Access without speech
5.2 Activation of accessibility features
5.3 Biometrics
5.4 Preservation of accessibility information during conversion
5.5 Operable parts
5.5.1 Means of operation
5.5.2 Operable parts discernibility
5.6 Locking or toggle controls
5.6.1 Tactile or auditory status
5.6.2 Visual status
5.7 Key repeat
5.8 Double-strike key acceptance
5.9 Simultaneous user actions

Not Applicable
Not Applicable
Not Applicable
Not Applicable
Not Applicable
Heading cell – no response required
Not Applicable
Not Applicable
Heading cell – no response required
Not Applicable
Not Applicable
Not Applicable
Not Applicable
Not Applicable

Remarks and Explanations
Heading cell – no response required
See information in 5.1.3.1 through5.1.3.16

Heading cell – no response required

Heading cell – no response required

Chapter 6: ICT with Two-Way Voice Communication
Notes: Jira cloud mobile apps are native iOS and Android applications. They are not subject to the requirements of this section.

Chapter 7: ICT with Video Capabilities
Notes: Jira cloud mobile apps do not have video functions. They are not subject to the requirements of this section.

Chapter 8: Hardware
Notes: Jira cloud mobile apps are native iOS and Android applications. They are not subject to the requirements of this section.

Chapter 9: Web (see WCAG 2.x section)

Page 51 of 59

Chapter 10: Non-Web Software
Criteria
10.0 General (informative)
10.1.1.1 through 10.4.1.3

Conformance Level
Heading cell – no response
requiredSee WCAG 2.x section
Software:• iOS: Not Applicable• Android: Not Applicable

Remarks and Explanations
Heading cell – no response required
See information in WCAG 2.x section

10.5 Caption positioning
Authoring Tool:• iOS: Does Not Support• Android: Does Not Support
Software:• iOS: Not Applicable• Android: Not Applicable10.6 Audio description timing
Authoring Tool:• iOS: Does Not Support• Android: Does Not Support

Authoring Tool (iOS and Android): Caption functionality is not provided in
the media player.

Authoring Tool (iOS and Android): Audio description functionality is notprovided in the media player.

Chapter 11: Software
Criteria

Conformance Level
Heading cell – no response
11.0 General (informative)
required
11.1.1.1 through 11.4.1.3
See WCAG 2.x section
11.5 Interoperability with assistive Heading cell – no response
technology
required
Heading cell – no response
11.5.1 Closed functionality
required
Heading cell – no response
11.5.2 Accessibility services
required
11.5.2.1 Platform accessibility
See 11.5.2.5 through 11.5.2.17
service support for software that

Remarks and Explanations
Heading cell – no response required
See information in WCAG 2.x section
Heading cell – no response required
Heading cell – no response required
Heading cell – no response required
See information in 11.5.2.5 through 11.5.2.17

Page 52 of 59

Criteria
provides a user interface
11.5.2.2 Platform accessibility
service support for assistive
technologies

Conformance Level

Remarks and Explanations

See 11.5.2.5 through 11.5.2.17

See information in 11.5.2.5 through 11.5.2.17

Software:• iOS: Supports• Android: Supports
11.5.2.3 Use of accessibility services
Authoring Tool:• iOS: Supports• Android: Supports
Software:• iOS: Not Applicable• Android: Not Applicable
11.5.2.4 Assistive technology
Authoring Tool:• iOS: Not Applicable• Android: Not Applicable
Software:• iOS: Does Not Support• Android: Does Not Support

Software (iOS and Android): As described in 4.1.2 Name, Role, Value, many
objects do not report one or more of role, state(s), properties, name, or
description to assistive technologies.

11.5.2.5 Object information
Authoring Tool:• iOS: Does Not Support• Android: Does Not Support
Software:• iOS: Not Applicable• Android: Not Applicable
11.5.2.6 Row, column, and headers11.5.2.7 Values

Authoring Tool (iOS and Android): As described in 4.1.2 Name, Role, Value,
many objects do not report one or more of role, state(s), properties, name,or description to assistive technologies.

No data tables
Authoring Tool:• iOS: Not Applicable• Android: Not Applicable
Software:Page 53 of 59

Criteria

Conformance Level• iOS: Supports• Android: Supports

Remarks and Explanations

Authoring Tool:• iOS: Supports• Android: Supports

Software:• iOS: Does Not Support• Android: Does Not Support

Software (iOS and Android):• As described in 1.1.1 Non-Text Content, some meaningful elements are
unlabelled• As described in 3.3.2 Labels or Instructions, some form fields use
placeholder labels which aren’t reliable speech interface triggers• As described in 4.1.2 Name, Role, Value, many elements do not reportat least one of name, role, or value to assistive technologies

11.5.2.8 Label relationships
Authoring Tool:• iOS: Does Not Support• Android: Does Not Support

Software:• iOS: Partially Supports• Android: Partially Supports
11.5.2.9 Parent-child relationships

11.5.2.10 Text

Authoring Tool:• iOS: Supports• Android: Supports
Software:• iOS: Supports• Android: Supports

Authoring Tool (iOS and Android):• As described in 1.1.1 Non-Text Content, some meaningful elements are
unlabelled• As described in 3.3.2 Labels or Instructions, many editor fields haveplaceholder text acting as a label• As described in 4.1.2 Name, Role, Value, many elements do not reportat least one of name, role, or value to assistive technologies

Software (iOS and Android): As described in 1.3.1 Info and Relationships,
some text used as headings on screen is not defined as suchprogrammatically.

Authoring Tool:
Page 54 of 59

Criteria

Conformance Level• iOS: Supports• Android: Supports
Software:• iOS: Partially Supports• Android: Partially Supports

Remarks and Explanations

Software (iOS and Android): As described in 4.1.2 Name, Role, Value, someelements don’t have a programmatic role declared (which determines thelist of available actions).

11.5.2.11 List of available actions
Authoring Tool:• iOS: Partially Supports• Android: Partially Supports

11.5.2.12 Execution of available
actions

11.5.2.13 Tracking of focus andselection attributes

Software:• iOS: Partially Supports• Android: Does Not Support
Authoring Tool:• iOS: Does Not Support• Android: Partially Supports

Software:• iOS: Does Not Support• Android: Does Not Support

Authoring Tool:• iOS: Does Not Support• Android: Does Not Support
Software:• iOS: Partially Supports
11.5.2.14 Modification of focus and • Android: Partially Supports
selection attributes
Authoring Tool:• iOS: Partially Supports

Authoring Tool (iOS and Android): As described in 4.1.2 Name, Role, Value,
some elements don’t have a programmatic role declared (which determines
the list of available actions).
Software:• iOS: As described in 2.1.1 Keyboard, an external keyboard can’t
execute some non-core functions.
• Android: As described in 2.1.1 Keyboard, an external keyboard can’t
use several buttons, menus, and other components on core path.
Authoring Tool:• iOS: As described in 2.1.1 Keyboard, many of the authoring toolfeatures are not accessible with an external keyboard• Android: As described in 2.1.1 Keyboard, a few authoring tool features
are not accessible with an external keyboard
Software (iOS and Android): The external keyboard focus cursor is almost
always visible, but as mentioned in 1.4.11 Non-text Contrast, the focus
cursor styling has very poor contrast.
Authoring Tool (iOS and Android): The external keyboard focus cursor isalmost always visible, but as mentioned in 1.4.11 Non-text Contrast, thefocus cursor styling has very poor contrast.
Software (iOS and Android): As described in 2.4.3 Focus Order, focus isoccasionally not managed after user actions or page transitions. Focus
sometimes goes to off-screen elements. Some focus pathing does not matchthe on-screen layout.
Authoring Tool (iOS and Android): As described in 2.4.3 Focus Order, focus

Page 55 of 59

Criteria

Conformance Level• Android: Partially Supports
Software:• iOS: Partially Supports• Android: Partially Supports

Remarks and Explanations
is occasionally not managed after user actions.
Software (iOS and Android): As described in 4.1.2 Name, Role, Value, someelements do not report their state or properties, let alone changes to those
attributes.

Authoring Tool:• iOS: Partially Supports• Android: Partially Supports
Software:• iOS: Supports• Android: Supports

Authoring Tool (iOS and Android): As described in 4.1.2 Name, Role, Value,
some elements do not report their state or properties, let alone changes tothose attributes.

11.5.2.15 Change notification

11.5.2.16 Modifications of statesand properties

11.5.2.17 Modifications of values
and text

11.6 Documented accessibility
usage

11.6.1 User control of accessibility
features

Authoring Tool:• iOS: Supports• Android: Supports
Software:• iOS: Supports• Android: Supports
Authoring Tool:• iOS: Does Not Support• Android: Partially Supports
Heading cell – no response
required
Software:• iOS: Not Applicable• Android: Not Applicable

Authoring Tool:• iOS: Not Applicable• Android: Not Applicable
11.6.2 No disruption of accessibility Software:features• iOS: Supports

Authoring Tool:• iOS: As described in 2.1.1 Keyboard, many of the authoring toolfeatures are not accessible with an external keyboard• Android: As described in 2.1.1 Keyboard, a few authoring tool features
are not accessible with an external keyboard
Heading cell – no response required

Software and Authoring Tool do not act as a control proxy for platform-level
accessibility features.

No disruption to accessibility features provided at the platform level
Page 56 of 59

Criteria

Conformance Level• Android: Supports

Remarks and Explanations

Authoring Tool:• iOS: Supports• Android: Supports
Software:• iOS: Partially Supports• Android: Partially Supports
11.7 User preferences
Authoring Tool:• iOS: Partially Supports• Android: Partially Supports
Heading cell – no response
11.8 Authoring tools
required
Heading cell – no response
11.8.1 Content technology
requiredSee WCAG 2.x section
11.8.2 Accessible content creation (If not authoring tool, enter “NotApplicable”)
Authoring Tool:
11.8.3 Preservation of accessibility• iOS: Not Applicable
information in transformations• Android: Not Applicable
Authoring Tool:
11.8.4 Repair assistance• iOS: Not Applicable• Android: Not Applicable
Authoring Tool:
11.8.5 Templates• iOS: Not Applicable• Android: Not Applicable

Software (iOS and Android): As described in 1.4.4 Resize Text, some text
truncates at larger system text sizes. Some text ignores system text size
settings.
Authoring Tool (iOS and Android): As described in 1.4.4 Resize Text, some
text truncates at larger system text sizes.
Heading cell – no response required
Heading cell – no response required
See information in WCAG 2.x section

Authoring Tool (iOS and Android): No format conversion
Authoring Tool (iOS and Android): No repair assistance mode provided that
prompts authors to create accessible content
Authoring Tool (iOS and Android): No templates provided

Page 57 of 59

Chapter 12: Documentation and Support Services
Criteria
12.1 Product documentation

12.1.1 Accessibility andcompatibility features

12.1.2 Accessible documentation
12.2 Support Services

12.2.2 Information on accessibility
and compatibility features

Conformance Level
Heading cell – no response
required
Software:• iOS: Does Not Support• Android: Does Not Support

Remarks and Explanations

Authoring Tool:• iOS: Does Not Support• Android: Does Not Support
See WCAG 2.x section
Heading cell – no response
required
Software:• iOS: Not Applicable• Android: Not Applicable

Authoring Tool (iOS and Android): There is no editor-specificdocumentation.

Authoring Tool:• iOS: Not Applicable• Android: Not Applicable
Software:• iOS: Does Not Support• Android: Does Not Support

Authoring Tool (iOS and Android): There is no editor-specificdocumentation for support services to use.

12.2.3 Effective communication

12.2.4 Accessible documentation

Authoring Tool:• iOS: Does Not Support• Android: Does Not Support
See WCAG 2.x section

Heading cell – no response required
Software (iOS and Android): Product documentation does not mention
accessibility or compatibility features

See information in WCAG 2.x section
Heading cell – no response required
Software (iOS and Android): Product documentation used by support
services does not mention accessibility or compatibility features

Could not locate any accessibility- or disability-specific feedback, support, or
contact channels. No accessibility or disability accommodations mentioned
in default channels.

See information in WCAG 2.x section

Chapter 13: ICT Providing Relay or Emergency Service Access
Notes: Jira cloud mobile apps are native iOS and Android applications. They are not subject to the requirements of this section.
Page 58 of 59

Legal Disclaimer
The information herein is provided in good faith based on the Jira cloud mobile apps at the time of the review and does not represent a legallybinding claim. Please contact us to report any accessibility errors or conformance claim errors for re-evaluation and correction, if necessary.

Page 59 of 59