tech support 8

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Thursday, 14 June 2012

Another Anti-IE Gimmick

Posted on 08:30 by Unknown



Internet Explorer has been the whipping boy of the internet for some time now, particularly Internet Explorer 6. Now it seems Internet Explorer 7 may be the new cool target.




Australian electronics seller Kogan has decided to impose a "tax" on users of Internet Explorer 7. The justification from Kogan's blog post:





One of the things stopping [us from keeping prices low] is our web team having to spend a lot of time making our new website look normal on IE7. This is an extremely old browser, so from today, anyone buying from the site who uses IE7 will be lumped with a 6.8% surcharge - that's 0.1% for each month IE7 has been on the market





Kogan proudly displays a screen shot of the message IE7 users will see (click for a full-size image):




Screen shot of Kolgan tax message in IE7.




The text from the message:





It appears you or your system administrator has been in a coma for over 5 years and you are still using IE7. To help make the Internet a better place, you will be charged a 6.8% tax on your purchase from Kogan.com




This is necessary due to the amount of time our web team has to waste to ensure our site appears correctly in IE7.




Avoid the tax, use a better browser: [images for Chrome, Firefox, Safari, Opera]




Why This Is a Gimmick




The claims made in the blog post and the statement are just not true. I'm not calling them outright lies, but they are at least misrepresentation.



Not a "Tax"




This is not a tax. It is a surcharge, as Kogan says in its blog post. However, in the message to end users it refers to it as a tax four times and even uses a "stamp" to imply it's a tax notice. A savvy user should get it, but this tongue-in-cheek attempt to look official is in contrast to the statement on the blog. This can be a problem from an accessibility perspective when you consider users with cognitive disabilities.



Nothing Informing Users of Tax Hike




The blog post claims the "tax" is assessed based on how many months IE7 has been around. This month it is 6.8%, next month it will 6.9%, in August it will be 7%, and so on. There is nothing to indicate that to users.



No Tax for IE6




There is no "tax" for Internet Explorer version 6. If there was a tax for IE6 using the same calculation as for IE7, then the rate would be 13% (as of this month). A simple argument is that the site is not intended to work well in IE6, and if that's the case then there is no reason to not also display a message to IE6 users saying as much.



Doesn't Work in IE7 Anyway




While visiting the site in IE7 to get the screen shot above, not only did it render poorly (if at all), it hung my virtual machine twice. Kogan claims it is spending effort to make the site look normal on IE7, although it not only doesn't look the same, it doesn't function the same. The 24 separate JavaScript files and 1MB of files (made up of 97 requests from 19 domains) probably doesn't help the page render. I would argue that Kogan is misrepresenting its efforts.



It Doesn't Need to Look the Same in IE7




Again, Kogan claims it spends time making the site look normal on IE7, but not only doesn't define normal, it doesn't acknowledge that it doesn't need to look the same. Kogan's decision to spend time and effort trying to replicate the exact same experience for IE7 is what is costing users, not users' inability to upgrade their browsers.



No Indication of IE7 User Base




Kogan does not state in its blog post how many users of IE7 come to the site. It may very well be only 3 users a year. If that's true, it makes this even more of a gimmick and likely would not have had the splash Kogan wanted. If far more, then Kogan can justify its position by providing an outline of how it will track the success of its campaign — short of proving that IE7 users who cannot upgrade won't be back.



Doesn't Suggest IE8 or IE9




Kogan doesn't tell users in its message to upgrade to a more recent version of Internet Explorer, it tells users to use a better browser and lists Chrome, Firefox, Safari and Opera. It doesn't even list Internet Explorer 8 or 9.



It's Bullying




I don't much care about rudeness. When I see language like this that talks down to me I typically decide the copywriter/management is/are an idiot and that's it. Not all users will feel that way, particularly users who cannot upgrade their browser. Having witnessed what happens when either non-savvy users or users who are trapped on a platform are told they aren't good enough, I am confident this message will only offend those on IE7. It's just a technical form of bullying. That it draws hoots of support from those who only care about the new shiny only bolsters my point.



