MarkUp Reference

A selection of further readings

• W3C - (X)HTML Notes, WDs, RECs
• (X)HTML Publications, Articles, Blognotes, Tips

W3C - (X)HTML Notes, WDs, RECs

General overviews and references to Markup specifications and closely related subjects

HyperText Markup Language (HTML) Home Page

[EN]

This is W3C's home page for the HTML Activity. Here you will find pointers to our specifications for HTML/XHTML, guidelines on how to use HTML/XHTML to the best effect, and pointers to related work at W3C. When W3C decides to become involved in an area of Web technology or policy, it initiates an activity in that area. HTML is one of many Activities currently being pursued.

http://www.w3.org/MarkUp/

HTML Working Group Roadmap

[EN]

This document describes the time line for deliverables of the HTML Working Group.

http://www.w3.org/MarkUp/xhtml-roadmap/

W3C Technical Reports and Publications

[EN] Overview http://www.w3.org/TR/

Übersetzungen von W3C Dokumenten

[DE]

Eine Übersicht sämtlicher in Deutsch erhältlicher Übersetzungen der W3C-Veröffentlichungen

http://www.w3.org/2003/03/Translations/byLanguage?language=de

Die W3C-Spezifikationen in deutscher Übersetzung und Kommentierung

[DE]

Die edition W3C.de hat die Veröffentlichung sämtlicher W3C-Empfehlungen (Recommendations) in deutscher Sprache und fachlicher Kommentierung zum Ziel. Die Kommentierung wird durch Experten des jeweiligen Gebiets angefertigt. Die edition W3C.de ist die einzige vom W3C legitimierte Publikation in deutscher Sprache. Als de-facto-Standards sind die W3C-Empfehlungen die Grundlage für das World Wide Web.

http://www.edition-w3c.de/

"HTML 1.2" - Hypertext Markup Language (HTML)

[EN]

A Representation of Textual Information and MetaInformation for Retrieval and Interchange

http://www.w3.org/MarkUp/draft-ietf-iiir-html-01.txt

Hypertext Markup Language - 2.0

[EN] RFC 1866 http://www.faqs.org/rfcs/rfc1866.html

HTML 2.0 DTD

[EN] http://www.w3.org/MarkUp/html-spec/html.dtd

HTML 3.2 Reference Specification

[EN]

The HyperText Markup Language (HTML) is a simple markup language used to create hypertext documents that are portable from one platform to another. HTML documents are SGML documents with generic semantics that are appropriate for representing information from a wide range of applications. This specification defines HTML version 3.2. HTML 3.2 aims to capture recommended practice as of early '96 and as such to be used as a replacement for HTML 2.0 (RFC 1866).

http://www.w3.org/TR/REC-html32-19970114

HTML 3.2 DTD

[EN] http://www.w3.org/MarkUp/Wilbur/HTML32.dtd

HTML 4.0 Reference

[EN] Web Design Group http://www.htmlhelp.org/reference/html40/

HTML 4.01 Specification

[EN] W3C Recommendation

This specification defines the HyperText Markup Language (HTML), the publishing language of the World Wide Web. This specification defines HTML 4.01, which is a subversion of HTML 4. In addition to the text, multimedia, and hyperlink features of the previous versions of HTML (HTML 3.2 and HTML 2.0 (RFC1866)), HTML 4 supports more multimedia options, scripting languages, style sheets, better printing facilities, and documents that are more accessible to users with disabilities. HTML 4 also takes great strides towards the internationalization of documents, with the goal of making the Web truly World Wide.

http://www.w3.org/TR/html4/

HTML 4.01- Index of Elements

[EN] http://www.w3.org/TR/html401/index/elements.html

HTML 4.01-Index of Attributes

[EN] http://www.w3.org/TR/html401/index/attributes.html

HTML 4.01 Strict DTD

[EN] HTML format http://www.w3.org/TR/html4/sgml/dtd.html

Modularization of XHTML

[EN] W3C Recommendation

This Recommendation specifies an abstract modularization of XHTML and an implementation of the abstraction using XML Document Type Definitions (DTDs). This modularization provides a means for subsetting and extending XHTML, a feature needed for extending XHTML's reach onto emerging platforms.

