Okay, maybe it’s a bit heavy-handed to liken that to designers who put their own personal preferences and styles above all else. In the first case, the majority of culprits know what they are doing is wrong but just don’t care. In the second case, the intentions aren’t nearly as bad.

But there’s a kernel of similarity. In both cases, the end result is potentially inconveniencing those with disabilities and putting your own desires and preferences first.

Of course designers have unique styles that they imbue into whatever they create. There is nothing wrong with that. The answer isn’t to create sterile, one-size-fits-all designs and layouts devoid of personality or vibrancy.

Just be sure when you’re creating your masterpiece to think about users as well. Like I mentioned last week in Taking Criticism in Web Design, be mindful that certain color contrasts will cause problems for users with color blindness or limited vision. Working within that guideline won’t stymie your creativity. It may technically be a “limitation” to work around, but really, text that is easily readable benefits everybody.

Creating a Flash sequence for images or advertisements can be a fully accessible option – just make sure you take the time to do it right, and follow guidelines such as Flash Techniques for WCAG 2.0 or Adobe’s own Adobe Flash Professional CS5 accessibility.

Similarly, video can really enhance a web experience when appropriate. It may seem like extra work and be a drag, but if you don’t provide captioning or transcripts, somebody with a hearing disability won’t be able to follow what’s been said or somebody with a visual disability won’t have a means of listening to a synopsis of what the video is about.

There is plenty of room within accessibility and web standards to be creative and achieve something with a distinct design brand. You may have to park a row or two back from the destination, but you still can get there and be happy with the end result.

Whether armed with lots of money and time or not, you have your voice — never be afraid to speak up when there are opportunities to make an experience more accessible. It can be on the micro level (“that font against that background is going to be really difficult for people with sight limitations to make out”). It can be on the macro level (“all those videos on the site? we really need to add captioning”).

You may lose. You may get a pat on the head and told to go play somewhere else. Keep trying!

Some approaches may work better than others. Stressing the moral and social obligations of creating accessible experiences is a valid, noble route — but businesses won’t always respond to that, even if their intentions are good. Spending money is spending money…and sometimes accessibility can be costly, such as the prospect of retrofitting a completed web site.

There are some great references like Developing a Web Accessibility Business Case for Your Organization to help.

I’ve been super jazzed about accessibility for the past couple years, but I know how easy it can be to feel you’re fighting a losing battle. There were times in my past job that I lost the energy when up against an overwhelming ambivalence towards accessibility (or even web standards in general). But then were were times like when I was able to enact color contrast improvements to an internal booking interface, to make it easier for someone with severe color blindness to better do her job.

Sometimes you have to pick your battles and alter your strategies, but don’t give up and let the fires of inaccessibility spread. Even small changes start to add up.

When you pour your creativity, heart and soul into something, it’s perfectly reasonable to have an intense pride of ownership. It’s natural — and a good thing — to care deeply about your work.

But when a designer is commissioned to create a web site or application, it’s imperative to separate the art from the artist. The designer isn’t making something for himself or herself – it’s for a client, and ultimately, for an end user. What the designer thinks is cool or cutting edge is -a- factor, but not the only factor.

Design is more than just pretty pictures — it has to be effective, clear, functional and accessible. Light gray text on dark gray backgrounds might be an “in thing” these days, but is the content even readable (for those with or without vision disabilities)? The glitzy masthead with in your face colors and constant motion may seem daring and impactful, but is it ultimately more of a distraction? Cool icons in place of traditional words for the main site navigation may seem a fresh approach…or does it leave users guessing where they are able to go?

It’s one of the toughest lessons, but a necessary step in the evolution of really good designers. Realize that when people are pointing out problems or concerns, they aren’t having a go at you personally. They’re looking out for brand needs, marketing needs, and user needs — hopefully all three in harmony.

On my very first design project, I remember pouring everything into the first of three comps. I spent a little less, but still a lot of effort on design two. Design three, I just threw together because they had asked for three, but I had forgotten that detail until the last minute.

Sure enough, they much preferred the third design. It stung a little. I put everything into the other two — what do you mean, you don’t want them?

Little by little, the sting of rejection or criticism lessened, until I finally reached a happy place where I could take any manner of critique, even scathing, and not get upset.

Again, it’s not really “your” design — it’s a vehicle for a business to raise awareness, convey information, sell a product….whatever it is they do. Moreover, it’s a gateway for customers to get what they need, and get it as quickly as possible. Those customers have varying degrees of technical acumen, and may even have disabilities ranging from blindness to motor skill limitations. These are the people using the website, not just the designer.

