An Open Letter to WHATWG

For the last decade or so, Web developers have been moving more and more towards standardization. With the advent and popularity of XHTML, we’ve all been encouraged to ensure that all of the elements we open are closed when we’re done using them, to use all lowercase type for entities and attributes (we could just as easily used all uppercase, but then we’d look like we were shouting in our code), explicitly define attribute values and more. We have come to a golden age in Web development.

Whenever we view the code from other Web sites, assuming it’s written in valid XHTML, it makes sense to most of us. We can tell specifically where paragraphs, divs, spans and other HTML elements begin and end. We have come a long way from the wild west days of the mid-nineties when anything could happen. Some of us are old enough and have been writing HTML long enough to remember the days when HTML was loose and fast and can also remember when browsers would do strange things when attempting to figure out where we really intended one element to end and another to begin.

Embed YouTube Videos With Valid Code

If you’ve ever tried to embed a YouTube video on your Web site, you may have noticed that the code they provide is not valid XHTML. I came across two blog posts today while doing some research that offer some alternative code that allows you to post YouTube videos on your site with valid code. Check them out if you are thinking of posting videos on your site or even your blog.

ARIA Landmark Roles – Increasing Accessibility

I stumbled across a neat tool to be used during Web site development the other day. The tool uses javascript to examine the page and presents you with an overlay report of the accessibility issues in the page. The tool was developed by and is available from Accessify. It’s called the “Quick Page Accessibility Test.” Installing the app is as simple as dragging it to your Favorites/Bookmarks bar. Then, whenever you visit a page, you can click on the bookmark and the accessibility tester will pop over the page you’re viewing (complete with context overlays).

Anyway, after I installed the application and tested one of my pages, I came across an accessibility warning I had never encountered before. The warning message looked something like “This appears to be a list of links. Perhaps this should be marked up with ARIA landmark role ‘Navigation’.” I had never heard of ARIA landmark roles, so I ran off to try to do some research on the subject. About all I was able to find in my first attempt were some abstracts from the W3C.

Manipulating the DOM with javascript – part 4 of 4

This is the final installment of my four-part tutorial on manipulating the DOM with javascript. So far, we have explored the createElement, appendChild, insertBefore, replaceChild and removeChild functions. In this final post, we will explore the createTextNode function, and will then put it all together into a real world example.

Manipulating the DOM with javascript – part 3 of 4

In my last post, we explored the appendChild and insertBefore functions. As I explained, those are two of the three main functions you can use to add a new element into your HTML page. In this post, we will explore the replaceChild and removeChild functions.

Manipulating the DOM with javascript – part 2 of 4

In my last post, I explored the createElement function to begin showing you how to add, remove and replace elements in your HTML pages with javascript. In this post, I will explore the appendChild and insertBefore functions. These are two of the three functions you will use to actually insert the new element you created in the last post.

Pages: