1. Older people have difficulties with drop-down and multi-level menus, because their manual dexterity, eye-hand coordination and space perception decreases. Also some move the mouse when clicking, or tremble, hence it’s more likely they slip off the menu. Hell, that happens to me frequently!

   However, did you notice the Windows Start Menu is more forgiving when you slip off an item? There’s a little delay before the secondary level is hidden. Perhaps we need an event-capturing script tolerating a slip from the menu rather than the immediate reaction of the mouseout event.

2. Nested menus are more complex. According to Hick’s Law orientation in a multi-level menu can take longer than multiple clicks in a flat menu with good information architecture. See an earlier article for the math.

3. The navigation must be accessible by keyboard alone. The result should be the same, whether you hover over an item or tab to it. So check for the focus event and CSS pseudo-class. Don’t forget to test backwards tabbing (shift tab). By the way, mobile devices have no mouse either…

   The tab order should be consistent and logical, i.e. not jumping around on a page. Also the focused item should be visible, for example highlighted with the default 1px dotted border some browsers draw around it. Some people think this is ugly and remove the default border. That is a no-no.

   And if you really want desktop behavior, add support for the arrow keys (event.keyCode 37-40). Keep in mind though that screen readers have predefined functions for the arrow keys in combination with the ctrl, shift, or alt keys. In JavaScript those keys can be detected with the event.ctrlKey, event.altKey, and event.shiftKey properties. Also crossbrowser event delegation for focus or blur events can be a bitch, thankfully PPK has a solution.

4. Users of AT should have means to skip content. That’s possible with semantic markup: a menu as (nested) list(s) enables them to jump to the next block. Also there should be a few skip links at the beginning of the code pointing to important sections on the page, such as content, navigation, or search. Mobile users also profit from that technique (try surfing eBay with Opera Mini ).

5. Pages never link to themselves. When I click on a link (the menu being no exception) I expect to land on a different page. Therefore it’s confusing to land on the same page. This happened to me recently when I was filling out a form on my mobile phone and got the same page with an error message. It took me a while to realize where I was. It’s the same whether you have a tiny screen or a low screen resolution to see things larger when you are visually impaired: you only see a small part of the page, so it’s hard to realize when something unexpected happens.

6. You can add some semantic sugar with the ARIA role property. In this case <ul role="navigation"> would be appropriate. I strongly encourage you to use ARIA as it is widely supported by browsers and screen readers, enhances a disabled user’s experience, and doesn’t break old browsers. A most recent introduction has been written by Gez Lemon for the Opera Developer Community.

7. If a second level navigation is initially hidden with display:none it won’t be in the screen reader buffer. Therefore off-screen positioning is a better idea, else you need to update the buffer by writing random values into a hidden input field.

8. A common problem in menus is limited horizontal space. Text should be scalable, and it must not jut-out into other page elements when it is enlarged. Even normal text can break a narrow menu when you think of internationalization. In German there are many composite words. While building a website for a competing brand I came across a menu item on the Philips website for “male grooming.” The German word „Körperhaarpflegesystem” is guaranteed to blow every menu!

   Another common problem that prevents scaling in menus are text graphics. I know marketing just loves to see the corporate font in the main menu, but text in images can’t be scaled, people with visual impairments can’t change text and background colors for higher contrast, and Flash Image Replacement like sIFR still has accessibility issues, is known to distort fonts, is CPU intensive and slow. The bottom line is: don’t use text as images, make textual information text.

So much for accessibility. Besides there are a few technical issues to consider: mobile devices often have problems with JavaScript or with layers. Some proxies in large companies filter JavaScript for security reasons, so you can’t rely on the ubiquitous availability, your script has to be unobtrusive, and you can’t rely on noscript either. Don’t even think of creating a menu from JavaScript arrays.

Moreover there’s a well-known bug in IE6 responsible for showing select lists always in front of any layers (like your second level menu), regardless of a z-index. Thankfully there are plugins like bgiframe for jQuery to solve this. Multi-level menus can bloat the code, event handling can be CPU intensive (use event delegation). And if large amounts of menu code is at the beginning, the real content gets further behind and less relevant for search engines.

