Hello,

While testing for 508 compliance for the Application Life Cycle Management / Mobile Carwash project, it was found that JIRA is not in compliance with the Federal Government 508/ Accessibility policies. Below are instances where such compliance is lacking. This purpose of this ticket is to bring these issues to your attention in the hopes that they are addressed or there is a remediation plan in place.

Please see details below. We have also included a Best Practice Recommendation for each issue and the reasons a fix should be implemented. Also, issue snapshots can be accessed through the attached PDF. Thank you!

Date Tested: 11/05/13
Point of Contact: Doug Hansen; Phone: 202-447-0790; Email: Doug.Hansen@hq.dhs.gov
DHS Component: OCIO/MGMT/ESDO
Project Name: Application Life Cycle Management / Mobile Carwash
Project Description: Provide a streamlined testing platform to mobile applications development teams within the Federal Government
Product Name & Version: Atlassian JIRA 6.1

508 ISSUES:
NOTE: See attached PDF for screen shots of each documented 508 Accessibility issue.

1). 21(a); 21(c) 1.1 Keyboard Access
A. An interactive element or function cannot be accessed or activated by keyboard.
Example: Cannot access first menu via keyboard

B. An interactive element or function cannot be accessed or activated by keyboard.
Example: Some applet icons are not keyboard accessible

C. An interactive element or function cannot be accessed or activated by keyboard.
Example: Keyboard shortcuts help screen is not keyboard scrollable

D. An interactive element or function cannot be accessed or activated by keyboard.
Example: Credits page: cannot access names via keyboard

E. An interactive element or function cannot be accessed or activated by keyboard.
Example: Cannot access Configure Fields via keyboard

F. At any time, there is no visual indication of the current focus (loss of focus).
Example: Visible focus lost in several places, e.g. after Tools menu

Best Practice Recommendation: Make all icons, images, fields, and interactive elements and functions accessible via keyboard.


2) B08 3.1 Color Dependence
A. In software, information is provided only by color.
Example: Toggle control shows which is selected by use of color only

Best Practice Recommendation: Provide information via other means beside color


3). 22(a) B07 2.2 Web: Images
A. A Web image does not have an ALT, TITLE or ARIA attribute.
Example: Some images (e.g. photo placeholder) are missing ALT/TITLE

Best Practice Recommendation: Include ALT, TITLE or ARIA attribute


4). 22(d) B22 11 Web: Style sheet Dependence
A. Programming code or other confusing elements are revealed on the page.
Example: Code is displayed when CSS is disabled

B. Programming code or other confusing elements are revealed on the page.
Example: Unidentified elements (e.g. unlabeled button) are revealed

Best Practice Recommendation: Remove confusing elements revealed on page


*5). 22(g) B13 10 Web: Data Tables*
A. Any data table's row or column headers are not identified programmatically.
Example: Tables are missing SCOPE markup

B. Any data table's row or column headers are not identified programmatically.
Example: Calendar is missing SCOPE=col

Best Practice Recommendation: Identify a table’s row/column programmatically.


*6). 22i B23 12 Web: Frames*
A. An iframe's Title or Name is non-descriptive.
Example: iframe names are not descriptive of content

Best Practice Recommendation: Include description on iframe.


7). 22(l), 31(a), 31(b) B161.2.3 Web: Links and User Controls
A. A scripted element does not have a unique and meaningful description.
Example: Javascript elements are missing description

Best Practice Recommendation: Include description on scripted elements


8). 22n B11 1.2.2 Web: Forms
A. A Web form field has no markup to associate it to its complete instructions and cues.
Example: Some form fields do not have associative markup (e.g. Search Filters)

B. A Web form field has no markup to associate it to its complete instructions and cues.
Example: Some instructions are not associated with their input fields

C. A Web form field has no markup to associate it to its complete instructions and cues.
Example: Error messages are not associated with their input fields

Best practices recommendation: Include associated markup with web forms


9). 22(o) B05 13 Web: Repetitive Content and Links
A. There is no method to skip repetitive content.
Example: No skip method provided

Best Practice Recommendation: Include a method to skip repetitive content


10). 22(p)B25 7 Time Outs
A. The application timed out without notification.
Example: No notification given

B. The application timed out without an option to request more time.
Example: No notification given

Best Practice Recommendation: Add notification for users before application timeouts


11). 31(a), 31(b) B16 1.2.3 Web: Links and User Controls
A. A link does not have a unique and meaningful description.
Example: "More" links and "Type …" links

B. A link does not have a unique and meaningful description.
Example: Some links are not uniquely identified

Best Practice Recommendation: Add unique and detailed descriptions to links


12). 31(a), 31(b) B17 9.1 Web: Language
A. The correct default language for the page is not programmatically set.
Example: Not specified

Best Practice Recommendation: Programmatically set the default language


13). 31(b) B09 3.2 Color Contrast
A. The contrast ratio is less than 4.5:1 for content background and foreground colors.
Example: Gray dropdown arrows (3.81:1)

B. The contrast ratio is less than 4.5:1 for content background and foreground colors.
Example: Selected menu (4.16:1)

C. The contrast ratio is less than 4.5:1 for content background and foreground colors.
Example: Grey text (2.61:1)

D. The contrast ratio is less than 4.5:1 for content background and foreground colors.
Example: Footer text (4.27:1)

Best Practice Recommendation: Increase contrast ratio to 4.5:1 for content background and foreground colors