The first place to look for information is in the section of the manual where you least expect to find it.
You are currently browsing the recent entries for February, 2005
I’ve been trying out InFocus from SSB recently. There’s no doubt that it is a very powerful accessibility and flexible validator that can be configured to taste. One of the configuration options allows you set set a maximum number of words that should allowed in an inline quote (default: 10 words) whilst another allows to pre-set the minimum number of words allowed within a <blockquote> (default: 10 words).
One of the big problems for keyboard navigators is that, unlike mouse users, they may find it difficult to see exactly which link they have moved to within a site menu or similar list of links. For some time now, designers have been making use of the CSS pseudo a:hover class to add rollover effects to links. Mouse users often find that the background colour to a link changes when they hover over it or the link loses its underline etc. Those using a keyboard to navigate often have no such visual assistance. On pages containing large numbers of links in close proximity to one another, this can be a real problem.
After a long time of declaiming against blogs and declaring them to be a complete waste of time, I’ve finally realised that they have their uses. Apart from the obvious SEO benefits that having a decent blog seems to offer (and I have to earn my living just the same as anyone else), it does give me somewhere to ramble on about some technical point or other.
For this, my family and coworkers will be truly grateful.
Of course, it will take some time to actually get a decent chunk of content up here, so bear with me.
Apart from being an entire continium all on its own, <q> is a potentially useful, and under-used, piece of markup. So what’s <q>?
According to the W3C specification:
qis intended for short quotations (inline content) that don’t require paragraph breaks.
So far, so good. We can use q to markup short inline quotations such as:
<p><q>We think this should be useful</q>, said W3C</p>
The problem arises when you start to look how q is implemented cross browser.