Re: Wrapping up the ACSS Module Ideas

You wrote:
> > 1. In the content, include a "skip" link that points to just after the
> >    navigation bar. Then, in the CSS stylesheet, hide that link for visual
> >    browsers.
> This would appear to be the *only* ideal solution. 

Actually it's not ideal. It is, IMHO, about style, but you must include 
extra content. Any solution that requires this should set alarm bells 

> > 2. Aural browsers could implement a feature whereby saying "skip"
> >    automatically jumps to the end of the current (deepest) element, or
> >    jump to the end of the element that contains the end of the current
> >    sentence, or some such.
> That wouldn't work because the DOM is often messy.

Mm. The problem is perhaps that HTML elements are exceedingly 
primitive: <table> encompasses an enormous number of different types of 
content. Obviously you can't specify meaning in CSS (e.g., defining 
TABLE {meaning: navigation}), so the only way from a presentational 
point of view is, as you suggested, to define the element's 
presentational level (e.g., presentation-level: optional | integral | 
never), and then decide what you want to do with it from this. 

> > 3. The content could be transformed using XSLT to include a skip link if
> >  the media is aural.
> But for that you would have to use CC/PP or some kind of scripting (ASP),

Nooooooooooooooooooo. OT, but if you think ASP is the only web 
scripting language you are wrong. Use PHP ( - not 
BASIC crap (uses C++/Perl-style syntax), faster, cross-platform, Free, 
support for pdf, gif, png, DOM, node-based XML (expat), flash, etc. 
It's also object-oriented (if you want). Repent before BASIC rots your 
mind :->.

-- Random fortune
There are people who find it odd to eat four or five Chinese meals
in a row; in China, I often remind them, there are a billion or so
people who find nothing odd about it.
		-- Calvin Trillin

Received on Wednesday, 18 October 2000 06:20:41 UTC