[KRRM-3] Research and Document Accessibility Standards for Kuali projects Created: 14/Sep/09  Updated: 08/Feb/12  Resolved: 07/Feb/12

Status: Resolved
Project: Kuali Rice Roadmap
Component/s: KEN, KEW, KNS - UI Struts Framework
Affects Version/s: None
Fix Version/s: Unspecified Future Release

Type: Rice Research Item Priority: Major
Reporter: Chris Coppola (Inactive) Assignee: Unassigned
Resolution: Complete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relate
relates to KULRICE-6092 Create Accessibility Status Report fo... Closed
Rely
is relied upon by KRRM-131 Implement Accessibility Standards Open
Priority Score: 6
Priority - KFS: Low
Priority - KC: Low
Priority - KS: Low
Priority - Rice: High
Theme:
Accessibility
Application Impact: No Impact
Effort Estimate: Low ~ 200 hrs

 Comments   
Comment by Cath Fairlie (Inactive) [ 13/Oct/09 ]

We would need more specifics on what is proposed before KS could give this a higher priority.

Comment by Eric Westfall [ 16/Oct/09 ]

There's not much information on this actual jira is this related to actually implementing proper accessibility standards or is this more of a research item to update our accessibility guidelines?

Comment by Eric Westfall [ 16/Oct/09 ]

If we make this a research item, the we would probably classify this as high from the Rice/non-kuali application perspective.

Comment by Eric Westfall [ 24/Mar/11 ]

I'd like to propose a target scope for this item. It seems to me like the first step here is to research and document our web accessibility standards and how we should approach analyzing the Rice software and KRAD framework to determine how to bring them up to those standards.

There then needs to be a follow up roadmap item to actually implement these accessibility standards in Rice.

Does this describe the appropriate scope for this item?

Comment by Sandra Agee (Inactive) [ 01/Apr/11 ]

The Scope as described above is confirmed.

Additional information:

URL concerning current KUALI documented standards...

https://wiki.kuali.org/display/KULRICE/Kuali+Development+Standards

Comment by Eric Westfall [ 07/Apr/11 ]

Just updating the summary of this issue to provide some additional clarification.

Comment by Eric Westfall [ 07/Apr/11 ]

I could use a little bit of help coming up with an estimate for this work. I'm not sure if 200 hours is really enough time to do this work or not.

Comment by Jessica Coltrin (Inactive) [ 21/Jun/11 ]

Assigning to Candace as the "owner" for this item since she's looking at Accessibility and as UX Architect this should be "owned" by her.

Comment by Candace Soderston (Inactive) [ 22/Jun/11 ]

Agree this is my work item. As a start, here are the Kuali related items I've found already exist on this topic. Point me to others you see. Work has been done in Kuali Student. First let's agree on where to put new/synthesized info, so that all devs can most easiily find it (in addition to logging JIRAs).

From Sandra Agee comment below - look in coding conventions topic: https://wiki.kuali.org/display/KULRICE/Kuali+Development+Standards#KualiDevelopmentStandards-StyleGuide

https://wiki.kuali.org/display/KULRICE/Rice+Accessibility+Guide#RiceAccessibilityGuide-Findingsandconclusion

https://wiki.kuali.org/display/KULSTG/Accessibility+Workspace

Comment by Candace Soderston (Inactive) [ 18/Jul/11 ]

Attended ARIA-hackathon with jquery UI team.
See https://docs.google.com/a/kuali.org/document/d/1yjWyig0iyDrhvCKme00M31R_DvtESGlGilceQh9am5E/edit?hl=en_US

Comment by Candace Soderston (Inactive) [ 25/Jul/11 ]

See https://wiki.kuali.org/display/KULRICE/Rice+Accessibility

JIRAs being logged under Component = Accessibility. For example, see KULRICE-5422.

Comment by Jessica Coltrin (Inactive) [ 05/Dec/11 ]

Research on this came in as a KS requirement for KRAD and it's being worked on for that.

Comment by Jessica Coltrin (Inactive) [ 07/Feb/12 ]

The work done for KS did not fully meet the requirements for this Jira and since the ARC never prioritized this as a 2.0 item, I removed the fix version so that the remaining work can be reprioritized in a further ARC vote. Research was done, but accessibility standards were not documented and agreed on yet.

Comment by Candace Soderston (Inactive) [ 07/Feb/12 ]

This research item was for 2.0, and is completed, with fix version(s) to be determined, so moving the fix(es) out of 2.0 now makes sense. ARC/TRC members can view the WCAG 2.0 status from the Googledoc link under the "What was found" section at https://wiki.kuali.org/display/KULRICE/KRAD+Accessibility+-+Baseline+evaluation. And all can view the "solutions for items that require new approach" slide deck that is linked to from that same section.

The accessibility standards are well documented in WCAG 2.0 (see http://www.w3.org/WAI/WCAG20/quickref/Overview.php) and in the Kuali Rice wiki (see https://wiki.kuali.org/display/KULRICE/Rice+Accessibility), completed in August 2011.

The JIRAs logged have been moved to Rice 2.2, KRAD component, and fixes are included in the KRAD 2.2 requirements list that is currently being worked at the KAI and by small KS/KRAD collaborative team, and will be reviewed with the ARC this week (see https://wiki.kuali.org/display/KULRICE/Rice+2.2+-+KRAD+Requirements).

All good to close this now, prior to Rice 2.0 RC2!!

Generated at Sat Nov 28 01:17:21 CST 2020 using JIRA 7.0.11#70121-sha1:19d24976997c1d95f06f3e327e087be0b71f28d4.