Last month, Expedia announced that they added several features in 2009, including:

• The ability to search hotels by criteria such as equipment for the deaf, accessible bathrooms, Braille, and ease of navigating through the room
• Their staff following up by contacting hotels for disabled customers to make sure their specific accessibility needs will be met

Expedia provided the statistic that they’ve gotten 500 requests each week related to these accessibility features since unrolling them in August of 2009.

By comparison, Travelocity, Expedia’s top competitor in the online travel arena, has a “Wheelchair Accessible” option among their hotel search options:

Orbitz has a “Handicapped rooms/facilities” option of their own:

Those are better than nothing, but Expedia deserves some credit for an actual, extensive means of searching hotels by different disability-friendly needs.

I work in the travel industry and hope this is a sign of good things to come. It took a lawsuit to spur action, but Expedia is making accessibility inroads. Let’s hope this is only the beginning.

Links were only identifiable by being a different color from the content around them. They weren’t bolded or underlined. A link was, for example, blue, amidst copy that was black.

This can cause significant problems for those with certain types of color blindness or vision limitations that prevent them from seeing certain colors. If you take color out of the equation, there is absolutely no way to visually identify which parts of these pages are links.

I think it can be confusing even for people with full vision, especially if the same color chosen for links is also used for other stylistic reasons.

It seemed like it was fashionable in the design world a few years ago to get away from the tried-and-true underlining of links. Even today there’s a fair number of sites who just have links as a different color.

If you’re dead set against using underlines for whatever design reason, at least make links a different color AND bolded so there’s differentiation between the rest of the content. Just make sure you don’t use bold for other, non-linking elements then.

It’s a time-honored expectation for links to be underlined on the Web — except in very few cases, I don’t think keeping it that way messes up too many awesome designs.

Some Tools For Testing Color:

Steve Grobschmidt (SG): I imagine some game types or genres are easier to be made accessible than others. And there are many different kinds of disabilities: visual, hearing, physical, cognitive, etc. How do developers balance making great, cutting edge games that still are playable for as many disabled gamers as possible?

Steve Spohn (SS): In a word, options. Options are extremely undervalued right now by the video game industry. In fact, most of the people who are unwilling or resentful of our work think that we want to change games in some way, and that is absolutely false.

AbleGamers wants developers to add options that can lend accessibility to video games for those that need a particular accommodation. No one wants to see video games “dumbed down” or made easier in any way. The ultimate goal is to add as many options that add value to a video game without taking anything else away. Items like remappable keys, subtitles, color blind options, mouse speed adjustments, and assistive device support, are all items that could add additional value to a title but for those who do not need any of those options, the game would not be hurt in anyway. In fact, if done correctly, those who do not need the accessibility may not even realize it’s there.

SG: How do you go about testing games? I see from your About Us section that there are staff members with disabilities of their own, including yourself. Do you just test games yourselves, or do you also reach out to other sources for testing?

SS: Our writers test every game personally. We have an in-house game review document that every video game must be put through. In addition, we have a rather large community that will keep us honest. If you read the review section, not everyone agrees with our assessments. This is because disabilities are widely varied, and everyone’s idea of how much accessibility is needed to be able to play a game changes.

We review games based on the ability to play them with standard equipment such as a keyboard and mouse. We then use the comments section to provide information on third-party assistive technology enabling some disabled gamers to play this or that. If there is a way to play a game, our members will find it.

SG: What kind of reception do you get from the gaming industry? Do you feel your presence and advocacy is being heard?

SS: Right now, I would say lukewarm. There are some companies, as I mentioned before, that are very receptive to our needs and requests. However, there are some that want nothing to do with accessibility because they believe adding accessibility increases production time and expenditures beyond what they must be. AbleGamers has definitely been making an impact in the accessibility movement; there are definitely large and small signs that we are becoming more important daily.

The most flattering was a twitter sent out by one developer to another developer saying “make sure to look out for AbleGamers at the conference. Accessible gaming is a good way to help advance your career.” At the point where you are beginning to be seen as a career advancer, you know you’re making a difference.

