In 1990, with the passing of the Americans with Disabilities Act, and again in 1998 with the passing of the Section 508 amendments to the Rehabilitation Act of 1973, Americans with disabilities won victories toward the better use of technology for all. Like curb-cuts outside office buildings or wheelchair-accessible bathrooms, the purpose of these acts was to enact laws which would (hopefully) guarantee many disabled members of society a more balanced and comfortable way to accomplish day-to-day activities that the majority of Americans take for granted.

Section 508 and the later WCAG–supplementary guidelines on accessibility from the governing group of the Internet, the World Wide Web Consortium (W3C)–are both instrumental in ensuring access to emerging technologies. With the importance of mobile, connective technology such as Web applications and company intranets, more and more Americans depended on technology to run their businesses and their lives. All of which mandated a certain level of Web accessibility to access information and perform tasks virtually such as email.

Most of the Web sites are currently (relatively) easy for Americans without disabilities to navigate. Visual clues, clean layouts, roll-over navigation, and streaming video are all commonplace technologies used to navigate the Web. Many of these, however, pose problems to Americans with disabilities: blind users cannot see where the navigation is on a page, deaf users cannot hear the content presented in a streaming video, users with mobility impairments cannot click on a news feed story before it scrolls away. These examples highlight the need to make the Web as accessible as possible now, while the technology is still fairly young. This is even more important as the Web becomes more and more a platform for social networking, open forums, and an online marketplace.

Last year, the corporate giant Target, was sued by the California Federation of the Blind (later the National Federation for the Blind) for discrimination. Target’s e-commerce section of their site contained discounts on products not available in brick and mortar stores. Though most sighted users could find the deals and had little to no problem, blind users could not get their deals due to poor code and perhaps a lack of understanding on the part of Target’s Web team (which happens to be run at least in part on Amazon.com technology).

Blind users use text-to-speech programs like JAWS or FireVox to navigate sites but must deal with the markup and code in a non-visual sense. Context clues such as “on the sidebar” or “at the bottom of the page” don’t mean much if the code is all spat out at once without visual clues filled in. The case ended last month with Target acknowledging that their site was not accessible enough, paying a $6 million settlement, and agreeing to restructure their entire Web platform. Target was commended for their changes and sites like Amazon.com, eBay, and Wal-Mart are working furiously to bring their sites up to par.

This settlement marks the first time that accessibility has really come into play in the private marketplace. Laws like the ADA and Section 508 are mandatory for public institutions such as schools, government bureaucracy and state program sites. However, they had been difficult to mandate for individuals. Many e-commerce and social media sites are currently hard for many Americans with disabilities to enjoy. The Web is one of the last frontiers of deregulated space and is still very young. By making accessibility a priority, developers, businesses, and governments set the groundwork for future expansion on the good examples. It makes good business sense to reach as many end users as possible to sell more products. It makes good governmental sense to reach as many of your constituents as possible. Plus it’s just a good, altruistic thing to do.

Even Google, one of the largest search engines on the planet, is “blind”– Google views content on a page in very much the same way a blind human user with a screen reader takes in information. It stands to reason then, that because everyone wants to make Google love them (and thus increase in the search rankings), accessibility is the way to go.

The late Dr. John Slatin, founding director of the Accessibility Institute at the University of Texas at Austin and a long-time contributor to the cause of accessibility, truly believed that by creating and shaping the Web to be as accessible as possible, usability would naturally follow suit. When a site is usable, information is easily conveyed to a user. This is something the creators of the Internet were always trying to accomplish better, faster, and easier.

By thinking about emerging technology in a way that will be easier–more accessible and more usable–for those who may have the most difficulty, all users will naturally benefit and the Web can unfold into a much better place for all.

SEO is concerned with metrics, robots, and page rank. The SEO expert is constantly trying to see what makes the search engine algorithms tick with tips and tricks to get your page seen, get traffic moved to the site, and make sure it stays that way. SEO isn’t easy and requires a fanatical instinct to keep track of what does and doesn’t work (as no one is really privy to how the search engines truly work) with one finger on the pulse of the news and one eye on how “black-hat” they can be. In old western films, the bad guys wore black hats, the good guys: white. Many practices in SEO can be what’s known as “gray hat” which is not quite “white hat” (read:good and above board), but makes you go, “hmmmm… I dunno”. “Black hat” SEO can get you banned from Google’s listing (the abyss from which there is no return) but “gray hat” stuff can get you up in the rankings faster than strict “White hat” stuff at times. There are also to types of SEO: Organic and Inorganic.

Organic SEO is little things you can do, in building a project, to grow the SEO. Clean, W3C-compliant code; clean, well written copy full of good information and keywords that users are searching for; frequent blog updates; links to the site as a good resource; and frequent visitors to the site are all good examples of organic SEO. Inorganic SEO involves paying for advertisements in the search engines: Google Adwords, for example, are examples of inorganic SEO, whereby paying Google, you appear higher. Those who have huge budgets and good resources can become very high in the rankings very quickly this way.

