Archive for the ‘Browsers’ Category

Email Accessibility

Monday, July 16th, 2012

We all know that emails are notoriously difficult to build across the vast swath of email clients, and you might think that there’s nothing you could do about making them as accessible as possible.

But you’d be wrong.

Let’s take this example from the most profitable company in the world: Apple.

An email footer from Apple, demonstrating their lack of understanding in accessibility.

When design hinders accessibility

Straight away we can visually see a number of accessibility issues.

  1. Colour contrasting. You can almost see why Apple have designed their ‘small print’ this way. They don’t feel that it’s important to the message contained in the email, so they’ve made it as invisible as they can, but this is wrong. Not all visually impaired users are blind. Most of them won’t even use a screen reader such as Jaws to have a site read to them; this is the last possible option for most people trying to retain their independence. Unfortunately Apple have chosen grey on grey – a VERY difficult colour combination for anyone to read, let alone those who have trouble distinguishing multiple shades of one colour for fine details.
  2. Size. Now, we all know this is ‘small print’, but why does small print exist on the web? The old ideas of limited print space and “Let’s make this as small as we can so nobody reads it” are long since past. The web contains as much space as you want, and the public are more appreciative of legal and privacy information than ever before. This size will only impede those who want to read it, and unfortunately that again will affect your visually impaired readers.
  3. Links. Apple have made the classic mistake with their links, a mistake which is so old it’s actually quite shocking that they have done this. ‘Click here’. Why? What does it mean? You might be forgiven for thinking that the surrounding text might explain why you want to ‘Click Here’, but what about your users using a screen reader? Many feature a mode to simply read out links so that a user can quickly navigate your site. To a screen reader, using the image above, this would sound as follows: “www.apple.com/uk/studentoffer”, “Click here”, “Click here”, “Click here”, “Click here”, “Click here”, “All Rights Reserved”, “Privacy Policy”, “My Apple ID”, “Click here”.

You probably aren’t in charge of an email department quite as large as Apple’s, but if you avoid these obvious mistakes then you can be sure that yours will be better.

Internet Explorer 9

Thursday, June 24th, 2010

Every web developer knows that Internet Explorer (IE) 6 is a pain. It has a lot of bugs, and a lot of newer code just doesn’t work. The problem is, we can’t stop coding for it – IE6 still has over 10% of the browser market share. Now, it was neglected for five whole years. Then version 7 came along. IE7 fixed a few of IE6′s bugs, but from a developers point of view wasn’t anything special. A couple of years later IE8 was released – which much improved rendering all round.

Now, IE8 is a good rendering browser, it’s not too bad at all. It doesn’t however support any of the ‘new’ features of the web. Experimental things such as HTML5 and CSS3 simply don’t work. Is that such a bad thing? Well, yes. Because every other major browser (Chrome, Safari, Firefox) supports a good chunk of them and there’s a lot of things that we as developers want to use, but can’t.

Take my website for example – if you’re here in any version of IE you’ll see a very plain and very square design. Any other browser and you’ll likely see rounded corners, text shadow and box shadow – three small parts of CSS3 that really improve the visual appearance of a simple layout like this one.

Now, suddenly, Microsoft have realised they’re in a browser war once more – fall behind too much and people will walk away. Why is that troubling for Microsoft? Well, if you can convince people to use a new browser how much harder is it to convince them to use a new operating system the next time they buy? With increasing proportions of the smart-phone markets both Apple and Google are making people more aware of their products – and training them in their ability to use them. Google launches its own OS soon, how many PC users will be swayed to a computer with Google OS or for the richer of you, OSX?

Back on topic – IE9, slated for release in 2011. Another IE – great I think, as a developer. Another browser to support, bug fix and nannify.

But

I did something silly the other day. I downloaded the IE9 platform preview (version 3) and stood back in awe. Not only does it perform well in the Acid 3 test (83/100 compared to 20/100 for IE8) which although doesn’t beat Chrome’s and Safari’s 100/100 perfect score – is a vast improvement, but it also does something magical (in the words of Steve Jobs). Take a look at the screen shots below. On the left we have Chrome, on the right we have the IE9 preview.

IE9 Asteroid DemoIE9 Fish Demo

That’s right. Google Chrome was by far the fastest JavaScript running Browser for PC and on a par with Safari. Not anymore. The new IE9 sports a new feature – background compiling of JavaScript. This fancy feature punches Chrome in the mouth and sprints away fast. A staggering 22 times faster in the fish test and immeasurably (but at least 60 times) faster in the asteroid test leaves you blown away.

This is a feature I’m definitely looking forward to!

One thing I will note though, Chrome still loaded and rendered pages faster than this IE9 preview.

Safari 5

Tuesday, June 8th, 2010

Apple released Safari 5 today but unfortunately it wasn’t quite as successful as they’d hoped. For several people running Windows (myself included) the following error appears when trying to launch it:

The procedure entry point JSValueMakeFromJSONString could not be located in the dynamic link library JavaScriptCore.dll

The procedure entry point JSValueMakeFromJSONString could not be located in the dynamic link library JavaScriptCore.dll

Thanks for that, Apple. I guess the Windows release wasn’t tested very well. Hopefully they’ll release an update to fix this issue soon. And knowing Steve, someone will lose their job and then be shot and run-over in a series of unfortunate events.

Update

To solve this issue do the following:

  • Uninstall Safari
  • Uninstall Apple Application Support
  • Delete the folder C:\Program Files (x86)\Safari
  • Delete the folder C:\Program Files (x86)\Common Files\Apple\Apple Application Support
  • Reinstall Safari

You *must* delete those folders because the installer is ‘clever’ and won’t overwrite existing files. The Uninstaller on the other hand is rubbish and leaves most of the files on your disk (hence an uninstall and reinstall without deleting the folders won’t work).