In conclusion, for an alleged quicker entry you pay with many disadvantages. Often drop-down menus just conceal a poorly planned information architecture. I would reconsider their usage.

Did I forget something? What’s your opinion on drop-down menus? Love them or hate them?

In this article

• Introduction
• Installation
• FAQ
• Changelog
• Discussion

Introduction

I always wanted to implement one thing since I started the blog: a simple inclusion of Amazon items. I didn’t want to search through results that existing plugins provided. When I wrote about something like a book, I already used machine tags to identify the subject! So I found the inspiration to write my first real WordPress plugin: Amazon Machine Tags.

Here’s what it does:

1. It identifies any tag in the machine (or triple) tag form book:isbn=1234567890 or amazon:asin=1234567890. That works with native tags from WordPress 2.3 and later, Bunny’s Technorati Tags, Jerome’s Keywords, or as inline text (see below).
2. Then it gets the item information and a thumbnail image from the Amazon Web Services API. That’s the real thing including prices and such, no cheap RSS feed.

3. The item(s) are displayed in the sidebar or in a blog article with a link to the visitor’s best match (if the ip2country plugin is installed) or a default Amazon shop of your choice. See examples in the sidebar.

   The “best match” is based on the visitor’s location. If she is from one of the six countries where Amazon has shops, that locale is chosen. If he is from Europe, the preferred language is matched to either France, Germany, or UK, with UK as default. If it’s neither a locale nor Europe, amazon.com is the default. Based on your location, do you think that’s a reasonable approach?

   Note that some items, like books in any language other than English, are only available from certain locales, so a visitor from the UK might not see German books you recommend.

4. If you are an Amazon Associate for that locale, your Associate ID is included automatically.

You can edit the server-side, semantic and valid XHTML output via XSLT, change the CSS, or translate the admin interface through .po files. Actually Amazon loads the XSLT file from your server and processes it on theirs, so you shouldn’t block HTTP access to the plugin directory, and localhost doesn’t work either.

Results can be cached for anything between one second and one hour, so you don’t need to worry even when you run an extremely popular blog.

The YUI Connection Manager is included to verify the Access Key in the admin interface via REST and unobtrusive AJAX.

I hope this little piece of software serves you well and you like it.

Installation

1. Get the latest version of the plugin from the WordPress site.
2. Upload the whole amazon-machine-tags folder into the /wp-content/plugins/ directory.
3. Activate the plugin through the “Plugins” menu in WordPress.
4. Get an Amazon Web Services Access Key.
5. Create a wp-content/cache/ directory with permissions set to 755, or 777 if you create the directory as root user.
6. Put <?php AMTAP::get_items(); ?> in your sidebar and start using machine tags.
7. Edit amtap-blog.css if you like.
8. If you want to use tags in a blog article, write [amtap book:isbn=1234567890] or [amtap amazon:asin=1234567890]. Thanks to paulinepauline for that idea.

Frequently Asked Questions

Does it work in the sidebar on Pages, too?

Posts have tags, pages don’t, so it doesn’t work on those by default. But there’s a plugin called tags4page that enables tags for pages. Works like a charm.

Is there a limit of how many items can be requested?

Yes, Amazon has a limit of 10 items per request. Since they are separate requests, you can use a maximum of 10 items in the content plus a maximum of 10 in the sidebar.

Would it be possible to cache the images?

Technically it wouldn’t be a problem, but the Amazon Web Services license explicitly forbids caching of images (see 5.1.10). Sorry.

I need to a larger thumbnail (medium), but can’t seem to find a place to edit the size of the image being requested.

The image size can be edited in the XSLT. The original result is a XML file that is transformed by Amazon using your local copy of amtap-html-sidebar.xsl and amtap-html-content.xsl, respectively. Replacing every occurance of .//aws:TinyImage with .//aws:MediumImage should do the trick.