Usability, as it relates to Web development, is the intuitive, human interaction with the system. How quickly can users perform tasks? How willing are they to perform a function? How do users react to information given? Given a question or task, how does the user find the answer or perform the task? All these things are involved in the development of a usable GUI (graphic user-interface) that the client will use. A huge component of this is the KISS principal (also known as Ockham’s Razor) in which the superfluous is stripped away and the simplest interface is best.

For the most part, these two things live in harmony in a project. In fact, many good SEO tricks are great for usability! Copy, for instance, when well written, is great for search engines to find keywords and presentation of choice information on whatever topic’s being written about. Obviously, well-written copy is a wonderful way for users to find, quickly and easily, instructions, information, or the answer to their problems. Linking through sites is also a great way to increase SEO, yet it’s just as good for usability, delivering a clear link to repositories of useful information right then and there.

When these disciplines clash, however, things get nasty. Not to take sides, but it’s often Usability that suffers when the titans meet. SEO is quickly backed up with hard numbers, site metrics, and analytical data sets. Usability relies on trust of the developer – how they know how to build sites the right way with the right information in the correct structure. A technique to increase SEO is to have URLs (in your address bar) that have lots of keywords. for instance, if you really care about being #1 for palm beach real estate, your “management team page” might be buried under search engine friendly named folders: “http://www.yoursiteurl.com/palm-beach-homes/palm-beach-real-estate/palm-beach-community/your-palm-beach-realator-home-team.html”. This is chock full of awesome terms in your link. But what if I am a user who’s at an internet cafe? I’m cruising for real estate with my friends, and I want to share this link. Barring using TinyURL, I’m stuck with this bulky URL that’s friendly to Google, but it’s no friend to me.

This is true when copy gets out of hand, as well. If Google and other search engines can only index what they can “see”, most of what is indexed is copy. It would make sense then, to increase the amount of copy on a site so there’s more for the search engines to index. Adding more copy, however, quickly overwhelms the site visitor. We live in the age of the instant gratifications – knowledge is quickly at our fingertips and we can, and do expect to be given what information we need quickly. If users have to sift through huge amounts of copy on every page, or perhaps worse, deal with multiple pages with only a little copy and have to click through three or four pages to find information that could have been regulated to one page, then the site fails its human visitors.

It’s important to have a good balance between SEO and Usability. You want Google et al. to find you, but you also want to keep your site visitors coming back for more. Google might bring you traffic and you want Google to like you, but a good site will get humans coming back for more and bringing their friends to see your site. As big and powerful as she is, Google doesn’t have any friends she’ll bring to you.

In an actual advertising agency, this is the work flow (for a Web project anyway): Account service finds new clients and makes sure they wanna come in. They present clients with a bid based on scope of work provided by the designers and developers. Then, once the client has signed the contract with the scope of work, the developers and designers help put together an information architecture – a flowchart of sorts that outlines the information and navigation – and then that’s approved by the client before a design is even thought out. Then, when the client approves the I.A., the creative team of the designers go to work. They present (usually) 3 comps to the client, an idea of what the final site will look like. The client will go back and forth with the creative team and pick one. Once the client gives approval, the developer team gets to work, cutting, slicing, and coding up the site (while this is all going on, the copywriter is busy writing copy for all the pages based on the I.A. that the client approved and the creative director’s instruction). Once the site is coded, the copy is approved by the client and the copy is then put into the site. Once the finished site is all loaded, the developer ports the site over and there’s a final site hand-off.

In this group: The account service comes to the development team with IA already done (this is really really messed up because the account service team, though experts in sales, are not developers. They don’t understand user interface and user experience like we do). They then give the team a promised deadline (they don’t even ask how long such a project would take, just “We promised the client six weeks” which after all the bullshitting back and forth with the client gives me about 2 weeks to code the whole damned thing) this is often due to the client turning over the keys to the castle to my company which effectively makes the company it’s own client and presents deadlines internally based on previous projects. I can’t argue because the account service (read:sales) are owners of the company. It’s like I’m working in the twilight zone advertising agency. Everything is done ass-backwards. The account service people were telling the creative team which photos to put on a page! This is, to me, wrong on so many levels – the creative director is above EVERYONE in an agency, they take direction from no-one and give direction to everyone. I was amazed at how little control and how backwards everything is done.

For my first three days, I was sweating bullets. I felt like someone had put a stone in the pit of my stomach and I couldn’t get rid of it! The last two days gave me a gleam of hope – I was called in two separate times to two different bosses office to explain to them agency work flow. They wanted to step up to the plate with the big advertising shops, but weren’t sure their process was going to float or sink them. I got to freely speak my mind and really let them know places where I thought they needed work. I made an information architecture that took a three-tiered navigation and 30 pages, and worked it down to just 8, pretty simple pages.

