Off the Top: Accessibility Entries


July 15, 2018

Mac Touchpad Dragging

I bought a Mac laptop for myself in 2001 and largely have been using the same version of the same set-up since then across 5 or 6 Macs since them (with one or two full nuke and repaves in there, but with those I pulled in my the applications and modification / customizations from preferences). In the past few months, I’ve been using a brand new Mac that is supplied by work / project and not only does it lack my outboard brain, but it doesn’t work like my heavily modified Mac.

The one thing that has been driving me crazy is I haven’t been able to sort out how I have a three finger drag on my personal MacBook Pro so I can have it on my one for work. It is frustrating as I go to click on an object to then drag it with three fingers to where I want it, or I go to the top bar of an app and place the cursor over it and use three fingers to drag the window to where I want. I do similar things to resize windows. I have looked in Better Touch Tool, thinking I had set it up there. I looked in Preference Settings for the touchpad, but no. Today I opened a lot of customization apps I have on my personal Mac and nothing.

I was looking in the Preference Settings in the Accessibility settings and found what I was looking for, the three finger drag. I would have never thought it would be in Accessibility. Given that my current personal MBP has a touchpad that the left half needs a lot of force to click on something and do usual tasks it does make sense that having a light touch manner of dragging things would be in Accessibility. Now I know how to fix one more thing on a work Mac to get it to my own personal Mac set-up so it gets closer to being an extension of me and less a tool I have to think about how to interact with rather than thinking about the work I am doing.



May 3, 2008

Getting Info into the Field with Extension

This week I was down in Raleigh, North Carolina to speak at National Extension Technology Conference (NETC) 2008, which is for the people running the web and technology components for what used to be the agricultural extension of state universities, but now includes much more. This was a great conference to connect with people trying to bring education, information, and knowledge services to all communities, including those in rural areas where only have dial-up connectivity to get internet access. The subject matter presented is very familiar to many other conferences I attend and present at, but with a slightly different twist, they focus on ease of use and access to information for everybody and not just the relatively early adopters. The real values of light easy to use interfaces that are clear to understand, well structured, easy to load, and include affordance in the initial design consideration is essential.

I sat in on a few sessions, so to help tie my presentation to the audience, but also listen to interest and problems as they compare to the organizations I normally talk to and work with (mid-size member organizations up to very large global enterprise). I sat in on a MOSS discussion. This discussion about Sharepoint was indiscernible from any other type of organization around getting it to work well, licensing, and really clumsy as well as restrictive sociality. The discussion about the templates for different types of interface (blogs and wikis) were the same as they they do not really do or act like the template names. The group seemed to have less frustration with the wiki template, although admitted it was far less than perfect, it did work to some degree with the blog template was a failure (I normally hear both are less than useful and only resemble the tools in name not use). [This still has me thinking Sharepoint is like the entry drug for social software in organizations, it looks and sounds right and cool, but is lacking the desired kick.]

I also sat down with the project leads and developers of an eXtension wide tool that is really interesting to me. It serves the eXtension community and they are really uncoupling the guts of the web tools to ease greater access to relevant information. This flattening of the structures and new ways of accessing information is already proving beneficial to them, but it also has brought up the potential to improve ease some of the transition for those new to the tools. I was able to provide feedback that should provide a good next step. I am looking forward to see that tool and the feedback in the next three to six months as it has incredible potential to ease information use into the hands that really need it. It will also be a good example for how other organizations can benefit from similar approaches.

Comments are open (with usual moderation) at this post at Getting Info into the Field with Extension :: Personal InfoCloud.



October 19, 2006

The Excellence of Accessibilty Presentations

One of the people I have met this past year and come to know better through traveling to and from Web Directions 2006 and hanging with at d.construct is Derek Featherstone. His presentations on the subject of accessibility are the best I have ever seen. The past year I have not had the opportunity to think, talk about, or develop around the subject of web accessibility (I had thought of this as a good thing, but I will explain that shortly) other than as an extension of semantically well structured information, which most conference I have been speaking at are related to in one form or another.

Derek is one of the first presenters that digs deep into accessibility beyond a set of rules, but also looks at usability for those with accessibility needs as the baseline for building great sites that work for all. He frames his presentations not as accessibility is for "them", but as it is for all of us. This focus is astoundingly refreshing and rare.

Derek digs into how JavaScript and Ajax, if done well (did you read that caveat, "done well"?), can actually improve accessibility. In his presentation Derek walks through how to think about interfaces, both rich and static, and improve upon them for everybody. Much of this is basic usability that is missed by many, but the rich interface elements are something I have not heard before from somebody talking about accessibility.

Lastly, Derek's presentation style is light and easy, which bring many people who are put off my accessibility into listening and learning. It is a great thing to watch people gain interest as he presents about a subject they did not care about. But even better is when they start talking about they now have a good framework to think about and approach accessibility does the power of Derek's presentation style and deep knowledge make a the subject come to life.

Granted I have not been reading much around accessibility for the past year, although I have had some great discussions about it with Matt May and Christian Heilmann at various points this year along the lines of rich interfaces and caring about those with accessibility needs. My lack of interest is not because I do not care about accessibility, but I have been burned out from dealing with the politics of accessibility in the U.S. Federal Government. I enjoyed working with the webmasters on the government side, but outside of that it was really painful. Most people would go out of their way to make unusable, poorly structured, semantically incorrect, let alone unaccessible sites just because they were told to make a site accessible. The long battles, even with those charged with caring and ensuring accessibility, made me very happy not to have to deal with accessibility for quite a while. Since you can get about 90 percent of the way to accessibility with just semantically well structured XHTML mark-up, which is the mark of any decent web developer, I have not considered the subject much beyond that in over a year.

