Please report any problems to the Shared Tools Team at    Broken Links? Missing Macros? WIKI Retiring Plugins
Child pages
  • ATR Meeting 2012-05-17
Skip to end of metadata
Go to start of metadata

NOTES - Agenda – Accessibility/Usability Assessment Tool Requirements, Review and Recommendations Team (ATR)


May 17, 2012 – 10:00-11:00 Union South


Team members: Judy Caruso, Chris Arndt, Lee Conrad, Gary DeClute, Tam Flarup, John Graham, Dan Jacobsohn, Ryan Kirk, Carrie Nelson, Vince Rose, Casey Schacher, Todd Schwanke, Eric Simons, Jennifer Sutherland, Joyce Tikalsky, Phyllis Triege, Peter Weill


  1. Meet and greet (all) OK


  1. Review notes from last meeting (all) – Judy did create list serve OK


  1. Review charter - Is this final? (all)

Judy added Tam Flarup. OK so far, but see items 4 and 5 below.

  1. “Accessibility” vs. “usability” – definitions (Phyllis)

Definitions from Phyllis:

From UIAccess :

  • Usability problems   impact all users equally, regardless of ability; that is, a person with a disability is not disadvantaged to a greater extent by usability issues than a person without a disability.
  • Accessibility problems   decrease access to a product by people with disabilities. When a person with a disability is at a disadvantage relative to a person without a disability, it is an accessibility issue.


  • International Standards Organization (ISO9241)
    "...the effectiveness, efficiency, and satisfaction with which specified users achieve specified goals in particular environments"
  • Jakob Nielsen (usability guru)
    "...the promptness with which users can learn to use something, the efficiency they attain while making use of it, how easy it is for them to remember how to use it, how error-prone it is and the level of satisfaction that they attain from using it
    "usability refers to how well users can learn and use a product to achieve their goals and how satisfied they are with that process"


  • The W3C (or World Wide Web Consortium)
    the ways in which "people with disabilities can perceive, understand, navigate, and interact with the web, and they can contribute to the web."   Web accessibility covers all types of disability, including those that you may be more familiar with and those that you may not, including visual, auditory, physical, speech, cognitive, and neurological disabilities and elderly users.  
  • Web accessibility is the practice of making websites and web applications inclusive and usable by people with all levels of abilities and disabilities.  

Some see accessibility as a sub-set of usability.   Others believe that there are important and sometimes conflicting differences between the two that support thinking of them as separate but complimentary disciplines.    



Do we want to keep accessibility in our charter?

Suggested: We acquire a tool or tools that address both web accessibility (primary) and usability (secondary). Also discussed: interoperability (e.g. meets various standards.)

  1. Discuss goals of assessing web accessibility (using campus policy)
    1. Organize as broad goals and more specific sub-goals.

See: AccessToolDiscussionResults20120517.doc

For next meeting: finish adjusting results.


  1. Decide which to work on

For next meeting.

From our last meeting: Scope is “anything that comes through a browser”

  • includes applications as well a web pages
  • mobile devices (will need to call on expertise for this)
  • PDF’s

For next meeting.


  1. Decide on meeting schedule and next steps

Meet every two weeks.  Is this time going to work? Next meeting would be May 31

Meet 5/24 and every 2 weeks after from 10-11:30 at Union S.

Next steps: See item 5 above.

  1. Other?


Next Meeting – 5/24 10-11:30 at Union South.


Topic: Review goal brainstorm and organize/prioritize/decide.

  File Modified
Microsoft Word Document AccessToolAgenda20120517NotesRevA.docx Oct 22, 2012 by GARY W DECLUTE
PDF File AccessToolAgenda20120517NotesRevA.pdf Oct 22, 2012 by GARY W DECLUTE



  • No labels