There’s hope yet for me here. I’m gonna try to stick it out for six months and see if I can take it. Wish me luck

ME: I do Web Development
HIM: huh?
ME: I build Web sites – all shapes and sizes
HIM: Oh, cool! My brother’s in a band and they want someone to do their MySpace page!
ME: Cool, I’ve done a few for bands. They’re not as easy as it seems.
HIM: So how much for a Website?
ME: How much is a car?
HIM: Uh, that depends, what kinda car?
ME: Exactly. If you wanna think of sites as a good, rather than a service, think in terms of investments like cars. How fast do you need to go? Where will you be driving? How long does it need to last? A Porsche doesn’t do too well off-road, you know?
HIM: Cool. So about how much for a MySpace?
ME: Well, MySpace sucks. You have to use a lot of hacks to get the code to do what you want and on top of that, you’ve got little room to work with. Remember, you’re paying for my time…
HIM: So, like $250 or thereabouts?
ME: Add another zero to that, mate – then we’ll talk, sad but true – shit’s expensive
HIM: *unintelligible gurgling noise*

And so it goes. This is really common with a lot of professionals (that is, I’m sure it’s happened to you in your job) and it stems from either preconceived notions about what a person does or it stems from having no idea what the job is. Asking me to do something like fix your email is like handing a mechanic at a bar an oil filter and asking him if he could fix your car. The mechanic’s off work. He fixes engines, yes the oil filter’s part of it, but are you gonna fork out for the time and labor?

Disclaimer: everything I’m about to say could be completely off base. I have not worked with the team yet and in fact not even met a fellow code monkey there. So even I have to take this all with a grain of salt.

I’m worried about job creep. I understand SEO, but I’m not sure that making a position dependent upon the SEO for the client I’m working on seems a bit much. I never claimed to be an expert on the subject and probably never will. I am not privy to the innermost workings of the great goddess Google and her spider minions. I do know what I know, and I hope that will serve me well.

I got the official and very pleasant letter of employment yesterday saying: programming world class coded websites (new & updates), e-mail marketing campaigns, landing pages, managing on page search engine optimization, identifying gaps in content, analysis using google analytics to improve rankings and conversions. Now, the Web program and the e-mail campaigns I can handle – it’s what I do. I can handle landing pages, it’s just an upkeep thing. My main concern is the “on page” optimization – this is a lot more than I’d normally do, I feel you really need specialized search engine gurus for this kind of thing – with every page optimized for a strict level of searchability. Research shows that as the algorithms incorporate more fuzzy logic sets, the more search engine optimization will depend on well-written content and clear, well done short paragraphs.

The part that also worries me (going in, at least) is the identifying gaps in content bit. The new group’s got an in-house copywriter but I get the impression I will need to be keeping up with the page SEO to the point that I’ll be telling the copywriter what new paragraphs we need on said page and which we need to remove. It’s always been my impression, that job belongs to the copywriter.

I’ll post more as it gets closer to my start date. I’m taking a week off between jobs, so that should afford me some time to relax a bit.

For whatever reason (I blame the relative youth of the tubes) there is little data out there on the people who are actually designing, coding, implementing, consulting, and basically sacrificing to make the Web a nice place. Thank goodness A List Apart, one of the finest online resources for people like me, decided back in 2007 to start a survey (the results of which can be seen here – 2007 survey results from a list apart) to document all this undocumented stuff.

I participated back in 2007 and I’m really glad I did. It really showed me how in and out of tune I was with the rest of my peers. I know I’m certainly WAY under-paid, I’m doing the job of roughly three people (thank the Web gods it’s not a design position on top of that), and it’s perfectly fine that I don’t have a degree in what I do because neither do about 46% of the industry!

I encourage all my peers out there to participate and help us figure out how to make this brilliant career work for all of us! If you’re a designer, a code monkey, a back-end sysadmin, or just a student making sites in your spare time, fill out the 45 question form (took me about 5 minutes) and we can see some cool results in the coming months! I love the fact that there are so many job titles from goofy pc-correct/ new-agey/ Web 2.0 “Information Implementation Engineers” to old school “Web-masters” to the bizarre “Lead Programmer” (that’s my title and it really makes no sense and insults those who actually do the hardcore coding tasks), there’s little standardization in the industry. I prefer “Web Developer” because I think it’s short and to the point.

When we jump into this kind of work we generally start from a flowchart. This chart outlines how the site gets structured and where the copy should go. We’re moving from a roughly sixty page (fifty of those are dynamic and populated by portfolio samples) to a 10 page site. This gets a little harrowing

