Main Page

From SDSU ATI Top 20

This page is intended to facilitate the work of the SDSU Accessible Technology Initiative (ATI) working group originally tasked with evaluating and remediating the "top 20" SDSU web pages by January, 2007. Based on revisions to the coded memo on accessibility, this task has been modified; see below for details.

Other SDSU ATI working groups are addressing web accessibility policy development, instructional materials, and procurement.

Contents

[edit]

Task

Revised Task
Campuses will select 15-100 sample websites representing an "administrative public website cross-section". These should include: campus main site, each college and school, disabled student services, random departments, divisions, and university portal. These sites are all to be evaluated by the automated Hi Software tool and remediated to 80% compliance. Then a sample of 20% of the sites are to be manually evaluated according to a defined process/checklist, and remediated to 100% compliance. A report of the project results, as well as a plan for implementing campus web accessibility within the specified timeline, is due May 15, 2007. The three primary web accessibility milestones as defined by the CO's ATI Timeline of 1/16/2007:
  • By May 15, 2008: Administrative sites considered critical to institutional access must be compliant, or an equally effective alternative form of access provided.
  • By May 15, 2009: Remaining critical administrative sites must be compliant, or an equally effective alternative form of access provided.
  • By May 15, 2012: All CSU websites must be fully 508-compliant, or an equally effective alternative form of access provided.

See below for the original task based on the initial CO guidelines.

[edit]

Process

Revised Process based on revised coded memo
Identification
  1. Identify 15-100 sample sites "to represent administrative public web site cross-section"
Evaluation and Remediation
  1. Perform automated evaluation on all sites using accessibility evaluation tool(s) (Hi Software)
  2. Sites are to be remediated to achieve a passing score of 80% or better, as documented in Hi Software detail reports
  3. Manually evaluate accessibility of the home page of 20% of the sample sites following the process specified for manual checking
  4. Remediate manually checked pages to 100% compliance
  5. Create report on manual checking process.
Final Reporting
  1. Submit report to CO with project results and transition plan to improve accessibility compliance within specified timeline.

See below for the original process based on the initial CO guidelines.

[edit]

Resources/Tools


Committee Members
Name Title Contact
Jim Julius (lead) Associate Director - Instructional Technology Services mailto:jjulius@mail.sdsu.edu / 619-594-5852
Happy Aston Manager, Online Communications - University Advancement mailto:happy.aston@sdsu.edu / 619-594-5744
Kevin Carter Director, Info. Systems - Student Affairs mailto:kcarter@mail.sdsu.edu / 619-594-4276
Rich Pickett Sr. Director - Info. Technology Services mailto:rich.pickett@sdsu.edu / 619-594-8370
Joe Shapiro Associate Dean - College of Extended Studies mailto:jshapiro@mail.sdsu.edu / 619-594-4906
[edit]

Action Items

  • 12/5
    • Jim to create Google spreadsheet to be shared by the committee for tracking web page identification
    • Committee members to identify assigned web pages, who is responsible for the page, and some initial evaluation
    • meet again 12/12, 10:30-12:00
  • 12/12
    • Kevin and Rich to test sites using tools
    • Rich to keep group informed about Hi Software purchase
    • meet again 12/19, 10:30-12:00 - consider initial evaluation results and manual examination process
  • 12/19
    • Rich to follow up with LB, Fullerton on their organization/processes
    • Rich/Kevin to share assessment data from work thus far
    • Kevin expanding/finalizing reporting spreadsheet for manual checking
    • Next meeting: pull together developers with our group to discuss nitty-gritty on Hi Soft and manual assessment processes for the Top 20 (1/16?)
      • Happy to check on pres. conf rm
    • Rich: Will Hi Software run on Mac?
    • Jim will check in with group after new year about getting together (briefly) prior to the 16th to do planning/agenda setting.
  • 2/19
    • Jim will update the list of sample websites to include all schools/colleges, all divisions, and some departments
    • Happy will determine the webmaster and manager responsible for each site
    • Meet again Monday 3/5, 1:15-2:15 pm - determine which sites to move forward with the process
  • 3/5
    • Happy will continue campus webmaster list in google docs, will give access to group + Cyndi C
    • Happy will talk with John Ross about involving associate deans' group in the web accessibility process
    • Rich will work with Chris F to get the AccMonitor results for our list of ~60 sites
    • Rich will check to see if HiSoft 23-seat training is a limit of theirs or ours; if not their limit, Joe may have a larger lab which can be used
    • We will meet again 3/19, 1:30 pm, AH 1132. Selection of 20% of the sites is primary; also consider developing FAQs or something similar.
  • 3/19
    • Rich will continue to work with Chris F to get HiSoftware results for our list of ~60 sites
    • Happy to continue to flesh out campus webmaster list
    • Need to produce a list specifically for the ~60 sites (Jim will get this going)
    • Would like Chris F and Cyndi C to start on a technically-oriented FAQ
    • Jim and Rich will start on a more general web accessibility FAQ (or something similar)
    • Once the 20% of sites have been selected for more thorough manual evaluation and remediation, will need to bring the affected webmasters together for orientation
    • Need to develop (or locate if one already exists) a form for webmasters to use during the checking/remediation process, not only to track progress but also to keep track of important ideas and thoughts. Jim will check into this.
    • Coordinate by phone/email as we need to begin moving quickly once the ~60 site initial eval is done ... no meeting scheduled for now
[edit]

Meeting Minutes

[edit]

Original task and process

Please note: the following is preserved here for historical purposes.

Original Task
Campuses are directed to select the top 20 (most accessed or the most critical) web pages on their main campus site and test these pages for conformance to Section 508 standards using both automated evaluation and manual testing processes. Pages frequented by individuals with disabilities should also be included should these pages not fall in the selected 20. A page is defined as a single url. In selecting the 20 pages, consider the following:
  • Include all pages on which people are more likely to enter your site ("home page," etc.)
  • Include a variety of pages with different layouts and functionality, for example:
    • Web pages with tables, forms, or dynamically generated results;
    • Web pages with informative images such as diagrams or graphs;
    • Web pages with scripts or applications that perform functionality

From CSU Web Accessibility Conformance Testing Process

The "Top 20" pages are to be identified, evaluated, and remediated by March 29, 2007. (NOTE: Deadline extended by 60 days from the original January 29th deadline.)
Original Process
Identification
  1. Identify 20+ pages
Evaluation
  1. Perform automated evaluation using accessibility evaluation tool(s) (Hi Software)
  2. Manually evaluate accessibility using tool output and checklists
  3. Examine pages using various browsers on various settings
  4. Examine pages using assistive technologies
  5. Evaluate informational/text content for simplicity/clarity
Remediation
  1. Remediate pages as necessary
Reporting
  1. Summarize and report findings
See Web Accessibility Conformance Testing Process
[edit]

Getting started

For information about using MediaWiki, please see the User's Guide for help.

Retrieved from "http://its.sdsu.edu/wiki/ati/index.php/Main_Page"