http://www.w3.org/TR/xhtml-modularization/

XHTML™ 1.0 The Extensible HyperText Markup Language (Second Edition)

[EN]

This specification defines the Second Edition of XHTML 1.0, a reformulation of HTML 4 as an XML 1.0 application, and three DTDs corresponding to the ones defined by HTML 4. The semantics of the elements and their attributes are defined in the W3C Recommendation for HTML 4. These semantics provide the foundation for future extensibility of XHTML. Compatibility with existing HTML user agents is possible by following a small set of guidelines.

http://www.w3.org/TR/xhtml1/

XHTML 1.1 - Module-based XHTML

[EN] W3C Recommendation

This Recommendation defines a new XHTML document type that is based upon the module framework and modules defined in Modularization of XHTML. The purpose of this document type is to serve as the basis for future extended XHTML 'family' document types, and to provide a consistent, forward-looking document type cleanly separated from the deprecated, legacy functionality of HTML 4 that was brought forward into the XHTML 1.0 document types. This document type is essentially a reformulation of XHTML 1.0 Strict using XHTML Modules. This means that many facilities available in other XHTML Family document types (e.g., XHTML Frames) are not available in this document type. These other facilities are available through modules defined in Modularization of XHTML, and document authors are free to define document types based upon XHTML 1.1 that use these facilities.

http://www.w3.org/TR/xhtml11/

XHTML 1 DTD

[EN] HTML format http://www.w3.org/TR/xhtml1/dtds.html

XHTML™ 2.0

[EN]

XHTML 2 is a general purpose markup language designed for representing documents for a wide range of purposes across the World Wide Web. To this end it does not attempt to be all things to all people, supplying every possible markup idiom, but to supply a generally useful set of elements.

http://www.w3.org/TR/xhtml2/

Extensible Markup Language (XML) 1.0 (Third Edition)

[EN]

The Extensible Markup Language (XML) is a subset of SGML that is completely described in this document. Its goal is to enable generic SGML to be served, received, and processed on the Web in the way that is now possible with HTML. XML has been designed for ease of implementation and for interoperability with both SGML and HTML.

http://www.w3.org/TR/REC-xml/

Namespaces in XML

[EN]

XML namespaces provide a simple method for qualifying element and attribute names used in Extensible Markup Language documents by associating them with namespaces identified by URI references.

http://www.w3.org/TR/REC-xml-names/

valid DTDs

[EN] List of valid DTDs you can use in your document http://www.w3.org/QA/2002/04/valid-dtd-list.html

XHTML media type test

[EN] W3C http://www.w3.org/People/mimasa/test/xhtml/media-types/

Style Guide for Online Hypertext

[EN] Tim Berners-Lee

This guide is designed to help you create a WWW hypertext database that effectively communicates your knowledge to the reader. It has been prepared in the light of comments by readers, and many demands by providers of online documentation.

http://www.w3.org/Provider/Style/All.html

Authoring Techniques for XHTML & HTML Internationalization: Characters and Encodings 1.0

[EN]

It is important to consider character encoding matters when producing internationalization content, and further to understand how to choose and declare encodings, how and when to use character escapes, etc.

This document is one of a series of documents providing HTML authors with techniques for developing internationalized HTML using XHTML 1.0 or HTML 4.01, supported by CSS1, CSS2 and some aspects of CSS3. It focuses specifically on advice about character sets, encodings, and other character-specific matters. It is produced by the Guidelines, Education & Outreach Task Force (GEO) of the W3C Internationalization Working Group (I18N WG). The GEO Task Force encourages feedback about the content of this document as well as participation in the development of the techniques by people who have experience creating Web content that conforms to internationalization needs.

http://www.w3.org/TR/i18n-html-tech-char/

HTML Techniques for WCAG 2.0

[EN]

This document provides information to Web content developers who wish to satisfy the success criteria of "Web Content Accessibility Guidelines 2.0" (currently a Working Draft). It includes techniques, code examples, and references to help authors satisfy each success criterion. The techniques in this document are specific to Hypertext Markup Language content although some techniques contain Cascading Style Sheet solutions. Deprecated examples illustrate techniques that content developers should not use. The techniques listed in this document are suggestions on how to conform to WCAG 2.0. However, they may not be the only way to satisfy each success criterion.