We have also been featured in most every online gaming magazine, Xbox 360 magazine, MSNBC, Apple.com, and many more.

SG: Looking at your crystal ball, is the gaming industry heading in the right direction? Are video and computer games getting more accessible?

SS: Accessibility is increasing in most ways but it is a constant battle. As new gaming systems like Natal, Wii, Tablet gaming, and others continue to become more mobile, games inherently become less accessible. Systems that require physical body movement are not ideal for those with physical impairments and mobile gaming such as iPhones and tablets are difficult for those with limited movement.

When the most advanced system only required two buttons and a directional pad, I could personally play any console game. As could one-handed gamers, most with physical impairments, and even those with very limited movement range.

Now, controllers have six or more buttons, shoulder buttons, and two directional pads. So, the games have advanced but the accessibility falls. The more complicated the controller becomes, the less accessible it is. Computer games are very similar in that every game could be controlled by a mouse 10 years ago and now, some do not use a mouse at all.

On the flipside, you now have things like hacked controllers, mods, assistive technology, and other customizable devices that can aid a disabled gamer with playing certain games. Most of these accessible devices are created by individuals who make these controllers one by one. We hope that someday gaming companies who produce these controllers.

It is my sincere hope that as accessible technology becomes more prevalent and developers learn how many potential customers are out there, video games will become more accessible. There are some wonderful technologies on the horizon. Things like nanos inserted into the body, eye trackers are becoming more accurate and less expensive, voice controlled gaming is becoming faster and more accurate, and many more advancements.

Thanks again to Steve for taking the time to talk about video and computer game accessibility — what’s working, what are the challenges, and where things should be headed.

Sort of like web site accessibility, it’s not about “watering down” the experience. Like Steve said, it’s about options. It’s about putting some extra effort into considering your entire audience.

I go back to a point I made earlier. I love video and computer games. If, tomorrow, I lost my hearing or something happened that limited my motor skills, I’d still love video and computer games. I’d still want to be able to enjoy them as much as possible.

I’m not disabled and I appreciate some accessibility-minded features. For example, because often times I play games at night and don’t want to have the volume jacked up, I turn sub-titles on for just about every game I play.

Dragon Age showed that you can make an all-around outstanding game with plenty of accessibility options. Let’s hope more and more game developers follow suit.

Series Recap:
AbleGamers Interview
AbleGamers Interview wrap-up

More about AbleGamers.com
AbleGamers.com
AbleGamers on Twitter

Furthermore, I’ll be honest that I hadn’t heard of AbleGamers.com before that news piece either. I’m extremely excited that I got the opportunity to do an email interview with Steve Spohn, the Associate Editor at AbleGamers and also the person who reviewed Dragon Age.

AbleGamers.com is an outreach of The AbleGamers Foundation, and a site devoted to catering to both hardcore and casual gamers with disabilities. In addition to great reviews that showcase the highlights and shortcomings of a game accessibility, the site also provides a community for disabled gamers to share and collaborate.

Steve is a disabled gamer himself. He has a rare type of Muscular Dystrophy called Spinal Muscular Atrophy (SMA). You can read more about Steve on his profile page.

Let’s jump right into the interview!

Steve Grobschmidt (SG): Overall, how would you rate the gaming industry’s consideration for disabled gamers?

Steve Spohn (SS): I think the industry is beginning to learn what they need to do; it’s just a matter of convincing them it is worth the money. I would currently rate them at 5 out of 10, mostly because a lot of games have subtitles. In addition, more games are beginning to add remappable keys, which is extremely important to those who have limited range or need third-party assistive equipment.

Unfortunately, they are still lacking in areas such as colorblind awareness, options for on-screen keyboards, ability to increase mouse speed, and other such mobility areas.

SG: Dragon Age was in the spotlight for winning the most accessible game of 2009 award. What are some other stand outs from 2009 and 2010?

