Recently, attention returned to concern about
the role of accessibility in the U.S. government transparency movement. While gov website operators might well deserve a good grade for effort, most sites have obvious failings that experts and users repeatedly point out. In this post, I show some of my personal problems and suggest corrective actions. Visually impaired people can hear a realistic experience with a capable, free screen reader to better understand how websites respond to an intermediate level visually impaired, task oriented user. Sighted readers and accessibility specialists are urged to consider alternatives to reduce causes for stumbling around.
Hear me Stumble Recording
Download MP3 recording (38 minutes, 17 MB) trying tasks at whitehouse, disability, data, and recovery .gov. Starting with some typical tasks, I get into each website far enough to identify and stumble over some problem, then later come back and analyze the cause in both the website and my own practice, written up below. These little experiments are certainly not definitive because someone more experienced with the website might take a very different route or the proper screen reader action just might not occur to me at the moment. So, listen if you’re patient and interested to these 4 segments and follow along in your browser to perhaps grok what I’m missing in the recording.
For the record, I was using Windows XP, Firefox 3.5, NVDA RC 09, and PlexTalk Pocket as recorder.
The BLUF — great availability of useful information but fall short of
excellence in usability
BLUF=bottom line Up front
The Obama administration has unleashed an enormous flow of energy and
information for citizens to use for their personal lives, political causes, and
general improvement of society. I really appreciate the nuggets of
explanations dispensed in RSs feeds and twitter streams, amplified by social
media communicators interested in technology and organizations with a special
thread of accessibility. I offer these stumbles as the only feedback I can
provide, hoping my analyses eventually reach into the administration and d.c.
government apparatus. My stumbles are not flat on my face, fallen and cannot
get up, but rather trips over seed bumps, unnecessary traversals around hazy
obstacles, and stops to reconsider the surroundings to decide my next safe
steps. Just like real physical life, these stumbles absorb way too much energy,
often discouraging me from completing a task. Informed by my own experience
building interfaces, databases, and websites plus software engineering methods
of testing, use cases, complexity measures, and design exploration, I truly
believe each stumble indicates a serious design flaw. The good news is that
while my stumbles may partially track with vision loss and continuing learning the rules of accessibility and assistive technology,
of the ‘curb cut’ principle suggest corrections will smooth the
way for other, abled users who are also troubled with usability difficulties
they cannot understand without the accessibility and usability framework.
Summary of my stumbles on typical .gov tasks
Task: Find a recent blog post received by RSS
: stumble: Post was not in recent list, didn’t know how to use archives, didn’t trust search
Follow up: Navigated around November archive, eventually found links to previous articles
Suggestions: Factor archives, Use landmark pattern for list sections
Comments: Now has a text only version but similar navigation problems
Grade: C. Text Only site isn’t much of an accessibility improvement, please work on organizing this mass of information. RSS feeds more useful than website. Also, use your clout to force social media services to become accessible, too.
Task: Discover information about public transportation in local community
: stumble: Found ” Transportation” main topic but could not reach specific information
Follow up: Read “how to use” and eventually figured out info organized by state
Suggestions: “See sidebar” isn’t sufficient so data needs better organization
Comments: Site content is effectively transmitted by RSS and Twitter. good survey can help improve site
Grade B: Good process, but not yet organized properly or communicating website use
Task: Trial download of a data set using search form
: stumble: Very hard to understand search form components distracting headings and social media,
Follow up: Eventually got search results, but unsatisfactorily
Suggestions: Start over
Comments: Only for wonks on salary, not advised for citizens
Grade: Incomplete, do over, or adapt expensive recovery.gov interface and data management
Task: Find recovery funding projects in Arizona
: stumble: Locating form for query and then results
Follow up: Found the form under non descriptive heading, easily set query, drilled down past top of page to text version of results table
Suggestions: Make the “Track the money” foremost part of page, submerging feature awards and website data
Comments: $10M+ project needs more usability and accessibility input
Individual Website Analyses
whitehouse.gov — this National Landmark needs ARIA landmarks
I don’t visit this site often but I do read occasional blog and press briefings in my Levelstar Icon RSS client. One article caught my attention, about encouraging Middle Eastern girls, and seemed worth a tweet to my followers with similar interests. But I needed a good web address so set off to navigate myself through the site.
I was surprised to find a link to an “accessible” version, not sure what that mean. It turns out to be “text only” which doesn’t mean much to me if the navigation is the same as a screen reader is abstracting from text decorations anyway. Hence, I was faced with a branching decision with no criteria for which branch to take, somewhat confusing.
As usual to refresh or familiarize myself, I take a “heading tour” to learn the main sections of the site and target the section for my task. Soon, I find the “blog” section but the article list is mainly on President Obama’s Asian trip, not reaching back as far as the article I wanted was a few days old. I declared a “Stumble” by not knowing how to use the archives, needing to train myself and wander a bit more off recording.
Following up later, I found myself confused about the organization of past material. I took the November link but ended up in more heaps of videos, blog posts, briefings, etc. Eventually, I got to blog article lists and found the web construct that linked to past articles, looks like “previous 1 2…. next”.
To analyze a bit further, let’s separate accessibility from usability. This task seemed to take a little more effort than needed, because I stumbled around learning the archive information architecture and list results patterns. Nothing in the screen reader or the HTML seemed problematic. Headings helped, not hindered. Perhaps this is a stubble that can only be prevented by more practice, but it’s possible we have a jumble of website content that could be factored to make paths easier to follow.
Traversing a list divided into sections is a common pattern, often intermixed with links to articles and media. The list of blog posts was indeed an HTML list that could be followed by items, but got strange at the end the next-previous section is labeled with something like LSQUO, which makes no sense in a screen reader. This construct is also easy to miss using links rather than items. Could this pattern be
standardized (see below)?
Duh, why didn’t I just use the website Search? Unfortunately, I have a deeply ingrained mistrust of site searches, mainly from getting gobs of results that don’t help. Like, how would I know the rules for making a good search query? Is it “Napolitano Abu Dhabi” with quotes where, and default being conjunction? And these words are not the easiest names to type correctly, so is there spelling correction? Well, it turned out “Napolitano” (2nd try) turned up the article about 4 results down but with the same search result bar construct. OK, I’m convinced to bring Search back into my website explorer toolkit. and will work to overcome bad experiences from past generations of website searches.
Overall, I grade myself as a B with my improving mental map of the site, but definitely prefer using the content by RSS feed, i.e. getting blog and briefings spoken from mobile device. Sorry, but whitehouse.gov still gets a C in my ratings, mostly from the need to have a stellar, near perfect website to model for not only .gov but also community, state gov, professional associations, universities, etc. Only 10 months into the website, the amount of content, useful individually, may grow into a giant heap of links that drive citizens away. Regarding accessibility, I simply don’t see the rationale for the text only site and recommend looking ahead to using better overall structure with landmarks (see below).
Disability.gov is very useful but maybe convoluted?
Disability.gov is a regular in both my RSS feed list and Twitter tweetroll. The site has a general framework of disability needs and resources. New resources and classes of resources per day of the week are routinely broadcast. I have a warm feeling when I see these, like somebody is actually looking out for me in that great USG bureaucracy.
For some local surveys, I anticipate needing data and examples of regional transportation systems supported by public and disabled communities. Ok, I know I’m delusional that a conservative wealthy retirement oriented city will even consider such a thing as services for economic, environmental, or social reasons. But, hey, there’s a sliver of hope. Indeed, this is a typical way the USG can foster citizen innovation through better and more transparent data.
The website navigation sidebar is straightforward with tasks and information topics. In the recorded session, I picked Transportation and then got stuck. I had a page headed Transportation, nice, with topic overview, but no real information, just a use the sidebar. Ok, but how? why? After, in my follow up, I figured out that information was organized by state, which makes sense, but wasn’t explicit when I stumbled.
Choosing Arizona from the state list, I found a number of resources, none of which lead directly to the Tri-city Prescott area. Tucson was well represented, but I knew that, been there, seen the buses, and vision services. Overall, I found this site satisfactory, with an encouraging amount of information, but I’m still somewhat befuddled about the relationship between topics and sidebar and details.
At one point, I was presented with a survey. Sure, I’ll give you feedback, thanks for asking. As usual, I didn’t know how long the survey would take, like how many questions. First accessibility glitch was that required fields were designated by some symbol not read by a screen reader in normal mode, probably an asterisk *. That meant I had to switch into listening more punctuation in the screen reader or just answer all questions. Silly, why not say REQUIRED, rather than use a little symbol. Next, I couldn’t figure out the form of answers, which turned out to be radio buttons labeled 1 to 10 and NA. Ok, that’s a lot of tabbing but not overwhelming, as I whizzed through the questions. Then, came a switch to some combo boxes for answers. Annoying, suggesting the survey wasn’t vetted by many people using screen readers, but not really too bad. Do other gov sites have comparable surveys? They should.
Overall, I rate myself and disability.gov with a B. I need more practice, and the website developers need more feedback. But really, I know they’re trying, and somebody will likely read this blog. Good job, and I truly appreciate the resources, framework, and the RSS and tweets.
data.gov for wonks, not citizens
Oh, my, this site is annoying. The headings are sparse and inappropriate. There’s a sideline off to social media sites that aren’t accessible and in the way. A link says “Click here” which indicates deprecated thinking and cluelessness about hyperlinking.
The main purpose of this site is a distribution point for datasets collected from various government agencies distributed in XML, CSV, and other formats usable in spreadsheets and statistical analyzers. Great, but the form is a mess.
I tried to query fo ex ampler datasets, any topic, from National Science Foundation. The agency list is long, painfully, with check boxes. That’s about 40 tab or next line key strokes to get to NSF. Then I found the Submit button. Not so good, which I learned by reading “No search results” at the bottom of the page! Most important effect of a search is to know if it succeeded, produces results, geez! What did I do wrong? Do I need to select format and make an explicit query? Ok, tried that with term “computers”, All Categories, All Agencies. Got 2 results this time, both on illegal exports, spooky and uninteresting.
Argh, I gave up. I’m sure this site will eventually be useful for policy wonks willing to train and practice, but I, an ordinary citizen with a research background, didn’t feel like I could get much out of here. Sadly, the form’s long list of check box agency names uncoordinated and un searchable was painful. But worse was not getting direct feedback about number of or absence of search results combined with uncertainty about the query actually executed. I had little confidence in either the site or myself as searcher, but, luckily, I don’t forecast any personal need for data.gov. Sayonara.
So, I rate this sucker a big Incomplete with good intents but pretty clueless about accessibility and usability. Hey, download NVDA and try this out yourselves, data.gov designers. There are lots of ways to design forms and search results. Back to the design stage, please Now that recovery.gov is launched at great expense, perhaps some of the interface and data management functionality can be used to refresh data.gov, but who am I to reorganize .gov :-)..
Recovery.gov Usable but Cluttered
Well, it wasn’t fun but I can use this website. The big problem is clutter. I go here to “Track the Money” and cannot find the form to do so. Uh, oh. Plenty of stuff about the site itself, some of the big featured expenditures, but where’s the form. Oh, there it is, under heading “Data, Data, and More Data”, cute but not obvious. This time, I decided to drill down on National Science Foundation awards in Arizona. Unlike data.gov, the agency selection was single choice reached by the convention of first letter, N, and a few key strokes to make the selection. All right, but now what?
So, the search seems successful yielding another page with lots of accessibility and agency clutter at the top I had to listen through. Back and forth a bit, I found the link to text presentation of the data, accompanied with a blue map.
Looking for text data, same boring junk at the top then up comes the table of rows of actual data. It’s hard to navigate by row and column, some columns have no real information, like I know I asked for ” National Science Foundation”, read in every row. But painfully working row by row I can find an interesting item like $80K created .17 job –wow! Indeed, the award details is there and readable and interesting.
The big problem with this iteration of Recovery.gov is that the website is in the way. I definitely do not plan to post anything on MySpace social media service but I have to listen to or bypass this silly text and thought too often to learn what’s on a page. It just seems goofy to send a Recovery dataset to a “friend” on a social network, although it could be relevant in a mature Twitter thread. If the gov goal is to incorporate social media into its normal workflow, then there are big questions of stability, accessibility, and much more of these profit-seeking, ad-driven enterprises.
I give myself an A for conquering this site, although I’m still stumbling around tables of data. Recovery.gov gets a B for assembling this information in readable form, although not in dataset forms as relative to missions like data.gov. In other words, it looks like a lot of page scraping to identify trends. My suggestion is simple: get the “Track the money” form front and center and press the website, social media, and features into the background. Overall, better than I expected, although the recording and further use leave a feeling of irritation, like having to sweep off a desk of junk to find a phone to get the information needed. Like, just give me control and let me track the money myself. I’ll be back.
General Suggestions for Improvement
It’s Time to Bring Landmarks to .gov
I’m getting spoiled by really accessible websites like AccessibleTwitter and BookShare that use the ARIA landmark feature to structure pages and search results. For example, the .gov sites could be separated into (1) agency logo and babble, (2) navigation, (3) main content, (4) reference to other gov sites and external services. Bookshare shows how to organize search results integrated with the next-previous results page bar.
Indeed, this brings up the issue of consistency among .gov websites, which could be kind of nice and helpful. Not meaning to squelch individuality of agencies or artistic license or experimentation with diversity, but a citizen wanting a simple answer to an information question isn’t as impressed with decorations as with ease of use, especially on return visits. And visually impaired users especially appreciate predictability, a trait shared with most human beings, when confronted with pure tasks. With all due respect,most visits to gov websites are not for tours through marble halls or to expand social networks to include anonymous civil servants, but rather to get a piece of info as fast and readable as possible.
Should gov sites link to inaccessible social web services? NO!
All gov 2.0 buzz seems to involve social media, as in Twitter, Facebook, and sometimes Flickr and MySpace. But the accessibility of most of these sites is way below that of the .gov sites. Can a website assert it is accessible if it links to patently inaccessible services? I think not. The good news is the movement toward alternatives like Accessible Twitter and accessible versions of YouTube. These should be mentioned in accessibility statements. Or, better yet, no links to unless these billion-dollar enterprises raise their accessibility levels to the acceptable status demonstrate by these alternatives. Perhaps there should be a warning label on sites known to be poorly designed or not for the newbie. The US government uses its clout for diversity, why not also for accessibility?
After spending several hours on these websites, knowing a lot myself about social media, the focus on social stuff seems rather silly considering the weight of the data involved. Am I, is anybody, going to post a link on MySpace or Facebook of a significant query and insight? I doubt it. Rather, these sites give an impression of trying to be oh, so cool, gotta get our stuff out to the fan pages on Facebook. Gimme a break. From a screen reader user, this is just pure clutter in the way of your main mission, stuff I have to listen to redundantly and irrelatively. Try it yourself and determine what value is really added from social media service references so prominently in users’ faces/ears. Even scarier, if gov agencies are adopting these inaccessible, unstable services for actual business, the traditional discrimination policies must come into play, as well as questions about judgement. For example, Twitter is a great news medium, but its rules can, and do, change at any moment.
How about a gov BEST and WORST practices competition?
I personally don’t get any value, but rather irritation, from the skip links and text size adjustments. First, the skip links are often just plain wrong, often enough to mistrust and not worth a false link and recovery. Text size adjustments are relevant to those who need large fonts not supplied by browser adjustments. Pages with good headings and landmarks don’t require skip links. Pages that aren’t crowded with text don’t need on-page text size adjustments.. To me, these are accessibility decorations that amount to screen reader noise. It’s rather jarring to find major inconsistencies among gov websites, e.g. text-only at whitehouse.gov but not others, different HTML form patterns, and greatly varying degrees of conventional accessibility.
As complained about in the whitehouse.gov blog lists, there’s a common pattern that might be nicely standardized. A list of, say 100, items is divided into sections with a bar of links: previous, 1, 2, … next. If you’re drilling down through several pages of results, getting easily into this bar is important. A landmark is a natural way of identifying results.
Does every search form have to be constructed differently? Above tasks required me to figure out the subdivisions of forms (usually not labeled) and then the form elements. There’s probably a special class of gov site users who can whack their way through a form down to a data set in no time. But the ordinary citizen has to struggle through understanding then mastering the form, finding results, and interpreting answers, which can take hours. How about an award for government service by providing a superior form that other sites can emulate? And give those web designers a bonus or promotion, too!
Sum up, getting better? Yes or No?
Overall, although using these sites made me rather grumpy, the trend is toward better accessibility, more usability, and genuine transformation of how citizens use USG data. My wishes are:
- Work on clutter and removal and helping users find direct paths to important data, i.e. work on the most significant use cases.
- Designers and maintainers of these website should listen to recorded TTS of their pages and contents for several hours to really appreciate the clutter effect of featuritis, accessibility decorations, and social media silliness.
- Cut down on the social media crap and rethink what really matters. Yes, these services are useful but really, do they deserve so much prominence? Will they still be here 3 years from now?
It just seems incongruous to think of sharing recovery datasets with ad-hungry “friend” oriented services. Most serious is the hypocrisy of declaring accessibility on a gov website when these lucrative services so actively ignore accessibility and force visually impaired service users to volunteer developed accessible alternatives.
- The most important use of this data is not visible to most citizens. Namely, RSS feeds are the best way for someone to monitor these sites, scanning article titles, downloaded to a mobile device, with rare visits to actual websites. How can the USG foster better offline use of important government developments?
- Is there a “curb cut” effect from feedback like this? I hope so, that fixing stumbles precipitated by accessibility bumps and usability gaps will help everybody.
- Finally, a cautionary warning I just heard from my CNN news feed. Many recovery awards seem to have fallen into fallacious congressional districts, making the whole record keeping of job data questionable. Apparently citizens reporting award data don’t know what congressional district they belong to (I’m AZ ONE, I think, maybe). Now, data base developers and instructors know, there’s a TRIGGER for that. Zip codes usually map to unique districts but that might not be a requirement or implemented yet. Just saying.
- Obama whitehouse.gov almost on target, January 2009
- Hear me Stumble around whitehouse, data, and recovery gov, May 31 2009 with recording
- Universally Designed from Knowbility.net comments on recovery.gov
- Series of gov web website evaluations from Jim Thatcher
- Let’s all use our headings, My Accessibility Check
Accessible Twitter, alternative interface,
Easy Youtube, alternative interface,
Accessible Youtube interface,
mobile, easier Twitter interface,
simpler, mobile Facebook interface
- Marco’s firefox accessibility blog tips on ARIA landmarks
- AYWC post “Are missing, muddled use cases the culprit for accessibility?”