http://www.w3.org/TR/WCAG20-HTML-TECHS/

HTML4 Test Suite

[EN]

The HTML4 Test Suite is based upon the W3C HTML 4.01 recommendation. This test suite is applicable to user agents (particularly visual user agents). The W3C Validator should be used for validation of document authoring.

http://www.w3.org/MarkUp/Test/HTML401/current/

Authoring Techniques for XHTML & HTML Internationalization: Characters and Encodings 1.0

[EN]

It is important to consider character encoding matters when producing internationalization content, and further to understand how to choose and declare encodings, how and when to use character escapes, etc.

http://www.w3.org/TR/i18n-html-tech-char/

Tutorial: Character sets & encodings in XHTML, HTML and CSS

[EN]

If a user agent (eg. a browser) is unable to detect the character encoding used in a Web document, the user may be presented with unreadable text. This information is particularly important for those maintaining and extending a multilingual site, but declaring the character encoding of the document is important for anyone producing XHTML/HTML or CSS. This tutorial will give you an understanding of the topic that will help you make the right choices when doing so. The topic is not as straightforward as it may sometimes appear, and the advice contained here is the end result of a great deal of thought and discussion.

http://www.w3.org/International/tutorials/tutorial-char-enc/

XHTML and RDF

[EN]

The aim of this document is to discuss the relationship between XHTML and metadata.

http://www.w3.org/MarkUp/2004/02/xhtml-rdf.html

The Matrix of W3C specifications

[EN]

The specifications in the Matrix are at least at Last Call stage, except if they are working on a Test Suite at Working Draft stage. As of July 2004 the Matrix contains 70 Recommendations, 18 Candidate Recommendations, and 15 Last Call Working Drafts.

http://www.w3.org/QA/TheMatrix

(X)HTML Publications, Articles, Blognotes, Tips

Tutorials, articles, reviews, and notes on selected subjects concerning Markup languages

WASP - The Web Standards Project

[EN/DE]

Founded in 1998, The Web Standards Project (WaSP) fights for standards that reduce the cost and complexity of development while increasing the accessibility and long-term viability of any site published on the Web. We work with browser companies, authoring tool makers, and our peers to deliver the true power of standards to this medium.

http://www.webstandards.org/

Tutorials @ W3C

[EN]

W3C’s mission is to develop and promote technologies for the Web. If the development of these technologies goes through the publication of technical reports, these specifications are usually not the easiest place to discover how to actually use these technologies. If you want to get started with one of the technologies developped by W3C, we encourage you to read first tutorials for this technology. This list aims to be exhaustive in listing tutorials or pages with links to tutorials on our site

http://www.w3.org/2002/03/tutorials

SELFHTML

[DE]

SELFHTML is the well known documentation of HTML, CSS, JavaScript, DHTML, XML/XSLT, CGI/Perl and more, with many additional tips for design, grafic, project management, etc.

http://www.selfhtml.org/

Programs vs. markup or Why HTML authoring is not programming

[EN] Jukka Korpela

The words "program" and "programming" are often used confusingly. This document tries to characterize what computer programs and programming languages are and how they differ from markup, both presentational and logical markup. This hopefully helps in understanding, for example, the different roles of HTML and programming languages like JavaScript and Perl in HTML authoring. The difference has some legal impact, too.

http://www.cs.tut.fi/~jkorpela/prog.html

Why attribute values should always be quoted in HTML,or the saga of the slashed validators

[EN] Jukka Korpela

There are several reasons why an HTML author should always put attribute values into quotes in HTML, although the formal rules allow the omission of the quotes in some cases. This document briefly lists some of the reasons. Then it tells a particular horror story of what an unquoted attribute value containing a slash may cause, due to an interesting discrepancy between validators (and the HTML specifications) and most browsers.

http://www.cs.tut.fi/~jkorpela/qattr.html

Alphabetical Index of Link Types

[EN]

