How Accessibility issues affect Information Architecture
Upcoming SlideShare
Loading in...5
×
 

How Accessibility issues affect Information Architecture

on

  • 5,151 views

When accessibility is required in a project, all the steps are affected, including information architecture as well. As IA is on the early phases, it can benefit the budget.

When accessibility is required in a project, all the steps are affected, including information architecture as well. As IA is on the early phases, it can benefit the budget.

Statistics

Views

Total Views
5,151
Views on SlideShare
4,493
Embed Views
658

Actions

Likes
13
Downloads
54
Comments
1

15 Embeds 658

http://alfonsomorcuende.com 308
http://www.itakora.com 128
http://blog.canal.cl 103
http://itakora.com 92
http://www.yahnyinlondon.com 11
http://www.slideshare.net 5
http://dashboard.bloglines.com 2
http://picthislife.com 2
http://webcache.googleusercontent.com 1
http://static.slidesharecdn.com 1
http://www.aichile.org 1
http://feeds.feedburner.com 1
http://www.planetaki.com 1
http://www.queleemos.com 1
http://www.alfonsomorcuende.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

How Accessibility issues affect Information Architecture How Accessibility issues affect Information Architecture Presentation Transcript

  • Hi there! I am an information architect and I would like to talk to you about how accessibility issues affect our work © Olga Revilla. 2009
  • But first of all, let me introduce the place where I work It’s a complex organization where we do ‘Internet things’
  • First of all, the I.T. crowd I call them ‘the technical wizards’ Servers Database administrators administrators
  • There are developers They code and test, and test, and test XHTML, AJAX, CSS… PHP, C++, Java…
  • And people who creates and edits interesting contents They feed the websites Texts Movies Pictures
  • And my two best fellows to create the look & feel We make a great team Creative Graphic designer
  • And of course, clients who always are asking things to the project manager I need… Yes, sir. I want… Yes, sir. I expect… Yes, sir. I will… Yes, sir.
  • Often clients ask us to make a [multimedia | 2.0 | social network | RIA | AJAX everywhere] website which also have to be [accessible] Of course, as cheap as possible, but that is not our battlefield, is it?
  • So an accessibility consultant was hired. He is continuously teaching us how to do it great
  • 2 things we have learned 1 Getting an accessible website involves all the steps of the project: from clients to I.T. That includes, obviously, information architecture
  • 2 things we have learned 2 The earlier the accessibility is taken into account, the cheaper the project will be. The fewer errors, the fewer corrections. The fewer corrections, the shorter time to get it.
  • So Information Architecture, as it is placed at the beginning of the project, has a very important role in keeping the budget low regarding accessibility issues. Let’s see some things I have learned
  • Usability ≠ Accessibility A determined group of users The maximum amount of users A determined context Whatever context A determined goal Different goals
  • The maximum amount of users Our target (obviously), but also… Age Place Knowledge Disability Elderly Another country Geeks Blind Adults Another language Advanced Color blind Teenagers Another culture Intermediate Deaf Children … Beginners Epileptic … … … Accessibility is not only about disability
  • Whatever context You can’t imagine all of them Device Screen Place Connection Laptop Giant Home DSL Mobile Big Bus queue Dialup Smartphone Small Airport 3G Television None … … … … Imagine ‘personas’ technique…
  • Different goals Including company’s goals, people can visit your site to… - Get your information - Use your information - Transform your information - Share your information - Get inspiration - … Imagine ‘scenarios’ technique…
  • So we have a great diversity of people, contexts and goals How to manage it? One simple rule
  • Make sure that information is in a plain, text version; then add design, features and functionalities. Ok, but client still wants it spectacular
  • Let’s see how to implement this rule by some examples Buuuhhh! Fancy, but… Yuhuuu Icons from http://www.iconspedia.com/pack/very-emotional-2353/
  • 1. Provide the information and the data Charts
  • 2a. Not everybody hears the voice Videos
  • 2b. Not everybody hears the voice Live videos
  • 3. Stress your prototype
  • 3a. Adapt to the screen 1024 320 800
  • 3b. Increase the font x1 x2 x2 x2
  • My prototypes bring some consequences…
  • I like your job, but you are telling me that I have to… Wait more time for prototypes Yes, sir. Buy the subtitles Yes, sir. Contract a language interpreter Yes, sir. How much more will they cost? Er…
  • That is not our war. If accessibility is a requirement (and morally always is), I have to take into account these matters. Let the client or project manager decide how to admin the budget.
  • Remember Lesson #2 The earlier the accessibility is taken into account, the cheaper the project will be. Legal audits will be passed easily More people will access to your info Less costs in regressions and fines More profit
  • Just to recap Accessibility issues affects all steps of the project. Many of them can and must be anticipated by IA.
  • Thanks for your kind attention. Any questions? Olga Revilla olga@itakora.com © Olga Revilla. 2009