History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRA-5574
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Jeff Turner [Atlassian]
Votes: 7
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
JIRA

Accessibility: Section 508 compliance

Created: 30/Dec/04 08:30 PM   Updated: 27/Feb/08 11:00 PM
Component/s: Web interface
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Participants: Hildy Feen, Ivan Benko [Atlassian], Jeff Turner [Atlassian], Jeffrey Walker [Atlassian], Jennifer Sutton, Jim Fruchterman, Mark D. Hamill and Scott Farquhar [Atlassian]
Since last comment: 20 weeks, 6 days ago
Labels:


 Description  « Hide
There are various improvements we could make to JIRA's accessibility:

http://www.webaim.org/standards/508/checklist

Section 508 compliance is necessary for sales to the US federal government sector.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Scott Farquhar [Atlassian] - 05/Jan/05 10:31 PM
We can use Bobby to test conformance:

http://bobby.watchfire.com


Mark D. Hamill - 13/Feb/07 08:34 AM
I would like to add how important 508 compliance is for the federal government sector. I am trying to get a waiver to purchase JIRA, but I am not sure I will be able to do it.

In general making the software WAI compliant should swat 508 compliance too. I have done limited testing on JIRA for 508 compliance. It is mostly not using <label> tags with forms, ALT text with images and having accessible HTML tables.

This will open up new markets for the product. Please do it!


Jeffrey Walker [Atlassian] - 15/Feb/07 08:43 AM
email to Jeffrey,

Yes, I am sorry to report JIRA has other accessibility issues. The U.S. federal government has a number of very specific criteria on what it takes for a web application to be considered accessible to those who are blind or have other visual impairments. We use software call ACCVerify to check web pages to see if they comply with Section 508 of the Rehabilitation Act, which is the law that we must follow. As I suggested though, if you follow WAI accessibility guidelines you also tend to solve 508 issues.

Here are some links:

http://section508.gov/index.cfm?FuseAction=Content&ID=12#Web

http://www.w3.org/WAI/

As I noted in the login page alone you have an image without an ALT attribute and an <input> field where the markup is not associated with text wrapped in the <label> tag. Since JIRA uses lots of tables, I suspect tables are missing column and row markup that would provide easy access to this information.

I am not sure I will be able to get a waiver to use the JIRA product, which would be a shame because it is an excellent product and I am sure you could use the sale. I hope your company will consider adding this compliance. If you have a templating system behind the scenes it would probably not be a terribly burdensome thing to add it.

I realize there are operating system features that improve accessibility however it doesn't matter from the U.S. government perspective. A web application out of the box must comply with Section 508 for it to be purchased.

Mark D. Hamill
Chief, National Internet Data Systems Unit
National Water Information System
U.S. Geological Survey
437 National Center
Reston, VA 20192

mdhamill@usgs.gov
Room 5A124
(703) 648-5298 FAX: (703) 648-5644


Hildy Feen - 15/Mar/07 04:52 PM
I, too, am interested in JIRA being Section 508 compliant. I have a user with disabilities who can not use JIRA. I understand that the JIRA sidebar frame takes up at least 50% of her screen real estate. Is there a way to suppress the sidebar frame and get the same functionality another way? At my work place, we are currently using JIRA (and Confluence) on several projects and are evaluating JIRA for our whole division. Being a State University, not being Section 508 compliant is a problem.

Thank you!

Hildy Feen
Sr. Information Processing Consultant
Univ. of WI-Madison
Div. of Information Technology
Madison, WI 53706
hildy.feen@doit.wisc.edu
608-263-6402


Jennifer Sutton - 29/Mar/07 03:54 PM
there are at least 2 blind user at my company that need Jira to be more accessible. some specific examples include:
1) inaccessible captcha for registration (there is a Jira bug already on this issue, #7460)
2) links don't read first letter with screen reader in firefox (e.g. HOME/BROWSE PROJECT/FIND ISSUES/CREATE NEW ISSUE at top of page, i.e. CREATE reads as "reet")
3) screen readers don't find the comment boxes and when you try to edit, it doesn't tell you that you are in the screen readers edit mode (also in Firefox)

Note that some of these work better in Internet Explorer


Jim Fruchterman - 31/Mar/07 05:00 AM
I was on the 508 Committee, and echo these concerns. Shouldn't be all that hard to nail most of the issues.

Ivan Benko [Atlassian] - 27/Feb/08 11:00 PM
http://about.becta.org.uk/
It is for people with disabilities such as those with sight difficulties.

(3:47 PM) Adele: It is pretty important that we know
(3:47 PM) Adele: We are looking at integrating the product into our software