ページツリー
メタデータの末尾にスキップ
メタデータの先頭に移動

Voluntary Product Accessibility Template® (VPAT®)

Revised Section 508 Edition Version 2.3

Tested on Jira Server/Data Center 7.13

2018 年 12 月

Table Information for VPAT® Readers

For each of the standards, the criteria are listed by chapter in a table.  The structures of the tables are: the first column contains the criteria being evaluated, the second column describes the level of conformance of the product regarding the criteria and the third column contains any additional remarks and explanations regarding the product.

  • When sections of criteria do not apply, or deemed by the customer as not applicable, the section is noted as such and the rest of that table may be removed for that section.
  • When multiple standards are being recorded in this document, the duplicative sections are noted and responded to only one time.  The duplicate entry will note the cross reference to the data.

Atlassian Pty Ltd Accessibility Conformance Report

Revised Section 508 Edition

VPAT® Version 2.3 – December 2018

Name of Product/Version: Jira

Product Description:    

Jira Software is an agile project management tool that supports any agile methodology, be it scrum, kanban, or your own unique flavor. From agile boards to reports, you can plan, track, and manage all your agile software development projects from a single tool. This is a web application, which has features of an authoring tool to which requirement s under 504 of Chapter 5 apply.

The scope of this VPAT is restricted to Specific pages listed in the table below. This includes 2 support documentation pages reviewed as a sample.

The application was accessed using login credentials provided for the test environment.

Id#

Web Page / Screen / Document Identifier

Location / URL

1

ログイン

/secure/Dashboard.jspa

2

Forgot login

/secure/ForgotLoginDetails.jspa

3

View profile

/secure/ViewProfile.jspa

4

Avatar Modal

/secure/ViewProfile.jspa

5

Preferences Modal

/secure/ViewProfile.jspa

6

View All Projects

/secure/BrowseProjects.jspa?selectedCategory=all&selectedProjectType=all

7

Specific Project

/secure/RapidBoard.jspa?projectKey=SP&r apidView=1&view=planning.nodetail

8

課題

/projects/SP/issues

9

Issue Options Modal

/projects/SP/issues

10

プロジェクト設定

/plugins/servlet/project-config/TCP/summary

11

Project Settings - Details

/secure/project/EditProject!default.jspa?pid=10200

12

Project Settings - Versions

/plugins/servlet/projectconfig/ SP/administer-versions

13

Project Settings - Components

/projects/TCP?selectedItem=com.atlassian.jira.jira-projects-plugin:components-page

14

Create a New Project

/secure/RapidBoard.jspa?projectKey=TEST&rapidView=2&view=planning.nodetail

15

Create a New Project – New Issue

/projects/TEST/issues/?filter=allopenissues

16

リリース

/projects/TCP?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page

17

Version Contents

/plugins/servlet/project-config/TCP/administer-versions?status=unreleased

18

Specific Components

/projects/TCP?selectedItem=com.atlassian.jira.jira-projects-plugin:components-page

19

View All Boards

/secure/ManageRapidViews.jspa

20

Project Board

/secure/RapidBoard.jspa?rapidView=1&view=planning.nodetail

21

Board Configuration

/secure/RapidView.jspa?rapidView=1&tab=filter

22

Create Board Wizard

/secure/ManageRapidViews.jspa

23

Board Configuration - Columns

/secure/RapidView.jspa?rapidView=1&tab=columns

24

Board Configuration - Quick Filters

/secure/RapidView.jspa?rapidView=1&tab=quickFilters

25

Board Configuration - Working Days

/secure/RapidView.jspa?rapidView=1&tab=time

26

Board Configuration - Issue Detail View

/secure/RapidView.jspa?rapidView=1&tab=detailView

27

レポート

/projects/TCP?selectedItem=com.atlassian.jira.jira-projects-plugin:report-page

28

バーンダウン チャート

/secure/RapidBoard.jspa?projectKey=TCP&rapidView=2&view=reporting&chart=burndownChart

29

Avg Age Report

/secure/ConfigureReport!default.jspa?selectedProjectId=10200&projectOrFilterId=project-10200&projectOrFilterName=Testing%20Create%20Project&reportKey=com.atlassian.jira.jira-core-reports-plugin:averageage-report

30

Archive Sprints

/secure/RapidBoard.jspa?projectKey=SP&rapidView=1

31

バックログ

/secure/RapidBoard.jspa?projectKey=TCP&rapidView=2&view=planning

32

Actriv Sprint

/secure/RapidBoard.jspa?rapidView=2&projectKey=TCP

33

Create Issue Modal

/secure/Dashboard.jspa

34

課題

/browse/TCP-3

35

Search Results

/browse/TCP-7?jql=summary%20~%20%22project*%22%20OR%20description%20~%20%22project*%22%20ORDER%20BY%20lastViewed%20DESC

36

System Dashboard

/secure/Dashboard.jspa

37

Manage Dashboard

/secure/ConfigurePortalPages!default.jspa?view=favourites

38

Create Dashboard

/secure/ConfigurePortalPages!default.jspa?view=favourites

39

ダッシュボード

/secure/Dashboard.jspa?selectPageId=10100

40

Add Gadgets Wizard

/secure/ConfigurePortalPages!default.jspa?view=my

41

Share Dashboard

/secure/ConfigurePortalPages!default.jspa?view=my

42

課題

/secure/admin/ViewIssueTypes.jspa

43

Issue Options Modal

/plugins/servlet/project-config/TCP/issuetypes

44

プロジェクト設定

/secure/project/BrowseProjects.jspa?s=view_projects

45

アドオン

/plugins/servlet/upm/marketplace/featured

46

Create new user

/secure/admin/user/UserBrowser.jspa

47

