Over himself, over his own body and mind, the individual is sovereignJohn Stuart Mill
Also relates to CSS Design
Since first discussing CSS Zoom as an alternative technique for accessible design earlier in the year, it has become an integral part of my design methodology. While this technique does come with disadvantages, especially related to images, I like the ability to enlarge an entire page to very high screen resolutions and similarly shrink the page to display satisfactorily in 640 x 480 dpi, without the worry of text or form fields breaking their parent containers.
In the latest incarnation of the Still Stoked website I have juxtaposed CSS Zoom with Doug Bowman's Sliding Doors technique to de-table-ise the three column design. The new layout relies on an extended banner graphic at the top of the page that can slide in out as the page is resized without affecting the look and feel of the page, while all the internal columns and text can grow and shrink freely. Enhanced accessibility and improved SEO were also high priorities for the site, so absolute positioning is implemented on the menu and side columns to allow the actual page content to appear first in the document structure.
The only complication that arose was incorporating a fixed width on the right hand column to ensure the background graphics remained locked together. A wrapper container is used to declare borders to house the left and right columns, where the left column is relative and, as just stated, the right column is fixed. But since the wrapper element contains floating elements (the internal columns) it must also have a width declaration. The problem is clear - how to combine a relative width and fixed border within the CSS Box Model.
The solution was to balance out the fixed width border of the wrapper container with a padding in its parent container as follows:
#cont {
position:relative;
/* [..snip..] */
width:50em;
padding-right:99px;
}
#wrap {
position:relative;
border:1px solid #83acd6;
border-width:0 99px 0 8em;
width:42em;
margin:0 -99px 1px 0;
padding:0;
}
So the relative components of #wrap (left border and width) balances out the width of #cont, while a right padding in #cont creates space for the fixed width right border in #wrap. For FireFox, Mozilla and Opera that seems to be job done, but the additional
negative right margin is required on IE6. Not too much of a challenge! But of course playing with the Box Model always heralds danger when our least favourite family of browsers are booted up!
As it happens, in this instance, the hack required to appease the IE5.x family is simple - just declare the same width for both #cont and #wrap. After all, this solution is simply a case of balancing the equations and for these legacy browsers borders and padding are declared internally to the width of the container. So if the containers
have the same width the browsers should be happy. I like to keep legacy hacks as far away from the main CSS file as possible, so these equal width declarations were placed in a file called using the mid pass filter (along with a few other Lost Child hacks for IE5.0).
This implementation of the CSS Slide and Zoom technique seems to work effectively across the entire range of PC browsers, and ICapture gave positive feedback for Safari. Please let me know in the comments of any glitches are observed on other browsers (IE5 for Mac perhaps?).
Posted on May 09, 2004 at 14:53:29. [Comments for CSS Slide And Zoom- 0]
Also relates to DOM Scripting
Jesse Ruderman's excellent collection of bookmarklets have become a vital development tool offering functionality for CSS fine tuning and accessibility auditing among other things.
Based around the Validation Bookmarklets collection, I have written a bookmarklet to display the values of all anchor title attributes within a page. This is particularly useful to view the alternative text for links out of context to ensure it makes sense. This could easily be extended to view the title attribute for all elements on the page.
Posted on May 09, 2004 at 14:51:57. [Comments for Link Title Bookmarklet- 0]
Also relates to Web Standards
I feel privileged to announce my application to join the Guild of Accessible Web Designers (GAWDS) has been accepted. The Guild, originally founded by Jim Byrne is still in development and has an admirable member community with some of the finest and most reputed accessibility developers in the world. A principle objective of the Guild is to
…promote a vision of the future that assumes accessible web design to be relevant, obtainable and not at odds with successful business practice or good visual and usable design.
With the official opening of the Guild set for the middle May, I hope I can find considerable time beyond client commitments to contribute extensively to the community.
Posted on Apr 24, 2004 at 14:13:08. [Comments for New GAWDS Member- 0]
This post does not relate to any other topics
The DRC formal investigation into web accessibility has released its findings today in this comprehensive report (PDF File, 406KB).
This report demonstrates that most websites are inaccessible to many disabled people and fail to satisfy even the most basic standards for accessibility recommended by the World Wide Web Consortium.
[snip.]
Organisations that offer goods and services on the Web already have a legal duty to make their sites accessible. It is clear from the investigation that these duties are not being fulfilled. The Commission's policy is to seek improvement in the first instance through advice and conciliation, and this report contains a range of recommendations to help website owners and developers tackle the barriers to inclusive design. However, where the response is inadequate, we shall be vigorous in the use of our enforcement powers; these range from namedparty Formal Investigations which can lead to sanctions against the owners of inaccessible websites, to the provision of support for test cases being brought by individual disabled people.
DRC Formal Investigation Report: Web Accessibility, Foreward vi.
The report raises some criticism of the overall ability of the WAI Guidelines and automated test suites for validating accessible sites and the WAI have posted a rebuttal to some potentially misleading analysis in the report.
Posted on Apr 14, 2004 at 14:12:42. [Comments for DRC Report Arrives- 0]
Also relates to DOM Scripting
One of my aims now the new site is up and running is to start writing some articles. I regularly find my blog entries become too drawn out, and ideally these would be better presented as short articles. As always, I am currently way too busy to really get underway with this. However, to get the ball rolling, I have posted a short article on creating DHTML content without compromising accessibility. It basically surmises the process I went through on a recent site development to create a manual image slideshow, hence allowing the maximum preservation of screen real estate.
I haven't found time to add a comments section following the article (which I do hope to do for all future articles, since discussion generally brings out further ideas and enhancements). However, feel free to post any remarks, criticisms, or errors for the article under this blog entry. I hope it is of use to those crossing the accessibility threashold.
Posted on Feb 25, 2004 at 23:04:08. [Comments for Article On Accessible DHTML- 0]