SS: There were no other games in the last year that have stood out like Dragon Age. Most games are around 6 – 7 in score because of visible accommodations such as subtitles and font size adjustments. However, World of Warcraft is a very accessible game, even though it was not launched recently. They have continued to try to improve their accessibility by working with AbleGamers. Not long ago, they even released a patch to assist colorblind gamers.

SG: Dragon Age got a 9.8 from AbleGamers.com, and well-deserved recognition. Mass Effect 2, also from Bioware, got a 5.0. Do you think that is more a reflection of the style of the game, or did Bioware drop the ball a bit after doing so well with DA?

SS: Bioware is a large company and each game is directed by different people, which accounts for the difference in accessibility. The producers and directors of Dragon Age definitely appreciated accessibility more than the Mass Effect people did. There is however, a slight drop expected because as soon as you mention FPS, many disabled gamers are left out without accessible technology, some of which is very expensive.

SG: Do any developers stand out for being more consistent than others in their attention to disabled gamers?

SS: So far, Blizzard has been the most accessible and accommodating company. There are still some developers such as NCSoft, that are very reluctant to talk to us.

One worthy of note from NCSoft is Aion, which recently included a program called GameGuard, which basically blocked every accessible technology that a disabled gamer would need to use. On-screen keyboards, sip and puff devices, and even some voice recognition technology were completely disabled. They did eventually repeal the program, and the makers of GameGuard contacted us to learn more ways to avoid blocking these technologies.

In the second half of this interview, I ask Steve about the expection of the gaming industry to reach out to as many disabilities as possible, as well as about how they go about testing games. That and more is coming later this week.

Thanks to Steve and Mark Barlet, the Editor in Chief at AbleGamers.com, for being so approachable and agreeable to doing this interview.

Series Recap:
AbleGamers Interview
AbleGamers Interview wrap-up

More about AbleGamers.com
AbleGamers.com
AbleGamers on Twitter

We’re down to the last question, about how to tackle web accessibility with less-than-receptive audiences.

Steve (SG): When people getting into web accessibility advocacy are met with obstacles such as businesses or cultures who do not “get it” or see its value, what advice would you give them?

Jennison (JA): The advice I would give someone would be similar to the advice I would give for any advocacy effort. Absolutely my first piece of advice would be to listen. Listen to understand what possible constraints and/or lack of knowledge may exist that is resulting in a business or culture not “getting it.” I truly believe no one sets out to build a website or application with the express intention to exclude anyone. That said, if, for example, a client does not explicitly state and fund accessibility as a requirement, a development shop cannot be expected to slip accessibility in just because it’s the right thing to do. In this case, the complaint and/or issue rests with the client not with the developer.

The other advice I would give, and again, it can be applied to any issue, is to keep the tone respectful throughout, as much as possible. While I mentioned earlier that I am seeing constructive conversations happening among and between the communities of developers, accessibility champions and end-users with disabilities, I have certainly seen a few not so constructive conversations on all sides. It’s obvious that none of this advances the cause at all. Of course it goes without saying that if you are being ignored or are just not getting anywhere, you may need to take a different approach, but I would hope that would be the exception and not the rule.

On a more practical level, when discussing web accessibility problems, as an end-user, don’t assume that the first person you communicate with will be highly technical and/or will know what you are talking about. I would highly recommend reading Contacting Organizations about Inaccessible Websites, which is I believe in draft stage. However, it is a document from the W3C’s Web Accessibility Initiative, and provides practical steps and templates on how to address the topic of web site inaccessibility.

I want to thank, for a final time, Jennison for taking the time to put together such extensive, articulate answers. He obviously put a great deal of thought and attention into them, and as you can see, he has a wealth of information from several different vantage points — from working in the business sector, education sector, and having a visual disability.

For anyone, like myself, who is taking on web accessibility and trying to wrap their head around where to go for information, how to advocate it effectively, etcetera, Jennison provided a lot of direction. He shared a ton of organizations and web sites that are great places to go for information, consultation and all-around insight.

