A bad Tool always blames the browser
By Mark Tennent in Reader
Posted in Internet on May 21, 2008 at 12:01 pm
Just how difficult is it to make a website nowadays? One which conforms to WWW3 standards, avoids browser or operating system-specific commands such as ActiveX and “just works”?
Very difficult, according to the firm who have the job of recreating the huge site developed by one of the UK’s leading charities for people with disabilities. Their brief is to give it a new look, rationalise some of the older elements and above all, to make it accessible for everyone.
They seem to forget about the millions of other sites around the world that are platform and browser agnostic and work with just about any browser. The Disability Discrimination Act 1995 makes it a legal duty to make websites accessible, the web developers in question only made it open to Windows and used a typeface so small that even on a large screen monitor one needs a magnifying glass to view the labels.
The site is still under development so it’s not fair to name names (yet) but the point is that the initial response of the developers was to blame the browser used to access the site rather than their coding. As it is, neither Safari or Firefox can address some elements, the two most-used, cross-platform browsers after Internet Explorer. Something is seriously wrong somewhere.
Broken Windows
After all, Windows is starting to look distinctly proprietary and limited to office locations. Sixty-six percent of people who bought a computer worth more than
Comment by Jacques Daviault - May 22, 2008 on 2:04 am
Why would web site creators stop hand-coding? The vast majority of them are beanie-wearing weenies of the worst kind, not terribly artistic or creative, and the type who love one standard to adhere to. Unfortunately that standard is that of the decrepit Internet Explorer, and it manages to be in dereliction of an uncomfortable number of the latest conventions adopted for the world wide web. As long as Microsoft pushes incessantly for its version of the web to be THE version of the web, up and coming, and in my opinion superior browsers, like Safari and Firefox will constantly struggle to keep up. Once again… shame on Microsoft, forever doing their best to ruin everyone’s computing experience while lining their obscenely wealthy pockets. But I’m not bitter, no no no…
Comment by pistro - June 23, 2009 on 6:38 am
I am having problems with jpeg files exported from Lightroom 2.2 http://www.ebook-search-queen.com/ebook/ligh/lightroom-2.2.all.html . I dont think ImageGetExifMetadata working properly for LR images. I can see the all exif information with a different programs. One of the errors:”Element Focal Plane Y Resolution is undefined in a CFML structure referenced as part of an expression. “. “Element Focal Plane Y Resolution” is there but CF can’t read it. I have tried all sorts with no luck.On the other hand it works for non LR jpg images. Any ideas?
Make a comment
Tag cloud
Archives
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
Most commented posts
Highest Rated Blog Posts
- Blinking Cursors (100%)
- iPhoniness (100%)
- Relevant eloquent pleading (100%)
- Frozen in Time Machine (100%)
- Moondrop to Agony (100%)
- Coding Monkeys and a Hat full of Sky (100%)
- Grrrr Growl (100%)
- Chasing the dragons (100%)
- It just sits there dribbling (100%)
- And the Winner is… Who cares? (100%)

