Overview
- Shows Web developers how to make the transition from HTML to XHTML, an XML-based reformulation of HTML that offers greater design flexibility
- Demonstrates how to work with CSS (Cascading Style Sheets)-now supported by ninety percent of browsers and integral to new site-building tools from Macromedia and others-and implement a consistent style throughout and entire site
- Explains how to make a site accessible to people with impaired vision, limited hand use, dyslexia, and other issues-now a legal requirement for many sites in the U.S. and the U.K.
Synopsis
For developers with knowledge of HTML, this manual explains how to use XHTML and CSS (Cascading Style Sheets) to build websites that are accessible and meet current requirements. Via the update of a fictional site, Duckett demonstrates how to create websites that will work in different browsers, page presentation, and compliance with Section 508 accessibility guidelines developed by the US government and the World Wide Web Consortium. He describes the differences between HTML and XHTML; CSS style, positioning, properties, and layout; tables and forms; testing the website; and future technology. There is no bibliography. Duckett is a freelance developer and consultant in London. Annotation © 2006 Book News, Inc., Portland, OR
Editorials
From Barnes & Noble
The Barnes & Noble ReviewWhy lose audience (or customers) when you don’t have to? Shouldn’t your site be accessible to everyone? If you’re becoming comfortable with CSS or XHTML, why not master the accessibility techniques needed to accomplish that? They’re surprisingly easy and non-disruptive. Here’s a book you can use as both a primer (or refresher) on XHTML and CSS and a practical guide to accessible design.
Jon Duckett begins with issues that apply independent of accessibility: moving HTML sites to XHTML, using CSS to build effective layouts, and so forth. Next, he turns to accessibility, covering everything from the absolute basics onward. What assistive technologies and guidelines are available? How do you provide text equivalents for nontext items? Check for dynamic content, color, and contrast issues? Create accessible forms and tables? And, crucially, test your site? He even previews emerging issues -- such as accessibility on mobile devices. Bill Camarda, from the June 2005 Read Only