JIRA - Jira Core Server 7.10 documentation-(Support documentation)

https://confluence.atlassian.com/jiracoreserver0710/jira-core-server-7-10-documentation-953145400.html

48

Jira-help-documents-(Support documentation)

https://confluence.atlassian.com/jiracore/jira-core-7-10-x-release-notes-950287441.html

Date: 

2019 年 3 月 26 日

Contact information: 

Peter Scobie

アトラシアン

363 George St, Sydney NSW 2000

メモ:  

Evaluation Methods Used: 

*Automation used aXe core rule engine 3.2

*Manual assessment based on Windows 10 – Firefox 63.0 – NVDA 2018.3.2 

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, at http://www.w3.org/TR/2008/REC-WCAG20-20081211/

Level A (Yes)

Level AA (Yes)

Level AAA (No)

Revised Section 508 standards as published by the U.S. Access Board in the Federal Register on January 18, 2017

Corrections to the ICT Final Rule as published by the US Access Board in the Federal Register on January 22, 2018

(Yes)

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 with equivalent facilitation.
  • 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.0 Report

Tables 1 and 2 also document conformance with: 

  • Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing
  • Chapter 6 – 602.3 Electronic Support Documentation

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

Table 1: Success Criteria, Level A

メモ:

Criteria

Conformance Level 

Remarks and Explanations

1.1.1 Non-text Content (Level A) All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below.

Controls, Input

If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Success Criterion 4.1.2 for additional requirements for controls and content that accepts user input.)

Time-Based Media

If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to Guideline 1.2 for additional requirements for media.)

テスト

If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content.

Sensory

If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content.

CAPTCHA

If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities.

Decoration, Formatting, Invisible

If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology.

Partially Supports

Exceptions:

  1. Some Informative/active images are missing meaningful alternative text in over 4 pages.
  2. Some Informative/active images are missing alternative text in over 16 pages.
  3. The short text alternative is missing in for the complex images in Avg age report and burndown chart screens.


           Accessibility problem it causes:

People who are blind cannot see images on a page. In order to give access to the information conveyed by the image, it must have a text alternative. The text alternative must describe the information or function represented by the image. Screen readers can then use the alternative text to convey that information to the screen reader user.
The text alternative is not appropriate for decorative images in over 5 pages.


  1. Decorative images are missing alt text in over 3 pages.


  1. A decorative image has an empty alt attribute (alt=""), but it also has non-empty title attribute in version contents page.

Accessibility problem it causes:

Decorative images do not add information to the content of a page. Examples of decorative images include an image whose content is provided by adjacent text, or an image that is used just for visual effect such as a hero image, a background image, a stock photo, or a decorative flourish. Decorative images should be coded in such a way that screen readers can ignore them.

  1. The text alternative does not serve the same purpose as the input type image in project settings details screen. 

Accessibility problem it causes:

The text alternative must describe the information or function represented by the image. Screen readers can then use the alternative text to convey that information to the screen reader user.
For informative images - images that convey information - the alternative text must communicate the intent, purpose, or meaning of the image in a way that serves as a true alternative for the image.

1.2.1 Audio-only and Video-only (Prerecorded) (Level A) For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such:

Prerecorded Audio-only

An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.

Prerecorded Video-only

Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.


Supports

There is no time based media available in the current iteration of the product.

1.2.2 Captions (Prerecorded) (Level A) Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such.

Supports

There is no time based media available in the current iteration of the product.

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such.

Supports

There is no time based media available in the current iteration of the product.

1.3.1 Info and Relationships (Level A) Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

Partially Supports 

Exceptions:

  1. aria-hidden="true" is used incorrectly in over 2 pages.

aria-hidden="true" MUST NOT be used on content that screen readers need to access.

Accessibility problem it causes:

Using the aria-hidden="true" attribute on an element removes the element and ALL of its child nodes from the accessibility API making it completely inaccessible to screen readers and other assistive technologies. Aria-hidden may be used with extreme caution to hide visibly rendered content from assistive technologies only if the act of hiding this content is intended to improve the experience for users of assistive technologies by removing redundant or extraneous content.

  1. header cell (<th>) markup is used within a layout table for “AVG age report” screen.

Accessibility problem it causes:

When content is arranged in a layout table that is not properly marked as a layout table, screen readers will erroneously read row and column data as a screen reader user navigates the content. Layout tables should not contain any semantic table markup such as <th> or <caption> elements or summary, scope or headers attributes. 

  1. Data table is missing header and data cell relationship in the calendar page.


  1. The form field does not have an explicit <label> element, title attribute, aria-labelledby or aria-label in over 22 pages.


  1. The form control is not correctly associated with its visible label either explicitly or implicitly in over  10 pages.
  2. The group of form controls is not associated with its group label in over 3 pages.


Accessibility problem it causes:

People who are blind cannot see the organizational structure of a table with data arranged in rows and columns with corresponding header cells. Hence they failed to understand the logical relationships of data arranged in a table. 


They cannot use the visual layout of a form to determine which labels go with which form elements. In order to be certain, which label goes with which form element, the label and form element must be programmatically associated. 


They  cannot use the visual layout of a group of related form elements and their shared group label - such as a question with a set of radio button answers - to determine the relationship between the form fields and the group label. In order to understand the relationship of the form fields, their individual labels, and their group label, the relationships must be expressed semantically.
Grouping controls is most important for related radio buttons and checkboxes.


  1. Heading levels are out of order in such a way that the structure of the page is not properly conveyed in 2 screens.


  1. Text is inappropriately marked as a heading in “issue options modal” and “JIRA - Jira Core Server 7.10 documentation” screen.


  1. Text appears and functions like a section heading but is not marked up as such in 9 pages.
  2. <dl> elements are not  directly contain properly-ordered <dt> and <dd> groups, <script> or <template> elements  in “View all projects” screen.
  3. <dt> and <dd> elements are not contained by a <dl> in 4 pages.
  4. <ul> and <ol> elements are not directly contain <li>, <script> or <template> elements in 3 pages.
  5. Content is not a list but is marked up as such in 5 pages.
  6. The description list is not marked up properly in 2 pages.
  7. The list or list item is not marked up properly in 3 pages.
  8. The nested list is not marked properly in “version contents” screen.
  9. Content appears like a list but is not marked up as such in “specific project” screen.

