(anonymous guest) (logged out)

Copyright (C) by the contributors. Some rights reserved, license BY-SA.

Sponsored by the Wiki Symposium and the Nuveon GmbH.

 
View Attach Info

Add new attachment

Only authorized users are allowed to upload new attachments.

This page (revision-2) was last changed on 20-Sep-2007 10:56 by RadomirDopieralski  

This page was created on 18-Sep-2007 23:58 by OliverSiemoneit

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 1 changed 3 lines
Some notes from an accessibility's point of view: Having a blockqoute markup is a good idea and at least in Germany one important criteria for an accessible site. Besides a blockqoute markup it would be also nice to have the inline version <q> </q>. For accessibility it is always a good idea to use semantic markup (<strong>) instead of normal markup (<b>). Code elements could be marked with <code> and so on. Note: blockqoute mustn't be used for indentation. Here in Germany also these things must be met:
* easy ways to mark a certain passage / a word with a <lang> attrib, so that screenreaders can adapt the pronounciation accordingly
* abbr, acronym is also very important to have. However this is not only markup I guess but calls for a deeper integration in the wiki engine (if you think of automtically resolving of abbr for example)
Some notes from an accessibility's point of view:
Having a block qoute markup is a good idea and at least in Germany one important criteria for an accessible site. Besides a block qoute markup it would be also nice to have the inline version <q> </q> (see [[Inline Quote Proposal]]).
Note: blockqoute mustn't be used for indentation.
----
General accessibility notes (possibly to be moved):
For accessibility it is always a good idea to use semantic markup (<strong>) instead of normal markup (<b>). Code elements could be marked with <code> and so on.
Here in Germany also these things must be met:
* easy ways to mark a certain passage/word with a "lang" attribute (in HTML), so that screen readers can adapt the pronunciation accordingly
* <abbr> and <acronym> are also very important to have. However this is not only markup I guess but calls for a deeper integration in the wiki engine (if you think of automatically resolving of <abbr> for example)
Version Date Modified Size Author Changes ... Change note
2 20-Sep-2007 10:56 0.98 kB RadomirDopieralski to previous trying to organize
1 18-Sep-2007 23:58 0.847 kB OliverSiemoneit to last
« This page (revision-2) was last changed on 20-Sep-2007 10:56 by RadomirDopieralski