|
|
Posted by Dr. Compynei on 03/13/07 13:15
"Bergamot" wrote:
> Dr. Compynei wrote:
>>
>> As part of my degree I am studying Web Development, and now I better
>> understand websites I am designing up the website of a charity (local
>> theatre) in CSS and XHTML 1.0 Trans.
>
> Were you instructed to use XHTML Transitional? If so, your instructor is
> incompetent.
Yes I was! Not for this specific project, but for a similar website, just
different content.
The instructor is a leading figure on sitepoint I believe.
>
>> Moving away from tables due to accessability problems etc etc.
>>
>> http://www.blt.org.uk/css/index.htm
>>
>> 1. Image Mapping. How is best to map the image to turn graphics into
>> hyperlinks.
>
> As someone else mentioned, the most accessible method would be plain
> text links styled with CSS. Using list mark up for navigation menus has
> become the accepted norm.
> http://css.maxdesign.com.au/listamatic/
>
> You can embellish with background graphics to get pretty much the same
> effect as the site has now and still be scalable with varying window and
> text sizes, but that is a bit advanced for a newbie. Keep it simple and
> you'll get better results.
Thanks for that, I will work with it.
>
>> 2. Scrolling. This is my main problem at the moment. When the page
>> gets
>> longer the content div just keeps going down the page, what I want is for
>> the site to be x% sizes of the screen (leaving some red border) no matter
>> what the resolution (upto a min of 800x600).
>
> Stop wanting this. If you're dropping layout tables for accessibility
> reasons, putting in a scrolling div would be substituting one
> accessibility problem with another, perhaps worse one. Scrolling divs
> are a navigation nightmare for keyboard users. They are cumbersome at
> best, unusable at worse.
That clears alot up. Many thanks for this.
> Were you instructed to use a scrolling div, too? :-(
No ;-). Just a thought.
Navigation:
[Reply to this message]
|