WCAG 2.0 Quick Reference

The W3C did not gain fame as a source of easy reading. The complaints about the WCAG 2.0 draft being really hard to read have been flying through the air for weeks. Now the W3C has issued the WCAG 2.0 Quick Reference. It still seems complex, but perhaps this is a step in the direction of making sense of it all. After a swift glance through it, one of my worries is that the software the average designer uses to create web content makes complying with some of these guidelines difficult.

Technorati Tags: , , ,

Tip: What is semantic markup and why should you care?

The word semantic gets tossed around a lot in connection with web design. A comment from someone made me realize I had overlooked discussing what that means here on Web Teacher. I use the word logical quite often instead, although I am not in a majority by talking about the logic of HTML tags as relating to sematics.

To me, however, HTML is simple because it’s logical. You can learn the majority of what you need to know about HTML in just a few hours. (It’s CSS that mortifies with its learning curve.) If text is meant to be a heading, there is a semantic (or logical) tag to create a heading element: h1, h2, h3, h4, h5, h6. Creating a bit of text that is big and bold and merely looks like a heading in a computer monitor is not the same thing. Why? Because the heading element carries the semantic meaning “this is a heading” as part of the markup. And that meaning attaches to the text no matter where or how the text is accessed: a computer monitor, a screen reader, a handheld, a cell phone, a printer.

Another way to think about it is to realize that HTML tags are self-describing. The tag itself explains the logic or semantics of what it is meant to markup. p describes a paragraph. li describes a list item. cite describes a citation. strong describes strong empahsis. See how that works?

Using the tags to create semantic meaning makes your content usable in any Internet-capable device with the logical organization carried with it.

In the move to separate content from presentation (or meaning from appearance) the first requirement is solidly structured semantic HTML. CSS can do literally anything with appearance, as long as there is a logical structure to the content that will hold up no matter how the content is styled. Without the proper HTML semantic underpinning for your content, no amount of CSS can make your page work in multiple Internet-capable devices.

In the world of semantic content, a table is used to display tabular data, a list is marked up as a list, indented text is only marked up as a blockquote when it actually is quoted material, text that needs emphasis is marked up as an em element, and so on through the logic of every HTML tag.

There is room for discussion about what element is semantically correct as markup for a certain bit of content. The lively discussions on topics about the best semantic markup for certain types of content at Simple Bits/Simple Quiz lead Simple Bits’ Dan Cederholm to write two excellent books about semantic markup: Web Standards Solutions and Bulletproof Web Design. If you want more detail about the topic, pick up one of those books and get the complete story.

Technorati Tags: , , , ,

Event: Web Accessibility Primer on WCAG 2.0

The Scottish UPA events date is May 23, 2006, not much advance warning to arrange a trip to Scotland, I know. Look all the way down the page for future events in the planning stages in the UK.

Out of four listed speakers for this event, two are women! But who’s counting?

Technorati Tags: , , ,

WaSP Accessibility Task Force Manifesto

Manifesto – The Web Standards Project: “Since its inception in 1998, the Web Standards Project (WaSP) has been campaigning for the general adoption of web standards. While great progress has been made in getting browser manufacturers, web designers and even some authoring tool developers to understand and leverage the advantages of standards, there still remain crucial parts of the “web equation” to be tackled.

“Assistive technologies (such as screen readers) that some people with disabilities use still do not consistently take full advantage of the possibilities offered by standards-compliant markup.
Sophisticated and expensive content management tools produce poor-quality, non-semantic, inaccessible markup.

“A lot of authoring software (including CMS and blogging tools) cannot be easily used by people with disabilities, because they don’t conform to Authoring Tool Accessibility Guidelines (ATAG) – the W3C recommendation for web authoring tools.
Corporations and their web developers mistakenly believe that accessible web development is incompatible with branding and beauty.

“Those that do care are often sold expensive and erroneous solutions by that new phenomenon: the Accessibility Snake Oil Salesman – companies claiming a thorough understanding of web accessibility issues and promising “miracle cure” systems that automatically take care of them, but only delivering solutions which are anything but accessible.

“The rapid adoption of DOM scripting and AJAX introduces further problems with regards to support by Assistive Technologies.

“The Accessibility Task Force believes that now is the time to address these problems. We want to highlight the daily issues faced by designers and developers which perpetuate inaccessible processes and output, and work toward the swift eradication of these problems. And we want to change the focus of accessibility from simply quieting an automated tool to addressing the real barriers encountered by real users of all abilities.”

Read the full manifesto.

Technorati Tags: , ,

High Ed Accessibility Policies

WebAIM has a survey of Web Accessibility Policies (and Pseudo Policies) in Postsecondary Institutions: “The list of policies on this page is not all inclusive, but represents a broad
sampling of policies across the United States and other regions around the
world. Many of these policies can be more accurately described as suggestions
than policies, since many institutions do not have any binding formal policy.”

Technorati Tags: ,

Two new accessibility tools

Use GrayBit v1.0: Grayscale Conversion Contrast Accessibility Tool – Main Page – Presented by GrayBit to visually convert a full-color web page into a grayscale rendition to test contrast. The other tool is Colour Contrast Analyser 1.1 from the Web Accessibility Tools Consortium. The Colour Contrast Analyser is primarily a tool for checking foreground and background colour combinations to determine if they provide good colour visibility. It also contains functionality to create simulations of certain visual conditions such as colour blindness.

Technorati Tags: ,

IBM’s WebAdapt2Me

California State University (Long Beach) made the news as an early adopter of WebAdapt2Me. InTouch Newsletter, Vol. 14, No. 1: “California State University, Long Beach is the first university anywhere to adopt WebAdapt2Me, an assistive technology from IBM that removes barriers to reading for people with print disabilities. This software exploits the flexibility of web information to produce reading environments that exactly fit the reading needs of each individual. Students, staff and faculty who are not blind, but who still have difficulties reading at the levels demanded by university life, can now read documents on the web effectively.”

Other related links: IBM Case Studies and CSU: LB news.

Technorati Tags:, ,