The <link> element is used to describe relationships to other documents for site management or to reference style sheets or script files. Here is a list of a variety of possible rel attribute values with description of their purpose.

http://fantasai.tripod.com/qref/Appendix/LinkTypes/alphindex.html

HTML Tidy Configuration Options

[EN]

Overview of configuration options for Dave Raggett’s HTML Tidy programme for cleaning up Markup.

http://tidy.sourceforge.net/docs/quickref.html

HTML Support History

[EN] Brian Wilson

Comprehensive tables of all HTML elements and attributes currently supported by Internet Explorer, Mosaic, Netscape and Opera. Support in the HTML 2.0, 3.2, 4.0 and XHTML 1.0/1.1 specifications are also detailed (as well as HTML 3.0 features implemented in current browsers.) This list breaks down the HTML elements and attributes by first letter and details the very first version of each browser and standard where support began.

http://www.blooberry.com/indexdot/html/supportkey/a.htm

Frames, nur ein Problem alter Browser?

[DE]

Seit ihrer Einführung mit dem Netscape Navigator 2 ist die Verwendung von Frames umstritten. Damals waren die Hauptargumente, dass zuviele Browser die neue Technologie nicht unterstützten. Angesichts der heutigen Verbreitung von grafischen Browsern, die Frames anzeigen, wäre es übertrieben, alle Seiten in einer framelosen Alternativversion vorzuhalten. Das würde den Pflegeaufwand für das Projekt fast verdoppeln oder die NOFRAMES-Version würde schnell veralten. Seit 1997 ist mit der Verabschiedung von HTML 4.0 die FRAME-Technik auch offizieller Teil der HTML-Recommendations des World Wide Web Consortiums, das dafür einen eigenen Typ von HTML-Dokumenten eingeführt hat: HTML 4.0 Frameset. Man sollte meinen, damit seien alle Vorbehalte ausgeräumt und der Verwendung von Frames stehe nichts mehr entgegen. Das ist leider nicht der Fall. Die eigentlichen Probleme mit Frames bestehen nach wie vor, angesichts der Weiterentwicklung des Webs teilweise noch in verschärfter Form.

http://www.subotnik.net/html/frames.html

Warum ALT Attribute Pflicht sind

[DE]

Nach den HTML 4.0 Spezifikationen ist für jedes Bild das mit <IMG> eingebunden wird, ein ALT Attribut notwendig. Dieser Artikel soll erläutern, warum das so ist, und wie man das Attribut richtig einsetzt. Einige Leser halten es für sinnvoll, sich zuerst die schlechten Beispiele anzusehen.

http://www.bjoernsworld.de/html/alt-text.html

Was sind DTDs?

[DE]

Damit Browser wissen, mit welcher Art von Dokument sie es zu tun haben, hat das W3C zusammen mit jeder neuen Entwicklung von HTML, HTML oder XML die so genannten DTD veröffentlicht. Die DTDs - Document Type Definitions - sind fester Bestandteil von HTML, XHTML. Um dem Browser mitzuteilen, welche Befehle, Attribute und Einschränkungen für die entsprechende Sprache gelten, was der Browser anzeigen soll, wie er CSS darstellen soll, bzw. wie er sich bei der Anzeige von CSS formatierten Dokumenten verhalten soll, wird die Doctype Deklaration verwendet. Die DTD ist genormtes Dokument, in welchem die Sprachstruktur definiert wird. Gegen diese Definition wird das Dokument abgearbeitet.

http://www.fabrice-pascal.de/artikel/dtd/

Tag Soup: How UAs handle <x> <y> </x> </y>

[EN] Ian Hickson

HTML user agents have to be able to cope with invalid markup, such as unclosed tags, tags closing in the wrong order, and tags where they aren't allowed, if they are to render the existing Web. Rendering the existing Web is rather critical, because if you fail to do so, no user will adopt you.

http://ln.hixie.ch/?start=1037910467&count=1

Error handling and Web language design

[EN] Ian Hickson

I’ve been following the recent burst of posts about whether XML should have required that Web browsers stop processing upon hitting an error (as it does) or whether it should have let Web browsers recover from errors in vendor-specific ways (like HTML does) with some amusement, because asking the question in this yes/no form misses the point: There is a third, better option.

