Category: html5


January 10, 2012

Accessible HTML5 Forms – Required Inputs

HTML5 has added a number of new element attributes, including 12 attributes used when creating forms. These Common input element attributes include 2 new Boolean attributes, the required attribute and the readonly attribute. Recently a number of current browsers have implemented native support for the ‘required’ attribute, and so I thought it would be useful to examine this attribute in more detail.

Read More

[Screen Capture: HTML code]

May 8, 2011

WYSIWYG support for @longdesc today

The @longdesc “discussion” just won’t go away. As HTML5 looms closer and closer towards becoming a Last Call document at the W3C, there is a full-court press to ensure that @longdesc remains in the specification.

Read More

[Photo: @poster]

January 26, 2011

The current problem with the @poster attribute of the <video> element.

Earlier this week, I posted a Change Proposal to the W3C HTML WG around a topic which seems to have drawn a bit of controversy and outright rejection from some members of the Working Group. I have suggested and proposed that when an author specifies an image file as a placeholder image for the video, that a means of properly ensuring the accessibility of that image be accounted for.

Read More

HTML5 Video

December 23, 2010

<video>, Accessibility and HTML5 Today

Back in July of 2009, I wrote a blog post spurred on by a dinner conversation with my friend Bruce Lawson. Since then, I’ve seen a few instances where people have pointed to that posting as important to understanding the issue of accessibility and video in HTML5. A lot has changed however since I wrote that piece, and I’ve been meaning to update that information for some time now. A recent email thread amongst some friends crystallized that requirement, and the following is adapted from the email note I wrote to that thread.

Read More

Web Standards: Yes please

February 8, 2010

Standard or Specification?

I believe what we have is a conflict of constituents.

What many people seem to be overlooking here is that we are writing more than just a Technical Specification for browser engineers, we are also writing a Standard, and I believe that the differences between the two is the major rub.

Read More