On top of all this, we are restructuring to allow for a Flash-based version of the site which will showcase Flash and dynamic content skills. We want to move away from the tired old portal with “here’s the bitching new Flash site with the latest and greatest and here’s the tired old piece of shit XHTML site that we update when we feel like it – you pick” and move towards “here’s our Flash site, where stuff moves and is fun and here’s our XHTML site loaded with SEO, great code, and really beautiful look which completes the package – explore both!”

Information Architecture is one of the most important steps in development. I don’t care how beautiful, how complex your site is, if it’s hard for users to navigate and find what they need quickly and easily, they will leave and not come back. This is a time-honored, more-labor-intensive-than-you-think, activity which happens between clients, developers and creatives that requires in-depth thought and knowledge before a design ever gets considered.

Creating IA for a Web site is like a well-planned waltz – every step needs to be in the right place, in time with the music or it doesn’t work. It’s the Information Architects who really make the base of the site, that give it the structure around which the copy flows and the design is stretched. If you’re not working with solid IA, you’re not working.

If the client wants something, let’s call it “stupid thing X”, the account service wants to make the client happy, so says, “of course we can do that”. Now “stupid thing X”, or STX, is only stupid because it’s stupid – not the client. The client is smart, I mean, they came to you to do their Web didn’t they? The problem is that they asked for STX without knowing that it was either not in their budget, not the right tech to get them to their goal, or something that is completely superfluous to the action of the site. We’ve all run into STX and we’ve all told the client why we though about it and think that there’s another way to get them where they need to go.

Because Account Service has already promised the client that development was going to get them their new, shiny, “stupid thing X”, we as developers look the bad guy when the Account Service rep complains that we have to go tell the client “stupid thing X” won’t work for her/him. This can be solved through consistent, clear inter-office communique.

The party line, so says the entity known as Wikipedia: “The Marxist-Leninist concept of democratic centralism involves strict adherence to, and defense of, a communist party’s positions in public, while in inner-party debate sessions, the line can be questioned, criticized, and changed if necessary.” This is what we mean by party-line. We can talk it all over inside the agency, but the client sees one face, one unified front set on helping them achieve their goals because we are a well-oiled, sleek uber-machine of creative awesomeness.

Account Service must be trained well, they need to understand how time and organizational structure in done internally. They should always be open to ask questions of creatives, and be trained in the subtle art of weaning a client to a line of “Well, that’s interesting! Let me run it by the creatives and see if there might be a more economical, or direct method to help you achieve our goals. It might be that that’ll work just fine!” This is helpful because it makes the client feel like a rather smart chap, shows her that her money is being well spent and the entire team is thinking of her and her goals for the site, and that the Account Service is taking care of everything (‘our’ goals makes the client part of the team, you see).

Account Service, go talk to your creatives – see what they have to say. Read their blogs, find out what they think. They like to rant a lot, so you’re bound to pick something up. Get out there and keep the client happy, but toe the party line on what you agree to!

I tried to unroll a version of WordPress ages ago to no avail. I’ve learned a lot about database (Db) mechanics since then. I was really amazed at how quick it was to unroll this stuff. I had a lot of help from the Apress book: Building Online Communities with Drupal, phpBB, and WordPress by Douglass, Little, and Smith.

I’m a big fan of the book, it really explains how to get these community building programs up and running in very short time. I think these are great tools for Web developers who don’t like to use Ruby on Rails or ColdFusion to build the big applications needed for those clients wanting “Web 2.0″ technologies (assuming they need them, of course) without actually having the time for their massive upkeep.

On the subject of “Web 2.0″ shit, I am sick, as a developer, of uninformed clients asking for technologies they know nothing about. “I want you to make the Facebook of *blank* for me,” or, “I’m hoping this will be a MySpace, but for *blank*.”

Do you know that massive social networking sites such as FaceSpace and Mybook require teams of programmers and full time development staff to be effective? Your $200, $2,000, or $20,000 isn’t gonna get you too far when you have me break it all down for you. This stuff takes years of production and R&D. Besides, what makes you think *blank* even goes on line and wants to talk to more *blank* and share their picks and whatnot?

Believe me, I’ve heard social networking sites proposed for the following groups: Ranchers, Architects, Telecomm CEOs, Golfers, Real Estate Agents, and Wedding Planners. Every one of these is a bad idea. If you want a social networking site for *blank* you better be sure as hell that *blank* would even log on to your site. Research saves you money and me time.

Sorry about that, but it’s been bugging me lately. I’m fully aware that blogs are a great way to increase SEO and interest in a site, however, few of us have the wherewithal or available free time to post everyday or every week. It’s as I tell my clients, you must be diligent. Train to write, research and read. If you feel you’re up to the challenge, go for it, but man… I’ve seen more blogs fail than succeed. Lets see if I can swallow my own medicine, shall we?

Putting on the Ritz