I have to share that it wasn’t until many months after following Jennison and conversing on Twitter that I even realized that he is blind. At first, I felt bad I didn’t catch that, that I wasn’t paying close enough attention. Then it hit me as he, again, worded it as being a web user who “happens to be blind”.

Jennison doesn’t beat you over the head with his disability. He’s a person who utilizes web sites like all of us do. He wants to access the same social media sites, the same information sites, the same transaction sites as any of us. Having or not having a disability makes you who you are, but at the same time it isn’t some bright, blinking badge on your shirt.

It’s the same thought that occurred to me as I became familiar with the AbleGamers organization, whom I recently interviewed and will be sharing next week. One of my favorite hobbies is video games. If, today, I lost my hearing or lost my sight, that wouldn’t automatically make my love for games go away. I’d then become a disabled video game enthusiast, and I’d want as much the same experience as before, as close as possible.

In closing, I’m very grateful that Twitter and my growing place in web accessibility has enabled me to meet people like Jennison Asuncion. I’m hoping to meet more people, attend accessibility conferences and unconferences, and learn from it all.

Series Recap:
Interview with Jennison Asuncion – part one
Interview with Jennison Asuncion – part two
Interview with Jennison Asuncion – part three and wrap-up

Steve (SG): What do you think the state of web accessibility in North America is right now? How would you grade the progress made thus far?

Jennison (JA): I would say web accessibility is in a pretty dynamic state right now, pardon the pun. The release in December 2008 of the much needed version 2 of the Web Content Accessibility Guidelines, along with other work by the W3C’s Web Accessibility Initiative (WAI) in where they are finalizing guidance on how to make dynamic content using AJAX and other technologies accessible via Accessible Rich Internet Applications (ARIA) is getting us to a better place when it comes to having a set of specifications to help broadly address Web 2.0 and accessibility.

In addition, companies are pushing out toolkits and libraries that contain accessible widgets and components that developers can use, such as IBM’s work on Dojo Dijits and Adobe’s work on Flex. There’s an excellent piece done by The Paciello Group identifying a number of accessible JavaScript UI Libraries.

And definitely not to be overlooked are the ongoing efforts of organizations such as: Mozilla, the Adaptive Technology Resource Centre (ATRC) here in Toronto, and Drupal, which are active communities making significant contributions to improving the state of web accessibility

People are increasing in both their appreciation for the importance of accessibility, and in their knowledge of how to code in an accessible way. This is thanks, in no small part, to dedicated organizations such as: WebAIM, the Illinois Center for Information Technology Accessibility, Equal Access to Software and Information (EASI), and Knowbility, each of whom provide accessibility resources, training, and in some cases tools, to the web community at large.

In fact, WebAIM and ICITA have developed free tools that folks can use, in part, to help test the accessibility of their websites. These include WebAIM’s WAVE and the Functional Web Accessibility Evaluator from the ICITA.

Admittedly, some of the effort driving web accessibility is being brought on thanks to legislative encouragement, such as the lawsuit involving Target.com, and the upcoming introduction of the Information and Communication Standard of the Accessibility for Ontarians with Disabilities Act (AODA). On the flip-side, I am always coming across developers who are genuinely wanting to make web experiences as accessible as possible. Dennis Lembree is one example of someone who saw gaps in the popular Twitter app, and decided to build Accessible Twitter.

I’m seeing a new business case being built and used, linking how developing sites to be accessible benefits not only users with disabilities, but also those using mobile devices to access the web, older-aged users, as well as search engine optimization. This positioning of increased benefits for the larger population, to me, can only help build the web accessibility value proposition in a more tangible way for those looking at the bottom line who still need convincing.

Through e-mail discussion lists and social media, I’m seeing an increase in the level of constructive conversations on web accessibility among and between the developer, the IT accessibility professional, and the end-user with disabilities communities taking place. Some of these conversations, I’ll say, are long overdue, but at least they are happening.

