Thursday, February 4, 2010

Do You Think Nami Is Hot?

Il redattore, tecnico dell’accessibilità

di Alessandra Repetto

Avete mai provato ad ascoltare un sito?
Bisognerebbe sempre "ascoltare" una pagina web: è il primo passo per capire cosa significa davvero accessibilità.

I non vedenti per navigare in internet usano gli screen reader, delle periferiche speciali che traducono il sito in linguaggio vocale.
Oltre alle sintesi vocali e alle barre braille, ancora troppo costose e poco diffuse, esistono anche altri dispositivi in via di perfezionamento: emulatori di mouse, tastiere espanse per i disabili motori, input vocale.

Un buon redattore sa che ci sono persone con diversi handicap: gli utenti possono essere persone cieche, ipovedenti o daltoniche, quindi è importante usare colori contrastanti per sfondo e scritte, come anche caratteri di dimensioni sensate.

A chi ha problemi uditivi è importante fornire sempre un'alternativa testuale ai file video e audio.
Un esempio: sto guardando un sito istituzionale di una pubblica amministrazione (quindi un sito che per legge deve farsi capire da tutti), e in particolare una pagina che riguarda gli Italians abroad.
I see: a band graphic where it says "emigration," a short introductory text and a picture of the early years of the century that portrays a community of immigrants in Argentina. The drive
voice reads the same page like this: "Bar A CHAPTER CONTRIBUTIONS COMMA COMMA THE MEASURES TAKEN BY THE GOVERNMENT AND MUCH MORE HARVEST FESTIVAL IN PAMPA ARGENTINA USEFUL INFORMATION FOR ITALIANS ABROAD POINT."
was the task of the editor to say / write that page that clearly speaks of emigration, also translate text in the contents of graphics bandwidth, to say that there is a photograph of the first century that depicts a harvest festival in the pampas of Argentina. Making a site

accessible - which basically means to adhere to programming standards - is still to everyone who is connected with a regular browser, rather than those using a WAP phone or a voice converter.

The official reference regarding web accessibility for disabled people are the WAI guidelines (Web Accessibility Initiatives) W3C (World Wide Web Consortium), which are based on an assumption in mind: Everyone should be able to access a site. There must be some sites specially created for the disabled, but each site should be accessible to all.

The rules are strict to ensure accessibility: the html code must be applied properly and the pages must be validated one by one, by hand, with the software (called, ominously, "validator") made available by the Consortium, to detect any unevenness in the code. From this point of view put under a site that is a rather mechanical.

While making a site accessible essentially means applying the provisions of the W3C in terms of code, many aspects of accessibility of direct concern to those who deal with texts and design is not only a code of "dirty" to make little access a page, the number one enemy of a site is bad writing. To this the editor is the true technical accessibility: it is the fault of a page who can not "talk", as his is the merit of a site that becomes a reference point for the entire community of surfers ...

0 comments:

Post a Comment