Accessibility problem it causes:

People who can see are able to quickly scan a page for headings, subheadings and Lists, nested lists to understand the content and structure of a page. People who are blind do not have this ability if heading texts and lists are not marked in a way that screen readers can understand. Heading text and hierarchy must be identified semantically with heading markup and Lists must be marked semantically in a way that correctly identifies the list structure and type. 


1.3.2 Meaningful Sequence (Level A) When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.

Partially supports

Exceptions:

  1. New content is not inserted in the correct location within the DOM in project settings details screen.
  2. The reading order (as determined by code order) is not logical or intuitive in over 3 pages.

Accessibility problem it causes:

Sometimes content must be read in a certain order to be understood. When screen reader users navigate page content, they hear the content in the order of the code in the DOM. If the order of the code and the visual order of content differ in such a way that meaning of content is changed, screen readers users may not understand the content correctly. The order of content in the DOM must be logical. The visual order of the content can differ from the source code order, as long as the reading order for screen readers is still logical and meaningful.

1.3.3 Sensory Characteristics  (Level A) Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound.

Partially supports

例外

  1. Information/instruction is presented in a way that requires the ability to see, and there is no alternate method to convey the information in over  4 pages.

Accessibility problem it causes:

instructions refer to elements on the page by their visual characteristics only and hence cannot be identified by  a vision impaired user.

例:

    1. Refer the “colored boxes on the graph's       legend in Burndown chart screen. They do not have any programmatic text alternative.”
    2. When the "Create Issue" & "Create subtask" modal window is open, and the 'Configure Fields' drop down menu has been opened, a visual cue is used to indicate the selected fields in project boards screen.




1.4.1 Use of Color (Level A) Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

NOTE

This success criterion addresses color perception specifically. Other forms of perception are covered in Guideline 1.3 including programmatic access to color and other visual presentation coding.

Partially supports

例外

  1. Color is used to convey information that is not conveyed in any other way in over 16 pages.


Accessibility problem it causes:

When color alone is used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element, people who are blind, have low vision, or are color blind will not be able to access that information

例:

    1. Refer  the arrows that indicate priority. They are shades of red and yellow pointing upward, and green downward in Create a new project screen.
    2. In the project settings sub-menu, the page that the user find themselves currently on is indicated using color alone.


  1. The color contrast ratio between link text and surrounding text is not at least 3 to 1 in over 20 pages.

Accessibility problem it causes:

When link text is visually differentiated from surrounding body text only by color, people who are color blind or with low vision may miss links. Link text must be differentiated from surrounding text either by: 1) an underline (or similar) in the default state, or 2) a contrast ratio of at least 3.0 to 1 between link text and surrounding text PLUS an underline (or similar) on mouse hover. When link text is adequately distinguished from surrounding text, people who have visual disabilities will be less likely to miss links.

1.4.2 Audio Control (Level A) If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.

NOTE

Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether or not it is used to meet other success criteria) must meet this success criterion. See Conformance Requirement 5: Non-Interference.


Supports

There is no time based media available in the current iteration of the product.

2.1.1 Keyboard (Level A) Level A)

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.

NOTE

This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not.

NOTE

This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.


Partially Supports

例外

  1. Some elements/actions  are not accessible by keyboard alone in over 28 pages.

 

  1. The element uses device-dependent event handlers and is therefore not accessible by keyboard alone in over 10 pages.

Accessibility problem it causes:

Some people cannot use a mouse due to vision or motor disabilities, which results to miss the functionality of an element.

 Content that can be operated with a mouse must also be made operable with keyboard. When content is operable through a keyboard, it becomes operable by a variety assistive technologies such as speech input software, sip-and-puff software, on-screen keyboards, scanning software, and alternate keyboards.

例:

    1. Refer to the "View as wallboard" link. It has tabindex="-1", which does not allow keyboard focus in Login screen.
    2. Applies to the modals from the issue menu (three dots that expand into a menu in the right panel). The elements do not receive keyboard focus and cannot be edited with the keyboard in create a new project screen.

2.1.2 No Keyboard Trap (Level A) If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.

NOTE

Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.


Partially supports.

例外

  1. There is a keyboard trap observed in 3pages.

Accessibility problem it causes:


Sometimes custom widgets, plugins, embedded applications, and other content formats can create a keyboard "trap" where the keyboard focus gets stuck in one place or within a widget or application. Keyboard traps can make interacting with web content extremely difficult or impossible for keyboard users. Keyboard users must be able to move into, and away from, any user interface component, simply by using their keyboard. When keyboard traps are removed, people who rely on a keyboard will be able to access all of the otherwise-accessible content.

2.2.1 Timing Adjustable (Level A) For each time limit that is set by the content, at least one of the following is true:

Turn off

The user is allowed to turn off the time limit before encountering it; or

Adjust

The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or

Extend

The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or

Real-time Exception

The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or

Essential Exception

The time limit is essential and extending it would invalidate the activity; or

20 Hour Exception

The time limit is longer than 20 hours.

NOTE

This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action.

Partially Supports

    1. The site time out function does not provide the user a way to turn off, adjust or extend the time limit in System dashboard screen.