You can view the original XML when you activate the “debug” option in the admin interface so that the request string is printed as a comment in the sidebar’s source code. XSLT is a very powerful tool, and there’s a lot more in the XML, for example customer reviews.

Are all options really required?

No. The only required field is the Amazon Web Services Access Key. You can leave the others, they are set to defaults then.

Changelog

• 3.0 (2009-07-31): Added signed requests for the new Amazon authorization requirement. Updated the API version to 2009-07-01 (please note: if you use your own XSL files, you must update the version in the XML namespace URL). Updated links.
• 2.0 (2008-07-18):
  1. Added fields for editing the sidebar headline, link target, and displaying rating stars.
  2. Added an error message if the plugin is run from a private IP address space like localhost.
  3. Changed priorities for price selection, they are now: LowestNewPrice, ListPrice, first offer, LowestUsedPrice.
  4. Added support for the display of an artist name.
  5. Added rating stars.
  6. Fixed EAN numbers with a dash.
  7. Fixed cutting of titles after a period.
  8. Changed CSS and XSL files. Take care when you edited those.
• 1.1.3: Changed amtap-admin.css and amtap-admin.inc.php to make the admin interface look prettier with WordPress 2.5.
• 1.1.2: Fixed a bug in amtap.php when there are no other tags but default tags.
• 1.1.1: Fixed the sort order of inline items, a bug for returning an error message when the cache file is not writable, and added Amazon’s limit of 10 items per request.
• 1.1.0: Fixed the display of inline tags on the home page. Improved regular expression for filtering inline tags.
• 1.0.6: Fixed a bug introduced through the new default items function when there were no items to be displayed in the sidebar.
• 1.0.5: Added an option for default items on every page. Changed amtap-html-sidebar.xsl to sort items in the order of the request.
• 1.0.4: Bugfix for replacement of dollar characters in content. Also content items are now cached separately.
• 1.0.3: Fixed the display of inline tags on category pages.
• 1.0.2: Changed the plugin path from amtap to amazon-machine-tags for consistency with the file structure in the zipped file.
• 1.0.1: Bugfix for native WordPress tags.

South by Southwest (SXSW) is a huge conference for interactive media as well as a film and music festival in Austin, Texas, March 7-11, 2008. Every year it attracts the best designers and developers, and there is an immense number of panels to choose from. Exactly 128, out of which 80 are chosen from an open submission process.

Gez Lemon and I plan to run a panel called “Get Rich, Remain Accessible,” naturally about WAI ARIA (Accessible Rich Internet Applications). Gez wrote a great article about ARIA liveregions, and I wrote that article at A List Apart, so it’s the perfect team. Together we would like to present:

1. The accessibility problems introduced by the current trend of web applications,
2. new ways to add semantic meaning, communicate importance, define relationships, and give focus to elements using WAI-ARIA,
3. how to limit the impact of these problems whilst WAI-ARIA is gaining support by user-agents, and techniques that work right now.

It would be nice if you took the time to vote for us at the SXSW panel picker application. The voting process is open until 11:59 pm, September 21. If you push our presentation to the top 80 you will ensure Gez and I actually make every effort to attend the conference as we will get free tickets for ourselves. Spread the word …

The W3C’s standards draft for Accessible Rich Internet Applications (ARIA) addresses those limitations. It provides new ways of communicating meaning, importance, and relationships, and it fills gaps in the (X)HTML specifications and increases usability for all users by enabling navigation models familiar from desktop applications. Best of all, you can start using ARIA right away to enhance the accessibility of your websites.

I held talks about the upcoming standards in Cologne and Frankfurt, which resulted in writing a blog entry about the topic that eventually became an article for A List Apart.

Update: there’s also a German translation of the article at Barrierekompass.

If you’d like to learn more I’ll be speaking at the BarCamp in Frankfurt on April 21-22, and the Infopark Internet Congress in Berlin on May 11th.

In this post:

• Dan Cederholm: Bulletproof web design
• Robin Christopherson: Beyond a code audit
• Cameron Moll: Mobile web design
• Nate Koechley: Yahoo! vs. Yahoo! vs. Yahoo!
• Tantek Çelik: Microformats: evolving the web
• “Hot topics” panel
• More presentations

The evening:before featured another get-together in a fancy work:after club, which can be summed up like this: Sweden won against Paraguay, and it was hard to talk to others because some notorious DJ wouldn’t turn down the volume. He desperately tried to get somebody on the dance floor switching from house music to r&b pop, but didn’t realize that was not what the audience wanted.

Bulletproof web design

If there was an award for best presentation, Dan Cederholm would get my vote! His slides were so well-designed, so clean, and the special effects (not seen in the PDF version) contributed to clarify the scope.

It was like Jeremy Keith’s presentation the day before, where you knew all the things he was talking about, still something made “click” and shifted your perception — and if it’s only that you think “that’s what I always needed to show to my designers!”

Scene from the early computer game Dig Dug (Atari 1983), where you pump up monsters until they explode

His example for thinking ahead showed a photo of a new warehouse in San Francisco, where the windows had been inserted to be future proof, but cemented over for the current use. So think ahead, because content amount and text size may vary, content changes and needs to be maintained, and because the environment can change. Take something off, like images, CSS, or JavaScript, and make sure the website still functions.

“The journey begins by letting go of control, and becoming flexible.”

John Allsopp, “A Dao of Web Design”

A lot of his examples worked by setting a 50% value for the horizontal or vertical background-position in combination with overlapping images, and he introduced the term “Dig Dug Text Test” as a metaphor for pumping up text and assuring the design is still not destroyed. Reminder to self: add more references to early 1980’s games in presentations, they are so cool!

Beyond a code audit

Robin Christopherson’s bad karma was that he relied on the unreliable wireless network in the conference center, therefore a few examples from the web refused to work.

But by struggling with the technical constraints he set a real-world example for the attending web developers. Robin is blind, and he did not notice the Windows XP bubbles popping up once in a while trying to alert him that the network was unavailable. He was unable to login on the QE2CC screen, because it was inaccessible and refreshed too often. Also most people I spoke with were deeply impressed by the incredible speed his screen reader was set to.

He had also prepared a couple of educational films about challenges on the web for people beyond the visually impaired, like a woman with learning disabilities who didn’t understand the word “disclaimer,” or a quadriplegic with a mouthstick and a voice recognition system, which was useless when the alt text in images or Flash applications did not match the displayed text. I know what a tremendous amount of work the production of such little films is, and I’m looking forward to access them on Robin’s site. Also check his speaker’s notes.

Mobile web design

Cameron Moll mentioned a few times that he had held this presentation a year ago. Therefore it was very professional, very slick, but a little unemotional and in my opinion not quite up to date.

Okay, there are more mobile phones than computers, more mobiles than landline connections, but he didn’t stress the incredible impact the wide adoption of Opera supporting JavaScript on cellphones will have. That’s finally a common platform for web applications using Ajax, as opposed to hundreds of different implementations of Java which are almost impossible to test. That’s a most remarkable development with the potential of revolutionizing mobile applications — Cameron hardly mentioned it, although this became public in November 2005.

Of course WML is dead, long live XHTML MP! You should serve content from a .mobi domain and concentrate on the contextually relevant information: People might check their eBay watchlist on their cellphone, but they don’t upload items to sell, so ignore features like that when developing for mobile devices.

Also my question about Vodafone and other carriers inserting invalid code in the pages they serve through their proxy might not have been clear enough, because Cameron replied it’s up to the carriers and the browsers how to interpret pages, while developers can control the code.

Unfortunately that’s untrue when carriers compress images more and insert JavaScript to get the original images with higher resolutions with a key combination. One script is inserted with the deprecated language attribute in the header, while the other comes after the closing </html> tag, thus rendering your valid XHTML strict code to tag soup. The problem not only manifests on mobile browsing devices, but also when you surf with a regular notebook using your mobile access. Therefore a @media handheld CSS, browser sniffing, or serving the MIME type depending on the HTTP accept header are all doomed. And there’s no way to prevent the carriers from doing such evil.