Finally, I’ve been fortunate enough to be exposed to a thriving and active research community where some of the brightest minds are trying to solve web and mobile accessibility challenges by building software and hardware solutions of all kinds. Jeffrey Bigham’s WebAnywhere – a browser-based screen reader, is just one example. If the opportunity presents itself, I encourage readers to attend an Assets or a W4A conference. There are others out there too, where there is a heavy emphasis on research-driven work.

Is it all a good news story? While the number of people who know about web accessibility or what needs to be done to make sites and applications accessible is on the rise, websites and applications are launched daily, for whatever reason, with little to know consideration for accessibility.

There are still common misperceptions out there such as: people with disabilities don’t use the web; adding alt text to images is all that is needed to make a site accessible; the only web users with disabilities needing consideration are blind JAWS screen reader users; accessibility can be dealt with at the end of development or in a “next” release; or making a site accessible will: take too much time, cost too much, and impact creativity.

The W3C’s Web Accessibility Initiative is certainly doing work around outreach and education. However, I still hear people lament about how looking at the Web Content Accessibility Guidelines (WCAG) V2.0 documentation is overwhelming, when all they want and have the time for is a handy list of what is required to make a site accessible.

Development tools, frameworks, and technologies are constantly changing, and these are being released at lightning speed. To further complicate matters, while technology vendors may make available accessible widgets, the reality is, developers may want or need to customize them or use others that are not accessible because they work better based on client requirements. Or, they may choose to build their own components altogether. Each of these situations will have an impact on how accessible the final end-product will be. Add to the mix the fact that many adaptive technologies, such as screen readers, screen magnification, and dictation software that some users with disabilities need in order to interact with the web are just not keeping up to pace when it comes to being able to work with the latest and greatest in rich internet technologies.

Involving users with disabilities in testing throughout the development lifecycle and/or using different combinations of browsers and adaptive software during testing, is still not commonplace. This is key, especially since much of the accessibility of rich internet applications rests on how techniques, controls, and technology are being implemented. This can only be validated through testing, and who better to test than the typical end-users themselves.

SG: Where do you see accessibility heading in 2010, and beyond?

JA: I’ll answer the question by saying where I’d like to see accessibility head in 2010 and beyond. We need many more real-world examples of websites and applications in the mainstream, as points of reference, which showcase how to use the latest and greatest widgets and technology in an accessible way. To be truly useful, these need to include not only sites that contain textbook perfect implementations, but also others that have varying levels of complexity that call for some level of thinking outside-of-the-box in order to make the site accessible.

We need to redouble our efforts around education and outreach, where the focus shifts from what is seen by some as preaching and prescriptive, to practical, hands-on, useful information using language that devs and others speak. This is especially critical given the emphasis today on initiatives like Government and health 2.0, and the mobile web, who knows what’s next.

I am excited by the emerging grassroots efforts to explore adopting the unconference model to educate and communicate with the development community on IT accessibility. This is just one way, and there are certainly other methods out there, such as exploiting YouTube.

I am worried that if we do not put a focus on education, that developers, in the absence of information they can use immediately, will go ahead and implement accessibility the best way they know how, potentially incorrectly, which will only lead to inconsistencies across the board.

At the same time, we also need to make it easy for people to make things accessible. This is especially true in our world of user generated content, where Grandma Sue could be posting a video. If adding captions requires a degree in Computer Science, she won’t do it.

The vendor community of screen reader, screen magnification, voice recognition and other adaptive technologies needs to be more visible and active in the ongoing accessibility conversations that are happening real-time. They need to be faster to market, and the technology needs to be compatible with what is being pushed out today, so that someone with a disability isn’t waiting for a new version of product X in order for them to use all of the features and functionality of a website that launched yesterday.