Derek's presentations and our long discussions regarding semantically well structured information as the basis for everything that has improved the web in the past few years, brought me back to enjoying the subject of accessibility. In saying this I am more sure now that those who wrote the U.S. Section 508 regulations and those on the Access Board have failed those who needed real accessibility so they could partake in this freedom of information we embrace.



September 14, 2006

Trip and d.construct Wrap-up

I am back home from the d.construct trip, which included London and Brighton. The trip was very enjoyable, the d.construct conference is a pure winner, and I met fantastic people that keep my passion for the web alive.

d.construct

The d.construct conference had Jeff Barr from Amazon talking about Amazon Web Services, Paul Hammond and Simon Willison discussing Yahoo and its creation and use of web services for internal and external uses, Jeremy Keith discussing the Joy of the API, Aral Balkan presenting the use of Adobe Flex for web services, Derek Featherstone discussing accessibility for Javascript and Ajax and how they can hurt and help the web for those with disabilities, myself (Thomas) discussing tagging that works, and Jeff Veen pulling the day together with designing the complete user experience.

Jeff Barr provided not only a good overview of the Amazon offerings for developers, but his presentation kept me interested (the previous 2 times my mind wandered) and I got some new things out of it (like the S3 Organizer extension for Firefox.

Jeremy was his usual great presenting form (unfortunately a call from home caused me to miss the some of the middle, but he kept things going well and I heard after that many people learned something from the session, which they thought they knew it all already.

Paul and Simon did a wonderful tag team approach on what Yahoo is up to and how they "eat their own dog food" and how the Yahoo Local uses microformats (Wahoo!).

Aral was somebody I did not know before d.construct, but I really enjoyed getting to know him as well as his high energy presentation style and mastery of the content that showed Flash/Flex 2.0 are fluent in Web 2.0 rich interfaces for web services.

Derek was fantastic as he took a dry subject (accessibility) and brought it life, he also made me miss the world of accessibility by talking about how JavaScript and Ajax can actually improve the accessibility of a site (if the developer knows what they are doing - this is not an easy area to tread) and made it logical and relatively easy to grasp.

I can not comment on my own presentation, other than the many people what sought me out to express appreciation, and to ask questions (many questions about spamming, which is difficult if the tagging system is built well). I was also asked if I had somebody explain the term dogging (forgetting there was a rather bawdy use of the term in British culture and using the term as those people who are dog lovers - this lead to very heavy laughter). Given the odd technical problems at the beginning of the presentation (mouse not clicking) things went alright about 5 minutes or so in.

Lastly, the man I never want to follow when giving a presentation, Jeff Veen rocked the house with his easy style and lively interaction with his slides.

I am really wanting to hear much more from Aral and Derek now that I have heard them speak. I am looking forward to seeing their slides up and their podcasts, both should be posted on the d.construct schedule page.

London Stays

The trip also included an overnight stay in London on the front and back end of the conference. Through an on-line resource I had two last minute rooms booked at Best Western Premiers that were great rooms in well appointed hotels. The hotels even had free WiFi (yes, free in Europe is a huge savings), which was my main reason for staying at these hotels I knew nothing about. I really like both locations, one near Earls Court Tube Station and the other Charing Cross Road and SoHo. The rooms were well under 200 U.S. dollars, which is a rarity in central London. I think I have a new place to track down then next time I visit London.

London People & Places

I had a few impromptu meetings in London and an accidental chat. When I first got in I was able to clean-up and go meet friends Tom and Simon for lunch at China Experience. We had good conversations about the state of many things web. Then Tom showed me Cyber Candy, which I have been following online. I was then off to Neal's Yard Dairy to pick-up some Stinking Bishop (quite excellent), Oggleshield, and Berkswell. I then did a pilgrimage to Muji to stock up on pens and all the while using Yahoo Messanger in a mobile browser (a very painful way to communicate, as there is no alert for return messages and when moving the web connection seems to need resetting often).

That evening I met up with Eric Miraglia for a great chat and dinner, then included Christian Heillmann (who has a great new book (from my initial read) on Beginning JavaSctipt with DOM Scripting and Ajax) in our evening. The discussions were wonderful and it was a really good way to find people of similar minds and interests.

On my last day in London I ended up running into Ben Hammersley as he was waiting for a dinner meeting. It was great to meet Ben in person and have a good brief chat. Somehow when walking down the street and seeing a man in a black utilikilt, with short hair, and intently using his mobile there are a short list of possibilities who this may be.

Food

My trip I had a few full English breakfasts, including one in Brighton at 3:30am (using the term gut buster), which was my first full meal of the day. The breakfast at the Blanche House (the name of the hotel never stuck in my head and the keys just had their logo on them, so getting back to the hotel was a wee bit more challenging than normal) was quite good, particularly the scrambled eggs wrapped in smoked Scottish salmon. The food the first night in Brighton at the Seven Dials was fantastic and a great treat. Sunday brunch at SOHo Social in Brighton was quite good and needed to bring me back from another late night chatting, but the fish cakes were outstanding. The last evening in London I stopped in at Hamburger Union for a really good burger with rashers bacon. The burgers are made with only natural fed, grass-reared additive free beef. This is not only eco-friendly, but really tasty. I wish there were a Hamburger Union near where I work as I would make use of it regularly.

Too Short a Visit

As it is with nearly every trip this year, the time was too short and the people I met were fantastic. I really met some interesting and bright people while in Brighton and I really look forward to keeping in touch as well as seeing them again.



August 20, 2005

Minor Changes in Off the Top

Last night I was able to add back the Quick Links (my current bookmarks from del.icio.us. This was due in great part to the folks at del.icio.us who now have a JavaScript that makes the process easy on you and easy on them (I am not sure how accessible this is as I have not tested it, but normally they are not accessible).

I also brought back to the link to just the Off the Top RSS feed, which has nothing but the last 10 entries in archaic RSS .91 format. I still am offering the wonderful Feedburner for Off the Top option, which has Off the Top entries, my del.icio.us entries, and my Flickr photo feed all bundled in one. I have quite a few people reading this in RSS on mobile devices at the moment and I thought I would make it easier for other that are going that route to get just the content of Off the Top.



April 18, 2005

Adobe Buys Macromedia

Adobe buys Macromedia was not the news I wanted to wake up to this morning. My sole issue is competition, as with out these two competing there is little push to advance. This is not a huge surprise, as many rumors the last few years that Macromedia was on the block (most were expecting Microsoft to buy it and then spin out ColdFusion and the application tools to an outside buyer).

If this goes through, we have Dreamweaver/HomeSite as the dominant web development tool (it is making great strides towards standards compliant development and GoLive needs much more work), desktop publishing is Adobe only, market share of image editing and creation (Photoshop and Illustrator) go to Adobe, application development goes to Macromedia with ColdFusion, then we have the tough call with Flash and SVG. Flash is dominant, but SVG is open and Flash lite (for mobile) has really upset many developers as the player is up to the carrier and phone maker to deploy, not the content creator. This last step has really pushed many Flash developers away from Macromedia as they work to focus on mobile. Rumors that Adobe was working on a SVG mobile tool with open deployment had many developers for mobile really excited.

My hope would be for Macromedia customer service and pricing and Adobe Premium Suite with Dreamweaver and Flash thrown in for a well rounded package.



August 19, 2004

Accessibility is Little More Than Web Best Practices

Today I gave my Accessibility is Little More Than Web Best Practices (124kb PDF) to the Adaptive Path User Experience Week 2004 DC attendees as a lunchtime presentation discussion. It was good to find folks that are in the DC area interested in Web Standards (a very big part of best practices) and figuring how to sell accessibility to their clients that are required by law to have accessible sites. This presentation is quite similar to my STC presentation, but has the addition of the few things that are required for accessibility that are not part of web best practices (these apply to tables and forms).



May 12, 2004

Accessibilty Benefits Everybody Presentation Posted

I have posted the Using Section 508 to Improve Internet Access to Information for Everybody presentation (in PDF) presented at the STC 51st Annual Conference. The session was a progressive panel on Section 508 (the U.S. law on accessibility for the U.S. Governemnt). The session focusses on the advantages of building accessible Internet information, which is very little more than using best practices for the Web. The presentation points out who else benefits from accessible sites, which is nearly everybody. But, the group the benefits the most is mobile users as accessible sites have all the optimization that mobile users need: Images can be abandoned; Navigation can be skipped; Users can use their keyboard to move about the page and site; The information linearizes properly; etc.



April 11, 2004

Using Section 508 to Improve Access to Information for Everybody

I will be speaking at STC in Baltimore (STC conference listed in Upcoming.org) on the subject of Using Section 508 to Improve Internet Access to Information for Everybody. It has been wild to watch people spend far more time and energy trying to shirk accessibility requirements than do what is needed. Meeting Section 508 (accessibility) requirements is rather easy, well for those that are even partially competent. One great benefit of accessible sites is the breadth of users that benefit from the steps taken to meet accessiblility requirements.

Oddly, there are those that are against meeting accessibility requirement. The only logical explanation is these people are not interested in getting their information into the hands of those that can use the information. Or another possible explaination is the producers of the information love irony.

Ironically, the FCC posts nearly all of its documents in PDF. Most of these documents are not even remotely accessible (accessibility is not fungible for 508 complient, as an item can be defined as accessible but still not meet Section 508 compliance, as accessibility is a very widely defined term). The irony is the organization that is behind pushing for mobile connectivity provides document that 95 percent of mobile users can not use on a mobile device. It seems the FCC just does not care (I would certainly hope they know better).



December 14, 2003

Sir Clarke Portends Humans will Survive the Deluge of Information

I had read the Arthur C Clarke Humanity will survive information deluge interview from OneWorld South Asia. I had pulled the print version of this article into AvantGo and read it on the train commute.

The article had some great insights into the flood of information. He pointed out that over time we have adapted our ways to cope and manage information. When the printing press was developed people wondered how they would ever keep up with everything and how they would ever read 1,000 books. Most opted not to read everything and became selective. The selection of reading benefitted the whole.

The interview does a wonderful job of highlighting responsibility and the challenges ahead. We have access to an extreme breadth of information and we must find ways to expand the access and accessibility to that information to all that are willing. Sir Clarke points out that not all technology is helpful and neither is there a technological solution for every problem, in fact technology can impinge progress.

I encourage you to read the article itself and get inspired.



November 1, 2003

iPIM and Chandler have a chair at the Personal Info Cloud

There are two articles that are direct hits on managing information for the individual and allowing the individual to use the information when they needed it and share it as needed. Yes, this is in line with the Personal Information Cloud.

The first article, The inter-personal information manager (iPim) by Mark Sigal about the problem with users finding information and how the can or should be able to then manage that information. There are many problems with applications (as well as the information format itself) that inhibit users reuse of information. In the comments of the article there is a link to products that are moving forward with information clients, which also fit into the Personal Information Cloud or iPIM concept. (The Personal Information Cloud tools should be easily portable or mobile device enabled or have the ability to be retrieved from anywhere sent to any device.

The second article is from the MIT Technology Review (registration required) titled Trash Your Desktop about Mitch Kapor (of founding Lotus Development fame) and his Open Source project to build Chandler. Chandler is not only a personal information manager (PIM), but the tool is a general information manager that is contextually aware. The article not only focusses on Mitch and the product (due late 2004), but the open and honest development practices of those that are building Chandler at the Open Source Application Foundation for Windows, Mac, Linux, etc. distribution.



July 20, 2003

Bray on browsers and standards support

Tim Bray has posted an excellent essay on the state of Web browsers, which encompasses Netscape dropping browser development and Microsoft stopping stand alone browser development (development seemingly only for users MSN and their next Operating System, which is due out in mid-2005 at the earliest).

Tim points out users do have a choice in the browsers they choose, and will be better off selecting a non-Microsoft browser. Tim quotes Peter-Paul Koch:

[Microsoft Internet] Explorer cannot support today's technology, or even yesterday's, because of the limitations of its code engine. So it moves towards the position Netscape 4 once held: the most serious liability in Web design and a prospective loser.

This is becoming a well understood assessment from Web designers and application developers that use browsers for their presentation layer. Developers that have tried moving to XHTML with table-less layout using CSS get the IE headaches, which are very similar to Netscape 4 migraines. This environment of poor standards compliance is a world many Web developers and application developers have been watching erode as the rest of the modern browser development firms have moved to working toward the only Web standard for HTML markup.

Companies that develop applications that can output solid standards compliant (X)HTML are at the forefront of their fields (see Quark). The creators of content understand the need not only create a print version, but also digitally accessible versions. This means that valid HTML or XHTML is one version. The U.S Department of Justice, in its Accessibility of State and Local Government Websites to People with Disabilities report advises:

When posting documents on the website, always provide them in HTML or a text-based format (even if you are also providing them in another format, such as Portable Document Format (PDF)).

The reason is that HTML can be marked-up to provide information to various applications that can be used by those that are disabled. The site readers that read (X)HTML content audibly for those with visual disabilities (or those having their news read to them as they drive) base their tools on the same Web standards most Web developers have been moving to the past few years. Not only to the disabled benefit, but so do those with mobile devices as most of the mobile devices are now employing browsers that comprehend standards compliant (X)HTML. There is no need to waste money on applications that create content for varied devices by repurposing the content and applying a new presentation layer. In the digital world (X)HTML can be the one presentation layer that fits all. It is that now.

Tim also points to browser options available for those that want a better browser.



June 1, 2003

Usability of users who listen to Web sites

Ginny Redish and Mary Frances Theofanos have written Observing Users Who Listen to Web Sites article for the STC Usability SIG Newsletter. This article is a great insight into how blind and partially sited individuals interact with Web Sites that are being read to them by devices. This is a must read article.

This article helps developers understand how auditory reader users consume information. There are many similarities to users how use their eyes, but some of the devices we commonly use to assist auditory readers, like skip navigation, are not used as many developers think. The accessibility assistive technologies are still needed and still requested, as thie article points out. This article provides a great insight for those people who do not have a sight challenged user to learn from and to test their products with. Those who do not actually test their work or have never seen their work tested can only guess what is going on. This article helps developers get insight that helps us develop for accessibility from step one, which is where we must be thinking of accessibility.



May 14, 2003

Building with Web Standards or how Zeldman got the future now

I awaiting Jeffrey Zeldman's Designing with Web Standards, which is available for order from Amazon (Designing with Web Standards). I have been a believer in designing with Web Standards for years, but it was Jeffrey that pushed me over the edge to evangelist for Web standards. One of the best things going for Web standards is it make validation of markup easy, which is one of the first steps in making a Web site accessible.

I work in an environment that requires Web standard compliance as it provides information to the public as a public good. Taxpayers have coughed up their hard earned dollars to pay for research and services, which are delivered to them on the Web. The public may access information from a kiosk in an underfunded library with a donated computer on a dial-up connection, but they can get to information that they are seeking. The user may be disabled and relying on assistive technology to read the public information. The user may be tracking down information from a mobile device as they are travelling across country on their family vacation. Each of these users can easily get the public information they are seeking from one source, a standard compliant Web page.

Every new page that is developed by the team I am on validates to HTML 4.01 transitional. Why 4.01 transitional and not XHTML? We support older browsers and 4.01 transitional seems to have pretty good access to information no matter the browser or device. We are not on the cutting edge, but we know nearly everybody can get the information their tax dollars have paid for. I dream of a day job building XHTML with full CSS layout, but with the clients I work for we still aim at the public good first.

I am very happy that Jeffrey has his book coming out as it should bring to light to more developers what it means to build to Web standards. Every contract that is signed buy the agency I work for must validate to HTML 4.01 transitional, but very few of the sites do when they come through the door to be posted. We provide a lot of guidance to help other developers understand, but finding a solid foundation to work upon is tough. When hiring folks many claim to have experience building valid sites, but most soon realize they never have to the degree to getting a W3C validation.

Building our pages to 4.01 does not mean we are going to stick with 4.01 forever. We plan for XHTML by closing all tags and stay away from tags deprecated in 4.01 strict. Much of what we create only needs a few scripts run to convert the pages from HTML to XHTML 1.1 transitional. Having the closing tags makes scripting to find information and search and replace much easier. (Enough for now, buy the book, we will have more later).



April 7, 2003

Flash takes bigs steps forward then over the cliff

Jeff Veen discusses the Macromedia attempt at accessibility for Flash in his most recent post. Flash MX is a great improvement, but still is not all the way to accessibility, and can still keep a well done site from meeting Section 508 compliance. One of the big downsides of the current Flash build is using Flash mixed in a page with HTML. A user must have the ability to use alternate methods to move around a page, which means with out a mouse. This is often done with tabbing or voice commands. Flash does now have the capability to replicate what has been done for years in HTML, but if you add a Flash element into a HTML page the focus never releases from the Flash component. A user can not tab anywhere or even escape from the page as the cursor is stuck. If the person could use a mouse this would not be a problem, but that is not what leads to compliance.

If you use mobile devices the Flash interface is a miserable experience as Flash is vector based and will shrink to fit the screen size. Imagine trying to use a screen designed for 800 pixels wide on a 220 wide mobile screen. Forget it.

The forms in Flash are not quite ready for prime time either. I was at a rack server trying to update information in a Flash form on the Macromedia site and I was tabbing because the hyper trackball was horrible. Flash walked me down the page, but the focus moved under the bottom scroll bar with out bringing the screen focus up so I could see the form box I was having to deal with. This is flat out unacceptable, as HTML has had this right for years. Not only that, but I had a validation error and the alert was placed at the top of the Flash screen and out of site as it had scrolled up. The ability to scroll or move the screen until the alert was clicked was disabled, this took expanding the screen to full size to click the bottom of a button on the alert that I could not read.

Flash needs a motto like, "Flash -- the tool that gives uneducated interface developers the ability to create unusable forms and user experiences just to have buttons and scroll bars with indiscernible color shades" or "Flash -- for interfaces you don't want people to use"

Macromedia seems to have taken large strides with Flash, but then just stepped right over the cliff.



March 14, 2003

Goodbye glasshaus and Wrox

Owen broke the news today that glasshaus books is gone. So is its parent company Wrox books and all the other imprints from this publisher. Matt has very kind words to say about glasshaus and I will concur that they were wonderful to review books for. I looked in to my work bag and found two of my five reference books that travel from home and work are glasshaus (Cascading Style Sheets: Separating Content from Presentation which is a great book to get to understand CSS1, CSS2, and the box model, and Constructing Accessible Web Sites a great reference book on accessibility). I have a few others that I get great use from also, including Usability: The Site Speaks for Itself as an overal inspiration book for redesigns and understanding the use of various pages.

A few years ago I was picking up Wrox books left and right. I have a few ASP, PHP, UML, and XML books (some that have migrated to boxes in the basement as I do not use or prefer that language at the moment. On the whole Wrox and glasshaus had great authors that really communicate well and create books that are very useful as resources and good reads.



January 22, 2003

W3C breaks the silence with captioning

Meryl notes W3C add captioning by adding a TTWG (Timed Text Working Group). This is a great addition for the W3C and those that have been left in silence.



January 6, 2003

Dumbing down of computer and information design books

My trip to bookstores in Florida had me seeing what the person on the street sees as computer books, "Dummies" guides. There were eight shelves of Dummies computer books with a handful of Microsoft publisher books thrown in for color variation.

When I returned home I took a trip to Barnes and Noble and found the computer Web section filled with GUI tool books (Dreamweaver, FrontPage, GoLive, etc.) where there were shelves of HTML, DHTML, CSS, Perl, proper design (by Zeldman and Veen), or Information Architecture books. This trend worried me more than what I saw in Florida. The GUI books did not get into proper markup or understanding of information. The books were concerned with how to make better use of more bandwidth. Not one place in the many books I pulled off the shelf did I see any mention of the user or information use (let alone information reuse). The beauty of learning how to develop properly is knowing when the GUI tools are wrong, but better is knowing what is built properly will work well on broadband and on mobile devices. If the information is important and cared about it should be made available, accessible, and usable.



January 5, 2003

Smart Mobs and Emergence provide sparks

I began reading Smart Mobs by Howard Rheingold the past few days. It is a fantastic book that covers a lot of ground, including free riders, game theory, mobile technology, information creation, and information use and reuse. The book is proving to be an excellent follow-on to Steven Johnson's Emergence. The two books are wonderful mind-joggers and fodder for new preceptions about information, technology, and the world around us. A trait that both share is excellent bibliographies and end-notes (the end notes in both books were not very user friendly and would seem to be structured for hypertexting and not paper books).

These two books put the focus on being future friendly, which does not mean any thing new, but reinforces my belief in properly structured information. Information use and reuse are the key elements in both books, which embrace bottom-up information creation and knowledge sharing. The need for access to information drives Smart Mobs, whether it is to grow open development or for mobile use access is important. The best access environment we have in place at the moment is valid HTML/XHTML that is used to properly structure the information.

This also requires thinking through every pixel on a Web page and understanding its purpose. Understanding the user will help provide a framework for building information interfaces. The information/content should take importance also that is why users are reading, not the entertaining graphics. Keep in mind we structured information can be reused on mobile devides that may not use your images, information may be scraped and repurposed, information may be printed, or read aloud to a person using a site reader while they are driving or read to a person with visual difficulties.

You may want to get your hands on either or both books and take a look for yourself and you may be inspired in new ways or have your beliefs in information and its used renewed.



December 14, 2002

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.



October 28, 2002

IA primer

This evening I went to Content and Coffee a networking/information sharing event for content editors and writers for the Web. This evenings event was focussed on IA and had Thom Haller, Cinnamon Melchor, Vera Rhoads, and Sharyn Horowitz on a panel. This was essentially a light overview of IA, but the folks did a really nice job explaining IA and how they sell IA and its benefits to their clients or management. I may also go to the November 11 event covering 508 accessibility issues as it is a fun topic and it is good to get other perspectives.


October 21, 2002

Helping hand to accessibility

The GlassHaus Constructing Accessible Web Sites book has been a great find. I began working to build sites and applications for use in Web browsers that had to be used by individuals with disabilities in 1997. Over these years I picked up a lot of hard won knowledge and experience, but have never run across a resource that fully backed what I had gathered. The GlasHaus Accessibility book not only echoes what I have learned, but has provided new insights to improve upon what I already have. The best part of this book is that I can point others to it and I am assured they will be able to build an accessible site or Web applications that can meet high standards.

Many folks think accessibility is a great inconvenience, but it takes a little thinking and planning to do it right from the beginning. Having a great resource at hand makes the process a cake walk. Not only are the processes and guides helpful for creating sites that are accessible for those that are disabled these steps outlined also make the information in the site future ready. Sites that are accessible are much easier to use with a handheld PDA device or from even a cell phone browser. Accessibility for everybody in more situations improves with structuring the information properly, which is all making Web enabled information really requires to get it ready to be consumed. Is your information ready to be consumed by everybody?



October 17, 2002

Markup gives structure to information

I have been missing a lot of things on the Web the past few weeks. I just found Steve Champeon's article on the importance of understanding mark-up over at Web Monkey. HTML markup, some call it HTML code (not correct), helps structure information so that it can be used and reused properly in the proper context. This is extremely important when you are trying to add style to the content, such as adding the desired size and weight to a header or modify positioning to an unordered list. I see a lot of HTML tags that are not used properly in the work we clean-up on a regular basis. There are very few applications, like MS Word that come close to using HTML markup properly. Cleaning up application generated markup is demoralizing as getting markup right in the first place is easier than having to clean up the mess made. Go read Steve's article and anything else you can put your hands on that he has written and you will be much better off than before, believe me.

Why is markup important? Many folks and applications try styling the information without considering the structure of the information. If you have much of a background in communication, journalism, information science, etc. you understand that information needs structure. There are headers that indicate to the user what the content and tone of the content that follows will contain. There are many elements on a page that need structure, like knowing where a paragraph begins and ends, where in the body of text an image should be tied, words that need to stand out (strong), a string of items in a list, or a structured ordered list with sub-elements. Not having thes information properly marked up would make understanding how to best treat that information very difficult. This may seem irrelevant to those that only deal with a Web browser, but if you want to read the informaiton on a PDA, print the information and use the best styling for reading, or need a screen reader to vocalize the words on the page and give the words that compise the information being communicated the same understanding you need structured information. It would be like trying to bake a cake with out sides on the pan, the cake needs structure to rise and be best consumed. People that guide you away from properly strucutring information, more often than not are not informed on the need and the benefits to structuring information.



September 25, 2002

Accessibility tool that does what it needs to and more

Last week (things on the house and moving front along with work have kept me a little more than busy) I was demonstrated a solid accessibility application. The folks from Deque walked us through their Ramp product. Not only does this application assess accessibility of HTML (as well as image motions in improper frequency ranges) and Java, but it also will walk you through the steps to correct what needs to be done to meet and exceed 508 compliance. This tool handles complex HTML tables very well and offers a lot of functionality and very capably. This tool blows away Usablenet's Lift ability to easily add headers and ids to very complex tables (which Lift can mangle or just not hanle well). The tool also will markup perfectly valid HTML, which is a great relief. This tool is not cheap, but it will save a great amount of time, do things right, and give those using wanting the information the ablity to get it. This gives those of us that spend our waking hours trying to get usable and accessible information into the peoples hands who want it, can use it, and have paid for it (that is what taxes do after all).


August 29, 2002

Polar Bear Arrives

A great day here, the O'Reilly's 2nd edition of Information Architecture arrived today. I have only perused it lightly, but will spend a little more time with it in the next few days. It looks like Lou and Peter really knocked themselves out. I have two other books that I am really enjoying and will write reviews of in the near future: the wonderful Constructing Accessible Web Sites and Usability: The Site Speaks for itself, which is great for learning how to think about making usable sites and not just following commandments from guru that do not apply to all situations.


July 14, 2002

Glasshaus developers books

A stop in to the local bookstore today has been strongly considering Constructing Accessible Web Sites and Usability: The Site Speaks for Itself both are Glasshaus imprints and seemingly very well written and well produced. The accessibility book covers a topic that is tough to get ones mind around initially and the book handles the topic wonderfully. I have been working with the accessibilty issue for a few years now and the book points out some areas that were of a help to me.

I balk a little at the hefty price of the books, which means I will be buying them on discount or sale. I know some of the folks that have contributed to the books, which helps me justify the costs, but not everybody is me. If the cost were a little lower, say a 30 U.S. dollar price point, it would be easier to buy a couple or more and hand them out to folks that really need them. The accessibility issue book is one that really needs a lower price point, but I know there are solid methods for pricing the books just under 50 U.S. dollars.



May 21, 2002

Accessibity for all

DIY accessibility is now at your fingertips.


April 26, 2002

Joe Clark runs real accesibility test on Flash MX

The accesibility guru, Joe Clark, writes the real Flash MX accesibility story. I know I have been waiting for somebody to actually test MX. Flash is taking the right steps, but it still is not fully there. When it comes to accesibility it is not a part of the way thing for those with disabilities, it either works or does not work.


April 10, 2002

Anitra writes a great article covering the breadth of Web accessibility. This feature is very much a tutorial and broad overview of the steps to take to make a site more accessibile.


April 5, 2002

The fine folks at Q42 have a color blindness check tool. This works to change your Web pages into a palette that a color blind person would perceive.


April 2, 2002

Accessibility benefits

The W3C provides an overview of the benefits of accessible web design. Building sites so they are accessible is not a task that much be done it is an asset.


March 12, 2002

One thing that I have had the benefit of viewing and discussing while at SXSWi is Flash. Folks from Macromedia have shown their soon to be released version of Flash. Flash MX (as it is named) has some very good new features, in its providing common Web development objects to help developers create scroll bars and the like very easily. The application seems to provide object or extensions to Flash that streamline the process to building something usable and consistent in Flash.

The best new feature of Flash is content can now be made accessible for those with sight disabilities. This is greatly helpful as Flash is largely a visual information development and presentation tool. The information is now usable by site readers that read information aloud stored in Flash. This has been a large hinderance for many folks who would like to adopt Flash into their development tool belt, but had restrictions that limited the use of Flash because it locked out a segment of the users who had visual disabilities.

There is one large element in Flash that is completely disappointing still. The information is not accessible for reuse. All Flash can provide is visual information presentation, which restricts a user's ability to copy and paste or to have the information machine readable. The information is locked in an unusable format for these purposes. What does this affect? If a hotel provides their phone number and address in their Flash presentation the user can not copy and paste the information out into their PIM (Outlook, Access, Palm desktop, etc.), to an e-mail, or text message that the user could read from their PDA or cell phone (given messaging capabilities). The user would also be restricted from grabbing the information to put together a matrix from which to make decisions or to supply to others to make their comparisons. The locking of information in Flash requires the user to retype the information provided, which introduces the ability for errors in the information that was carefully crafted.

Not only do human users have the inability to re-purpose the information, which is a great benefit to those providing the information, but machines are precluded from accessing the information. If the same hotel wants to be included in their city's chamber of commerce listing on the CCoC Web site the hotel information can not be easily extracted by the CCoC as it could be from HTML (using an id tag) or XML. The information is locked again in an unusable and un-reusable format. The creators of the content lose, and could possibly lose big by not having information that is easily reused. This becomes increasingly important with the growing use of Web Services that rely on machine readable or machine accessible information.

Why the hotel scenario? Macromedia used the hotel demonstration to highlight some of their great new features. As I watched the presentation I kept wondering if the information was still unusable for purposes other than reading or having the information read to the user. It was later confirmed the information was still un-reusable, but Macromedia is also aware of this strong down side to the information presentation and is working hard at fixing the issues.



January 27, 2002

I keep rereading Nathan's Rant from July 2001 concerning experience design, its state of being and his first book on the subject. Visual presentation and creating an experience for the user is quite helpful when presenting dry or complex information. Today visual presentation must be accompanied by versions of the same information for the visually impaired, well at least many of us live in that world. This adds new twists and challenges to create compelling information sources for an array of user types. For me, Nathan's works have always been an inspiration and a trigger for solid thinking and problem solving.


January 16, 2002

Shirley Kaiser discusses accessibility and Adobe Acrobat on her site.

There is one element in Adobe Acrobat that does not meet the Government's 508 compliance, if this is the yard stick being used for accessibility. The area of non-compliance is complex tables. PDF tags only have TABLE, TR, TH, and TD tags available, which do not accept scope. Scope is what helps the complex tables become compliant in HTML. The only acceptable method for providing information in complex tables is HTML, at this point. One work around is to make the complex tables attachments or addendum and remove them from the original document (should the complex tables be provided in PDF format) and only supply them in HTML.

To keep it clear a complex table is one that has more than one set of header rows and often one of the header rows would span a selection of other rows. An example would be a table showing fiscal quarters of the year and the months that fall within these quarters, which would then show rows of related numbers. The top two rows create a complex header as each quarter header spans three rows and defines the months directly below them. Voice readers will capture these relationships quite well with the use of "scope tags" in HTML (this would look like <th scope="col"> for header tags and <td scope="row" in the first cell of the table's rows). Unfortunately, PDF does not have a corresponding tag.

I also pointed out that the more current Web browsers permit using CSS with printer designations that allow for a better representation of the information. This would help those people build one application, whether it be a Website or a PDF that prints in the desired manner and is accessible.

This may help keep yourself and your readers in the clear if 508 is their standard upon, which their accessibility work is being performed. Unfortunately there are no compliance standards, only guidelines. But, for most federal government organizations it is meet all of the targets to be compliant. 508 is a pass/fail hurdle.

Further information on 508 may be found at www.usability.gov/accessibility/index.html.



January 13, 2002

Content management is back at the forefront of every aspect of my digital life again. Content management revolves around keeping information current, accurate, and reusable (there are many more elements, but these cut to the core of many issues). Maintaining Websites and providing information resources on the broader Internet have revolved around static Web pages or information stored in MS Word, PDF files, etc. Content management has been a painful task of keeping this information current and accurate across all these various input and output platforms. This brings us to content management systems (CMS).

As I pointed to earlier, there are good resources for getting and understanding CMS and how our roles change when we implement a CMS. Important to understanding is the separation of content (data and information), from the presentation (layout and style), and from the application (PDF, Web page, MS Word document, etc.). This requires an input mechanism, usually a form that captures the information and places it in is data/information store, which may be a database, XML document, or a combination of these. This also provides for a workflow process that involved proofing and editing the information along with versioning the information.

Key to the CMS is separation of content, which means there needs to be a way to be a method of keeping links aside from the input flow. Mark Baker provides a great article, What Does Your Content Management System Call This Guy about how to handle links. Links are an element that separates the CMS-lite tools (Blogger, Movable Type, etc.) from more robust CMS (other elements of difference are more expansive workflow, metadata capturing, and content type handling (images, PDF, etc. and their related metadata needs)). Links in many older systems, often used for newspaper and magazine publications (New York Times and San Francisco Chronicle) placed their links outside of the body of the article. The external linking provided an easy method of providing link management that helps ensure there are no broken links (if an external site changes the location (URL) it there really should only be one place that we have to modify that link, searching every page looking for links to replace). The method in the Baker article outlines how many current systems provide this same service, which is similar to Wiki Wiki's approach. The Baker outlined method also will benefit greatly from all of the Information Architecture work you have done to capture classifications of information and metadata types (IA is a needed and required part of nearly every development process).

What this gets us is content that we can easily output to a Web site in HTML/XHTML in a template that meets all accessibility requirements, ensures quality assurance has been performed, and provides a consistent presentation of information. The same information can be output in a more simple presentation template for handheld devices (AvantGo for example) or WML for WAP. The same information can be provided in an XML document, such as RSS, which provides others access to information more easily. The same information can be output to a template that is stored in PDF that is then sent to a printer to output in a newsletter or the PDF distributed for the users to print out on their own. The technologies for information presentation are ever changing and CMS allows us to easily keep up with these changes and output the information in the "latest and greatest", while still being able to provide information to those using older technologies.



January 2, 2002

An USA Today article on poor product design provides insight that is helpful not only to product development, but also application development. The insights (while not new to most of us, but most likely very new to USA Today readers) include not including the consumer early enough in the process, product design team not well balanced, and technology runs amok.

These very closely apply to Web/Internet/Application development's downfalls. Not including the user in the development phases and/or testing with users early and throughout the development process. Having a development team that does not have a balance of visual, technical, and production skills can be problematic. Lastly, projects that are technology for technology's sake, very rarely offer success.

Conversely, success comes from getting these things right, involving the user and understanding how users would interact and use what you are building. Having a balanced team so that visual, technical, and production issues can be addressed and solved appropriately. And lastly knowing when and how to best use what technologies will drive success.

This last element, understanding the technologies, will help you get over the hurdle of accessibility/508 compliance. It will also help you find the best tools to interact with the users of the site/application. Having DHTML elements to provide action on a site or to serve information, when the user audience does not fully have the capability of addressing or handling the presentation, will have detrimental effects. Know what your elements your users have turned on and off in their browsers and what versions they are using. It is important to know what threshold of user profile can be the cut-off for developing a site. If 10% of your users have JavaScript turned off should you still develop elements of your site that are JavaScript dependant without providing an alternate service? Know and set this percentage threshold, as it will help understand why you can and can not use certain technologies.



December 6, 2001


December 2, 2001

We are all trying to make our sites more accessible. Some of us do it because we have to and others of us do it because it is the right thing to do. No matter what our mission to many of us it is a new twist to our regular routines and we could use some help. Those of us that use Macromedia products now have help in Macromedia's Solutions Kit of Accessability.


November 14, 2001

Molly Holzschlag writes the 14 Ways to Talk Clients Out of Ruining their Sites, which is a wonderful article that will help back-up the guidence we have been giving clients. Going over the top is never the best practice. Some of the suggestions are: skipping the test phase, client-centered design, ignoring accessibility, poor site structure, everything above the fold, too many effects, and splash pages. These are the no nos, or do with great restraint. Please enjoy the article and share it with decision makers and those that think they get it.


November 6, 2001

IBM's Ease of Use Center offers articles, links, and resources that cover a wide gamut of offerings to help development for the user's benefit. The resource is full of wonderful offerings.

The feature story in October was The Purpose of the Machine is to Augment Us, which focusses on Franco Vitaliano of VXM Technologies in Boston, MA. "Maybe the intelligence of a system is not in the computer sitting inside a war room or on a desktop," he says, "but in what we call the communications cloud."


Previous Month

This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License.