E-mail List Archives
Re: Creating compliant websites using PhotoshopSliced files...
From: Joshue O Connor
Date: Jan 4, 2007 4:40AM
- Next message: Tim Beadle: "Re: Creating compliant websites using Photoshop Slicedfiles..."
- Previous message: Emma Duke-Williams: "Re: Serif vs sans-serif"
- Next message in Thread: Tim Beadle: "Re: Creating compliant websites using Photoshop Slicedfiles..."
- Previous message in Thread: Christian Heilmann: "Re: Creating compliant websites using Photoshop Slicedfiles..."
- View all messages in this Thread
Christian Heilmann wrote:
> creating a final layout and then slicing it up into different
> parts to put it together as a web page in HTML again is probably the
> worst approach to creating an accessible web site
Christian is right, as this approach to graphic design for the web
really does not translate well in accessibility terms. In short, don't
export your designs as sliced images. There are several reasons for
this. When you are slicing a large image (say a page layout with
rollover effects on buttons etc) it is very easy to get carried away and
rather that using broad strokes to divide the image you can create some
very small slices. For each of these slices the application (Image Ready
or Fireworks etc) will generate HTML that tells the browser where to
reposition the slice, its size and other properties etc. The code that
these applications produce is bloated and AFAIK has no semantic aspect
(well it was the last time I exported sliced images) and I would feel
that it probably has not improved. If it has improved and If anyone on
the list can add to this thread, please do.
You could also take the view that you wish to slice your images and then
edit the exported HTML by hand - to clean it up and add alternate text
etc. However, even this method goes against the grain of Web
Standard/Accessible design at the very least because the HTML that the
editor exports is embedded with the HTML page so even for relatively
small images with only a few slices, this can generate a lot of bloated
code that will increase your page size, So this method is the antithesis
of separating content from presentational elements.
A better approach is to get to grips with CSS and improve your basic
HTML knowledge - This is a more powerful and cleaner way to create more
beautiful and accessible websites.
Josh
********************************************************************
NOTICE: The information contained in this email and any attachments
is confidential and may be privileged. If you are not the intended
recipient you should not use, disclose, distribute or copy any of
the content of it or of any attachment; you are requested to notify
the sender immediately of your receipt of the email and then to
delete it and any attachments from your system.
NCBI endeavours to ensure that emails and any attachments generated
by its staff are free from viruses or other contaminants. However,
it cannot accept any responsibility for any such which are
transmitted. We therefore recommend you scan all attachments.
Please note that the statements and views expressed in this email
and any attachments are those of the author and do not necessarily
represent the views of NCBI
********************************************************************
- Next message: Tim Beadle: "Re: Creating compliant websites using Photoshop Slicedfiles..."
- Previous message: Emma Duke-Williams: "Re: Serif vs sans-serif"
- Next message in Thread: Tim Beadle: "Re: Creating compliant websites using Photoshop Slicedfiles..."
- Previous message in Thread: Christian Heilmann: "Re: Creating compliant websites using Photoshop Slicedfiles..."
- View all messages in this Thread