PUBLIC MARKS from Monique with tag webdesign

we present here some possible changes and improvements to WCAG 2.0, and items that we hope might help you better understand and implement optimal accessibility

But as a designer, I need to know the full range of options — and limitations — I have at my disposal when building a design for a client. jQuery presents some amazing options for design.

Le site rgaa.net présente sous une forme navigable et accessible les 187 tests de l’annexe 2 du RGAA.

Recently, Everett Zufelt posted an excellent blog post titled: Are You Confused by HTML5 and WAI-ARIA Yet?. In his post, Everett outlines a number of areas in which the evolving HTML5 specification and the WAI-ARIA specification conflict with one another in ways which can cause confusion among web developers.

It can seem brilliant to setup fancy animations and fade-in effects for each of your sub-menus. And with the jQuery UI library it’s never been easier to scale these out into your own solutions, either. But everything fancy and sleek will simply not fit into each design. The purpose of any navigation is lead visitors deeper into your website by the simplest methods possible.

Les référentiels, les checklists, les guides de bonnes pratiques sont avant tout des outils de prévention des risques.

With some simple JQuery, you can force browsers to give focus to the targets of skip nav links, plus highlight the target section temporarily so sighted users know they’ve arrived.

There is some controversy about the idea of sighted web designers and developers using screenreading software to test web sites for accessibility. Some people suggest one must use a screenreader to test their sites. Others believe it is counter productive. I think that very few sighted people can get the correct results by using screenreaders to test a website. I further think that too many people think that the accessibility testing is complete once they’ve used a screenreader on their website.

On le voit, le Web qui véhicule tant d'images est très mal servi par les navigateurs.

Les formulaires web sont encore et souvent négligés, parfois recouverts d’une couche graphique plus néfaste que pratique, et rarement considérés comme un puissant levier de transformation qu’il s’agisse de produit, de service ou d’information. Ce livre blanc a pour ambition de traiter cette problématique de complétion que l’on retrouve associée à chaque formulaire au travers d’une vision croisée entre accessibilité, ergonomie et esthétique.

The techniques in this article explain how we can leverage this powerful capability of CSS to also change imagery, alter the navigation on hand-held devices, and set up default CSS for compatibility older browsers.

Accessibility can often seem daunting and complex but in fact there are only four types of disability you need to be aware of. Through groupings, simulations and quick fixes, UX and accessibility consultant Ian Hamilton shows that the basics are actually surprisingly simple

Colors have a huge effect on readability. This is why you need to choose them wisely so that they not only create esthetically pleasing combinations but also make it easier for users to read the text. Text is an integral part of any site and we shouldn’t punish visitors for coming to our site by using hard to read color combinations.

I've created this page to attempt to convince you. It shows examples and lists six reasons why it's a good idea and three common arguments against them (some of which I refute).

Pour répondre à cette question voici nos trois experts du jour : Daniel Glazman, Karl Dubost et Raphaël Goetter.

I think vendor prefixes are hurting the Web. They are hurting Web authors. They are hurting users of browsers. They are hurting competition in the Web browser space. I think we (people developing browsers and Web standards) should stop hurting the Web. It would also make sense for browsers to implement other browsers’ prefixed features to the extent existing content uses prefixed features.