Accessibility problem it causes:

People with disabilities such as blindness, low vision, mobility impairments, and cognitive limitations may require more time to read content or to perform functions such as filling out online forms. If a session has a time limit, it may be difficult or impossible for some users to perform the required action before a time limit occurs. People must have the ability to turn off or extend time limits while interacting with content.

2.2.2 Pause, Stop, Hide (Level A) For moving, blinking, scrolling, or auto-updating information, all of the following are true:

Moving, blinking, scrolling

For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and

Auto-updating

For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.

NOTE

For requirements related to flickering or flashing content, refer to Guideline 2.3.

NOTE

Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.

NOTE

Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so.

NOTE

An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken.

Supports

Atlassian Jira does not contain a part of moving, blinking, scrolling, or auto-updating content.

2.3.1 Three Flashes or Below Threshold (Level A) 

Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.

NOTE

Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.


Supports

Atlassian Jira does not contain a part that flashes more than three times in one second.

2.4.1 Bypass Blocks (Level A) A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.

Partially Supports

例外

Title is missing for the frame in View profile screen.

Accessibility problem it causes:

When iframes do not have titles, screen reader users are not able to determine the content of the iframe - and whether or not they want to interact with it - without first entering and exploring it. Every iframe requires a descriptive and unique title attribute value. This allows screen reader users to understand what type of content to expect within an iframe such as a video, navigation links, advertisement, etc.

2.4.2 Page Titled (Level A) Web pages have titles that describe topic or purpose.

Partially Supports

例外

Page TITLE does not identify purpose of page in 2 pages.

Accessibility problem it causes:

People who are blind cannot visually scan a page for a main heading or similar feature to quickly determine the purpose of a particular page. The <title> element is the first thing a screen reader reads when loading a page or switching to a new browser tab. A descriptive <title> element gives screen reader users a quick overview of a page without having to read the page itself.

2.4.3 Focus Order (Level A) If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.

Partially Supports

例外

  1. There are some empty tab stops are observed in over 3 pages.
  2. Focus order/tab order  is not logical in over 19 screens.

Accessibility problem it causes:

When keyboard focusable components do not receive focus in a logical order, or  results to an empty tab stop people with mobility impairments, reading disabilities, and low vision are all impacted. The keyboard focus order must be logical and consistent with the layout of the content. A logical focus order makes interaction with content predictable for people who rely on a keyboard to interact with web content.


  1. Focus is not maintained within the modal. It is possible to tab out of the modal in over 10 pages.
  2. When the modal is activated, focus is not placed on the modal in over 3pages.
  3. When the modal is closed, focus is not returned to the triggering element in over 11 pages.


Accessibility problem it causes:

Modal dialogs overlay page content and prevent users from interacting with the content behind the modal dialog until it is dismissed. If sighted keyboard users or screen reader users can tab to content behind a modal dialog window, they may become disoriented or confused. Both keyboard focus and screen reader focus must be trapped within a modal dialog until it is dismissed. When both keyboard focus and browsing are trapped within a modal dialog, screen reader users are able to interact with it as intended.

  1. Item in focus is visibly hidden but still keyboard accessible in over 3 screens.

Accessibility problem it causes:

When an element that is not visible receives keyboard focus, sighted keyboard users and screen reader users may be left wondering if they are missing content or functionality. Every focusable element must have content and be visible. Then sighted keyboard users and screen reader users will know where their focus is and can be certain they are not missing content or functionality.

  1. The menu is not the next thing in the sequential navigation order after the control that triggered the menu in Dashboard screen.
  2. The modal is not the next thing in the sequential navigation order after the control that triggered the modal in Calendar. 

Accessibility problem it causes:

When a person who is blind opens a modal dialog and keyboard focus is not moved to it, it can be extremely difficult, if not impossible, to know that the modal dialog has appeared and to interact with it. Keyboard focus must be moved to an appropriate place in the modal dialog. This allows screen readers to announce the modal dialog and allow users to interact with the modal dialog with the keyboard.

  1. When the tooltip is closed, focus is not returned to the triggering element in Dashboard and Add gadgets wizard screen.

Accessibility problem it causes:

When a tooltip dialog is closed, if focus is not explicitly placed back on an element, keyboard focus and screen reader focus will be lost - sometimes sending the focus back to the top of the DOM. Screen reader users may become disoriented, not hearing their new location and not knowing where their focus is. When a modal dialog is closed, focus must be placed back on the element that triggered the modal dialog or, if that element no longer exists, on another element that provides a logical workflow. This allows screen readers to announce the element that has received focus so screen reader users know where they are and allows keyboard users to interact logically with the content.

  1. The use of TABINDEX is not logical and has created a tab order that does not preserve the meaning of the element in “left navigation” screen.
  2. Visual focus moves, but programmatic focus remains on the same element in Specific project screen.

Accessibility problem it causes:

When keyboard focusable components do not receive focus in a logical order, people with mobility impairments, reading disabilities, and low vision are all impacted. The keyboard focus order must be logical and consistent with the layout of the content. (Note: This does not mean that the focus order has to be identical to the visual order, as long as the user can still understand and operate the content.) A logical focus order makes interaction with content predictable for people who rely on a keyboard to interact with web content.




2.4.4 Link Purpose (In Context) (Level A) The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.

Partially Supports.

例外

The purpose of the link is not clear within its context in view profile screen.

Accessibility problem it causes:

When link text - along with its immediately surrounding content - does not completely describe the destination of a link, people who are blind, and people with mobility impairments, reading disabilities, and low vision may have more difficulty understanding the purpose of a link so they can decide whether they want to follow the link. In order to sufficiently describe a link's destination, the link text and its immediately surrounding content must provide a complete description of the destination. 