How Kogan is Being Dishonest




Kogan claims on its blog that "we all have a responsibility to make the Internet a better place. By taking these measures, we are doing our bit." Given that the site doesn't even support IE7 nor does it help users with useful language, I am suspect. If Kogan's claim is true, then Kogan should donate the "tax" money (it clearly isn't using) to support organizations who cannot upgrade for financial reasons, perhaps starting with not-for-profits in its hometown.



Yes, There Are Users Who Cannot Upgrade




There are users who are trapped in work environments that will not allow an upgrade. There are users who are not technically savvy and don't know how. There are users who cannot afford a new computer with a newer OS. There are users who can only access the web from libraries or internet cafes. There are users who stay on a browser version because it works with their add-ons (such as accessibility software).




Kogan is a private business (I assume based on the site) and may choose which customers to support. It doesn't need to even try to support IE7 (I argue it doesn't anyway). However, its gimmick will be taken up by web developers who only see arguments to support their own bad behaviors and who may very well work for organizations where supporting all users (poor, disabled, technically clueless, trapped) is necessary.




If a web developer cannot come up with valid reasons on his or her own for why someone may not be able to upgrade, then I argue that person is a terrible web developer.




If you still don't understand, I refer you to some of my past posts on this topic, each of which contains some nugget on browser use assumptions:






  • Exclusion Is a Feature Now, May 10, 2012


  • Don't Blame Opera, Blame Devs, April 27, 2012


  • The Return of “Best Viewed in…” March 4, 2012


  • Don't Expect Microsoft's Auto-Update to Kill IE6, December 23, 2011


  • Test in Lynx and Print, It's Your Job, December 12, 2011


  • Everything Will Be the New IE6, December 8, 2011


  • Selection Bias When Reviewing Browser Stats, March 13, 2011


  • Microsoft Promoting the Death of IE6, March 4, 2011


  • Beyond Hash-Bangs: Reliance on JavaScript Is a Bad Idea, February 9, 2011


  • Google's Web Book May Not Help Those Who Need It Most, November 29, 2010


  • How Many Users Support JavaScript? November 5, 2010


  • IE Below 50%, But Not Universally, October 12, 2010


  • IE9 Beta Coming, But Microsoft Just Wants You to Dump IE6, September 8, 2010


  • RIP IE6 (Not Really, But Here's to Hoping), March 4, 2010


  • Microsoft Doesn't Like Chrome Frame, September 25, 2009


Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in accessibility, browser, internet, rant, standards, UX | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Social Media Day 2011 in Buffalo #smdayBUF
    Last night marked the second Mashable-sponsored Social Media Day here in Buffalo. With 154 RSVPs for the event, the venue, The Eights Bist...
  • Web Accessibility Sorta-Infographic
    WebAIM is a non-profit organization within the Center for Persons with Disabilities at Utah State University. It has a reputation (perhaps o...
  • Now the Mobile Web Is Dead?
    It was barely two years ago that I scoffed when Wired declared the web dead ( Enough about the Death of the Web ). Fast forward to today and...
  • Browser Performance Chart
    Jacob Gube has posted a handy chart over at Six Revisions titled " Performance Comparison of Major Web Browsers ." He tests the c...
  • Facebook, HTML5, and Mis-Reporting
    My Twitter stream and the headlines of sites across the web yesterday lit up with Facebook's CEO blaming its stock price (failure to mee...
  • The Science of Trust in Social Media
    I am one of those people who always needs to see proof of some assertion, evidence to back up a claim. While I can accept anecdotal evidence...
  • ICANN Moves .org Away from VeriSign
    This Saturday, the .org top-level domain (TLD) will no longer be privately managed. With VeriSign's contract with ICANN for management ...
  • Speaking at Mom 2.0 in Houston, TX
    I will be in Houston this week to speak at the Mom 2.0 Summit (Feb. 18-20, 2010, Houston, TX). To make it a little easier to describe, here...
  • Algonquin Studios Gets Local Press
    I'm taking an opportunity to brag a little about my company, Algonquin Studios , being featured today in the Business section of our lo...
  • App Store Meta Tags
    Why yes, Dominos, I'd love to tap again to get your real home page to order a pizza when I could have done it right here, below your ove...

Categories

  • accessibility
  • Adobe
  • analytics
  • Apple
  • apps
  • ARIA
  • Bing
  • Blink
  • Brightkite
  • browser
  • Buzz
  • Chrome
  • clients
  • css
  • design
  • Facebook
  • Firefox
  • Flash
  • fonts
  • food
  • Foursquare
  • g11n
  • geolocation
  • globalization
  • Google
  • Gowalla
  • html
  • i18n
  • ICANN
  • infographic
  • Instagram
  • internationalization
  • internet
  • Internet Explorer
  • JavaScript
  • JAWS
  • Klout
  • L10n
  • law
  • localization
  • Lynx
  • Mapquest
  • Microsoft
  • mobile
  • Netscape
  • ning
  • Opera
  • patents
  • picplz
  • Plus
  • print
  • privacy
  • project management
  • QR
  • rant
  • RSS
  • Safari
  • SCVNGR
  • search
  • SEM
  • SEO
  • social media
  • Sony
  • speaking
  • standards
  • SVG
  • touch
  • translation
  • Twitter
  • typefaces
  • usability
  • UX
  • Verizon
  • video
  • W3C
  • WAI
  • WCAG
  • WebKit
  • whatwg
  • Wired
  • WOFF
  • xhtml
  • Yahoo
  • YouTube

Blog Archive

  • ►  2013 (39)
    • ►  December (1)
    • ►  November (7)
    • ►  September (4)
    • ►  July (3)
    • ►  June (2)
    • ►  May (5)
    • ►  April (3)
    • ►  March (6)
    • ►  February (2)
    • ►  January (6)
  • ▼  2012 (63)
    • ►  December (2)
    • ►  November (4)
    • ►  October (5)
    • ►  September (5)
    • ►  August (4)
    • ►  July (6)
    • ▼  June (7)
      • Twitter Cards Are Now Valid HTML
      • Accessibility Bookmarklets and Tools
      • Another Anti-IE Gimmick
      • ICANN Announces Requested gTLDs
      • Image alt Exception Change Re-Re-Requested
      • Copying Content Styled with Text-Transform
      • Picplz Shutting Down, as Free Services Often Do
    • ►  May (7)
    • ►  April (8)
    • ►  March (5)
    • ►  February (3)
    • ►  January (7)
  • ►  2011 (67)
    • ►  December (5)
    • ►  November (7)
    • ►  October (5)
    • ►  September (4)
    • ►  August (8)
    • ►  July (3)
    • ►  June (8)
    • ►  May (3)
    • ►  April (1)
    • ►  March (6)
    • ►  February (6)
    • ►  January (11)
  • ►  2010 (100)
    • ►  December (8)
    • ►  November (7)
    • ►  October (5)
    • ►  September (10)
    • ►  August (7)
    • ►  July (11)
    • ►  June (12)
    • ►  May (6)
    • ►  April (8)
    • ►  March (10)
    • ►  February (5)
    • ►  January (11)
  • ►  2009 (51)
    • ►  December (9)
    • ►  November (6)
    • ►  October (21)
    • ►  September (13)
    • ►  August (2)
  • ►  2003 (3)
    • ►  October (1)
    • ►  January (2)
  • ►  2002 (9)
    • ►  December (1)
    • ►  June (3)
    • ►  April (1)
    • ►  March (3)
    • ►  January (1)
  • ►  2001 (1)
    • ►  February (1)
  • ►  2000 (4)
    • ►  October (1)
    • ►  July (1)
    • ►  June (1)
    • ►  January (1)
  • ►  1999 (7)
    • ►  November (1)
    • ►  September (2)
    • ►  August (2)
    • ►  July (1)
    • ►  June (1)
Powered by Blogger.

About Me

Unknown
View my complete profile