As an IT accessibility professional who happens to be blind, I would like to see more people with disabilities get involved in the field of web accessibility in the years to come. As a profession, there is absolutely a need for more people with disabilities working at the testing and coding level. However, we also need more people with disabilities at the tables where business, thought, policy, and IT conversations are taking place that will shape where the web will be headed in the years to come.

In the final installment of this interview, Jennison will give advice on how to deal with obstacles that the business world may put up in one’s quest to make web sites more accessible. I’ll also share some final thoughts about this outstanding experience.

Stay tuned!

Series Recap:
Interview with Jennison Asuncion – part one
Interview with Jennison Asuncion – part two
Interview with Jennison Asuncion – part three and wrap-up

Jennison is also a respected, insightful voice in the social media world, on Twitter and LinkedIn in particular.

Steve (SG): Tell us a little about yourself. What do you do in the field of web accessibility?

Jennison (JA): I’m a big jazz and live comedy fan, a shameless networker, and I enjoy cross-country skiing.

In terms of the field of web accessibility, I work in Toronto for one of Canada’s banks. Part of my role involves consulting with developers so that what they are putting out there is as accessible as it can be to either our employees or clients with disabilities.

Somewhat related, by night, I co-direct the Adaptech Research Network, where we have been conducting research into the use and accessibility of information and communication technologies by college and university students with visible and non-visible disabilities for over ten years. This has helped me build perspective on the wide-range of experiences of end-users with a variety of disabilities who interact with technology which I take into my day-job. I really feel lucky to have a foot in both the corporate accessibility and the academic research areas for that reason.

SG: Why did you take an interest in the subject?

JA: Without wanting to overstate the obvious, the Web is such a part of many of our lives, professionally, recreationally, and personally. This is only set to increase, and at a faster pace. Case in point, look at all of the social media tools out there.

The web has also opened up so many opportunities that might not have been possible say four or five years ago for everyone, but especially for people with disabilities. So, doing my part to assure that this landscape can be made as accessible as possible just feels like the right thing to be doing.

SG: In your experience in the field of web accessibility, what sorts of things about people with disabilities using the Internet have surprised you the most?

JA: How resourceful and willing a good number of users with disabilities are in figuring out ways to make a website work for them, even though it’s not necessarily that accessible to begin with. I’m not saying that’s the ideal situation whatsoever, but, for example, as challenging as, say Facebook can be from an accessibility perspective for some, there are folks with disabilities who have found ways to make features and functionality work for them.

The other thing that doesn’t surprise me, as much as it serves as something I need to always remember, is that there is still a whole group of users with disabilities, who are not tech-savvy and connected through things like Twitter, who may be using older versions of adaptive hardware and/or software who are out there. With little to no formal training, many of them come online to check their e-mail, may do a bit of online browsing, and that’s about it. Or they only use a computer at work, not at home. They know nothing about Accessible Rich Internet Applications (ARIA), and/or may not be able to afford to upgrade their systems.

It’s those people that I worry are being left behind. Left behind, insofar as they may one day visit a website that they’ve known and experienced one way for a long time, but all of a sudden, because of a site upgrade, they discover the user experience of the site has drastically changed. Maybe their browser is no longer supported, or their adaptive technology is not providing them with any useful information at all, rendering the site useless to them. If they cannot upgrade their systems for what ever reason, then what?

I’d like to thank Jennison (something I’m sure I’ll be repeating numerous times over the next week!) for taking the time to share his reflections on accessibility.

Next time, we’ll ask Jennison where he feels accessibility stands right now, and where it’s headed in 2010 and beyond.

Series Recap:
Interview with Jennison Asuncion – part one
Interview with Jennison Asuncion – part two
Interview with Jennison Asuncion – part three and wrap-up

It isn’t at all redundant. Making a web site “accessible” doesn’t strictly mean making it easier to navigate for those with disabilities. By structuring a website with clean, correct and orderly code, images and text with sufficient color contrast, supplying meaningful alt tags, logical tabbing order, etcetera, you’re creating an experience that’s all around better for all visitors.

