Uploaded image for project: 'Kuali Rice Roadmap'
  1. Kuali Rice Roadmap
  2. KRRM-3

Research and Document Accessibility Standards for Kuali projects

    Details

    • 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

      Attachments

        Issue Links

          Activity

          Hide
          cfairlie Cath Fairlie (Inactive) added a comment -

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

          Show
          cfairlie Cath Fairlie (Inactive) added a comment - We would need more specifics on what is proposed before KS could give this a higher priority.
          Hide
          ewestfal Eric Westfall added a comment -

          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?

          Show
          ewestfal Eric Westfall added a comment - 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?
          Hide
          ewestfal Eric Westfall added a comment -

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

          Show
          ewestfal Eric Westfall added a comment - If we make this a research item, the we would probably classify this as high from the Rice/non-kuali application perspective.
          Hide
          ewestfal Eric Westfall added a comment -

          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?

          Show
          ewestfal Eric Westfall added a comment - 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?
          Hide
          sagee Sandra Agee (Inactive) added a comment -

          The Scope as described above is confirmed.

          Additional information:

          URL concerning current KUALI documented standards...

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

          Show
          sagee Sandra Agee (Inactive) added a comment - The Scope as described above is confirmed. Additional information: URL concerning current KUALI documented standards... https://wiki.kuali.org/display/KULRICE/Kuali+Development+Standards
          Hide
          ewestfal Eric Westfall added a comment -

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

          Show
          ewestfal Eric Westfall added a comment - Just updating the summary of this issue to provide some additional clarification.
          Hide
          ewestfal Eric Westfall added a comment -

          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.

          Show
          ewestfal Eric Westfall added a comment - 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.
          Hide
          jcoltrin Jessica Coltrin (Inactive) added a comment -

          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.

          Show
          jcoltrin Jessica Coltrin (Inactive) added a comment - 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.
          Hide
          csoders Candace Soderston (Inactive) added a comment -

          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

          Show
          csoders Candace Soderston (Inactive) added a comment - 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
          Show
          csoders Candace Soderston (Inactive) added a comment - Attended ARIA-hackathon with jquery UI team. See https://docs.google.com/a/kuali.org/document/d/1yjWyig0iyDrhvCKme00M31R_DvtESGlGilceQh9am5E/edit?hl=en_US
          Hide
          csoders Candace Soderston (Inactive) added a comment -

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

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

          Show
          csoders Candace Soderston (Inactive) added a comment - See https://wiki.kuali.org/display/KULRICE/Rice+Accessibility JIRAs being logged under Component = Accessibility. For example, see KULRICE-5422 .
          Hide
          jcoltrin Jessica Coltrin (Inactive) added a comment - - edited

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

          Show
          jcoltrin Jessica Coltrin (Inactive) added a comment - - edited Research on this came in as a KS requirement for KRAD and it's being worked on for that.
          Hide
          jcoltrin Jessica Coltrin (Inactive) added a comment -

          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.

          Show
          jcoltrin Jessica Coltrin (Inactive) added a comment - 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.
          Hide
          csoders Candace Soderston (Inactive) added a comment -

          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!!

          Show
          csoders Candace Soderston (Inactive) added a comment - 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!!

            People

            • Assignee:
              Unassigned
              Reporter:
              coppola Chris Coppola (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: