When a little JavaScript is too much

August 30, 2007 at 8:31 am | Posted in Assignments, HTML, Programming | Leave a comment

Create a Lightbox effect only with CSS – no javascript needed at Emanuele Feronato provides a simple solution to create a basic light box using predominately CSS. The promise of liberating the conundrum of presenting images, often photographs, within the virtual space of a webpage using simple techniques drew a large amount of interest (myself included) and feedback.

That the title promises no JavaScript, but the substance of the solution relies upon it, drew ire from most commentators. Some provided constructive feedback, others provided their own solutions, and still others were quick to point out which particular browser failed to display correctly.

There are tons of Lightbox scripts in the web, each one with its unique features and limitations, but all require massive use of Javascript or the installation of javascript frameworks.

Which captures the current problem. JavaScript creates a perception of complexity, of insistent pop-ups, of browser incompatibilities, of bloat. People who desire to create virtual light boxes want implementations they can use without needing Computer Science degrees.

JavaScript predates CSS. Current CSS progress extends CSS with modifiers such :active and :focus. These improvements allow CSS to supplant and remediate JavaScript with similar functionality. This follows current programming design to favor abstract descriptions in favor of explicit control. While the light box may be a case of There is More Than One Way To Do It (TMTOWTDI), in the end very few of the comments eschewed the solution for avoiding JavaScript, but rather using too much JavaScript.

A discussion of <blockquote>’d interviews

August 28, 2007 at 12:07 am | Posted in Assignments, HTML | Leave a comment

In Should interview answers be marked up with a <blockquote>? PPK discusses the quoting of interviews and conversations in HTML.

The website of a Dutch ministry has been tested for compliance with the Web Guidelines. I have been asked to supply a second opinion, which I’m currently writing. I came across a complicated semantic point that I’m not quite sure of; hence I’d like to ask your opinion.

The main question according to PPK is…

…if interview answers count as quotations. After all, they are almost never direct, literal quotations of the interviewed person. Instead, the journalist usually changes the texts a little bit to remove the erms and such, and to create grammatically correct, readable sentences.

Semantically <blockquote> sets off text that is cited from another textual source (such as in this post). By using a block quote, authors acknowledge that the cited text comes from another source. However, PPK makes the point that journalist will usually need to edit dialog to a printable form. Journalists replace useless bits of mumblings (such as these) and conversational phrasing with coherent sentences.

Rather than reach a conclusion, PPK poses the question of appropriateness of <blockquote> to his readers.

The responses discuss other solutions. For instance, <dt> / <dd> pairs may create appealing visual results, but if reproduced aurally make little sense. Tables provide structure, but provide little semantic meaning. Most responses agreed that within current HTML, nothing quite completely captures the ordered nature of a dialog. Finally, PPK reaches the conclusion that for the time <p> provide the best compromise until <dialog> in HTML 5.

The discussion is interesting because of the various solutions provided. Yet, no one approach completely solves this issue. That web designers need to consider the aural representation of documents says a lot about the strides in accessibility the web has made in recent years. The balance of visual versus aural rendering illustrates the importance of clean markup combined with CSS to control document presentation.

Create a free website or blog at WordPress.com.
Entries and comments feeds.