accessibility

Page Accessibility Evaluation Tool from Acid.JS

ACC.Checker.JS is a free tool designed to evaluate page markup and help you identify accessibility errors. According to the selected options and stringness, ACC.Checker.JS will look for missing alt attrbiutes on <img /> tags, title attributes on anchors and accesskeys. The tool will also check if your readiobuttons or checkboxes are supplied with label tags and if the fieldsets in your forms are described with a legend.

ACC.Checker.JS has two modes of operation – automatic (when page loads) or manual (upon user click action). The manual mode can be used to detect accessibility flaws on markup generated on the client with JavaScript, after AJAX, DOM changes and actually any modifications to the source code after page load.

When evaluation is finished, ACC.Checker.JS displays the report in a convenient Web 2.0 way and provides link with additional information about every accessibility error it has encountered.

List of Detected Common Accessibility Errors

  • Missing or empty alt attribute on images.
  • Missing or empty title attribute for links and button elements.
  • Missing label tags for radio buttons and checkboxes.
  • Missing legend tags for fieldsets.
  • Missing summary attribute on tables.
  • Missing or empty title element on the page.
  • Missing or empty accesskey attribute for button elements.
  • Obtrusive JavaScript event handlers (onclick, onmouseover, etc) in markup.

View ACC.Checker.JS demo or download it. The tool is also included in the latest version of Acid.JS Web 2.0 Component Library. User’s manual and help is available on this page.

Advertisements

UX – Abuses, Misuses and Misinterpretations of the Term

* This post does not aim to offend real UX engineers, it is just my personal view as a professional developer, based on a 7+ years of experience in the field of web development.

In the era of the highly misused and rather vague term Web 2.0, being a UX engineer (also – expert, guru, developer or whatsoever) has become a quite fashionable occupation.

Unfortunately, neither most of the employers, nor the future UX guru employees do not even have the slightest notion of what stands behind the two letter abbreviation, which soon leads to persisting conflicts between UX persons and developers.

A typical UX job description that may be found in job ads reads:

The company X is looking for a skilled User Experience developer with expert knowledge of PhotoShop, FireWorks or other design software.

And not even a word about usability, accessibility, code semantics and front-end development skills.

UX is not a lonely island in the ocean of web development, but rather a collective term for expert skills in:

– Usability
– Accessibility
– User Interface design
– Strong front-end programming (xhtml, css, javascript) skills
– Code semantics
– Sound knowledge of web standards, best practices and strategies
– Wireframing and prototyping
– User testing

The UX developer with strong design skills is hired after an interview on which developers are not invited, and in a few days the devs receive the first work of the new UX expert – in most of the cases a bulky graphic file with absurd, strange and unusual design, a living hell for the front-end developer, who is responsible to port this Web 2.0 beauty into a beautiful, accessible and usable code.

The first conflict – if the front-end developer is a really experienced professional, he or she asks for a meeting with the UX guru where he talks to him or her and politely advises them to reconsider the design, as it has nothing to do with the good UX practices. The UX person feels offended and tries to defend, and points out exactly those unusual characteristics of his design, which makes it a real piece of Web 2.0 art. Afer a few attemtps, the front-end guy gives up, codes the design, gives the templates to the back-end developers, and finally the application, along with its state-of-the art design and UX is online.

And then come the support tickets from angry customers. Users complain about the unusual layout, complain that they get lost in the sloppy (pardon – Web 2.0) navigation, etc. And guess whom are such support tickets assigned to? To the back-end developers? No, their server code works like a charm. To the UX engineer? Of course, not – he or she is responsible for the design only, and that particular design has been approved for coding from his or her team leader or boss. To the frontend developer? Exactly, right to the point. And everything starts over. The frontend person tries to explain to the UX person the most common web-design strategies, mentions of Jacob Nielsen (I am sure that 70% of those who call themselves UX engineers have never heard of him) and finally, after the usual verbal battle the front-end developer gives up, the back-end guys give up as well, and the compaining customers are assured that the UX issues have been logged in the bug tracking system and will be fixed soon (i.e. never, or close to never).

Next, there comes the moment, when the UX guru, having acquired enough confidence in their misunderstood UX skills decides that the company he or she works for, and especially the evil developers are against him or her and quits. The UX specialist knows that UX is a fashionable occupation and he or she will not remain unoccupied for long.

But the legacy of that UX work remains, and the support tickets keep coming, and soon the team, responsible for the development of the product with the killer Web 2.0 features finds themselves just before a total redesign and reconsideration of the code, its semantics, accessibility, usability, etc. But this time without alleged UX developers and other Web 2.0 gurus.

UX is not an occupation or job description at all. Once more – UX is a collective term for skills that are not studied at school or at university, but acquired at work, the very result of the experience on the web.

Writing my First Book on Web-development

A few days ago I started writing a book named XHTML, CSS and JavaScript: Introduction to Modern Browser Programming, Semantics and Accessibility of the Code. It covers the contemporary techniques and strategies of writing modern, semantic, accessible and valid xhtml code and unobtrusive javascript. You may register for an early preview of the book on my email – info@wemakesites.net