3.1.1 Language of Page (Level A) The default human language of each Web page can be programmatically determined.

Partially Supports.

例外

The primary language of the page is not defined in over 2 pages.

Accessibility problem it causes:

Most screen readers can read several different languages. Screen reader users select a default language when installing and configuring their screen reader. If no language is specified in the HTML document, the screen reader will read the document in the user's default language with a pronunciation that often makes it impossible to understand the content, if default language doesn't match the document language. 

3.2.1 On Focus (Level A) When any user interface component receives focus, it does not initiate a change of context.

Partially Supports.

例外

When the element gains keyboard focus, there is an unannounced change to the page in Archive sprints screen.

Accessibility problem it causes:

When a major change of context occurs - such as an opening a new window, moving focus to another element, a submitting a form - while a keyboard user is tabbing through a page, they may become quite disoriented or, much worse, they may be completely blocked from using the content. Any component that is able to trigger an event when it receives focus must not change the user's context. This will ensure that keyboard users can successfully navigate their way through a page in a predictable manner.

3.2.2 On Input (Level A) Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.

Partially Supports.

例外

When the user selects or inputs a value, a substantial change occurs without warning in System dashboard screen.

Accessibility problem it causes:

People expect that selecting a link or a button may cause a change of context - such as an opening a new window or page, moving focus to another element, a submitting a form. Whenever the mere act of entering text into an edit box, checking a checkbox or radio button, or navigating to an option in a select control causes an unexpected change in context, some users - especially people with vision or cognitive disabilities - may become quite disoriented or confused. Changes in context should only occur when selecting a link or button - not when changing the setting of a checkbox, radio button or select - unless the user is informed ahead of time. This will ensure that users can interact with a page in a predictable manner.

3.3.1 Error Identification (Level A) If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.

Partially supports.

例外

Input validation failures are not described in text in create dashboard and share dashboard screens.

Accessibility problem it causes:

When form fields that have an error are not clearly identified with a text-based error message people who are blind or have low vision may not be able to understand that an error has occurred and what went wrong. In order to provide feedback that can be accessed by all users, error messages must be provided in a text format. Error messages must indicate which input is in error - either by the text of the error message or programmatically - and the nature of the error. This will allow people to recover from mistakes while filling out a form.

3.3.2 Labels or Instructions (Level A) Labels or instructions are provided when content requires user input.

Partially supports.

例外

  1. No visual label is present and the purpose of this field is not clear without a visual label in over 7 screens.
  2. Label is not persistent in Create a new project-new issue and specific project screens.
  3. field labels do not remain visible in over 5 pages.
  4. Additional instructions to successfully use the component are needed but not provided for people with disabilities in over 4 pages.

Accessibility problem it causes:

Filling out forms correctly can be one of the more time consuming and frustrating online user experiences, and it can be even more challenging for people with disabilities. The single easiest way to prevent user errors is by providing clear and persistent labels and instructions that are available to everyone at all times. Labels and instructions should: 

1) be clear and informative, 

2) disclose any constraints such as required data formats or ranges, and 

3) identify required fields. Well-designed labels and instructions provide enough information so people can fill out forms without undue confusion or errors.


4.1.1 Parsing (Level A) In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.

NOTE

Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete.

Partially supports

例外

  1. ARIA attributes must conform to valid values but not coded so in over 15 pages.
  2. Required ARIA children role not present: (menu item, menuitemradio, menuitemcheckbox )  in over  5 pages.
  3. Html elements are not properly nested in “Jira help documentation” screen.

Accessibility problem it causes:

Invalid code - such as incorrectly nested elements - doesn't always cause accessibility problems, but it can, especially if there are errors in the parts of the markup that screen readers rely on to communicate the semantics of the web page to users. Incorrectly nested elements - have the potential to cause serious or critical issues for screen reader users.

  1. The page contains duplicate id values in over 17  pages.

Accessibility problem it causes:

Invalid code - such as duplicate IDs on a page - doesn't always cause accessibility problems, but it can, especially if there are errors in the parts of the markup that screen readers rely on to communicate the semantics of the web page to users. Duplicate ID values have the potential to cause serious or critical issues for screen reader users with form labels, custom widget labels, error message / form field associations, table header associations, and any aria- attributes (such as aria-labelledby and aria-describedby) that reference ID values. 

4.1.2 Name, Role, Value (Level A) For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.

NOTE

This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification.


Partially supports.

例外

  1. There are aria attributes, which are extensively used in the menu, which are not needed and creates limited access or no access to the elements present in the menu in Issues screen.
  2. The element appears and functions like a button but is not marked up as such in over 14 pages.
  3. Incorrect/incomplete use of ARIA for the custom control fails to expose an element to assistive technologies in over 12 pages.
  4. The element appears and functions like a link but is not marked up as such in left navigation screen.
  5. The element appears and functions like a menu but is not marked up as such. The state of the active menu too is not exposed to assistive technology in over 2 pages. 
  6. The element appears and functions like a menu and is not appropriately marked up as such in issue screen.
  7. Elements appear and function like tabs but are not marked up as such. The state of the active tab too is not exposed to assistive technology in over 7 screens.
  8. The button does not have an accessible name. As a result its purpose/function is not exposed to assistive technology users in over 8 pages.
  9. Buttons are missing discernible text in over 7 pages.
  10. The custom control does not have a text label/name in issues screen.
  11. Link missing accessible name in over 8 pages.
  12. Link missing discernible text in over 16 pages.

Accessibility problem it causes:

Every user interface control must have a role along with any applicable states and properties so that screen reader users know how to interact with the control. Native HTML elements - such as <button>, <a>, <input>, <select> - already have a role, and their necessary states. If you create a custom version of a native HTML element or a custom control or widget that does not have a native HTML equivalent, you must add the relevant role(s) and any applicable states and properties using ARIA as well as expected keyboard interactions.

