Thread Subject: Revised Taxonomy Attached for Friday's Call

Note

This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.

From: David Wysocki
Date: Thu, Feb 22 2007 7:10 PM

Greetings - I have attached the revised Taxonomical Table with
improvements based on last week's discussion. Again the table is
intended as a tool as we venture into the significant challenge we face
with the wide variety of new hardware interfaces we need to address.
Most of which that have either emerged since the basic interfaces
addressed within the original 508 or emerged as new products have
entered and diversified the IT marketplace with their unique combination
of functions and physical interfaces. The challenges we have include:

1. The need to identify the wide variety of new hardware interfaces,
especially in the variety of new IT that 508 must now address and be
addressed by our subcommittee

2. The need to consider potential accessibility issues for the
variety of new interfaces

3. Identify solutions (which may be addressed by IT accessibility
and/or AT Interoperability)

4. Consider solutions across accessibility themes (e.g., mobility,
vision, hearing, cognitive)

5. Consider existing standards for issues identified by our
subcommittee

6. Manipulate the solutions into a succinct set of recommendations
that will universally address hardware interface accessibility
regardless of the application or product



I have proposed the attached taxonomy as a tool to assure we can begin
to address all six of the above issues. The primary 5 "Interface
Functions are:

I. Text/Number Entry

II. Visual Output (Display)

III. GUI & Other Navigation

IV. Auditory Output



Again, this is a tool for our process, not the recommended method or
format for our recommendations to the Access Board. I think it works
well for the first several columns/levels to assure we are pulling in
all existing and/or possible physical interfaces. Though the tool
itself currently has a few challenges. Some of the issues I have come
across while creating it:

* It gets a bit cumbersome as one progresses out to the
succeeding columns (e.g., between access considerations and
recommendations). This could be corrected with a different format or
numbering system and as we reach those columns while it gets populated -
Open for feedback here

* I tried my best at making it accessible by using a heading for
each level. There may be a better way of doing this



I think if we get a couple, few people volunteering to populate the
primary 5 "Interface Functions - 1st column (especially roman numerals I
through IV

we could make significant headway in identifying the variety of
interfaces and access considerations we need to consider for a start. I
look forward to discussing it more tomorrow. Thanks much! - David





David J. Wysocki, MS, OTR, ATP

Assistant Vice President,

Workforce Development / Assistive Technology

Easter Seals National Office

230 W. Monroe St., Suite 1800

Chicago, IL 60606

Direct Line: 312-551-7175

Receptionist: 312-726-6200

Fax: 312-726-1494

TTY: 312-726-4258

Email: = EMAIL ADDRESS REMOVED =



Be an angel of change. You can change the lives of people with
disabilities.

Earn your wings at www.easterseals.com <http://www.easterseals.com/>

  • Next message in Thread: None
  • Previous message in Thread: None

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University