Inaccessible HTML Tags
[Skip to: content] [Skip to: navigation]

XHTML 1.1 - Served as application/xhtml+xml

Inaccessible HTML Tags

Inaccessiblility

Here are a few (x)HTML elements that show the implications of Inaccessible HTML Tags:

Frames

Frames are used to divide the website into several independent parts, each consisting of a separate HTML page. There are many drawbacks to using frames:

Besides, you are making things harder on yourself. Frames are so 90's anyway!

Tables

Some designers tend to interpret "don't use tables for layout" as "don't use tables at all". That is not the idea. If what you're marking up is tabular data, it belongs in a table, so a table is what you should use. There are ways to build data tables, which are more logical and accessible.

Read more:

Tables for web design layouts are so 90's anyway!

Forms

Forms are often marked-up in un-semantical ways, because the (X)HTML code isn't using the elements to make forms accessible and easier to use. The elements <label>, <fieldset> and <legend> are meant to be used.

Read more:

JavaScript and cookies

Avoid depending on JavaScript. More people than you might think have JavaScript turned off in their browser, for security reasons, or to avoid pop-up windows. Also, users may have a browser that doesn't support JavaScript anyway. According to TheCounter.com, 6% of web users have no JavaScript. W3Schools.com reports 8%.

Most cases where JavaScript is being used, it is just fluff anyway, and doesn't actually benefit the visitor. Of course there are cases where JavaScript can be proved usefull. One example is validating form input.

You don't have to avoid using JavaScript. It does mean that you should nothave a website depend on JavaScript to work.

The same thing goes for cookies. Do not use cookies in a way that makes the web site stop working if the visitor doesn't accept them.

Back to top

So you see, website accessibility is something every web designer is responsible for.