Off the Top: Information Application Development Entries
Showing posts: 106-120 of 189 total posts
Accessible persona
I was reminded today of Marcus a persona in Mark Pilgrim's Accessibility tutorial for Weblogs (and anybody else interested). Marcus is actually a real person (as pointed out by Mark), which drives the persona home. This may be my favorite example currently for accessibility.
At work we constantly get outside developers turning over non-accessible sites or applications. The client I work for is put through the painful task of explaining what needs to be done to meet Section 508 requirements. The teeth pulling the client goes through is shameful as the outside contractors want every single item spelled out and they want to know why (they usually have built the application or site through reusing a previous product built by somebody that is no longer there and that way they can do the job cheaply and make a better profit, had they built from the beginning knowing and understanding the requirements it would have been easy and inexpensive to do). Often times I am asked to help define what needs to be done and why something fails compliance, usually as a sanity check (accessibility has been an area of strength for four years or more). The regulations are very broad and do not define the exact actions that should be avoided (this is the correct approach to allow for technological improvements).
Marcus is a great example to have on the shelf as much of the information I work with during the day is public information that the taxpayers paid for, whether they are sighted, physically able, have their hearing, or not. We know that there is a decent number of users that come to government sites from publicly available systems (like in libraries) that have technology that is nowhere near current. These people should be able to get to the information and use the information and applications around it as others can use it. Marcus is usually what we see as worse case scenarios using Lynx, but also what we think of as our baseline. Knowing Marcus exists and is really helps greatly.
There is also a benefit side to building accessible information, it is future ready information. The information that is fully accessible is ready to use with no (or is rare cases slight) modification on mobile devices. This is the wonderful thing about building accessible information. One of the first steps is building information that validates to a standard. The next thing is separating style from the content by using style sheets, which make it easy to over ride any style that is problematic or to easily allow for scalable styles. This two helps create information that is future compatible. Accessible information can also be easily reused in from its presentation as it is built to standards that ease.
Accessible information is also structured properly. Structuring information properly is far more than how it looks, it is how is marked up. A header on a Web page has an "h1, h2, etc" tag around it, which eases the ability to build a table of contents or use that header as a contextual aid to summarize the information below it (that is if headers are tagged properly and the content in the header is properly descriptive). Structuring the information helps the information be reusable out of the Web page as that is what HTML does, provides structure elements in the markup tags. If information to be reused has needs (including structure and context that is easily discernible), which validating HTML provides as a basic foundation -- of course there is much that can be improved upon the basic HTML markup, but it addresses the information needs. Building accessible information applications (Web sites included) keeps money from being wasted in the future and it does not require buying a third-party application, which are often cause more problems than they solve where accessibility is concerned (this will not always be the case).
As Joe Clark's book, Building Accessible Websites points out accessible does not mean ugly or plain. Joe walks the reader through how to make beautiful sites that are also wonderfully to folks like Marcus (side note: Mark Pilgrim edited Joe's book). Another excellent book on accessibility, and is my favorite book on accessibility, as it works very well for Web application developers (and I agree with its approach to information in complex tables more than Joe's approach) is Accessible Web Sites. These are two great resources for leaning how to do things properly. I will be working on longer reviews of each in the near future.
User Centered Design and beyond
There are a handful of synonymous terms I have been running into and using in the past few months. Most of us understand User-Centered Design (UCD) as a concept and practice. UCD helps us build successful information applications, including Web sites, that are usable by those that want to use them, have to use them, or are seeking the information contained within them. UCD does not fully focus on the developers, the project owners (clients or mangers), but puts the focus on the end users of the information or digital services. This approach to development provides a wonderful return for those that engage in this practice as it is demoralizing for those that have spent time or paid money for development to have an information application that is not used (if it is not demoralizing it could be time to find a new profession).
Information wants to be found by those that seek it and Web sites, applications, and poor interfaces should not stand in the way of those wishing to consume the information. Information should be prepared and presented with consumption in mind. Many times digital information is a service that is used to assist the consumer of not only that information but other elements like a person buying a product. In a sense we not only create User-Centered sites and applications but Customer Service tools. This focus is very helpful when working on a site that will serve as communication between an organization or person and another organization or person. The experience between these two parties in this information transaction should be effortless. Just like a physical experience we don't like standing in a long line only to get to the front of the line to have the person tell you they can not help you and you have to go to another location or that there is no process to get your money back. As customers we want effortless experiences in the physical world as well as our digital environments. Customer service has been a focus of the physical business world for years and UCD is the digital equivalent. UCD has as its focus providing not only an enjoyable experience to perform the task, but also a more pain free method of correcting errors and problems (the folks at 37 Signals call this contingency plan design and are ready and will in to teach those that do not understand it).
While customer service is mantra in the private sector, Citizen Services or Citizen-Centric Services are becoming the focal point for the public sector. Governments have learned and have turned their digital focus on the citizens. Yes, governments are beginning to "get it". It is not about the technology, but about the consumer of the services. One of the central tenets of a governments is providing services. One of these services is gathering, aggregating, and providing information. Getting the information into the hands of those wishing to consume this information has been the struggle. Not many years ago we had learned to use a Post Office box in Colorado for a government clearing house for information, now we should only need a Web browser.
The government was one of the first entities to take advantage of the Internet to post information. Some U.S. federal government agencies created sites as early as 1993 and have been keeping them running ever since. More and more the government created sites and posted information. The down side was there was little of anything other than general Internet search engines to get the user to the information or service they desired. In the past year or two this focus has begun to move from just posting information where it was grown (in what appears to most citizens to be arcane bureaucratic and political organizations with undecipherable acronyms) to tying these information repositories to central jumping off points. FirstGov is the mother of the effort and has been guiding the Citizen-Centric focus. Many agencies have turned their eGovernment offices and staff toward the mindset of providing electronic Citizen-Centric services. Many agencies are working to provide jumping off points to information and services that are commonly sought and now available on the Internet. These portals remove the morass of acronyms and the need to understand organizational structures for the common citizens that have paid their taxes and are looking for a return on that investment in the form of electronic information or digital services.
Yes, many of us are now fixing the mess of information digitally thrown onto the Internet by providing structure to this information and making it findable and usable by the people interested in consuming the information or the products the information provides a gateway to. We now have the User-Centered Design umbrella to tie the roles and processes together that we use to help the User, Customer, or Citizen. These handful of terms are used for the same focus that makes the digital world a less frustrating, more friendly, and usable environment.
Networked PIM
Victor quickly discusses and points to a networked Personal Information Manager. This tool, which early Apple developer Andy Hertzfeld has helped with, seems to be a tool that would be of great benefit for digital projects.Yahoo does PHP
Yahoo presentation on why they are moving to PHP. This would make a great interview of write-up as PowerPoint presentations are largely worthless with out the speaking that accompanies them. This is one presentation that has a tiny bit of information that makes me crave for more. I use PHP here as a scripting language of choice. I love being able to use it at work for many of the reasons outlined by Yahoo. It is better than ColdFusion, ASP, or JSP as far a server requirements, secure, and time to market. The flexability and speed which one can develop is tough to beat, except for the flexability of Perl (there is a reason it is called the duct tape of the Internet). The maxim has been use PHP where you can and Perl where you must. Other languages pale in comparison, but have marketing dollars, which drive the hype. [hat tip Cam and Anil]Wahoo, Books
What a wonderful week in books. I just received Christina Wodtke's Information Architecture: Blueprints for the Web today and it looks fantastic. I have only leafed through it briefly, but it seems to cover the basis wonderfully and provide excellent guidence on how to get through IA successfully.
Saturday I picked up Jesse James Garrett's The Elements of User Experience: User-Centered Design for the Web and have read it in little snippets and have made it through a very good chunk in no time. Much of what I have learned over time, from experience, or from great thinkers like Jesse, which leads to successful Web sites or information applications is in this book. Knowing the steps and phases of approaching development will help you greatly. Jesse has it down for all to read and it is wonderfully written.
I am very glad to not only know these to folks, but that they are sharing what they have learn for others to gain from their experiences. This sharing is what the Web was build upon and will keep the Web improving into its next generations and incarnations. Congratulations guys!
Udell encounters UDX
John Udell writes Interaction Design and Agile Methods over at O'Reilly Net. The article was sparked by Alan Cooper. To many of us ethnographic studies and using persona are not new ideas, but to Udell it is foreign, which makes this a good read.Hierarchy of Information Needs
Lou discusses the relationship between information architecture and technology, which sparked the following brain dump on my part:
This subject of information and technology has been of interest with me for quite sometime. The term "IT" has been vastly dominated by the technology portion of the term. Oddly, in organizations that have Chief Information Officers (CIOs) and with out Chief Technology Officers (CTOs) the CIOs role is largely focused on technology to serve the information (this is fine), but the stress has been technological solutions. As nearly all of us in the IT field know, the technical solutions are far from perfect (I know nothing is life is perfect) and many times require reworking business processes to take advantage of the technologies best traits. This is much akin to Keith's point about technology companies selling products and not whole solutions.
In my work I came to it from the information and communication side many years ago and along with it I married the technology side, as it was a wonderful pairing with great promise. Over the years I have heard more than anybody's fair share of, "we don't have to worry about knowing the information, we can code around it". This is the point, I learned when you pull in the reins on the technical team. This is what drew me deeper into the realm of the technical side.
If we look at information from the communication viewpoint and what role the information will play as it transfers information to humans and to other machines for use and also reuse. We have to understand the information as its basic levels, similar to Maslow's "Hierarchy of Needs". What are the human elements thatare intended, i.e. what purpose does the information serve? What properties does the information need in order to transmit this information for best use? If the information is corporate sales trends and assessing and tacking variables that impact these trends, then we have to identify the human audiences that will be using this information. The basic level of "Information Need" is do we have the proper data or information to be able to create this type of report. Do we have the information types to provide usable information for the various audiences and do we understand the vocabulary of these audiences (vocabulary in this sense can be textual and visual as some audiences may best understand the information in charts and graphs, while others will best understand textual quantitative indicators). Do we have the basics to begin building this content, which will be tied to a technological question as to how the data and information is captured and stored? Once we can answer yes to these information, human, and technical questions we can move up the "Information Needs” hierarchy. It is also at this point that we know we can publish some information to have some folks make use of it, but we know the use of the information at this point will be far from optimal and the information may not be used in its proper method.
The next level would be questions of information use. We have established we have the data and content to build the information, but how will the information be used and who/what will be using the information. These questions will help shape the information structures and the medium(s) used to convey the information. The information may require different vocabularies that need to be established or used so the different audiences can best understand and make use of the information. What is the environment that the information will be used in and in what context? When these answers are established, only then can the technology to be used for the varying mediums be established. This level gives a great level certainty that the information and its use will be effective.
Far too often the technology is chosen with out asking these questions and the medium is used is driven by the technologies limitations, which limits the information's use and efficiency. Many organizations found that their reliance on storing all information in Adobe Acrobat did not fit their efficient information needs. Acrobat works best for replicating print versions of information and has other properties that work passably, like searching the text, providing information that is accessible to those that are handicapped, quickly accessing sections of that information over a network connection, etc. Many corporations found it was best or even desired to not store their information in Acrobat, but to offer the information in Acrobat as an output of another information storage methods that provided far greater information use and reuse (this does not apply to every organization as their are some organizations that make proper and efficient use of Acrobat and it serves that organization perfectly). These organizations came to the conclusion that the information was the primary importance and the information and its use should drive the technology.
The next step is to determine how the information can be optimized to take advantage of the mediums being used. This will allow the information to have the most impact. As the medium and technologies have been chosen to best present the information, at this point there are steps that can be taken to improve the marriage between the medium and the information. For example, we know that one of the mediums for the information will be Web pages; the information will need to be structured in a manner that takes advantage of the possibilities with that medium. The Web browser gives us the ability to present textual information and charts together, while providing relatively easy access to more detailed information and/or an interactive media presentation that permits the user to see the charts change over time based on the selection of these different variables (done with Flash, DHTML, etc.). Similar information could be offered in a PDF of the printed report that would print on 8.5 by 11 inch paper and one for A4 paper (the international standard paper size).
The last phase it validating and testing the information dissemination. We continually need to test to ensure we have identified all the audiences that are using the information, we are capturing all the data and information is required and makes sense to have for the information's use, we are capturing and storing the information in a means that is efficient for our needs to use the information, we are providing the audiences the information in a means that is most usable and efficient for them, and the information is being found and used.
This Information Needs hierarchy allows the marriage of technology to information where and when it makes sense. This Information Needs seems to be the basis for the user centered design, information architecture, knowledge management, experience design, etc. There is an understanding of the balance that is required between the creators of the information; the information itself; the technology to capture, store, process, and present the information; and the users of the information.
In the past few years the technology and not the information nor the user of the information were the focal points. Money has been spent on technologies that have failed the purchasers and the technology and the whole of the information technology industry gets blamed. There is a great need for people that are willing to use their minds to create the foundation for information, its use, and the technologies that can help make this more efficient. The balance and the steps in the proper order must be there to give information and technology a chance.
Adaptive Path to DC
Last September I attended a two day User Experience Workshop put on by Adaptive Path. This was one of the most conprehensive sessions/classes I had ever been to on the approach and skills needed to develop a usable Web site. As many of us know the Adaptive Path folks are taking this great session on the road and adding a third day using a local professional to help bring it all home. This may be the most productive money you spend all year. Those that come to your sites and pay for your work with receive an even greater benefit. Do it for yourself and for the users of what you produce.
The following is a better description by the Adaptive Path folks describing the Washington, DC (actually held in Arlington, Virginia) sessions:
Design theories don't help if you can't make them work in actual day-to-day practice. Increasingly, sites must respond to the realities of scant budgets and greater financial return. Adaptive Path's User Experience Workshops will prepare you to meet these challenges with usable tools for putting design theory into practice today. You'll spend the first two days with Adaptive Path partners Jeffrey Veen, Peter Merholz, and Lane Becker. They'll show you how to incorporate user goals, business needs, and organizational
awareness into your design process. You'll develop a project plan, learn methods for research and design, and create clear documentation. You'll learn the same strategies Adaptive Path has successfully practiced for a wide range of companies, including Fortune 500s, startups, and not-for-profits.
Additionally, on day 3 we will be joined by information architect extraordinaire Thom Haller, who will talk about "The Value of Structure." In this workshop, he'll draw on twenty years experience in professional communication to explore the possibilities inherent in structure, and its value to others. As participants, you'll have the opportunity to see structure through users' eyes. You'll learn a measurements-based, performance-focused structure for gathering, evaluating, chunking, knowing, and organizing content. You'll have a chance to "sample" different structures (such as narrative) and see how they offer value to organizations and their constituencies.
You'll leave the workshop inspired and equipped with design techniques and a library of documentation templates that you can use right away -- so that your web site will satisfy your users, your management and you! But wait--there's more! Or, rather, less! As in--DISCOUNTS! If you sign up with the promotional code "FOTV" (without the quotes), we'll knock the price down from $1,195 to $956 -- a 20% discount.
For more information: http://www.adaptivepath.com/events/wdc.phtml
PHP development with Apple's OS X Developer Tools
Apple provides information to use Apple's Developer Tools (for OS X) to build PHP. This will be a very nice mobile tool.Baking versus frying CMS
Aaron discusses baking versus frying with content management and updates bake and fry CMS ideas. The idea is to bake content, which is using your content management system to produce static pages. The alternative is to fry from the CMS by providing truely dynamic content. There are a few reasons why one should choose the frying method:
- Frequent (hourly or semi-daily) updates of informaiton
- Multiple dependancies (information linking to and from many points)
- Unlimited resources
- Many variation of presentation of the data
- Providing user slicing and dicing of informaiton capabilities
- Many external content providers
This list does not capture everything, but also provides maleable guidelines. There are many advantages to baking (publishing static content pages) from a CMS:
- Speed of delivery
- Archievable version
- Ease of troubleshooting and maintenance
- Editable output pages
- Use templates to generate valid mark-up and perfect 508 compliant pages
- Using reusable content pieces that provide consistancy and accuracy of information on all presentation layers
- Keeping various application elements well maintained
Aaron provides good links for further discovery of your own.