Yahoo! vs. Yahoo! vs. Yahoo!

I went to this presentation because Nate Koechley recently published his smart concept paper about graded browser support, which we immediately adopted. What I didn’t expect was a most impressive roller coaster trip through browser performance!

Yahoo! has a beta version out for their new portal, also Yahoo! Photos and Yahoo! Mail is under development. All of them make more or less heavy use of DHTML and Ajax. Yahoo’s goals were increasing performance by 300%, adding interactivity (vulgo: drag & drop), and supporting web standards.

For a fast response they used techniques like CSS sprites, or memory management. In Nate’s words browsers are still “a pain in the ass,” and “the web is the most hostile software engineering environment imaginable.” DHTML leaks memory like a sieve, so for each constructor use a destructor. Instead of adding events to thousands of email objects Yahoo! used the existing document.onmousemove event and checked if the mouse was over an object or white space, then passed the event to that object or drew a rectangular choice box. Key concepts are conservation, destruction, and recycling iFrames (about:blank). Use Drip as a tool for measuring memory leaks, test extreme object counts, test long interactions, and test extensive navigation.

Also their developers prefer JSON over XML because parsing XML degrades performance greater than linear as XML size increases.

They have identified HTTP requests as a main performance killer. Browsers still only process two or four HTTP requests at a time, especially start pages are not cached as effectively as they imagined, and parsing JavaScript freezes the browser. Therefore they rather serve a single large file with CSS in the header, and JavaScript as close to the </body> tag as possible.

Regarding browsers it is faster to develop for standards, than patch. Browser support must not be binary, and it does not mean “the same.”

Expecting two users using different browser software to have an identical experience fails to embrace or acknowledge the heterogenous essence of the Web.

There are more IE5 browsers out there than IE 5.5, and IE7 “already moved the needle.”

With all the DHTML and Ajax I was concerned about accessibility, but in a sidenote I almost missed Nate mentioned the IBM contribution for DHTML accessibility. Wonderful!

Microformats: evolving the web

When microformats are even on the radar of Bill Gates, how could I ignore them? I had no clue before Tantek Çelik’s presentation @media 2006, and now I’m implementing them in this post. Microformats are virulent.

Basically you insert a few class names into your code, like

1. <p class="vcard">
2. <a class="url fn"
href="http://tantek.com"> Tantek Çelik</a>
3. </p>

There are microformats for contact cards, calendars, reviews, geo information, and many more. Even the Creative Commons license and the PICS label implemented in this page count as microformats. XFN and XOXO, too.

You can parse this page through a Technorati contacts feed service or use a tool like the Tails extension for Firefox, and voilà, there’s a vcard you could import into your address book (if there wasn’t this Thunderbird bug which prevents exactly this). With the hcalendar microformat you synchronize your calendar with event schedules on a website accordingly.

There are a few issues I ran into when I implemented hcards, and the documentation could have more examples, but they are on Tantek’s to-do list. Also sometimes it means extra, non-semantic markup, but as microformats increase semantic meaning, I assume it gets Tim Berners-Lee’s blessing. So go for it, microformats are definitely among the web’s next big things!

“Hot topics” panel

I had the pleasure to meet Molly Holzschlag earlier in a coffee break, and while I was sorry I couldn’t attend her session I18N, awakening the sleeping giant, I’m confident I didn’t miss much information as I am pretty familiar with her old articles in her regular column in WebTechniques and the current activity of the W3C I18N group, where she is a member.

Jens Grochtdreis reports in his blog about the passionate presentation she gave earlier, and although there is more technical experience and awareness in Europe with multilingual websites, rarely they pay respect to cultural differences, like the meaning of colors. Molly gives everything to educate on I18N and promote web standards, she is also a member of WaSP. I’m glad she seems to have found a way to get some help and support, as she is an outstanding, but sensitive person.