Clean, concise site navigation benefits everybody. Descriptive links that actually identify where they are taking you benefits everybody. Forms that are properly labeled and orderly benefit everybody.

There are also people visiting your site with slower Internet connections. There are those who prefer browsers other than just Internet Explorer or Firefox.

There are also visitors to your sites who particularly prefer semantic, clean code. They’re called search engines. Poor or nonexistent titles and header tags hurt search relevant, in addition to giving screen readers a hard time identifying pages and elements.

Accessibility covers a whole lot of ground beyond just disabilities.

I was really impressed by the extent to which a place like IndependenceFirst goes in making all aspects of their facilities accessible. Some examples didn’t surprise me, like having bathrooms and shower facilities that are fully usable by those with various disabilities, or a cafeteria with accessible appliances. Others were just things I’d have never thought of.

There is an extensive library of assistive technology devices available for use, some I recognized and others that were completely foreign to me. They were several cases with all manner of these devices — keyboards, telephones, calculators, clocks, measuring cups, to just name a few.

IndependenceFirst has a program in which they help people with disabilities get recycled computers. This includes training such as accessing the Internet. We got a glimpse of this Computing Recycling area. There are even local Milwaukee businesses that send volunteers over to get donated computers up and running.

I had never even considered the idea of an accessible copy machine, but we got to see one. Also, in the tour of the Wellness Center, Carol Voss pointed out a wheelchair-accessible weight scale, something that is very rare, even for hospitals.

It’s probably pretty obvious that I came away from visiting IndependenceFirst with a deep appreciation for their services. Four straight blog posts about my experience ought to prove it! After building a rapport with IndependenceFirst through social media, I was glad to finally see the place and meet people like Carol Voss.

I feel I’ve learned a lot in my first year of delving into web accessibility, but I’m coming to realize that there is a huge difference between reading insightful articles and online materials, and actually firsthand watching how disabled people interact with the world around them.

Watching Scott Mayer cruise — and occasionally stumble — through web sites, just trying to do basic tasks like pay bills online, really phased me, in a good way. Even someone who’d like to think of himself as enlightened to web accessibility has a lot to learn!

For me to call myself a true web accessibility expert, I’m going to need more direct contact with disabled web users. You can’t truly understand what they go through by solely checking web sites yourself and running automatic tests.

(Special shout to to friend and colleague Michael Seidel for sharing the photos of the assistive equipment and the computer refurbishing room)

In my last couple posts, I recapped the insights of Shawn Henry and Scott Mayer. That was only part of the experience. After their presentations, we were treated to a tour of the IndependenceFirst facilities.

Carol Voss, the Public Relations and Marketing Director as well as the Twitter voice for IndependenceFirst, took our small group around the building. It was really great to finally meet Carol in person, after many months of Twitter conversations as well as the email interview she had done for this blog in summer. (See IndependenceFirst interview part one, two, and three)

It wasn’t news to me that constructing a building for an organization servicing the disabled requires special considerations. However, it was both surprising and deeply impressive to see the extent of it.

For example, consider the floors. In the hallways, the floors have darker borders, to serve as a visual waypoint where the halls continue and where they lead to doorways.

Also, no matter the flooring material — carpeting, tile, wood, whatever — all surface transitions are completely flat and even. This is very important for those traversing room to room via wheelchair or with difficulties walking. It also requires a tremendous level of attention and detail by the building constructors.

Something else that I hadn’t considered before but makes perfect sense — there are activation buttons for opening doors just about floor level, in addition to their typical higher location. This enables somebody unable to use their hands to open the door with their foot.

Similarly, door handles as well as scanners for security access are lower than you typically see at other offices, to further increase accessibility to wheelchair users.

This is the just the physical makeup of the building, but such details go a long way in making it easier for those with disabilities to fully utilize the facilities. If you think that’s impressive, in my next post, we’ll share even more examples. From copy machines and weight scales to cafeterias and library rooms, there are a whole lot more accessibility considerations within the walls of IndependenceFirst.