Minggu, 23 Januari 2011

WCAG 2.0 Moves To Proposed Recommendation


So the big news of this week wasn’t the result of the US Election, it was the news that the technical material of the Web Content Accessibility Guidelines 2.0 (WCAG 2.0) has been completed and real world example implementations have been provided for all of the guidelines / success criteria. This is great news and means that WCAG 2.0 has now moved on to being a W3C Proposed Recommendation.


The next, and final stage for WCAG 2.0, is final publication which is expected to happen in December 2008. We will then have a modern, stable set of guidelines to reference as an alternative to the ageing WCAG 1.0.


Further Reading


Examining WAI-ARIA Properties




I have updated the accessibility extension to display all WAI-ARIA properties.



ARIA Properties



I've added a function to the toolbar to display all ARIA roles and properties defined in a document. The properties are displayed in a new tab, along with the value of the property, the element the role is defined on, the parent nodes, and the markup fragment. The following is example output from running the function.




List of ARIA properties and their values, along with the parent nodes and markup fragment in a table.




The properties functionality is a catch-all to report all ARIA properties. The toolbar can highlight live regions, document landmark roles, and general roles individually.



"

Hidden barriers: multiple links in headings


Most of you won’t believe what I’m about to describe, and would never use heading structure in this way. This post isn’t for you, it’s for the people who believe that it’s OK to wrap several links inside a single heading tag, or in fact use one heading to enclose one or more other elements or types of content .


If you find this difficult to comprehend, you aren’t alone, it came as an enormous surprise to me too, but I’ve recently seen four different sites using one heading to enclose at least one other element.




The problem this causes is that because heading markup is meant to enclose a single entity, a heading, and screen readers announce the beginning, the end and the level of each heading, whatever is inside the opening and closing tags gets announced as a single item.


Example 1: several links inside one heading


When several links are placed inside a heading, tabbing to any of the links causes screen reader announcement of all links, so the user has no idea which link has focus. If you have access to a screen reader check it out yourself.


Link 1 Link 2 Link 3 Link 4


For those without a screen reader, the output when the focus is on Link 1,is “Link 1 Link 2 Link 3 Link 4 heading level 4 link”. Tabbing to the second, third and subsequent links produces identical output.


I believe that the web authors who created the live example, probably wanted to mark up the links to aid navigation. What they should have done is identify the purpose of the links, for instance “Site-wide navigation” and used that as the content for the heading markup, immediately before the first of the links. (Which of course should have been in a list.)


The code that produced this is:


<h4><a href=”#”>Link 1 </a> <a href=”#”>Link 2 </a> <a href=”#”>Link 3 </a> <a href=”#”>Link 4 </a></h4>


Other problems


The above example is among the worst that I’ve come across, but other mixed content within one heading can cause almost as much confusion, Recently encountered instances include:




  1. Using heading markup to apply a given style to an entire paragraph, including one or more links. This has a similar effect for screen reader users as the multiple links issue, but with the added confusion that the whole paragraph sounds as though it’s a link.


  2. Including an image within heading markup, alongside the valid heading text, (presumably to help with positioning). Any text value given to the image ALT attribute will be announced as part of the heading, even though it may have nothing to do with it.


  3. Including a related link within heading markup, for instance a heading “News” and its related “RSS feed” link both inside the opening and closing heading tags. This almost sounds as though it would be a good idea, but it isn’t. The benefit of having the heading, and thus the topic of the RSS link announced when the link has focus, is cancelled by the mis-information that there’s no “News” heading only a heading for “News RSS feed”.


So please just use heading markup for heading content. Not to enclose all of the content covered by the heading, nor for styling, positioning or link context.

Opera Web Standards Curriculum


From the introduction: “Learning Web Standards just got easier. Opera’s new Web Standards Curriculum is a complete course to teach you standards-based web development, including HTML, CSS, design principles and background theory, and JavaScript basics. It already has support from many organizations (including Yahoo! and the Web Standards Project) and universities. The first 23 articles are currently available, with about 30 more to be published between now and late September.”


This is excellent news. Hopefully it will lead to a better web. If you run a consulting company this could be a compulsory course for GUI developers.

Fangs for Firefox 3 available


Sorry for the delay. Here is an updated version (1.0.4) of Fangs for Firefox 3. Your previous version may not update automatically in which case you need to uninstall it, restart Firefox, and then download/install it from the Fangs project page.


A big thank you to Stuart Middleton who showed me the necessary steps to get rid of the annoying security warning that Firefox 3 displays for unsigned extensions.

Finnish quality criteria for public websites

Finnish quality criteria for public websites: "
The Finnish government has published their quality criteria for public websites in english. This makes it possible to compare your own national guidelines to thos of other countries. Quoting from the intro page:

The purpose of the quality criteria is:

  • to act as a tool for developing and assessing public web services
  • to improve the quality of public web services for both users and producers
  • to increase the benefits from public web services.


I have updated the Index of Government Guidelines page and search engine to include this version.
"

Swedish National Guidelines for Public Sector Websites


The Swedish National Guidelines for Public Sector Websites takes an integrated approach to usability, accessibility and standardization. The purpose of the Guidelines is to support the procurement, development, and maintenance of a website by a public administration so that it offers equal opportunity usage for all citizens. The 2006 version has now been translated to english.


Quoting from the announcement: “The Guidelines are divided into chapters which can be read separately depending on the reader’s role and responsibilities. The order of the chapters is intended to mirror the lifecycle of a website.



  • Chapter 1 covers the overall communications objectives of a website, which should be used as the basis for its development.

  • Chapter 2 presents the development process as steps towards a defined objective.

  • Chapter 3 shows methods for website design and web page coding, along with web standards.

  • Chapters 4 and 5 describe the basic content and services a website should provide, giving additional information on how to write for web-based media as well as methods for keeping the website up to date.

  • Chapters 6, 7 and 8 cover the development of web content for mobile devices, Content Management Systems (CMS) / authoring tools, and assistive technologies (AT).


A survey carried out in February 2007 showed that over 90% of those responsible for public administration websites in Sweden were aware of the Guidelines, with 80% or more actively using them.”


The Guidelines are published under the Creative Commons Attribution 2.5 Sweden license.