Next Friday, we’ll be upgrading the markup on Wufoo public forms to HTML5 based on the research we gathered on [HTML5 form support](http://www.wufoo.com/html5/). We’re doing this to help improve the semantics of our forms, which is great for improved accessibility, and to make sure that Wufoo can be in a position to use the latest form features implemented by browsers as they come out. While these changes should not affect the majority of our users, we are pre-announcing the changes to give users that take advantage of our [Custom CSS](https://help.wufoo.com/articles/en_US/kb/Theme-Designer/#customCSS) features to adjust their CSS stylesheets so that nothing will look wonky after the transition. If you’re using a custom theme on your form **without** using the Custom CSS feature, you won’t have to do anything. All themes will upgrade automatically to accommodate the new HTML5 markup changes.
Currently, Wufoo forms were all written to conform to the XHTML 1.0 Transitional specifications set by the W3C.
On April 1st (and no, it will not be a joke), we’ll be using the more elegant HTML5 doctype.
To allow the new semantic markup to work on older version of Internet Explorer, we’ll also be including a reference to load the HTML5 Shim script.
A number of fields will utilize the appropriate field types based on the information they’re collecting. The **Number** and **Currency** fields will both use `type=”number”` instead of `type=”text”` after the change. The **Email, Website and Phone Fields** in Wufoo will use the corresponding `email`, `url` and `tel` types. Unfortunately, because the hooks for handling the styling for browser side validation is not well supported yet, we’ll be adding the `novalidate` attribute to the `