article archives
Just to make it clear: we are hiring. We have open positions for both Senior Designers, with 5-7 years experience, Junior to Mid-level designers, with 0-4 years, or genius college students with our paid summer internship. All positions are located here in Salt Lake City, with amazing benefits and possible relocation. We are also interested in exploring telecommuting options for remote HTML/CSS experts. Interested?
To apply online, please visit our jobs website at http://lds.org/emp/hr and see the listing for Interaction Designer. Or get right to it and shoot us an email with your resume and portfolio link.
posted by
jason
on Tuesday, Mar 25, 2008
I recently decided to step down as the Director of User Experience in the IT department of the Church. While I thoroughly enjoyed my work as a Director (best job of my life to date), I found myself longing to get more hands on in product design and development. I’ve now started as a Product Manager assigned to the Priesthood department where I’m working on new ideas for how the Church uses the Internet.
So, we have a new job opening. We need a new Director for our User Experience group. You can read the official job description for the full details, but let me give you my quick “unofficial” job description and a thought.
This job rocks! It has great management support. Joel Dehlin, our CIO, is our biggest fan and supporter. It’s a very challenging job. You have to be a great leader to a team of very talented and competent professionals. It’s a job that has a multitude of different kinds of end-users. Our end-users include Church employees, General Authorities, missionaries, Church leaders, Church members, and people who do not belong to our faith. Many of our solutions have to be global and work in a variety of languages and cultures. This job requires you to be a leader in the IT department. You need to work effectively with the CIO and the other Directors to accomplish department-level objectives and goals. Finally, and possibly the most challenging, you need to figure out what a user experience group should be and do at the Church. I’ve learned that you can’t just copy and paste what you’ve learned in previous jobs into the Church. Practices and approaches that have worked in other organizations, don’t always work or apply here. You have to discover the Lord’s Way to do your work. Working in that position the past two years has been a fun, wonderful, challenging and growing experience for me as I’m sure it will be for my replacement.
The person we need may come from a very unexpected place or they might come from our current team. I don’t know, but I am confident the Lord will help us place the right person in this position. Let me make a sincere request. If you are feeling a prompting regarding this position, either to suggest it to someone else or to consider it yourself, please act on that prompting. There are plenty of great places to work in the world doing meaningful, important work. If the Lord wants you where you are, we want you there, please stay there and have the impact He intends. The Lord needs good people doing good things everywhere. However, consider that the Church is also a great place to work where you can do meaningful, important work. If the Lord wants you here, we want you here. In this matter, like many others, you and others will be blessed if you seek to know the Lord’s will and then follow it. Again, if you’re feeling a prompting, I simply ask that you act on it. I suggest you also take a good hard look at the full job requirements as well. Thanks!
posted by
tadd
on Tuesday, Mar 25, 2008
In a recent article, Scott Berkun outlines some thoughts about innovation that have also been brought up often in recent team discussions. The bottom line of both the article and our discussions is that effective creativity (as opposed to self-expression) is not usually something 100% original, but an arrangement of existing parts or ideas in novel ways. What’s often required to solve a problem is not “original genius,” but curiosity, keen observation, and persistence.
Here are some key quotes from Scott’s excellent article :
- The biggest secret of innovation is that anyone can do it.
- The common trap about newness is the assumption that new means something the universe has never seen before. This turns out to be the third most ridiculous assumption in the history of mankind.
- As long as your idea, or your use of an existing idea, is new to the person you are creating it for, or applies an existing concept in a new way, you qualify as an innovator from their point of view, and that’s all that matters.
- The tool kit of every innovator typically includes three things: questions, experiments, and self-reliance.
- Progress depends on people thinking independently and following their curiosity as far as they can, including doing things others around them refuse to try.
posted by
ted
on Monday, Mar 17, 2008
So Cameron recently asked us to write about our experience working here in 200 words or less… I’m thinking SIX words might be more interesting. Six Word Memoirs, famous and obscure
posted by
bea
on Tuesday, Feb 12, 2008
Happy new year everyone. It is like Christmas time on the other side of the world! Hope you have a great beginning in the Year of Rat. Good fortune and good health to you and your family.
posted by
tim
on Saturday, Feb 09, 2008
My recent post on the accessibility of Adobe Flex prompted a response from Adam Lehman, an employee of Adobe. His blog post humorously titled “Is Adobe Flex Really Accessible? You bet your robot voice it is!” talks about a few aspects of Adobe Flex which he claims makes it more accessible than the alternatives. Unfortunately, the issues raised in my original post remain, for the most part, unaddressed.
Adam says on his blog:
I think where Aaron had a rough time is that most of the accessibility information on Adobe.com for Flex needs to be updated. It looks like all of the information is based off of Flex 1.5. It’s definitely something that needs to be addressed and our accessibility team is working on it. I’m also willing to bet that all the applications Aaron tested weren’t the best examples of applications designed to be accessible.
I would point out that the applications I tested were those on the above mentioned site that were specifically recommended by Adobe as examples of accessible apps. It is not clear from Adam’s post whether or not those applications are also in need of being updated. It is also not clear if the Jaws scripts (which, as you will recall, I could not get to install on either of two machines) are also slated for update, as they were not mentioned at all.
It is great that Adobe seems to be actively working towards making Adobe Flex accessible. However, “working on it”, and actually being accessible are two very different things.
Again, if I am wrong, I would love to know about it, and I will of course update this blog with any new information. However, at this point, without having actually experienced an accessible Adobe Flex application, I can not recommend it as an accessible solution, though I do hope that that will change.
Sorry for the lack of comments. I’ll keep bugging the admins and hopefully we’ll have them soon. In the meantime, please feel free to email me at cqannqonawq@ldqschuqrchq.org (removing all of the hopefully spam-bot foiling q’s.)
posted by
cannona
on Friday, Feb 08, 2008
Short answer: no, at least not as far as I can tell.
When I first heard that Adobe Flex was accessible, I was naturally quite excited. I had heard about how powerful the technology was for building rich web apps, and I couldn’t wait to try it. Unfortunately, I didn’t get around to taking a closer look until recently, when I was asked to conduct an evaluation by some folks at work.
Adobe has some sample Flex applications available which supposedly show off there accessibility. Unfortunately, they didn’t seem to work that well for me with Jaws 9.0. Almost none of the controls were readable.
Digging around a little more on the adobe site brought me to their page on using Adobe Flex with Jaws where I read:
In order to most effectively use the JAWS screen reader with an Adobe Flex application, users must download and install scripts. These scripts enable some
of the accessibility features of Flex and allow users to utilize the standard JAWS keyboard shortcut to enter Forms mode on a larger set of user interface
controls than would otherwise be possible. It is important to direct users with visual impairments to this page so that they will have the necessary scripts
to use JAWS effectively.
A little background may be in order at this point for those who are less familiar with Jaws for Windows. Jaws is a very powerful screen reading program, and part of its power comes from the ability to use custom scripts. Unfortunately, many users have never installed Jaws scripts, and may not even realize that it is an option.
So, undaunted, I downloaded the Jaws script files to try the demo again. Just one problem. The scripts would not install. I tried on two different computers with a few different versions of Jaws with no luck, and it appears I am not the only one to encounter this problem.
I find this situation to be quite disappointing, as Adobe has done a lot for accessibility in the past. However, as it stands now, the claim that Adobe Flex is accessible seems to be nothing more than marketing hype.
Hopefully, Adobe will put some more time into making Flex truly accessible. It would also be nice if they could get Freedom Scientific (the company which owns and maintains Jaws for Windows) to bundle the scripts with the program as has been done for many other applications. However, until that happens, I can not recommend Adobe Flex.
I would love to be proven wrong, so if you know of a way I can get this to work, please email me at cqannqonawq@ldqschuqrchq.org (removing all of the hopefully spam-bot foiling q’s.)
Update: This post sparked a response from an employee of Adobe. See this post for further details.
posted by
cannona
on Wednesday, Feb 06, 2008
We should have been more prepared for this but we now have a new mini-site live: Gordon B. Hinckley.
I designed this page Sunday night when I found out President Hinckley passed away. I shared it with a few product managers and after prototyping (with Aaron Barker and Emmy Southworth), editing, intellectual property, correlation, AV production, quality assurance, development oversight, networking, and publishing, we finally pulled it off.
This site shrank the experience we have on developing projects that take months into one week. Granted it is only a page but there was definitely a lot to learn from in a short time. It also shows the care we take when the Church publishes official information.
Thank you to all those who helped with this: Larry, Tom, Mindie, Brent, John, Aaron, Emmy, Scott, Brian, Wade, Greg, Jimmy, and more.
(My favorite thing on this page is the timeline. Special thanks to Aaron for making this happen.)
And if you’re wondering about the next president’s site, yes, we are preparing for that now.
posted by
gilbert
on Friday, Feb 01, 2008
The 2008 edition of the Bad Usability Calendar is out and available for download. Go get it.
posted by
randy
on Monday, Jan 28, 2008
Ten years ago this month I returned from serving a full-time mission in Mexico. Just two months following my return I found myself again in Mexico, returning to the headquarters of my mission for a special conference at which Gordon B. Hinckley, president of The Church of Jesus Christ of Latter-day Saints, would be speaking, along with Elder L. Tom Perry.
In a bizarre turn of events, the night before he was to speak I was asked to translate from Spanish to English for both President Hinckley and Elder Perry as they sat and listened to the other native Spanish leaders scheduled to speak the following day. You can imagine I didn’t sleep much that night, pondering at length how I was ever going to translate for a man revered by many, myself included, as a prophet of God.
The following morning I sat on the stand about a dozen chairs down from where President Hinckley would be seated. As he entered the building I had the privilege of greeting him. I’ll never forget the look on his face as we shook hands. It was one of being physical exhausted, likely due in part to the fact that he was traveling to several locations throughout Mexico within just a few days, and definitely due in substantial part to being 87 years old.
Incredibly, this was ten years ago. I’m certain he was rarely less tired during those latter ten years than on the day I saw him. And yet he never rested, figuratively (and probably literally). I remain in awe of all that he accomplished, dedicating more temples than any other church president, among other very notable efforts.
As an aside, I totally botched the translation. I considered myself fairly fluent in Spanish at the time, but because we were in an enclosed, round, completely concrete stadium, the reverberation from the stadium speakers and my location on the stand made it nearly impossible to hear what was being said. Since that day ten years ago, I’ve long wished I could greet him anew for the chance to apologize for my deficiencies that day. However, being the incredible, humble man he was, I’m certain it was of little consequence to him. “Carry on, good brother” or something along those lines presumably would have been his reply.
We’ll miss you, President Hinckley.
posted by
cameron
on Monday, Jan 28, 2008
Today I stumbled across Behavior-Driven Development-BDD for the first time. It’s an evolution of the thinking behind Test-Driven Development-TDD. The theory is intriguing. I like the focus on behaviors rather than tests. It appears to be more user experience and results oriented.
At its core are three principles which really ring true with me:
- Business and Technology should refer to the same system in the same way
- Any system should have an identified, verifiable value to the business
- Up-front analysis, design and planning all have a diminishing return
But the reason I bring this up is because of the “story” model they present for stating requirements:
Model
As a Role
I want Feature
So that Benefit
Example
As a savings account holder
I want to transfer money from my savings account to my checking account
So that I can get cash easily from an ATM
Most requirements or feature requests only have the “what” portion of that statement. How cool would it be to keep the “who” and the “why” right next to the “what” of each requirement?
I don’t know if the cost/benefit is there for this approach. Again, I just read some articles today. It could take a lot of time to gather all of a project’s requirements this way. But there would definitely be some value. Think of the inevitable prioritization discussions. Which feature is most important? I’m certain that keeping the who and why as a part of those discussions would lead to better decisions.
I’m a big Ruby on Rails fan. Because of this BDD reading, I finally took a look at RSpec, a BDD framework for Ruby. I’m equally intrigued here and intend to try this out on my current project.
They expand on the “story” model adding scenarios.
Story: transfer from savings to checking account
As a savings account holder
I want to transfer money from my savings account to my checking account
So that I can get cash easily from an ATM
Scenario: savings account has sufficient funds
Given my savings account balance is $100
And my checking account balance is $10
When I transfer $20 from savings to checking
Then my savings account balance should be $80
And my checking account balance should be $30
Scenario: savings account has insufficient funds
Given my savings account balance is $50
And my checking account balance is $10
When I transfer $60 from savings to checking
Then my savings account balance should be $50
And my checking account balance should be $10
RSpec then allows you to build this story and scenarios right into the actual code. The RSpec site has more on that.
Again, would it be valuable and useful to gather requirements like this prior to coding? We have to get at least some of this information before we can complete this feature. This just seems like an interesting way to document that information. For what its worth, it’s got me thinking new thoughts.
posted by
tadd
on Wednesday, Jan 23, 2008
Peruse our latest search logs, from “thin spaces” to “dumb cannons.”
Also previously posted: We’ve got what you’re looking for… or not.
posted by
ted
on Tuesday, Jan 22, 2008
Jared Spool writes in a recent article, “Designing an account registration and sign-in process that doesn’t frustrate users turns out to be very difficult to achieve. It looks easy at the outset, but a pile of subtleties can sneak up on your experience, making something that should be simple become stressful for the users.” He’s right; something that should be so easy is so easy to get wrong. Here’s a summary of Spool’s “8 Design Mistakes to Avoid” for account sign-in, along with a few of my own observations:
- Mistake #1: Having a Sign-in In The First Place. I couldn’t agree more. I see so many sites that require a sign-in without providing any apparent value to the site, and (worse) no value to the user—a recipe for a zero return rate.
- Mistake #2: Requiring Sign-in Too Soon and Mistake #3: Not Stating the Benefits to Registering. People need to be motivated first. You have to show them at least some of the goods before they will entrust you with their time and information.
- Mistake #4: Hiding the Sign-In Button and Mistake #6: Not Providing Sign-in Opportunities at Key Locations. (No comment.)
- Mistake #5: Not Making “Create New Account” or “Forgot Your Password” a Button or Link. Between my wife and me, we probably forget at least one ID or password per week. How ‘bout you?
- Mistake #7: Asking for Too Much Information When Registering. Usually the designer wants a clean, straightforward experience, but someone on the business or marketing side wants to turn a legitimate registration need into a 10-page segmentation survey! Designers—push back! Convince the business side that you should ask the bare minimum, or wave goodbye to most of your registrants.
- Mistake #8: Not Telling Users How You’ll Use Their Information.
For more discussion and examples, see the full article . Also see Aaron Cannon’s post on the impact captchas could have on disabled users as part of a sign-in process.
Also see Spool’s follow-up article with 8 more sign-in design mistakes.
posted by
ted
on Friday, Jan 04, 2008
Lake Superior State University publishes an awesome er, a really neat list of words they consider overused and abused. Some of them are dear to me, such as “sweet” when it means “awesome”.
posted by
kurt
on Tuesday, Jan 01, 2008
If you’ve been online longer than a day or two, you’ve undoubtedly been confronted with a CAPTCHA: one of those annoying collections of numbers and letters that you have to type into a form before you can continue. A lot of complaints have been made about their inaccessibility, but what are the alternatives? Even more importantly, when are captchas necessary, and when are they overkill?
Before trying to answer the above questions, I would like to define captcha. In short, the definition of a true captcha is a test which can be designed by a computer, but only answered by a human. In addition, each test should be unique with a high degree of probability. If you think about it, this is actually a very difficult problem, and its only going to get more difficult as computer speeds increase and the computer sciences advance. In fact, many captcha schemes currently in use have been broken, although the processing time often makes this impractical for attackers. But again, as time goes on, this will be less of an issue.
When deciding whether a captcha is warranted, at least three factors need to be considered:
- Is your site high traffic or a high value target?
- If an attacker gained access, could they cause a serious problem for you or your users?
- Are there other less intrusive ways to keep out attackers?
If the answer to 1 is no, you should consider the fact that it is probably easier for an attacker to just spam you manually rather than write a script to do so. If 2 is no, then why burden your users needlessly? If 3 is no, then again, think of your users and find an alternative.
If your site is small, you might try a weaker type of captcha which is accessible. For instance, you could create a list of simple questions and answers, and then present your users with a random one from the list. The problem with this is obvious; an attacker can just keep hitting your page until they’re reasonably certain that they’ve seen all of your questions, and then alter their spamming software accordingly. However, if your site is small enough, it probably won’t be worth the effort, and the attacker will either go some where else, or just answer the question manually (which is obviously something which no captcha can protect against, no matter how good).
But what if your site is a high value target, and you definitely need a captcha? There are still a few alternatives. You can setup a standard captcha for most users, and provide an email address or phone number (hopefully with TTY) that disabled users can use to verify that they are in fact a real person. This has the advantage of being accessible to practically everyone, while being hard for an attacker to automatically thwart. The drawbacks are that it would cost money and time to maintain, and, depending on how you had it setup, might require the user to wait for a call back or returned email. Unless the user can gain access in a timely manner, however, I would not consider that they are being given equal access. In addition, (if you provide a phone number) it may not be available to all users, such as those without the ability to make international or long distance calls.
The other option of which I am aware is to set up an audio captcha in addition to a standard visual one. The benefits are that, once it is setup, it would require almost no maintenance, and most disabled users wouldn’t have to wait for a return email. The disadvantages are that it is not accessible to deaf-blind users, and persons who can’t hear the file for what ever reason. It may also not be as secure as a traditional image captcha, although this undoubtedly depends greatly on the implementation.
So how do audio captchas work? Essentially, they work like visual captchas, except that instead of reading a series of numbers (and sometimes letters) you listen to them.
If you do a Google search for audio captcha, you will find a few pre-made solutions. Unfortunately, none that I have found are adequate. They provide a little security, but not much. One problem with all the ones I have seen is that they use synthesized speech to produce the captcha. However, synthesized speech is highly predictable, in addition to being a little hard to understand at times. This means that all an attacker has to do is find out how a computer says each letter, and then match those patterns in the captcha. The other closely related problem is that the program does not introduce any randomness into the captcha, aside from the selection of the characters. This is like having a visual captcha with no variation in how the letters are displayed; it would be very susceptible to analysis by optical character recognition software.
A very few audio captcha generators seek to introduce a little more variability into their captchas by randomizing the voice, pitch, and speed, but I contend that this is still not sufficient to increase the computing cost to the attacker by much. However, it probably does make the captcha more difficult to understand for the user.
So what is the solution? I believe the best and most secure option currently available is to create an audio captcha with human read characters. It must also have a lot of random noise added to it to make pattern recognition more difficult. A good audio captcha generator should do as many of the following as is feasible:
- string together the human read audio characters with randomly varying spaces between them (an exponential distribution works well for this).
- Randomly Vary slightly the speed, pitch, and/or length of each character (A Normal Distribution works well for this).
- If possible, each character should be read by the same person several times varying slightly the manner it is said, and the program should randomize which of the pronunciations it chooses to present to the user.
- Randomly generated noise should be added to the output.
- Random bits of speech from a person of the opposite gender of the reader should be mixed into the audio. (This helps because the human brain is good at distinguishing between different voices and tuning out those of no interest, though reversing the mixed-in speech can help minimize distraction.)
- Each PCM audio sample should be randomized slightly (A Normal Distribution with a low variance is good for this; too large a variance causes too much distortion and makes the speech unintelligible).
- Add random types of echo to the characters.
- Encode the audio into a proprietary format which is not easily converted.
As with visual captchas, care must be taken to insure that your security measures don’t effect the usability of the captcha. However, the above mentioned techniques should make it more difficult to automatically recognize your captcha text, though it is certainly not impossible. Nevertheless, Google, Microsoft, and other companies have been using many of the above techniques for several months; you can make your own conclusions.
I believe that captchas are currently one of the biggest barriers to accessibility. Unfortunately, there appear to be no perfect solutions. Even the last option is pretty secure, but its still probably not as good as the traditional image captcha. Further thought and research is definitely needed, so if you have any ideas, please don’t keep them to your self.
For further information and some history, see the Captcha article from Wikipedia.
posted by
cannona
on Friday, Dec 14, 2007
If a minivan is a sure sign of impending doom (per Jeremy Clarkson), then I must be on death’s door in my 12 passenger full-size van. But there are unexpected design benefits to a really big vehicle…
We graduated to the van upon the birth of our seventh child (yes, seventh), and our Ford Expedition no longer had enough seats. (We now lovingly refer to it as “the little car.”) So we went shopping for something with 9 seats.
Unfortunately, you can’t easily find a car with 9 seats. You can get 8, 12, or 15 without much effort, but finding a 9-seater is… Well, it’s like George Banks in Father of the Bride—frustrated that his hotdogs come in packs of 8 while the bun company only sells packs of 12, he is convinced that there’s a conspiracy to force him to buy 4 more buns he doesn’t need! Clearly, the auto industry, in a conspiracy against large families, has made the next step up from 8 seats a gargantuan leap of 50% to 12 seats. (And the first dealer we went to actually tried to talk us into a 15 seater because they didn’t have a 12 seater on the lot! I honestly don’t think it would have fit into my garage…)
So now I have 3 empty seats. But you know what? It’s one of those “bugs” that ends up being a design feature. Three seats means there is space between children. Always a good thing. Three empty seats means enough room to put your books or games next to you on a long road trip. Three empty seats means less feet getting stomped as the clan clambers into position. All in all, three empty seats has been a good thing.
The surprising thing—the full-size van gets very close to the same gas mileage as “the little car”. Go figure!
In closing, hail to the intrepid parents who refuse to be daunted by the car industry’s flagrant attempts to limit family size to 8 or less! Hail to empty seats! Hail to the people movers!
posted by
ted
on Monday, Dec 10, 2007
Visit adobe.com today and receive a shocking surprise of a look that resembles more of a junk pile of web trends, then the website of an industry leader in digital design products. The purpose behind the redesign was to put more emphasis on the content rather than the UI, and work better on wider screens. Unfortunately, I believe the UI is so disgracefully designed it hinders the readability and usefulness of the content and becomes the primary focus.
Flash video headers engulf most of my 15” screen and I can’t see the content. On a 7 Mbps connection, the site slows down so much that the drop down menus are useless, until the center flash video has completely loaded and played. When I hover over the dropdown menus, I interact — unintentionally — with the flash content beneath the dropdown menu. I have such a hard time getting past the navigation, I can barely get to the content and I find myself closing the window rather than surfing any farther.
Coming back later, with the navigation cached, I get to the community pages for designers. My eyes are continually drawn to the empty gray space on the right and top. I have a hard time focusing on the article summaries squished to the left in a 783 pixel wide box, further confined into three columns, each 150 pixels wide. How in the world does this work better for wider screens? I can’t take the claustrophobia any longer and close the window again.
For a site that should be showcasing the best use of its own products, it fails miserably. Content can only emerge when the user interface is so well designed, it works silently without intruding rough edges or poorly aligned spaces into the experience.
posted by
emmy
on Friday, Dec 07, 2007
A lot has been written on the opening of new browser windows and how you shouldn’t do it because it annoys and confuses just about everyone, especially the blind and visually impaired. However, I feel that, while it can be over used, it definitely has its place.
For instance, if I am filling out a long and complex form, and I click a help button for a field, I don’t want to be whisked off to another part of a page,
or to another page entirely with out an obvious way to get back. I don’t want to have to worry about my form session being preserved.
When a new browser window is opened, I can flip back and forth between the form and the help window as much as needed, and when I’m done, I just close it.
To be honest, I don’t find them to be nearly as annoying as some writers claim, and in fact, they can be quite convenient when used right. Of course,
this is just my opinion, and less experienced users, or users of screen magnification might have a different view. Still, it may bare looking into. My
personal feeling is that whether or not a user will have difficulty with spawned windows is probably less a question of disability and more a question
of experience with the web.
posted by
cannona
on Wednesday, Nov 28, 2007
A dear friend of mine lost her cat companion Marmaduke last Thanksgiving. It makes me more aware of all the subtle layers that come with this holiday—we can be appreciative in the midst of our grief, happy to have the memories even when they are raw, and sometimes a bit stressed about not being unequivocally cheerful on this day.
I have a personal Thanksgiving tradition of sitting down and listing all the things that I am grateful for. Typically at the top of my list are the many subtle kindnesses of friends and strangers alike. Especially and particularly I am deeply appreciative of those kindnesses that are extended to me when I am hurting, for whatever reason.
So I sent my friend a card, and thoroughly understand that she doesn’t want to celebrate. I would encourage you to reach out in whatever way you can to those that you know are conflicted at this time. Perhaps it is the first Thanksgiving after the death of a loved one. Perhaps it is the first time the next generation hosts and cooks. Perhaps it is the first time a child will not be at home for the holiday. Whatever the reason, if you see pain that you can comfort, try to do so! Even if it just means a smile and gentleness in the face of grumpy stress.
Perhaps NEXT year, you’ll be on someone’s gratitude list!
posted by
bea
on Tuesday, Nov 20, 2007
To many amateur bakers, making bread is a mysterious and often frightening process. For this reason, it is often avoided. Those who do decide to take the plunge usually are extremely careful not to vary the recipe one bit. In fact, most cookbooks with bread recipes warn strongly against experimentation. Some make the reader feel as though using one more egg than recommended would cause their kitchen to catch fire and their family to die a horribly painful death of bread poisoning. And so, the myth is perpetuated that bread making is a very complex process, the inner-workings of which can only be understood by those bakers with a doctorate in breadology. They forget that our ancestors (a few of whom had to be at least slightly dumber than they are) made bread on a regular basis with no problems.
Fortunately, there are a few enlightened authors who have written books explaining, in essence, how bread works. Many people are surprised to find out that it’s really quite simple. In fact, once they understand the basics, many home bakers find that they no longer need a recipe or even measuring utensils, and they go on to make excellent bread by guess work and intuition alone.
It has been my experience that many people who learn about accessibility are led down a similar path as would-be bread bakers. They are handed a recipe and told, “This is what you are to do, and if you don’t do this exactly, those crazy disability advocates will come after you with their blood-thirsty lawyers.” They are told things like, “mark headings up as such,” and “put skip-to-content links at the top of pages.” What all too often is not mentioned is why. The reader is not told, for example, that most screen readers have a hotkey which, when pressed, will present the user with a list of all of the headings on the page, and that this is often used to “skim”, just as a sighted user might look down the page to see what was typographically emphasized. No mention is made of the fact that persons who must use the keyboard as a result of limited mobility, find skip links a huge time saver, because they don’t have to tab through all those links that one usually finds in abundance at the top of most pages.
What is worse, sometimes advice is given that is just plain wrong. For instance, it is a common misconception that every image on a page should include an alt attribute with a verbose description. In actuality, only images with important information should be provided with descriptions, and those should be as brief as possible. For example, if there was an image which said “50% off this week on all orders over $50”, then that should clearly be provided with alternative text. However, if there was a picture of a man using a particular product, I’m really not interested in hearing “picture of a man looking pleased as punch to be using the new ultra-lite USB hair drier,” or worse, “picture of a man.” I really don’t care about what image the designers chose to use as eye-candy. I can’t see them, and descriptions of meaningless images just waste my time and delay my getting to the information I’m really interested in.
So, what’s a baker to do? Unfortunately, the efficient use of a screen reader takes time to learn, so it is not all that practical to simply install a demo version and try out your site. Your best bet is to learn the accessibility recipe, but then go on to learn why each step is necessary and important. However, in the end, one must ask the question, could a person with no sense of taste learn to make good bread? I believe they could. The real question is, could they do it consistently? Also, how will they know when they’ve botched it. The only real way to know would be to ask someone with a sense of taste, or, in other words, ask a disabled user to test it. As the person suffering from ageusia receives additional feedback on his or her bread, their skills will increase, and they will get it right more of the time.
So, in short, learn all you can about the why of accessibility, and then go do your best. Most of the time, it will probably be good enough, and almost certainly better than if you just blindly follow a recipe.
A great book, which gives a lot of good detail on the why and how of accessibility is Web Accessibility: Web Standards and Regulatory Compliance by Andrew Kirkpatrick, et al.
posted by
cannona
on Friday, Nov 09, 2007