I’ve been thinking about a moment in my interviewing for the position, that illustrated a simple, yet important principle of user experience — asking questions first.

One of the people interviewing me explained a scenario in which we needed a console for a piece of equipment. The console required several elements, including:

He then handed me a piece of graph paper, a pencil and an eraser. Amidst my typical interview jitters, I grabbed the pencil and started drawing. I think I asked a couple questions about the equipment, but hastily came up with a simple sketch of the display.

He thought it was a good stab. Then he mentioned that the users would wear big gloves, and the display would need buttons large enough to account for that.

Now, an interview for many reasons is not “real life”. You have a tiny window to encapsulate your qualifications and history. Overall, I felt I portrayed myself very well. Obviously well enough, because I got the job!

But the minute he mentioned the gloves thing, I mentally started kicking myself. I would have known such a detail if I had asked some basic questions about the target users before picking up the pencil.

To successfully create any experience– be it an application, a web site, a console — you need to understand who will be using it and how.

Again, that was just a simple interview question.

In the real world, finding out specifics about users should be the starting point. Interviewing actual users reveals a lot. User testing along the way helps focus your sketches, wireframes, designs, etcetera.

In short, if you take the time to frame up in advance who your target users are, and test what you are creating along the way, you will better ensure that the end product is actually usable and accessible.

The kickoff topic was content strategy, and they knocked it out of the park by having two exceptional speakers, Gretchen Thomas (Content Strategy: It’s Not All Greek slides) and Margot Bloomstein.

Since then, I’ve been thinking about how content strategy correlates with accessibility. Effective content presentation most definitely helps create a more accessible experience.

Let me count (some of) the ways!

Content comes in different shapes and sizes. I’ve worked with people who still equate content with just the text on the page.

Content is many, many things of all shapes and sizes, including:

• Information copy
• Images
• Video
• Comments
• Keywords and metadata
• Search engine optimization tags and information

Content is quite the umbrella, and we’ve talked many times about how many of these examples are very important in an accessible experience.

Just some examples of content’s role in accessibility:
Copy needs to be clear, direct and easy to understand. Ramble too much or get cute with flowery words, analogies or corporate speak, and those with cognitive disabilities may struggle mightily to understand the information. Even those without disabilities may get lost or simply move on to somewhere else where they can more easily get what they need.

We’ve talked about images and video plenty of times. Choosing imagery with poor color contrast may prevent those with various types of color blindness from effectively seeing what it is you’re displaying. Poor or absent alt tags will block those using screen readers from understanding what the image they cannot see is representing, or may never know there’s an image there at all. And of course video without effective captions or transcripts is just moving pictures to those who cannot hear.

Like many aspects of accessibility, poor content strategy affects many within your audience, whether they are disabled or not. Effective messaging, imagery, placement of information, etcetera will enable users to get the information they need, research and/or buy the product they are interested in…whatever it is they are coming to your site to do.

A week from today, I am starting a new job — and it’s directly in User Experience.

When I wrote The Evolution of a Designer, I talked about how time, experience and passion naturally progressed my career towards user experience. I no longer saw myself as strictly a designer or coder, but instead someone striving to build, from concept level through completion and beyond, experiences that users, whether they are disabled or not, can easily understand and navigate through towards whatever their end destination.

What I didn’t realize on that day in March is that, mere months later, I’d get the opportunity to join a User Experience team being formed from the ground up.

I’ve been at the same organization (The Mark Travel Corporation) for over twelve years. I consider myself blessed to have had the opportunity to forge a rewarding career in the Web industry, from an entry-level HTML coder to seasoned web designer to manager of a large team of designers and producers.

Throughout that journey, I’ve learned a lot of things. One, I’ve realized that the most beautiful designs in the world are just pretty pictures if they don’t get the user exactly where they need to go. I’ve realized that whatever the experience — a web site, an application, etc. — content that is poorly-crafted or with no clear strategy will destroy it. And I’ve certainly realized how incredibly easy it is to overlook disabled users in creating these experiences.

Now, I’m delving into a role in which I can truly, day in and day out, focus on getting all of that right, and making a difference along the way. When a large company firmly establishes that user experience needs to be in front of everything they build, that’s a tremendous, exciting opportunity.

I’m beyond thrilled.

As I travel down this path, I’m sure I’ll have plenty to share along the way.

Using automated tools are a tremendous help in figuring out problematic code or color contrasts that just don’t feel like they are sufficient. However, your testing shouldn’t end there!