Anyway, she was part of the “hot topics” panel, where questions from the audience where considered by a group of experts: Molly, Jon Hicks, Jeremy Keith, Eric Meyer, and Tantek Çelik. They had a lot of fun and agreed CSS has become more mainstream in the last year, as you don’t have to defend CSS against table layout anymore. Well, reading the discussions in German forums and reviewing the code of other websites, there’s still a lot of educational work to be done. Also they talked about the accessibility of Ajax, and mashups as the next big thing, but you can read a decent transcript of the session in Stuart’s blog over at Muffinresearch.

Conclusions

If you have followed me this far, you can see @media was a big inspiration, it was a lot of fun, especially the after event on Saturday, and I can only recommend the conference! There are endless flickr pictures and quite a few blog entries on Technorati if you need further impressions. Um, and never mind the British food …

More presentations

Here are the presentations in the parallel track I couldn’t attend. Also there will be pod- and videocasts available soon.

• Dave Shea: Fine typography on the web
• Andy Budd: Bug hunting
• DOM Scripting: The Next Level
• Andy Clarke: The fine art of web design

In this post:

• Eric Meyer: Keynote
• Jeremy Keith: Using DOM scripting to plug the holes in CSS
• Chris Wilson: IE: 7 and beyond
• The new accessibility guidelines: WCAG 2.0
• Jeffrey Veen: Designing the next generation of web apps

Introducing geeks to a social life

There was some socializing the evening before the conference where I met with a couple of Germans, like Jens Grochtdreis who initiated the German web standardista group “Webkrauts”, Jan Eric Hellbusch whose website I had noticed before for some master theses about accessibility, or Tomas Caspers who is a member of WaSP and the mastermind behind the accessibility portal Einfach für alle. Actually I wasn’t the only one to notice he looks like the lost fifth member of the German punk band “Die Toten Hosen”?… Also that’s where I met Roger Johansson, whose technical blog 456 Berea Street is a must-read for CSS and accessibility aware coders.

So my first day on @media began with a walk through polluted London air along surveillance cameras and anti-tank barriers along the Houses of Parliament over to the queue in front of the Queen Elizabeth II Conference Center (QE2CC) where we got nice bags and name tags. I would suggest shawls with the @media logo for next year to stand a chance against the bloody cold air conditioning while it was 28° C outside.

Eric Meyer: Keynote

The conference started with a keynote by Eric Meyer with his personal impressions of the last ten years of the web. Quite interesting since I’ve been reading his articles on Web Review, where he published among other things the famous CSS browser compatibility chart, a great companion in my struggle with 4th generation browsers.

Looking back, he realized the following truths:

1. Small groups of dedicated experts can change a lot (e.g. the CSS Samurai, or Tantek Çelik who introduced doctype switching).
2. Free information is an essential part of any new web technology’s adoption.
3. You don’t hear much anymore from people or companies who kept information as a “personal advantage.”
4. You might be the first who thought about a certain solution. Savour this moment, and then share it.

Using DOM scripting to plug the holes in CSS

As an example, Jeremy Keith introduced the techniques of Buck Owens, the first musician to “hack” the tinny sound of early radios by replacing the bass with a regular guitar. So his tracks sounded better and got more airtime. Using DOM scripting to work around incomplete CSS implementations or to simulate CSS 3 behavior is basically the same, as long as there aren’t yet browsers with “great bass.”

Okay, most of the stuff in his presentation sounded familiar, and I’d rather set zebra stripes on table row backgrounds server side. Still I got some inspiration how to do some things better. For example it never occurred to me to combine selectors like

1. document.getElementById("id") .getElementsByTagName("p")

Or I never thought of using a universal selector in JavaScript:

document.getElementsByTagName("*")

Also the next time I’m manipulating an object’s class, I promise to do it by writing some reusable functions like

1. document.getElementByClassName()
2. function addClass(element, className)

And after I createElement I should set more attributes by setting a className instead of adding each attribute separately.

