Welcome to WebmasterWorld Guest from 188.8.131.52
Forum Moderators: ergophobe
I may be writing a page about the use of keyboard shortcuts. I'm surely going to use the
element to my advantage.
...to copy use the keyboard buttons <kbd>Ctrl</kbd> + <kbd>C</kbd> simultaneously to copy.
I need to set up a glossary of definitions. I'm surely going to use the
element to my advantage.
Do you think an intimate understanding of HTML Elements and Attributes are imperative to accessiblity and usability?
How do you Accessorize your website?
Index of HTML 4 Elements
Index of HTML 4 Attributes
But what advantages does <kbd> give you?
The Keyboard Element allows you to use a "correct" semantic wrapper. For example, the
element would be appropriate when writing instructions for using a keyboard.
I tend to avoid "non-mainstream" HTML, as it can whack support for older browsers, and support for older browsers is the #1 thing you can do to make your site accessible.
Actually these are HTML 4 Elements and Attributes that are supported by all browsers. There are elements and attributes which are Deprecated and those are marked as so on the links provided above.
I tend to avoid "non-mainstream" HTML.
I guess it all comes down to what type of visitor you are targeting. That would definitely determine the type of markup structure you utilize.
Thanks for the clarification.
I agree. I think there are a lot of tags that may be more appropriate for accessibility, but aren't used that much, or are used incorrectly because the intent is not clear.
The one that immediately springs to mind is a mutated list, such as a
used where the number is stripped out, or a
used where the number is added, or a
, where only
tags are used.
is best for accessibility.
* Correct use of
I am also a big fan of frequent use of
The <pre> gives you a fixed pitched font.
<em> and <strong> instead of <i> and <b>?
Only where appropriate. I've seen more misuse of <em> and <strong> than other elements. For example, WYSIWYG editors these days come out of the box wrapping <i> with <em> and <b> with <strong>. The users are real quick to highlight text and click that B button to give it visual style. They don't realize that they are creating a semantic nightmare in their code. ;)
P.S. I still use <i> and <b>. Its an old habit that is hard to break. Since they have no semantic meaning I figure what the heck, its still valid markup and it provides me with a quick way to visually style the text. I'll use <em> and <strong> only when I need semantic meaning.