From a developer viewpoint, picking the low-hanging fruit (the
easy stuff to fix) might look like a good approach, but what if the
things that present the greatest barriers are also the things that are
hardest to fix.  For example, an early version of ABC.com opened onto a
full screen graphic with no text at all, that was a server side map.
Completely inaccessible.  Fixing the things on subsidiary pages wouldn't
help overall accessibility because a user could never get to those
pages, although the designer might be able to report that 90% of our
pages have been fixed.

       Denis Anson, MS, OTR
       Computer Access Specialist
       College Misericordia
       301 Lake St.
       Dallas, PA 18612
       email: [log in to unmask]
       Phone: 570-674-6413


       > -----Original Message-----
       > From: * EASI: Equal Access to Software & Information
       > [mailto:[log in to unmask]] On Behalf Of Alan Cantor
       > Sent: Wednesday, November 20, 2002 12:46 PM
       > To: [log in to unmask]
       > Subject: Re: COMPLIANCE WITH WEB ACCESSIBILITY
       >
       > Last week at the Accessing Higher Ground conference in Boulder,
I
       > picked up a flyer from WebAim (www.webaim.org) that describes a
       > five-step web remediation process: "the fast track to
accessibilty."
       > Here it is in outline:
       >
       > 1. Evaluate your current site.
       > 2. Fix the easiest issues first.
       > 3. Fix your templates.
       > 4. Fix all HTML-related issues.
       > 5. Fix all non-HTML issues.
       >
       > The flyer goes into more detail.
       >
       > Alan
       >
       >
       > Alan Cantor
       > Project Manager
       > Strategic e-Government Implementation
       > e-Government, OCCS
       > 416-212-1152
       > [log in to unmask]
       >
       > >>> [log in to unmask] 11/20/02 03:26AM >>>
       > Hi all,
       >
       > Our college's teaching and technology just had a meeting
       > today with its major focus and agenda being web site
       > accessibility.  The major question came up for me to ask
       > the experts from this listserv as follows:
       >
       > Given that each of our Maricopa community colleges have
       > hundreds, if not thousands, of web pages (including
       > courses on the web.    This all comes after several
       > years of development and .....recently the staff and
       > faculty are now realizing the responsibility to have the
       > web sites/pages be ADA/508 compliant.
       >
       > The question is this:   Iin what order of the web
       > sites/pages do we need to ensure are accessible.  We
       > know that we definitely need to have the home page be
       > 508 compliant along with its links.
       >
       > Please comment and advise.  Thank you in advance for
       > taking the time to submit your replies to the above
       > question.
       >
       > Jack Clevenger, Coordinator
       > Disability Resources and Services
       > Mesa Community College
       > Mesa, Arizona