Comments on: The fluid elastic reboot http://nickcowie.com/2006/the-fluid-elastic-reboot/ Web standards, accessibility and such like with a bias toward Government web sites Wed, 11 Apr 2012 22:22:55 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: WEB 3.0 » Blog Archive » ¿Así que querías saber de CSS? http://nickcowie.com/2006/the-fluid-elastic-reboot/comment-page-1/#comment-37557 WEB 3.0 » Blog Archive » ¿Así que querías saber de CSS? Sat, 18 Apr 2009 01:24:42 +0000 http://nickcowie.com/2006/the-fluid-elastic-reboot/#comment-37557 [...] The Fuid Elastic Reboot - Nick Cowie [...] […] The Fuid Elastic Reboot — Nick Cowie […]

]]> By: Nick http://nickcowie.com/2006/the-fluid-elastic-reboot/comment-page-1/#comment-37051 Nick Fri, 27 Jun 2008 09:54:15 +0000 http://nickcowie.com/2006/the-fluid-elastic-reboot/#comment-37051 RE Mogul a few issues here, the SWF header will work in any Windows machine with the flash plugin and javascript turned on. No flash or javascript and you get the alternative content. In Mac OS or other *nix devices, the problem with layering occurs because how the flash plugin interacts with the underlying system. In other words flash works with hidden hooks inside the Windows OS. Either these hidden hooks do exist in *nix systems or flash does not interact with them. By the Adobe definition of accessibility (late model computer with windows XP or newer and a current version of JAWS or Windows Eyes) the SWF header is accessible. It is also accessible to lower specifications by my design. The big difference between the SWF header and using an elastic image is size. The .swf file is only a few kilobytes, a .jpg equivalent is over 500kb. Bandwidth is still important, here in Australia there are people who have a choice of a 28kps dial up connection or paying $2.00 a Mb for faster wireless download. And image maps are not accessible or work in mobile devices. RE Mogul a few issues here, the SWF header will work in any Windows machine with the flash plugin and javascript turned on. No flash or javascript and you get the alternative content.

In Mac OS or other *nix devices, the problem with layering occurs because how the flash plugin interacts with the underlying system. In other words flash works with hidden hooks inside the Windows OS. Either these hidden hooks do exist in *nix systems or flash does not interact with them.

By the Adobe definition of accessibility (late model computer with windows XP or newer and a current version of JAWS or Windows Eyes) the SWF header is accessible. It is also accessible to lower specifications by my design.

The big difference between the SWF header and using an elastic image is size. The .swf file is only a few kilobytes, a .jpg equivalent is over 500kb. Bandwidth is still important, here in Australia there are people who have a choice of a 28kps dial up connection or paying $2.00 a Mb for faster wireless download.

And image maps are not accessible or work in mobile devices.

]]> By: RE Mogul http://nickcowie.com/2006/the-fluid-elastic-reboot/comment-page-1/#comment-37043 RE Mogul Thu, 26 Jun 2008 20:03:33 +0000 http://nickcowie.com/2006/the-fluid-elastic-reboot/#comment-37043 If the ALT Text/Metaquery is an issue one could simply snap-in an image over ALT Text. Doing such a thing for a header would require gigantic ALT Text, and a graphic defined in ems. If the ALT Text/Metaquery is an issue one could simply snap-in an image over ALT Text. Doing such a thing for a header would require gigantic ALT Text, and a graphic defined in ems.

]]> By: RE Mogul http://nickcowie.com/2006/the-fluid-elastic-reboot/comment-page-1/#comment-37042 RE Mogul Thu, 26 Jun 2008 19:59:19 +0000 http://nickcowie.com/2006/the-fluid-elastic-reboot/#comment-37042 The SWF header is buggy in a variety of Alternative Layouts/Browsers. The images on the Elastic Images Page are not. The issue is the layering. Any thoughts on layering for accessibility? Also: why is the web so reticent about image mapping. Surely there is an efficient mapping TECHNIQUE that is accessible? The SWF header is buggy in a variety of Alternative Layouts/Browsers. The images on the Elastic Images Page are not.

The issue is the layering. Any thoughts on layering for accessibility?

Also: why is the web so reticent about image mapping. Surely there is an efficient mapping TECHNIQUE that is accessible?

]]> By: RE Mogul http://nickcowie.com/2006/the-fluid-elastic-reboot/comment-page-1/#comment-37041 RE Mogul Thu, 26 Jun 2008 19:45:53 +0000 http://nickcowie.com/2006/the-fluid-elastic-reboot/#comment-37041 If only a way to turn-on Clear-Type... On page load... Without IE... Outline Fonts (& SWF) render without anti-aliasing. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Perhaps an Outline Font could be embeded in a piece of XML, and loaded style-sheet-esque. Such fonts could be easily whisked-away with < 5k bandwith consumption, on the orginating page load. The Outline Font could also be used for the HEADER, and sub headings. I would imagine one could put all sorts of things into a font package: symbols buttons, or ANY REOCCURING ELEMENT on the page. The beauty: browsing devices are generally text first, and images second -- which is precisely how the page would prograde. Script could replace Alt text with Outline Font ASCII. And... The Loathsome IE handles snap-in fonts NATIVELY! The solution would also solve the image-scaling dilema for functional elements. Most browsers already scale font respectably. If only a way to turn-on Clear-Type…
On page load…
Without IE…

Outline Fonts (& SWF) render without anti-aliasing.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Perhaps an Outline Font could be embeded in a piece of XML, and loaded style-sheet-esque. Such fonts could be easily whisked-away with < 5k bandwith consumption, on the orginating page load.

The Outline Font could also be used for the HEADER, and sub headings. I would imagine one could put all sorts of things into a font package: symbols buttons, or ANY REOCCURING ELEMENT on the page.

The beauty: browsing devices are generally text first, and images second — which is precisely how the page would prograde.

Script could replace Alt text with Outline Font ASCII.

And… The Loathsome IE handles snap-in fonts NATIVELY!

The solution would also solve the image-scaling dilema for functional elements. Most browsers already scale font respectably.

]]> By: stelt http://nickcowie.com/2006/the-fluid-elastic-reboot/comment-page-1/#comment-382 stelt Tue, 09 May 2006 20:36:51 +0000 http://nickcowie.com/2006/the-fluid-elastic-reboot/#comment-382 Though SVG support is not nearly perfect out-of-the-box ubiquitously, there's a bit more than you mention: see http://svg.startpagina.nl One of the most popular Mozilla extensions is FlashBlock, that renders a PLAY button instead of Flash content. Both formats have a range of things for which using that format is great. These ranges partly overlap. Though SVG support is not nearly perfect out-of-the-box ubiquitously, there’s a bit more than you mention: see http://svg.startpagina.nl

One of the most popular Mozilla extensions is FlashBlock, that renders a PLAY button instead of Flash content.

Both formats have a range of things for which using that format is great. These ranges partly overlap.

]]>