http://ln.hixie.ch/?start=1074730185&count=1

HTML and XHTML Frequently Answered Questions

[EN] Steven Pemberton

If you ever wondered about the difference between HTML and XHTML this FAQ provided by the W3C is a good start for getting answers.

http://www.w3.org/MarkUp/2004/xhtml-faq

Extending XHTML: Target and Strict

[EN]

That the target attribute is not by default allowed in valid XHTML 1.1 or XHTML 1.0 Strict continues to be a source of frustration for designers. It simply doesn't have to be. Others -- Jacques Distler and Dave Hodder, namely -- have pointed out that XHTML is designed to be modular and that it's easy to extend the specification by creating your own DTD. Jeffrey Zeldman suggests caution.

http://dionidium.com/2004/05/xhtml-tests

DCMI Metadata Terms

[EN]

This document is an up-to-date specification of all metadata terms maintained by the Dublin Core Metadata Initiative, including elements, element refinements, encoding schemes, and vocabulary terms (the DCMI Type Vocabulary).

http://dublincore.org/documents/dcmi-terms/

Expressing Dublin Core in HTML/XHTML meta and link elements

[EN]

This document describes how a Dublin Core (DCMI) metadata record can be embedded into an HTML/XHTML Web page using HTML/XHTML elements.

http://dublincore.org/documents/dcq-html/

Accessible HTML standards

[EN]

The following explanations are mandatory knowledge for any Front End Developer working on a project that has to fulfil the accessibility guidelines set by the W3C and enforced by the UK Government Standards or the US Section 508 standards. Accessibility means making the web site accessible for everybody, regardless of software, hardware or mean of web access. Surfers can use web sites with browsers, text browsers, switch access or screen readers. An accessible web site has to ensure that each of these ways can be used to reach the same goal. This does not mean that the web site has to be bland and boring, it means that the HTML has to be good and understandable for even the most basic means; more visual experience or usability enhancing elements get added later. This is nothing new, all it takes is some more discipline of the HTML scripter.

http://www.onlinetools.org/articles/accessible_standards.html

Separation: The Web Designer’s Dilemma

[EN]

With all the discussion about separating presentation from content (and structure), it’s easy to lose track of the goal. So let’s step back, define our terms, and take a look at why it matters.

http://www.alistapart.com/articles/separationdilemma/

Flash Satay: Embedding Flash While Supporting Standards

[EN] Drew McLellan

I’ve worked with Flash for several years and have always been slightly dissatisfied with the markup needed to embed a movie in web pages. When I recently published a site in XHTML, my dissatisfaction with the markup grew as I realized that it simply wasn’t valid in this context and was bloating my pages to unacceptable levels. A leaner, standards-compliant method of embedding Flash movies was called for.

http://www.alistapart.com/articles/flashsatay/

Fix Your Site With the Right DOCTYPE!

[EN] Jeffrey Zeldman

You’ve done all the right stuff, but your site doesn’t look or work as it should in the latest browsers. You’ve written valid XHTML and CSS. You’ve used the W3C standard Document Object Model (DOM) to manipulate dynamic page elements. Yet, in browsers designed to support these very standards, your site is failing. A faulty DOCTYPE is likely to blame.

http://www.alistapart.com/articles/doctype/

Better Living Through XHTML

[EN] Jeffrey Zeldman

An unauthorized companion to the Online Style Guide of the Branch Libraries of The New York Public Library

http://www.alistapart.com/articles/betterliving/

How to Read W3C Specs

[EN] J. David Eisenberg

The World Wide Web Consortium is the keeper of the specifications for all the technologies on the web. As a web designer, you might have visited their site (w3.org) to find the answer to a question about XHTML, or to find out more about a new technology like XSL Formatting Objects or Scalable Vector Graphics. So you go to the specification, and almost immediately retreat in utter confusion. “This,” you think, “is totally unreadable.” Actually, it is readable—if you know one key piece of information.

http://www.alistapart.com/articles/readspec/

HTML is not an acronym...

[EN] Craig Saila