In addition, the action of the control should be achievable by screen reader users as well.


  1. Auto-suggested names are not exposed in Issue options modal screen.

Accessibility problem it causes:

screen reader and other assistive technology users should know the Auto suggestion feature availability and functionality of the control otherwise they may lose the functionality of an element .

  1. Current state is not being conveyed to screen reader user in over 5 pages.
  2. Custom checkbox missing role and state in Issue options modal screen.
  3. Link's current sort-order is not conveyed in create a new project-new issue and search results screen.
  4. Pressed state is not being conveyed to screen reader user in system dashboard screen.
  5. The expanded/collapsed state is not exposed to assistive technology in over 15 pages.
  6. Selected state is not being conveyed to screen reader user in over 4 pages.
  7. Table sort state is not being announced to the screen reader in system dashboard screen.

Accessibility problem it causes:

States and properties are attributes used to convey essential information about an element to screen readers and other assistive technologies. Some roles require certain state and property information - such as the checked/unchecked state of a checkbox .Native HTML elements provide those required states and properties, so nothing more needs to be done. If you create a custom version of a native HTML element or a custom control or widget that does not have a native HTML equivalent, you must add the relevant states and properties using ARIA. for example, aria-current for currently active element.


  1. date picker function is not compatible with AT in over 3 pages.
  2. Drop down inaccessible to the screen readers in Specific project screen.
  3. Element not accessible to screen reader in create a new project and create a new project-new issue screens.
  4. Menu items not accessible by screen reader in Project settings screen.
  5. Screen reader cannot activate links in expanded menus in over 2 pages.
  6. The screen reader focus cannot advance past the Description field in Create issue modal.
  7. Button not accessible to screen reader users in Create a new project-new issue screen.
  8. Cannot activate menu items while screen reader in use in Search results screen.
  9. The information that the 'Widget' is added to the parent page is not exposed to screen reader users in Add widgets modal.
  10. Text (sprint label)not announced by screen reader in “Issue” screen.


Accessibility problem it causes:

Content that can be operated and achieved by visual users also be made operable with screen reader users as well. Otherwise they would not able to achieve the functionality of the control.

  1. The link does not have an href value defined in over 3 pages.

Accessibility problem it causes:

Links made from <a> elements must have an href attribute to be valid hyperlinks. Without an href attribute, screen readers will not know that the text within the <a> element is a hyperlink and it will not be keyboard focusable.


Table 2: Success Criteria, Level AA

メモ:

Criteria

Conformance Level 

Remarks and Explanations

1.2.4 Captions (Live) (Level AA) Captions are provided for all live audio content in synchronized media.

Supports

There is no time based media  available in the current iteration of the product.

1.2.5 Audio Description (Prerecorded) (Level AA) Audio description is provided for all prerecorded video content in synchronized media.

Supports

There is no time based media  available in the current iteration of the product.

1.4.3 Contrast (Minimum) (Level AA) The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following:

Large Text

Large-scale text and images of large-scale text have a contrast ratio of at least 3:1;

Incidental

Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.

Logotypes

Text that is part of a logo or brand name has no contrast requirement.


Partially supports

例外

  1. Few Link texts and regular texts lacks 4.5 to 1 contrast ratio  with their background colors in  over 38 pages.
  2. The color contrast ratio between the link text and its background is not at least 4.5 to 1 on hover and/or on focus in over 9 pages.

Accessibility problem it causes:

People who have low vision or are colorblind may have difficulty reading text if the contrast between the text its background is insufficient. When the contrast ratio between text and its background is adequate, people who have low vision or are colorblind are more likely to be able to read the text.


1.4.4 Resize text (Level AA) Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.

Partially supports.

例外

  1. Text content is lost at 200% zoom in over 5 pages.
  2. Zooming and scaling is disabled in “Forgot login” screen.

Accessibility problem it causes:

People who have low vision may not be able to read text at its default size. Browsers allow people to zoom the page, but sometimes the text is cut off or functionality is obscured as the page is zoomed. Content must be flexible enough to be scaled to 200% by the browser without having text cut off or functionality lost. When text is able to be scaled up to 200% by the browser, more people with mild visual disabilities will be able to read it without requiring the use of assistive technology such as a screen magnifier.


1.4.5 Images of Text (Level AA) If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following:

Customizable

The image of text can be visually customized to the user's requirements;

Essential

A particular presentation of text is essential to the information being conveyed.

NOTE

Logotypes (text that is part of a logo or brand name) are considered essential.


Supports.

Atlassian does not contain any images of text content.

2.4.5 Multiple Ways (Level AA) More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process.

Supports.


2.4.6 Headings and Labels (Level AA) Headings and labels describe topic or purpose.

Partially supports.

例外

  1. The label does not clearly convey the purpose of the control in over 2 pages.
  2. The label does not clearly convey the purpose of the control in system dashboard screen.

Accessibility problem it causes:

The label should properly convey the purpose of the form field. This is especially true for people with reading or other cognitive disabilities and people who are blind and use a screen reader. When labels/headings are not clear and descriptive, people can find the difficulties  in seeking the information and understand the relationships between different parts of the content .

2.4.7 Focus Visible (Level AA) Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.

Partially supports.

例外

  1. The focus indicator (e.g. border or dotted underline / background etc.) is not clearly visible as one tabs through the page in over 19 pages.

Accessibility problem it causes:

When a visible keyboard focus indicator is not provided, sighted keyboard users will have no idea which link or control has focus making it extremely difficult, if not impossible, to interact with the content. 

3.1.2 Language of Parts (Level AA) The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.

Supports.

The content of all pages tested only have content in the primary language.