Similarly, don’t assume that a non-disabled person testing their site or application with assistive technologies is good enough. I’ve been asked by well-intentioned fellow non-disabled web designers, “Well, how can we get our hands on a screen reader to do testing?”

The best way to ensure your experience is as accessible as possible is to reach out to actual disabled users for testing.

This hit home for me when I watched Scott Mayer (Multiple Facets of Accessible Design – Scott Mayer presentation) demonstrate how blind users navigate both good and bad experiences via a screen reader.

For one, the speed at which the automated voice spoke was surprisingly rapid — and he even slowed it down for our benefit! Two, a sighted user trying their hand at a screen reader just isn’t the same as someone who is completely dependent on one and uses it day in and out.

Sure, a web surfer with hearing can plug their ears and watch a video, but afterwards, they can simply unplug them and go about their lives. A deaf user doesn’t have that luxury. You may think a pretend session gives you a glimpse into their world, but it doesn’t really.

Having access to disabled testers may be challenging depending on the resources in your area. There are some alternatives on the web, such as forums like the Accessify Forum, where you can post a site and ask for feedback.

The bottom line is that, whenever possible, you should use multiple avenues of testing for accessibility, the best being actual disabled users who could be part of your audience.

This weekend’s question:
What are your favorite, go-to accessibility blogs and web sites?

Feel free to submit one choice, or 100. Any and all comments are welcome.

If you’re new to accessibility and still figuring it all out, but are a devotee to user experience, sharing general user experience blogs is just dandy too.

I’ve maintained my Related Links page here and there, but would like to do a better job showcasing the many great accessibility resources out there. I’d love to hear the sites other people frequent.

Thanks in advance!

Example: “Let’s talk offline.”
Example: “We’ll have a go/no-go meeting.”

As easy a target as it is, I’m not about to go into the general absurdity of office lingo and corporate speak — I’ll leave that to great sites like Corporate Trash.

“Dovetailing” (there’s another one) with jargon catchphrases are excessive acronyms. I suppose it’s easier to speak with fewer words by making everything an acronym, but it’s painful to anybody on the outside trying to decipher the code.

Regardless to how easier it makes things to talk in such ways internally, it poses a user experience and accessibility problem if you litter your outward-facing web site with them.

Let’s start with acronyms. While some like FYI (for your information) are reasonably well-known, others may not be. Don’t assume that the outside world is on to all your shortcuts. Be sure to spell them out or use the <acronym> or <abbr> tag. Most screen reader devices read aloud the associated title tag, such as <acronym title=”For Your Information”>FYI</acronym>. In the browser, a dotted line appears under the item within the acronym or abbr tag, and mousing over will reveal the full description.

There seem to be different schools of thought as to if you need to use these tags on every single acronym, even if it’s used multiple times. On the one hand, only using the tag in the first instance may pose a problem if someone skips around the content and misses that initial explanation.

On the other hand, using the tag ten times for the same acronym seems a bit excessive too, especially if it’s a long one, like CAPTCHA.

Not sure where I stand on the issue, I tend to just use the acronym tag in all cases, even multiple times with the same acronym. Whatever you do, just make sure that when you need to use acronyms, there’s an explanation of what they stand for.

If the acronym is one your company made up for some sort of internal process, and basically nobody in the outside world would understand it without a frame of reference (like the initials for a department), just spell it out in your web site content. If they work for you or do business with you, they’ll learn the acronyms when it makes sense.

As for using corporate jargon and catchphrases in your content on an outward-facing web site? I say skip it. People, whether they are disabled or not, are coming to your site to either make purchases or learn more about you. Just give them concise, impactful, clear content.

Be direct.  Save the cute expressions, sports metaphors, or whatever else for your meetings…or be merciful, and stop them altogether.

One key point we made – user experience isn’t one step in the process, to be executed once and checked off. It’s pervasive.

Web accessibility goes hand in hand with user experience. After all, what is accessibility but building experiences that are usable for everybody?

That also means that web accessibility isn’t a checkbox on your to-do list. It isn’t a singular task that you “do” and move on. It’s constant.

It’s something you think about when:

• you are card-sorting the key elements of a web site.
• you build wireframes of the information you’re presenting.
• you consider color contrasts, typography and layout while designing the page.
• you enter every single line of CSS, HTML, JavaScript, Flash, etcetera
• you ask users — disabled and non-disabled — to test out your new web experience and share what works and what doesn’t.

User experience and accessibility aren’t individual tasks at one specific point in time. They are ways of thinking that carry through every aspect necessary to build a web site or page.

Don’t marginalize either by ignoring them or relegating them to one tiny line item in your project.