HTML is, however, an abbreviation. So what is an acronym? Unlike, say the French language, there is no official body that determines what is and isn’t proper English. Like the Web, though, there are a series of recommendations from recognized organizations. And, again, like the Web, there are those who disagree with the generally agreed upon usage. Nevertheless, most lexicographers would likely agree with Merriam-Webster’s Collegiate Dictionary.

http://www.evolt.org/article/HTML_is_not_an_acronym/17/35750/

ABBR and ACRONYM are for user agents not for end users

[EN] Jesper Tverskov

The WCAG (1.0) guideline 4, checkpoint 4.2, about ABBR and ACRONYM, has for a long time been too unclear to implement. The drafts for XHTML 2.0 and WCAG 2.0 seem to have solved most problems.

http://www.smackthemouse.com/20040108

Activating the Right Layout Mode Using the Doctype Declaration

[EN] Henri Sivonen

In order to deal with both old tag soup written to old browser quirks and new standards-compliant pages, Mozilla (and Mozilla-based browsers, such as Netscape 6, Netscape 7, Camino, Galeon, Phoenix/Mozilla Firebird, and Beonex), Mac IE 5, Windows IE 6, Safari and Opera 7 have two main layout modes. In one mode the layout engine attempts to comply with W3C Recommendations. In the other mode the layout engine tries to mimic old browsers. In Mozilla these modes are known as “the Standards mode” and “the Quirks mode” respectively.

http://www.hut.fi/~hsivonen/doctype.html

Sending XHTML as text/html Considered Harmful

[EN] Ian Hickson

A number of problems resulting from the use of the text/html MIME type in conjunction with XHTML content are discussed. It is suggested that XHTML delivered as text/html is broken and XHTML delivered as text/xml is risky, so authors intending their work for public consumption should stick to HTML 4.01, and authors who wish to use XHTML should deliver their markup as application/xhtml+xml.

http://www.hixie.ch/advocacy/xhtml

Content Negotiation und XHTML beim IE

Christoph Schneegans[DE]

Das Zusammenspiel von Content Negotiation und XHTML führt unter gewissen Bedingungen dazu, daß der Internet Explorer HTML-Dokumente wie XML behandelt.

http://schneegans.de/bugs/ie-xhtml-content-negotiation/

Mime-Typen

[DE] SELFHTML

Mime steht für Multipurpose Internet Mail Extensions. Aus dem Namen geht hervor, dass das, was da spezifiert wird, ursprünglich für E-Mails gedacht war - und zwar für E-Mails mit Attachments (englisch für Anhang). Solche so genannten Multipart-Mails enthalten die gesamten zu übertragenden Daten in einer Datei. Innerhalb der Datei musste eine Konvention gefunden werden, wie die einzelnen Teile (z.B. Text der Mail und angehängte ZIP-Datei) voneinander zu trennen seien. Dabei wurde auch ein Schema entwickelt, das der interpretierenden Software mitteilt, um welchen Datentyp es sich bei dem jeweils nächsten Teil der Mail handelt. Das Schema erwies sich nicht nur für E-Mails als nützlich. Fast immer, wenn entfernte Programme (z.B. Web-Browser und Web-Server) wegen einer bevorstehenden Datenübertragung miteinander kommunizieren, geht es auch um die Art der zu übertragenden Daten. Dabei hat sich im gesamten Internet das Schema der Mime-Typen durchgesetzt. Auch im Web stößt man an verschiedenen Stellen auf Mime-Typen.

http://www.selfhtml.net/diverses/mimetypen.htm

The 'text/html' Media Type - RFC 2854

[EN] Daniel W. Connolly

This document summarizes the history of HTML development, and defines the 'text/html' MIME type by pointing to the relevant W3C recommendations; it is intended to obsolete the previous IETF documents defining HTML, including RFC 1866, RFC 1867, RFC 1980, RFC 1942 and RFC 2070, and to remove HTML from IETF Standards Track.

http://www.faqs.org/rfcs/rfc2854.html

The 'application/xhtml+xml' Media Type - RFC 3236

[EN] Mark A. Baker

This document defines the 'application/xhtml+xml' MIME media type for XHTML based markup languages; it is not intended to obsolete any previous IETF documents, in particular RFC 2854 which registers 'text/html'.

