Why 508 applies to Information Architecture

Someone pointed out to me that my last post on ADA and section 508 was a little confusing. My particular site, being a government site, also uses approved templates--these tie in to 508 because the idea is that the templates are designed to handle resizing of text without jumbling or distorting. To be honest, there is a web team at my work that deals (very bravely) with all of these highly important and sometimes frustrating issues.

As described in my last post, I think that fair and equal access are huge issues in providing information. However, providing fair and equal access is sadly the road less traveled, and those of us who strive to do it do need to put in extra effort.

To reframe how 508 (a GUI issue, seemingly) applies to Information Architecture, I'll aim this post at individuals who were not in 501 last semester where we talked about different needs exhibited by different groups in information seeking behavior.

In a technical light, "fair and equal access" is most frequently called "universal usability." In "Chapter 14: Ethics" of Moreville and Rosenfeld's Information Architecture, under the section about physical access, section 508 is discussed. Also discussed is Ben Schneiderman, who extended the sentiments of 508 to include not just differences in physical ability, but uniqueness in all ability in the concept of universal usability. Different people think differently. Labels aren't intuitive to everyone--this concept is one we explore frequently in the field of Linguistics.

For a prominent example, read here about Benjamin Lee Whorf and the "empty" gasoline barrel. An "empty" gasoline barrel might be perceived as less dangerous because it is labeled "empty"--but "empty" gasoline barrels are actually more dangerous because it's the fumes that ignite. This opens the door to the idea that different cultures, languages, backgrounds...anything, really, could affect a person's cognition and what they perceive as useful or intuitive in the ways of information architecture and labels. To put it simply, what works for me might not work for everyone--I need to consider different abilities (physical and mental, with all abilities being equal and different) to more fully serve my users.

In terms of real world examples of information architecture being affected by issues of universal usability, I have quite a few. First, I couldn't find the page requirements for my final project in 840 (this probably sounds really stupid to some of you, as we're in a program about finding information). I was looking near the top of the project description, where I had trained myself to look because that's where other syllabuses have located it. After asking, I was told the page breakdown was located within the project directions; a completely valid way to do things, but not intuitive for me. Now, if I had read more thoroughly, I would have found it--but if everyone read websites thoroughly, there would be no sense in creating information architecture, would there?

In libraries, we are now seeing a shift from using the Dewey Decimal System to one that organizes the book as they might appear in a book store. Why? Well, the short answer is that DD is designed for use by librarians (who love highly organized structures, like databases) but not for patrons (who like browsing bookstores). Dewey Decimal is intuitive for librarians who are socialized to use it, but not for the end user patrons. The information architecture wasn't developed with the consideration that not everyone thinks like a librarian--the patrons are differently abled in their information seeking habits.

In terms of my project, 508 and universal usability are central to development, and because I work on a team with programmers and designers, and because I like those people, I'm not going to sit back and say "not my problem" to 508 and usability issues. Even Morville and Rosenfeld say that "information architects have a role to play in creating useful, usable systems, that work for diverse audiences" (pg 343). They also advocate that:

"As an information architect, you can define any or all of these ethical dimensions as 'not my problem'. Maybe the responsibility really belongs with the client, the business manager, the authors, the usability engineers, or the users themselves. Or, maybe we'll all just wait for a superhero to save the day." (pg. 344)

When working in a team, I believe that information architecture is the problem of the information architect because everyone is there to serve the user, and where 508 and the template allows things to go on the screen can change how many labels are used or what they appear as. It can change how much information we put on any given page for easy readability. It can change the amount of explanation we feel necessary for the terminology and jargon used on the site. I may not even be allowed to use a search bar (for some reason that will be explained to me via email), and that would affect my information architecture a great deal.