HTML and CSS Reference
In-Depth Information
“HTML5 Powered with Graphics, 3D, and effects”
“HTML5 Powered with Device Access”
“HTML5 Powered with Performance & Integration”
Technology names are optional and can be combined (by adding the word “and” prior to
the last technology selected). The badges can be generated with Badge Builder 5000 in
both horizontal and vertical orientations. The HTML5 mark with or without wordmark,
supporting elements, technology classes, and sticker templates are available as separate
SVG and PNG files. The HTML5 logo is also available as a one-color version. All badges are
released with the Creative Commons Attribution 3.0 License [36].
“Made with Cascading Style Sheets”.
Accessibility icons: “WAI-A WCAG 1.0”, “WAI-AA WCAG 1.0”, “WAI-AAA WCAG 1.0” [37],
“WAI-A WCAG 2.0”, “WAI-AA WCAG 2.0”, and “WAI-AAA WCAG 2.0” [38].
Semantic Web technology buttons: “GRDDL”, “OWL”, “POWDER”, “RDF”, “RDFa”, “RIF”, “SKOS”,
and “SPARQL” [39].
However, W3C is not the only institution that releases technology icons and logos. Here are some examples:
“Unicode encoded”
“Dublin Core used here”
“Java—Get it now”
“HCARD”, “XFN FRIENDLY”, and icons and logos for other microformats [40]
“Cynthia tested” [41]
“SEO friendly”
“NO popups, NO spyware”
“Powered by PERL”
n /10— (where n is a number between 1 and 10) [42]
In this chapter, you learned that there are powerful, efficient tools to check your web documents for errors. They can
be used during development and are very useful for redesign. Many of these validators are free tools and are available
online. The most commonly used ones are markup validators and CSS validators, because the markup and style
sheets are core web site components and can be validated automatically. Validating web site accessibility is a real
challenge, because several aspects of WCAG often require human decision.
The last chapter will enumerate the most common errors that result in invalid markup, style sheets, news feed
channels, and accessibility barriers.
Search WWH ::

Custom Search