When he mentioned CSS 3, I learned that Safari is already capable of handling multiple background images. And I liked his introduction of the geeky Star Trek term of a “Kobayashi Maru scenario” for a no-win situation, or his translation of object detection

1. if (document.getElementById) { }

with “you must be this high to ride.” Rather cool, and a very entertaining presentation.

IE: 7 and beyond

Chris Wilson worked on the Mosaic browser (that’s, like, Netscape 1 — scary, isn’t it?) and on IE ever since version 2. Praise him for first implementing CSS in IE3, blame him for some nasty bugs he’s personally responsible for in IE6. Also he’s the one who wrote he will quit (and probably become a professional surfer) the day he loses his passion or IE gets mothballed again.

After some blatant promotion for all the outstanding new features and fixes in IE7, things you can read about in the IEBlog if you haven’t yet, he came to the interesting facts:

First of all, they are planning the next two releases now, and it won’t take another five years until IE8 will emerge. Also IE7+ for Windows Vista is only marketing speak, what counts is that it has the same features as IE7 for Windows XP, except for some vista-only security and parental control. IE7 will ship in “second half 2006.” More precisely, the Malaysian Vista developer Jabez Gan disclosed earlier that December 6 will be the release date.

Because of the deep interaction with the operating system they can’t push it as a critical Windows update, but they will “strongly encourage people to update.” The new fonts won’t be deployed with the update, more likely in a separate package, simply because with Unicode support some are too large.

On a technical side they are aware of developer’s problems to test on multiple versions of IE. Though it is technically hard to have a friendly co-existence of multiple IEs because they provide the operating system, it should be possible to create side-by-side versions of the browser only. Yay, that’s what we want!

Also they would like to support the XHTML MIME type, but want to do it right, later. Same is true for advanced DOM support, or passing the Acid2 test. What’s next for the web? Mashups, RSS, microformats, and XMLHttpRequest (did you know there’s a W3C working draft?). XForms is on their radar, but they need to coordinate efforts with other browser vendors.

Besides Chris recommended some tools like an expression finder to spot CSS hacks, or an application compatibility toolkit, stuff you can download as part of the Internet Explorer 7 Readiness Toolkit from Microsoft with a genuine copy or from someplace else without.

The new accessibility guidelines: WCAG 2.0

I had hoped that by visiting the panel about WCAG ['wu:kæg] I could avoid having to read the unreadable myself, but I was disappointed. You will read in another post about it. Not much else to tell about that panel, except WCAG 2.0 is probably not as bad as we have thought. There are notes and the slides available on accessify.com.

Designing the next generation of web apps

Jeffrey Veen is the partner of Jesse James Garrett who gets all the attention for coining the term “Ajax.” Anyway, Ajax is so going to change our world. Like the automobile, or the Great Depression. Some will get more mobile, some will get greatly depressed when the web becomes inaccessible.

In another panel the speakers agreed that Ajax can make live easier as an enhancement (Jeremy Keith calls it “Hijax”), but shouldn’t be a world of pain for the others. Actually I can see some of Jeff’s examples (use Stuart Colville’s notes to understand the slides) as an enhancement. Like giving immediate feedback when input fields in a form validate, while degrading gracefully by giving feedback after a regular submit.

You can enhance understanding by coloring and visualizing rainfall values in a nicely designed table, or you can further enhance it by making it interactive with a fader to choose cities on a map. But I can’t imagine how to have both.

In another example he showed a mashup of Google Maps with a Chicago crime database. Nice, but how can that be made accessible? So that people without JavaScript, or screen reader and braille display users with JavaScript can access the raw data table that lies under the visualization?

There was a lot of talk how today’s websites will be tomorrow’s web applications, but like Nate Koechley put it: You can’t just copy one aspect of desktop applications while ignoring the accessible alternatives. Desktop applications are accessible with multiple input devices, like a mouse or a keyboard. Screen readers can get the content. Don’t you forget it when developing the “next generation off apps.” There’s more than just good looks.