Details

    • Epic Link:
    • Rice Module:
      KRAD
    • KRAD Feature Area:
      UIF Component
    • Application Requirement:
      KS
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      There are 3 types of table structures in KNS and KRAD that today lack some of the standard tag structures required to meet W3C and government standards (in the U.S., for example, section 508 and 504 of the Rehabilitation Act, which are being harmonized with WCAG 2.0 now that there is a W3C world-wide technology standard - for additional information, see references section below). These tag structures define the semantic relationships between and among the inter-related elements, for example between header rows and columns and their associated cells.

      This is not a problem for sighted users, who can infer the relationships from the relative visual placement and other visual treatments. For example, sighted users can infer that a shaded row placed at the top of a table is a column header row. However, tables that lack the required standard tag structures, don't convey their table inter-relationships programmatically. In real usage terms, this means they can't be accurately interpreted by end users who use standard assistive technologies in order to access applications (applications include websites for enrollment, bill payment or other financial handling, curriculum planning, online library systems, online education, in classroom technologies, or other).

      KRAD will provide improved support to applications to enable them to more easily comply with code standards, by adding the missing tag structures into the code-base and templates for all to use.

      More info... https://wiki.kuali.org/display/KULRICE/KRAD+-+Table+semantics+-+uplift+to+code+standards+%28including+accessibility%29

        Attachments

          Issue Links

            Activity

            Hide
            wwashington William Washington (Inactive) added a comment - - edited

            Removing this previous comment about Fluid's reorder component, as I think it was posted in the wrong Jira.

            Show
            wwashington William Washington (Inactive) added a comment - - edited Removing this previous comment about Fluid's reorder component, as I think it was posted in the wrong Jira.
            Hide
            wwashington William Washington (Inactive) added a comment -

            Can we utilize any of Hans Hillen's code for this since he's demonstrated an accessible example of jquery tabs: http://hanshillen.github.io/jqtest/#goto_tabs

            Show
            wwashington William Washington (Inactive) added a comment - Can we utilize any of Hans Hillen's code for this since he's demonstrated an accessible example of jquery tabs: http://hanshillen.github.io/jqtest/#goto_tabs
            Hide
            christieheitkamp Christie Heitkamp (Inactive) added a comment -

            Chris Rodriguez please review and provide any additional info

            Show
            christieheitkamp Christie Heitkamp (Inactive) added a comment - Chris Rodriguez please review and provide any additional info
            Hide
            hbeery Heather Beery added a comment -

            This may be covered in the component spec doc for Table Design & Functionality https://wiki.kuali.org/display/UXI/Tables+design+and+functionality

            Show
            hbeery Heather Beery added a comment - This may be covered in the component spec doc for Table Design & Functionality https://wiki.kuali.org/display/UXI/Tables+design+and+functionality

              People

              • Assignee:
                Unassigned
                Reporter:
                wwashington William Washington (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Time Tracking

                  Estimated:
                  Original Estimate - 2 weeks
                  2w
                  Remaining:
                  Remaining Estimate - 2 weeks
                  2w
                  Logged:
                  Time Spent - Not Specified
                  Not Specified