3.2.3 Consistent Navigation (Level AA) Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.

Supports


3.2.4 Consistent Identification (Level AA) Components that have the same functionality within a set of Web pages are identified consistently.

Supports


3.3.3 Error Suggestion (Level AA) If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.

Supports


3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true:

Reversible

Submissions are reversible.

Checked

Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.

Confirmed

A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.


Supports


Revised Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Note: Not applicable (Reference: E204.1 and E205.4 of Appendix A to Part 1194 – Section 508 of the Rehabilitation Act:
Application and Scoping Requirements.

Criteria

Conformance Level 

Remarks and Explanations

302.1 Without Vision:

Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that does not require user vision.



302.2 With Limited Vision:

Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited vision.



302.3 Without Perception of Color:

Where a visual mode of operation is provided, ICT shall provide at least one visual mode of operation that does not require user perception of color.



302.4 Without Hearing:

Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that does not require user hearing.



302.5 With Limited Hearing:

Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited hearing.



302.6 Without Speech:

Where speech is used for input, control, or operation, ICT shall provide at least one mode of operation that does not require user speech.



302.7 With Limited Manipulation:

Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that does not require fine motor control or simultaneous manual operations.



302.8 With Limited Reach and Strength:

Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that is operable with limited reach and limited strength.



302.9 With Limited Language, Cognitive, and Learning Abilities:

ICT shall provide features making its use by individuals with limited cognitive, language, and learning abilities simpler and easier.



Chapter 4: Hardware

Notes: The ICT covered by this VPAT is not hardware. As such, the requirements of this chapter do not apply. 

Chapter 5: Software

メモ:

Criteria

Conformance Level 

Remarks and Explanations

501.1 Scope – Incorporation of WCAG 2.0 AA:

The requirements of Chapter 5 shall apply to software where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.

EXCEPTION: Where Web applications do not have access to platform accessibility services and do not include components that have access to platform accessibility services, they shall not be required to conform to 502 or 503 provided that they conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0.

See WCAG 2.0 section

See information in WCAG section

502 Interoperability with Assistive Technology

Heading cell – no response required

Heading cell – no response required

502.2.1 User Control of Accessibility Features:

Platform software shall provide user control over platform features that are defined in the platform documentation as accessibility features.

Not Applicable

As it is a web only application

502.2.2 No Disruption of Accessibility Features:

Software shall not disrupt platform features that are defined in the platform documentation as accessibility features.

Not Applicable

As it is a web only application

502.3 Accessibility Services:

Platform software and software tools that are provided by the platform developer shall provide a documented set of accessibility services that support applications running on the platform to interoperate with assistive technology and shall conform to 502.3. Applications that are also platforms shall expose the underlying platform accessibility services or implement other documented accessibility services.

Heading cell – no response required

Heading cell – no response required

502.3.1 Object Information:

The object role, state(s), properties, boundary, name, and description shall be programmatically determinable.

Not Applicable

As it is a web only application

502.3.2 Modification of Object Information:

States and properties that can be set by the user shall be capable of being set programmatically, including through assistive technology.

Not Applicable

As it is a web only application

502.3.3 Row, Column, and Headers:

If an object is in a data table, the occupied rows and columns, and any headers associated with those rows or columns, shall be programmatically determinable.

Not Applicable

As it is a web only application

502.3.4 Values:

Any current value(s), and any set or range of allowable values associated with an object, shall be programmatically determinable.

Not Applicable

As it is a web only application

502.3.5 Modification of Values:

Values that can be set by the user shall be capable of being set programmatically, including through assistive technology.

Not Applicable

As it is a web only application

502.3.6 Label Relationships:

Any relationship that a component has as a label for another component, or of being labeled by another component, shall be programmatically determinable.

Not Applicable

As it is a web only application

502.3.7 Hierarchical Relationships:

Any hierarchical (parent-child) relationship that a component has as a container for, or being contained by, another component shall be programmatically determinable.

Not Applicable

As it is a web only application

502.3.8 Text:

The content of text objects, text attributes, and the boundary of text rendered to the screen, shall be programmatically determinable.

Not Applicable

As it is a web only application

502.3.9 Modification of Text:

Text that can be set by the user shall be capable of being set programmatically, including through assistive technology.

Not Applicable

As it is a web only application

502.3.10 List of Actions:

A list of all actions that can be executed on an object shall be programmatically determinable.

Not Applicable

As it is a web only application

502.3.11 Actions on Objects:

Applications shall allow assistive technology to programmatically execute available actions on objects.

Not Applicable

As it is a web only application

502.3.12 Focus Cursor:

Applications shall expose information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface components.

Not Applicable

As it is a web only application

502.3.13 Modification of Focus Cursor:

Focus, text insertion point, and selection attributes that can be set by the user shall be capable of being set programmatically, including through the use of assistive technology.

Not Applicable

As it is a web only application

502.3.14 Event Notification:

Notification of events relevant to user interactions, including but not limited to, changes in the component’s state(s), value, name, description, or boundary, shall be available to assistive technology.

Not Applicable

As it is a web only application

502.4 Platform Accessibility Features:

Platforms and platform software shall conform to the requirements in ANSI/HFES 200.2, Human Factors Engineering of Software User Interfaces — Part 2: Accessibility (2008) listed below:

A. Section 9.3.3 Enable sequential entry of multiple (chorded) keystrokes;

B. Section 9.3.4 Provide adjustment of delay before key acceptance;

C. Section 9.3.5 Provide adjustment of same-key double-strike acceptance;

D. Section 10.6.7 Allow users to choose visual alternative for audio output;

E. Section 10.6.8 Synchronize audio equivalents for visual events;

F. Section 10.6.9 Provide speech output services; and

G. Section 10.7.1 Display any captions provided.

Not Applicable

As it is a web only application

503 Applications

Heading cell – no response required

Heading cell – no response required

503.2 User Preferences:

Applications shall permit user preferences from platform settings for color, contrast, font type, font size, and focus cursor.

EXCEPTION: Applications that are designed to be isolated from their underlying platform software, including Web applications, shall not be required to conform to 503.2.

Not Applicable

As it is a web only application

503.3 Alternative User Interfaces:

Where an application provides an alternative user interface that functions as assistive technology, the application shall use platform and other industry standard accessibility services.

Not Applicable

As it is a web only application

503.4 User Controls for Captions and Audio Description:

Where ICT displays video with synchronized audio, ICT shall provide user controls for closed captions and audio descriptions conforming to 503.4.

Heading cell – no response required

Heading cell – no response required

503.4.1 Caption Controls:

Where user controls are provided for volume adjustment, ICT shall provide user controls for the selection of captions at the same menu level as the user controls for volume or program selection.

Not Applicable

As it is a web only application

503.4.2 Audio Description Controls:

Where user controls are provided for program selection, ICT shall provide user controls for the selection of audio descriptions at the same menu level as the user controls for volume or program selection.

Not Applicable

As it is a web only application

504 Authoring Tools

Heading cell – no response required

Heading cell – no response required

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

Authoring tools shall provide a mode of operation to create or edit content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 for all supported features and, as applicable, to file formats supported by the authoring tool. Authoring tools shall permit authors the option of overriding information required for accessibility.

See WCAG 2.0 section

See information in WCAG section

504.2.1 Preservation of Information Provided for Accessibility in Format Conversion:

Authoring tools shall, when converting content from one format to another or saving content in multiple formats, preserve the information required for accessibility to the extent that the information is supported by the destination format.


Partially supports.

Supported formats: XML and Microsoft Word.

Not all accessibility markup from the source page are carried over to the saved Word doc

For instance, logical reading order in the source document is not reflected correctly in the destination word document.


504.2.2 PDF Export:

Authoring tools capable of exporting PDF files that conform to ISO 32000-1:2008 (PDF 1.7) shall also be capable of exporting PDF files that conform to ANSI/AIIM/ISO 14289-1:2016 (PDF/UA-1).

Does not support.

Output PDF is untagged and has multiple accessibility issues.

504.3 Prompts:

Authoring tools shall provide a mode of operation that prompts authors to create content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 for supported features and, as applicable, to file formats supported by the authoring tool.

Does not support. 

While adding an attachment like a screenshot, the tool does  not

prompt for a caption that could serve as alternate text.


504.4 Templates:

Where templates are provided, templates allowing content creation that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 shall be provided for a range of template uses for supported features and, as applicable, to file formats supported by the authoring tool.

Partially supports.


No template pages were observed in the scope of testing.

Chapter 6: Support Documentation and Services

メモ:

Criteria

Conformance Level 

Remarks and Explanations

601.1 Scope:

The technical requirements in Chapter 6 shall apply to ICT support documentation and services where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.

Heading cell – no response required

Heading cell – no response required

602 Support Documentation

Heading cell – no response required

Heading cell – no response required

602.2 Accessibility and Compatibility Features:

Documentation shall list and explain how to use the accessibility and compatibility features required by Chapters 4 and 5. Documentation shall include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

Not applicable.

Requirement#502 of Chapter5 applies mainly to software and not to a Web application.

602.3 Electronic Support Documentation:

Documentation in electronic format, including Web-based self-service support, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0.

See WCAG 2.0 section

See information in WCAG section

602.4 Alternate Formats for Non-Electronic Support Documentation:

Where support documentation is only provided in non-electronic formats, alternate formats usable by individuals with disabilities shall be provided upon request.

Not applicable.

Support documentation is provided electronically.

603 Support Services

Heading cell – no response required

Heading cell – no response required

603.2 Information on Accessibility and Compatibility Features:

ICT support services shall include information on the accessibility and compatibility features required by 602.2.

Not applicable.

Requirement#502 of Chapter5 applies mainly to software and not to a Web application. Besides, ICT support services were not evaluated as part of this scope.

603.3 Accommodation of Communication Needs:

Support services shall be provided directly to the user or through a referral to a point of contact. Such ICT support services shall accommodate the communication needs of individuals with disabilities.

Not supported.

Product support available to paying customer was not evaluated as part of this scope.

Pages / Documents That Do Not Support One or More Success Criteria   

  1. Add Gadgets Wizard
  2. Add widgets modal
  3. Archive Sprints
  4. Avatar Modal
  5. Avg Age Report
  6. Board Configuration
  7. Board Configuration - Columns
  8. Board Configuration - Issue Detail View
  9. Board Configuration - Quick Filters
  10. Board Configuration - Working Days
  11. バーンダウン チャート
  12. Create a New Project
  13. Create a New Project – New Issue
  14. Create Board Wizard
  15. Create Dashboard
  16. Create Issue Modal
  17. ダッシュボード
  18. Forgot Login
  19. 課題
  20. Issue Options Modal
  21. 課題
  22. ログイン
  23. Manage Dashboard
  24. Preferences Modal
  25. Project Board
  26. プロジェクト設定
  27. Project Settings - Components
  28. Project Settings - Details
  29. Project Settings - Versions
  30. リリース
  31. レポート
  32. Search Results
  33. Share Dashboard
  34. Specific Components
  35. Specific Project
  36. System Dashboard
  37. Version Contents
  38. View All Boards
  39. View All Projects
  40. View Profile
  41. JIRA - Jira Core Server 7.10 documentation
  42. Jira exported word for an issue.
  43. Printable HTML output
  44. Jira-help-documents.
  • ラベルなし