Note: You are currently viewing documentation for Moodle 1.9. Up-to-date documentation for the latest stable version is available here: Semantic HTML.

Semantic HTML: Difference between revisions

From MoodleDocs
 
(23 intermediate revisions by the same user not shown)
Line 1: Line 1:
== The case for semantic HTML ==
== The case for semantic HTML ==


It is easy to create HTML that ''works'', but current best practice suggests that creating valid and '''Semantic HTML''' is an important goal for various reasons including [[Usability|usability]] and [[Accessibility|accessibility]].  
It is easy to create HTML that ''works'', but current best practice suggests that creating valid and Semantic HTML is an important goal for various reasons including [[Usability|usability]] and [[Accessibility|accessibility]].  


Unfortunately, while validation is a relatively easy task to understand and achieve, creating semantically correct HTML is a lot more subjective and open to debate.
Unfortunately, while validation is a relatively easy task to understand and achieve, creating semantically correct HTML is a lot more subjective and open to debate.
Line 7: Line 7:
== Examples for semantic HTML ==
== Examples for semantic HTML ==


Instead of writing something like
Here are some examples of non-semantic HTML taken from the current Moodle markup (layout and styling is done with CSS which isn't shown here).


=== List instead of DIVs ===
=== List instead of DIVs ===
Line 27: Line 27:
</code>
</code>


(Example taken from Moodle's Site Administration block.)
(Example taken from Moodle's ''Site Administration'' block, see [[User:Frank Ralf/Semantic HTML1]].)


=== Indentation without ''spacer.gif'' ===
=== Indentation without ''spacer.gif'' ===
Line 56: Line 56:
</code>
</code>


(Example from Moodle's Course Category list.)
(Example from Moodle's ''Course Category'' list, see [[User:Frank Ralf/Semantic HTML4]].)


For more examples how to make Moodle HTML more semantic you might have a look at this work in progress: [[User:Frank Ralf/Semantic HTML1]].
 
== Separating structure and styling ==
 
Don't use inline styles but put any styling information in a separate CSS.
 
BAD:
<code php>
<td style="width:180px" id="left-column">
</code>
 
GOOD:
<code php>
<style type="text/css">
<!--
td#left-column {width: 180px;}
-->
</style>
 
<td id="left-column">
</code>
 
(Example taken from one of Moodle's standard themes.)
 
== Avoid "divitis" and "classitis" ==
 
"The div tag is a block-level element that defines a section within a document. Divs are thus suitable for building the structure of Web pages. The div tag is also used to describe content that cannot be properly described by other more semantic tags. When developers do not understand the semantic meaning of other block-level elements, they often add more div tags than are needed."
 
Source: [http://www.smashingmagazine.com/2009/04/08/from-table-hell-to-div-hell/ "Table Layouts vs. Div Layouts: From Hell to… Hell?"] by Geir Wavik, from ''Smashing Magazine''
 
Another disease in the CSS world is called "classitis", the excessive use of classes (mainly for non-semantic reasons). For examples and hints to avoid this see [http://www.cssnewbie.com/combating-classitis/ "Combating Classitis with Cascades and Sequential Selectors"] by Rob Glazebrook.
 
Here's an example for a meaningless class:
 
<code php>
<a class="link" href="admin/register.php">...</a>
</code>


== Further resources ==
== Further resources ==
Line 86: Line 121:
== See also ==
== See also ==


* [[Development:XHTML]]
* [[Accessibility]]
* [[Accessibility]]
* [[Usability FAQ]]
* [[Usability FAQ]]
* [[CSS FAQ]]
* [[CSS FAQ]]
* [http://www.sitepoint.com/blogs/2010/03/16/the-tragic-comedy-that-is-rich-text-editing-on-the-web/ "The Tragic Comedy that is Rich Text Editing on the Web"] - SitePoint blog
* For more examples how to make Moodle HTML more semantic you might also have a look at this work in progress: [[User:Frank Ralf/Semantic HTML1]].


[[Category:Developer]]
[[Category:Developer]]
[[Category:Accessibility]]
[[Category:Accessibility]]
[[Category:Usability]]
[[Category:Usability]]

Latest revision as of 15:24, 16 March 2010

The case for semantic HTML

It is easy to create HTML that works, but current best practice suggests that creating valid and Semantic HTML is an important goal for various reasons including usability and accessibility.

Unfortunately, while validation is a relatively easy task to understand and achieve, creating semantically correct HTML is a lot more subjective and open to debate.

Examples for semantic HTML

Here are some examples of non-semantic HTML taken from the current Moodle markup (layout and styling is done with CSS which isn't shown here).

List instead of DIVs

BAD:

 <a href="#" name="d16">
   <img id="vh_div16indicator" src="pix/closed.gif" alt="Closed folder">
     Security
 </a>

GOOD:

  • <a href="#">Security</a>
  • (Example taken from Moodle's Site Administration block, see Frank Ralf/Semantic HTML1.)

    Indentation without spacer.gif

    BAD:

    <tbody> </tbody>
         <img class="spacer" src="pix/spacer.gif" alt="" height="10" width="20">
         
         <a href="/course/category.php?id=3">Quizzes</a>
    
    1

    GOOD:

    • <a href="/course/category.php?id=3">Quizzes</a>1

    (Example from Moodle's Course Category list, see Frank Ralf/Semantic HTML4.)


    Separating structure and styling

    Don't use inline styles but put any styling information in a separate CSS.

    BAD:

    GOOD: <style type="text/css"> </style>

    (Example taken from one of Moodle's standard themes.)

    Avoid "divitis" and "classitis"

    "The div tag is a block-level element that defines a section within a document. Divs are thus suitable for building the structure of Web pages. The div tag is also used to describe content that cannot be properly described by other more semantic tags. When developers do not understand the semantic meaning of other block-level elements, they often add more div tags than are needed."

    Source: "Table Layouts vs. Div Layouts: From Hell to… Hell?" by Geir Wavik, from Smashing Magazine

    Another disease in the CSS world is called "classitis", the excessive use of classes (mainly for non-semantic reasons). For examples and hints to avoid this see "Combating Classitis with Cascades and Sequential Selectors" by Rob Glazebrook.

    Here's an example for a meaningless class:

    <a class="link" href="admin/register.php">...</a>

    Further resources

    Online:

    Books:

    See also

    • For more examples how to make Moodle HTML more semantic you might also have a look at this work in progress: Frank Ralf/Semantic HTML1.