http://www.faqs.org/rfcs/rfc3236.html

Auxiliary Benefits of Accessible Web Design

[EN]

This document is one of several resources created to assist the preparation of a business case for the implementation of Web accessibility. It describes the many business, technical and other benefits to the organization above and beyond the straightforward benefits to people with disabilities that can be realized by applying the Web Content Accessibility Guidelines (WCAG 1.0) to Web sites.

http://www.w3.org/WAI/bcase/benefits.html

My Web site is standard! And yours?

[EN] Karl Dubost

Here you will find easy, painless techniques and ideas to improve your Web site quality and make your Web site valid. This document is intended for HTML users, developers working on Web applications, and Web masters.

http://www.w3.org/QA/2002/04/Web-Quality

Richtlinien zum barrierefreien Webdesign

[DE]

Barrierefreies Webdesign - manchmal auch Zugänglichkeit oder Accessibility genannt - ist die Kunst, Webseiten so zu programmieren, dass jeder sie lesen kann. Beim Design von Webseiten wird oft nicht berücksichtigt, dass viele Menschen körperliche Einschränkungen haben. Dann bilden bestimmte Techniken der Programmierung »Barrieren« für deren Zugang zum Internet. Dies können fehlende Texte zur Beschreibung von Grafiken, eine unglückliche Auswahl der Farbkombinationen, unklar strukturierte Webseiten, nicht bedienbare Navigationsmechanismen u.a.m. sein. Wenn aber Webgestalter auf eine gute Programmierung achten, erleichtern sie Menschen mit Sinnes- und Körperbehinderungen das Surfen im Netz, anstatt sie daran zu hindern. Die wesentlichen Kriterien und Hinweise für ein barrierefreies und somit auch behindertengerechtes Webdesign werden durch die Barrierefreie Informationstechnik-Verordnung (BITV) geregelt, die am 24. Juli 2002 in Kraft trat. Bei der Einhaltung der BITV wird insbesondere - aber nicht nur - der Zugang zu Webseiten durch Blinde und Sehbehinderte gewährleistet.

http://www.barrierefreies-webdesign.de/richtlinien.php

What is a good standard? An essay on W3C’s design principles

[EN] Bert Bos

Why doesn’t HTML include tags for style? Why can’t you put text inside SMIL? Why doesn’t CSS include commands to transform a document? Why, in short, does W3C modularize its specification and why in this particular way? This essay tries to make explicit what the developers in the various W3C working groups mean when they invoke words like efficiency, maintainability, accessibility, extensibility, learnability, simplicity, longevity, and other long words ending in -y.

http://www.w3.org/People/Bos/DesignGuide/introduction

Was ist ein guter Standard? Ein Essay über die Designprinzipien des W3C

[DE] Michael Jendryschik

Warum enthält HTML keine Tags fürs das Styling? Warum kann man in SMIL keinen Text einfügen? Warum enthält CSS keine Befehle zur Transformation eines Dokuments? Warum, kurz gesagt, modularisiert das W3C seine Spezifikationen und warum auf genau diese Art und Weise? Dieser Essay versucht, zu erläutern, was die Entwickler in den verschiedenen W3C-Arbeitsgruppen meinen, wenn sie von Begriffen wie Effizienz, Wartbarkeit, Zugänglichkeit, Erweiterbarkeit, Erlernbarkeit, Einfachheit oder Langlebigkeit reden.

Dies ist die deutsche Übersetzung des Essays »What is a good standard?« von Bert Bos [DE]

http://jendryschik.de/wsdev/trans/designguide/

Net Twits

[EN] Lachlan Hunt

This WeBlog is a gallery of websites that basically, just get it wrong! The aim is to showcase the stupidity of some of the worst HTML-Terrorists. It's not just about the millions of average website builders who use image-text navigational links, tables for layout, or nothing but <font> tags. This blog aims to point out those who take that little extra step in making their site difficult to use, completely inaccessable, totally annoying or just hypocritical!

http://www.lachy.id.au/blogs/nettwits/

Please report broken links to keep this reference listing up-to-date and to ensure its quality