1990 Americans with Disabilities Act & your website 

We've probably all heard the stories of brick-and-mortar businesses running foul of the Americans with Disabilities Act, and what it meant to them as businesses both financially and disruptively. Now it's coming to a website near you - maybe even yours!

The ADA - a quick history 

Along with it's companion, the 2008 Americans with Disabilities Amendment Act, the legislation was enacted to address equal access for all people regardless. However, due to the early adoption date, the original Act, and, to a some degree, the subsequent Amendment, did little to give guidelines on adoption in the World Wide Web (WWW).

The Act is comprised five Titles, with Title III (Public Accommodations) applying to website design. This title prohibits private places of public accommodation from discriminating against individuals with disabilities. Your website is considered a "private place" which offers "public accommodation". What this means is your website is privately owned and managed (private place), yet anyone who has a computer can get access to it (public accommodation).

The penalties for non-compliance with the provisions of the Act can be quite severe. Under Title III the maximum penalty for a first offence is

Yes, I confess, the title is a little melodramatic! However, when it comes to your online and IT security, a little paranoia is a good thing! The truth is, there are people out there just waiting to get you. There's an Alan Parson's Project song "The Voice" that sums it up well in one line... "He's gonna get you!"

(As an aside, Alan Parsons was the sound engineer on Pink Floyd's record breaking album "Dark Side of the Moon".)

Good security protocols are your first line of defense. Make strong passwords and don't leave them lying around. If you're really paranoid, change them regularly. Don't use the same password over multiple sites. 

But good passwords is only part of the solution. With the technology available to hackers today, even the best passwords and security protocols are vulnerable. The second string to your online safety is maintaining good backups. Your backups should be both local and remote for good safety.

Making solid local backups 

Your first step in a solid backup regime is saving locally. This doesn't mean just to your hard drive. Those are day to day use files. I think of backups are archives - most of the time, these

When we began CitrusKiwi 9 years ago, no merchant processor would touch us. No surprise really. Brand new company, owner brand new to the USA, no credit history. We had a lot going against us. So we went with PayPal. And, for 9 years, they have provided reasonably good service. Yes, they're expensive; yes, their reporting is a joke; yes, their search and filtering is an even bigger joke. But at least they gave us an account and they've improved from when we first signed up. But, finally, it was time to move on.

So, we signed up with Total Merchant Services. Setup was slow - well over a month to get the account in place and connected with Authorize.net. On top of that, we were never sent any documentation regarding our account - didn't know how to log in even! So, we processed a few transactions, and, despite the initial issues, business seemed to be working. Until last week....

I had a couple of clients say they were having issues setting up their payments. Then I began to get declined emails - Error code 38 - "The Global Payment System identification numbers are incorrect. Call Merchant Service Provider."