Useful Links: PowerPoint, Microformats in HTML5, dConstruct audio

PowerPoint Accessibilty at WebAIM tells you how to create an accessible PowerPoint presentation. The news for Mac users is not good.

Extending HTML5 – Microformats at HTML5 Doctor is a must read and explains the “wrinkles.”

As most microformats use only class and/or rel — basic parts of HTML that remain unchanged in HTML5 — these microformats are completely fine in HTML5. Yay! However there are a few wrinkles to keep us on our toes.

While you’re there, be sure to read the comments, too. They are important.

dConstruct 2010 is Jeremy Keith’s report on the recent conference. Included are links to the talks from the event and links to other bloggers reports on the event.

ARIA: A Quick Overview

ARIA is Accessible Rich Internet Applications, a set of standards under development by the W3C. It’s part of the WAI (Web Accessibility Initiative).

ARIA provides ways to describe roles supported by content. Roles include such things as “menu,” “treeitem,” “slider,” and “progressmeter,” Roles can also describe structure, with roles like “article,” “heading,” “complementary,” and “rowheader.”
ARIA provides properties that describe state. State properties can include things like “checked” for a check box, or “haspopup” for a menu. Properties can also describe parts of a page that may be updated—for example, stock quotes—or properties for drag and drop resources.

Providing information about roles and properties makes the page more accessible. The WAI-ARIA Overview states,

It especially helps with dynamic content and advanced user interface controls developed with Ajax, HTML, JavaScript, and related technologies. Currently certain functionality used in Web sites is not available to some users with disabilities, especially people who rely on screen readers and people who cannot use a mouse. WAI-ARIA addresses these accessibility challenges, for example, by defining new ways for functionality to be provided to assistive technology. With WAI-ARIA, developers can make advanced Web applications accessible and usable to people with disabilities.

Roles and properties are added as properties to HTML elements. Examples:

<div role=”main”>
<nav role=”navigation”>
<div role="button" aria-haspopup="true">

Where to learn more

Useful Links: Accessibility Failures, Gates on Education, downgrade your iPhone

10 Common Accessibility Problems from Dingo Access is a well explained list of common failures. For each problem, the solution is provided. The list is derived from WCAG 2.0 recommendations.

Bill Gates: In Five Years the Best Education Will Come from the Web. What do you think about this?

I haven’t had a bit of trouble with iOS 4 on my iPhone 3, but apparently some people have. Lifehacker tells you how to go back to iOS 3 if you need to. My biggest problem with my iPhone is when I hold the phone with my left hand, my cheek bone activates the mute button. Very annoying.

Document outlines in HTML5

There was some discussion about HTML5 document outline in the comments to my recent post HTML5: the new hgroup element. I thought the topic deserved a post of its own.

We’re all familiar with the DOM, that treelike structure that outlines the contents of an HTML document. Here’s a snippet of a DOM tree as displayed in Firebug.

firebug example of DOM

In HTML5, you can still navigate the DOM tree and can still outline a page of HTML based on the content of the page. The change in HTML5 relates to headings.

In previous versions of HTML, the heading elements (h1–h6) were assumed to reveal the structure of the document. They could be outlined and navigated with assistive devices. The way headings will reveal structure has changed in HTML5. In HTML5, there is something called ‘sectioning content.’

Elements that fall into the category of sectioning content include article, aside, nav, section. Each element of sectioning content potentially has a header, and that header forms part of the document outline. Let’s look at some examples.

<h1>My Adventures with Dreamweaver</h1>
<h2>Or, how I learned to love Code View in 3 easy lessons</h2>
<h2>Lesson One</h2>
<p>blah, blah, blah</p>
<h2>Lesson Two</h2>
<p>blah, blah, blah</p>
<h2>Lesson Two</h2>
<p>blah, blah, blah</p>

In HTML4, the <h2>Or, how I learned to love Code View in 3 easy lessons</h2> would appear in the document outline as if it were a section heading. But, in fact, it is a tagline or subtitle for the h1 it follows.

In HTML5, if this were marked up as a section or an article with a header element containing a hgroup element, the <h1>My Adventures with Dreamweaver</h1> would be recognized as the head of that section of content and the outline would reflect that. Here’s how it might look formatted that way.

<section>
<header>
<hgroup><h1>My Adventures with Dreamweaver</h1>
<h2>Or, how I learned to love Code View in 3 easy lessons</h2>
</hgroup>
</header>
<h2>Lesson One</h2>
<p>blah, blah, blah</p>
<h2>Lesson Two</h2>
<p>blah, blah, blah</p>
<h2>Lesson Two</h2>
<p>blah, blah, blah</p>
</section>

The h2 elements for Lesson One and so on would show up in the outline as subheadings in that section of content. But the second heading in the hgroup would not form part of the document outline.

There’s an online HTML5 Outliner that will let you look at your HTML5 pages and see exactly how they are outlined. It’s a good tool to help you understand how someone tabbing through the headings of your HTML5 document would see the document structure and navigate.

Useful Links: validators, keyboarding, Gmail, fake ads

The W3C has a new validator at validator.w3.org/unicorn they are calling a “unified” validator. Unified because it checks HTML (including HTML5), CSS, and RSS feeds.

The validator at validator.nu also checks HTML5, and can be set to check for ARIA roles as well.

Introduction to Keyboard Maestro from ATMac has a discount offer good through August.

Google came out with multiple account sign in yesterday. Here’s how to use it, from Demo Girl.

Fake Vintage Ads for Facebook, YouTube and Skype. Something to make you smile today.

HTML5 and screen readers

It’s been on my mind lately to try to find out how well a screen reader will navigate a page of HTML5. I’m particularly wondering about how hierarchy would make sense if there were to be a series of articles on a page, all with an h1 in a header element.

HTML5, ARIA Roles, and screen readers in May 2010 is a research report based on several screen readers. They are JAWS 11, Window-Eyes 7.11, NVDA 2010.1, and SAToGo 3.0.202. The results are different for each screen reader.

On YouTube, you can see a video of JAWS reading the liferay.com homepage, which has “lots” of HTML5.

Using WAI-ARIA Landmark roles gives screen reader results, mainly about how landmark roles are handled. This article also explains what ARIA landmark roles are and how to start using them. Be sure to read the comments about this article.

On the WebAIM blog, Aaron Anderson is working his way through a series of articles about various aspects of HTML5. The series is dubbed future web accessibility and to date includes a look at semantic elements, video, canvas, and several other HTML5 elements.

Interesting articles, even though they don’t exactly answer my question about multiple h1 elements on a page.

Accessible HTML for Knowbility

I’m doing a training session for Knowbility today. It’s a session on accessible HTML, training some trainers who work on various state of Texas sites. The people I’ll work with will be the ones who scatter through state agencies and make sure the people they train know how to write accessible HTML.

I can’t release the training materials because Knowbility is reserving them for the people attending the training. The aspects of HTML that I’ll talk about include headings, links, alt text, data tables, and forms.

I won’t have time to talk about video captioning, but I wanted to provide a reference for the trainers so they’d know where to look for information. Knowbility usually trains users in MAGpie for this. I wondered if YouTube did a decent job. I hadn’t seen anyone mention whether YouTube does a good job making video accessible with their new captioning service, so I asked Knowbility director Sharron Rush about YouTube’s service. She said that the service works great if you provide a transcript. It isn’t reliable if you depend on voice recognition.

I’ve been a supporter of Knowbility and what they do for a long time. This is the first time I’ve worked with them. I’m delighted to be officially associated with this wonderful organization, even in this small way.