|
|
|
|
Bad HTML Habits
|
|
|
|
|
Even the best HTML jockey has likely developed habits along the way that hinder accessibility. You may have grabbed at style sheets to alleviate your dependence on FONT formatting tags, but as you tweak your way through the HTML world, you're probably still using some renegade code that works but isn't exactly up to spec.
Tweaking Headings
Priority 2 - For example, user agents may be able to build a table of contents by reading the headings on a Web page. So, using H1 through H6 tags to structure your information is important, and using these tags simply to size text can cause problems.
Tweaking Spacing
Transparent images have become a de facto workaround by which many Web builders elude HTML's layout limitations. These images, however, can make it difficult for user agents to distinguish between real content and ancillary images such as spacers. Instead, use style sheets to control margins, spacing, and other page elements. (CSS2 also offers new styles that address white space.)
Tweaking Indentation
Another no-no is using block quotes or list containers to control indention. Both are common workarounds used by Web builders to indent paragraphs or whole pages. The problem is that software may interpret and deliver information a certain way because of the tag. So, a text-to-voice reader might interpret the block quote information as a quote and read it accordingly when, in fact, you were just trying to indent a paragraph. Again, style sheets offer the best solution; they allow you to separate the formatting and visual appearance of the material from the structure of the page.
|
|
|
|
|
Tweaking Text
Another culprit is the use of absolute text formatting tags instead of relative ones. <B> and <STRONG>, for example, may render the same in many browsers, but they do not mean the same thing. The <STRONG> tag, as well as the <EM> tag, was designed to indicate structural emphasis that could take the form of either a visual change (font, size, and style) or an audible change (inflection, volume, and pitch).
Don't Ignore These Tags
Priority 1 - You need to provide alternative content if you're creating pages with certain elements:
* When you use SCRIPT, provide NOSCRIPT information.
* When using FRAMES, provide NOFRAMES information.
* When using EMBED, provide NOEMBED information.
* When using APPLETS, use ALT text.
* When using FRAMESET, make sure to use TITLE.
* Provide a text-only alternative to audio or video.
Even if you only explain why the user isn't receiving the information, you will be alleviating some confusion.
|
|
|
|
| |
|
| |
|
|
|
|
|
|
