Web standards

W3C, WASP, A List Apart, Open Web, OpenSource, Evolt, WSG, QuirksMode, W3QC, Accessify

CSS3-which way to go

June 6, 2008 Posted by

Many people feel that the first version of CSS was a breakthrough – it’s hard to disagree with that. CSS2 was received somewhat less enthusiastically – a lot of people were pointing to the fact that there was no clear vision for the further development of this standard. Time flies quickly, and 10 years after the birth of CSS1 a new version (CSS3) is looming in the horizon. There are a lot of voices of support and criticism (which is prevailing). When cruising the blogosphere, I found at a very interesting article on the evolution of CSS – (strongly critical).
The article is written by Alex Russell, who believes that such important issues as inheritance and variable replacement should have been already implemented in CSS 2. It turns out that you can’t find these either in the CSS 3 draft. Instead, the people working on the development of CSS focus on less ambitious goals. The fact is that, at the moment, the question of inheritance is highly neglected, although CSS is somehow handling this issue. Sometimes, you want to import one uniquely “named” class (previously defined) into another. Unfortunately, such a mixing is disallowed, and you have to hardcode the values, which unnecessarily inflate the entire code.

Talks in June

June 2, 2008 Posted by

HTML 5-two serializations

May 10, 2008 Posted by

There are many misinterpretation of the HTML 5 specification. For many, the HTML 5 syntax seems to be one of the great uncertainties. How is it in reality? HTML 5 specification is the description of a vocabulary that you can write in two different syntaxes: HTML and XML depending on your needs.
The previous versions of the HTML vocabulary (HTML+, HTML 2.0, HTML 3.2) were written using SGML syntax rules. HTML 4 has two syntaxes: SGML (called HTML 4.01) and XML (called XHTML 1.0).
SinceSGML has never been deployed in browsers, HTML 5 defines a new serialization called html.


May 9, 2008 Posted by

This is a quick guide how to design a web page so that it is easy to use for people with disabilities.
The accessibility issues should be addressed mainly by webmasters, because they are directly responsible for complying with the accessibility standards.

A few reasons why to comply with accessibility standards

  • Google behaves like a visually, mentally, and physically impaired user. You don’t want to help the disabled, help your site rank better in SERPs. Do it for yourself!
  • Users of mobile devices (cell phones, PDAs, etc.) have similar problems as the disabled. Don’t want to help them, think of it as a fast growing market that can make you a lot of money. Do it for yourself!
  • A lot of companies don’t allow plug-ins or scripts in browsers. After all, as an Internet business, you have to think about people who like browsing the Web on their coffee break.
  • Links must look like links. They must clearly distinct color (e.g. blue, because it is the “safest” for all those having problems with distinguishing colors). If the user can’t see the links, how he/she is supposed to navigate through your site.
  • Have you heard of attribute accesskey. People who have difficulties using the mouse will be able to quickly use the link that has an accesskey assigned to it (for instance, <a accesskey=”1″> Home </a> ). If the user doesn’t have a mouse, it’s too difficult to navigate through the site. It means lost customer!
  • Use alternative text for images or your message “Buy here” may never be discovered!.