Over the years of being a web developer with a focus on accessibility, I have mostly dealt with widely-adopted, standardized UI components, well supported by assistive technologies (AT). For these types of widgets, there are concise ARIA authoring practices as well as great tools like axe-core that can be used to test web components for accessibility issues. Creating less common widgets, especially those that have no widely-adopted conventions for user interaction can be very tricky.
See the original article here:
Enter The Dragon (Drop): Accessible List Reordering
Since hearing about HTML5 and CSS3, then later reading Hardboiled Web Design by Andy Clarke, I have been working on a presentation to help me introduce these development methods to my clients. If all I said to them was, “These are the latest development methods, but there will be visual differences in your website across browsers,” I’m sure you can imagine the response I would get.
Most of my clients these days tell me they want the following:
Originally posted here:
Dear Clients, The Web Has Changed. It’s Time To Use CSS3 and HTML5 Now.
Last year, WordPress launched arguably its biggest update ever: WordPress 3.0. Accompanying this release was the brand new default theme, TwentyTen, and the promise of a new default theme every year. Somewhat surprisingly, TwentyTen declares the HTML5 doctype but doesn’t take advantage of many of the new elements and attributes that HTML5 brings.
Now, HTML5 does many things, but you can’t just add <!doctype html> to the top of a document and get excited that you’re so 2011.
Using HTML5 To Transform WordPress’ TwentyTen Theme