Archivi categoria: accessibilità

Comunicazione efficace!

Mi segno questi due link che sono state due buone letture dell’estate!

la prima è la mini guida sul pensiero critico, che aiuta ad esporre meglio i concetti ed a non cadere in errori logici comuni.

http://philosophy.hku.hk/think/resources/miniguide.php

ed ha anche un sacco di tutorial!!

La seconda è una lista delle cose che servono ad ampliare la comunicazione in una comunità, ed ad attirare giornalisti:

12 Tips For Doing Journalism With Communities

Animazioni ed accessibilità

mi segno un articolo sui disturbi vestibolari legati alle animazioni:

http://alistapart.com/article/designing-safer-web-animation-for-motion-sensitivity

e sull’accessibilità con un simulatore di problemi alla lettura:

http://webaim.org/resources/

molto intelligente anche se applicato malissimo.

Time usability in web app

da http://www.nngroup.com/articles/response-times-3-important-limits/

The basic advice regarding response times has been about the same for thirty years [Miller 1968; Card et al. 1991]:

  • 0.1 second is about the limit for having the user feel that the system is reacting instantaneously, meaning that no special feedback is necessary except to display the result.
  • 1.0 second is about the limit for the user’s flow of thought to stay uninterrupted, even though the user will notice the delay. Normally, no special feedback is necessary during delays of more than 0.1 but less than 1.0 second, but the user does lose the feeling of operating directly on the data.
  • 10 seconds is about the limit for keeping the user’s attention focused on the dialogue. For longer delays, users will want to perform other tasks while waiting for the computer to finish, so they should be given feedback indicating when the computer expects to be done. Feedback during the delay is especially important if the response time is likely to be highly variable, since users will then not know what to expect.

buoni principi

>>>> In your web projects try to:
>>>> 1. Start with needs*
>>>> 2. Do less
>>>> 3. Design with data
>>>> 4. Do the hard work to make it simple
>>>> 5. Iterate. Then iterate again.
>>>> 6. Build for inclusion
>>>> 7. Understand context
>>>> 8. Build digital services, not websites
>>>> 9. Be consistent, not uniform
>>>> 10.Make things open: it makes things better
>>>> *user needs not government needs

Ma dove andranno quei soldi?

http://www.www2015.it/registrations/

Super e molto interessante conferenza sugli standard HTML5 e l’uso del web.

Costo minimo per partecipare ai 3 giorni: 580 euro.

Con gli sponsor che hanno non riescono a fare una conferenza OPEN?!?! bho..

quando il web è un lusso..

AH. MA SOLO IN ITALIA!

perchè se poi guardate gli altri appuntamenti del W3C..  http://www.w3.org/

Sono gratuiti o a 50 euro la cena post talk..  ma in che paese sono nata!!?!

 

 

3 passaggi per la UX, user experience

  • The research phase is where you immerse yourself in the project to get the background you’ll need to make design decisions later in the project. During this phase you will try to learn as much about your client’s business, objectives, users and competitors as possible.
  • The design phase is where you work out how what you are designing will work and how it will fit together. This phase will define its scope, its features and functionality and how it behaves.
  • The validation phase is where you identify whether what you came up with in the design phase actually works with its intended audience. This phase is typically followed by further rounds of design and testing to solve the problems you inevitably find when you test with users.

legge europea sui cookies

Il nostro sito utilizza un cookie per sapere se lo hai già visitato oppure no. Continuando la visita ci autorizzi a procedere. Sappi che può disattivare i cookies dal tuo browser se non li gradisci.

Dall’8 maggio 2015 tutti i siti web europei per legge sono obbligati a dichiarare il loro utilizzo.

I cookies sono piccole informazioni, temporanee o permanenti, che il tuo browser memorizza visitando i siti web ed alcuni di questi potrebbero ledere la tua privacy. Ti consigliamo di approfondire l’argomento:

firefox: https://support.mozilla.org/it/kb/Attivare%20e%20disattivare%20i%20cookie

chrome: https://support.google.com/chrome/answer/95647?hl=it

Inoltre esistono estensioni per i browser che ti aiutano a gestire la tua privacy (www.ghostery.com), pensaci.

___

Sei proprietario di un sito web? come mettersi a norma entro l’8 maggio 2015:

  1. Analisi dei cookie e tracker del tuo sito
  2. Creazione di una pagina con l’informativa su cookies e privacy, possibilmente aderente alle p3p del w3c
  3. Inserimento nel footer di un link a quest’ultima.
  4. Installazione di un plugin per il tuo CMS che mostri un pop up informativo alla prima visualizzazione del sito
  5. Configurazione di questo plugin

 

__

Altre informazioni sulla privacy:

http://www.garanteprivacy.it/web/guest/home/docweb/-/docweb-display/docweb/3118884

http://www.garanteprivacy.it/home/doveri

http://www.youronlinechoices.com/uk/protecting-your-privacy

http://www.softwaretestinghelp.com/website-cookie-testing-test-cases/

Modelli per la compilazione della privacy:

http://www.privacy.it/modelli.html

ARIA

http://www.w3.org/TR/wai-aria/complete

da stampare! sono 94 pagine :(

 

Per l’accessibilità delle applicazioni web, nuova normativa passata a raccomandazione.

 

Abstract
Status of This Document 1. Introduction

1.1. Rich Internet Application Accessibility
1.2. Target Audience
1.3. User Agent Support
1.4. Co-Evolution of WAI-ARIA and Host Languages 1.5. Authoring Practices

1.5.1. Authoring Tools

1.5.2. Testing Practices and Tools 1.6. Assistive Technologies

2. Using WAI-ARIA
2.1. WAI-ARIA Roles

2.2. WAI-ARIA States and Properties

2.3. Managing Focus
3. Normative Requirements for WAI-ARIA 4. Important Terms
5. The Roles Model

5.1. Relationships Between Concepts 5.1.1. Superclass Role
5.1.2. Subclass Roles
5.1.3. Related Concepts

5.1.4. Base Concept 5.2. Characteristics of Roles

5.2.1. Abstract Roles
5.2.2. Required States and Properties 5.2.3. Supported States and Properties 5.2.4. Inherited States and Properties 5.2.5. Required Owned Elements 5.2.6. Required Context Role
5.2.7. Accessible Name Calculation 5.2.8. Presentational Children
5.2.9. Implicit Value for Role

5.3. Categorization of Roles 5.3.1. Abstract Roles

5.3.2. Widget Roles
5.3.3. Document Structure 5.3.4. Landmark Roles

5.4. Definition of Roles
6. Supported States and Properties

6.1. Clarification of States versus Properties 6.2. Characteristics of States and Properties

6.2.1. Related Concepts 6.2.2. Used in Roles 6.2.3. Inherits into Roles 6.2.4. Value

6.3. Values for States and Properties
6.4. Global States and Properties
6.5. Taxonomy of WAI-ARIA States and Properties

6.5.1. Widget Attributes
6.5.2. Live Region Attributes 6.5.3. Drag-and-Drop Attributes 6.5.4. Relationship Attributes

6.6. Definitions of States and Properties (all aria-* attributes) 7. Implementation in Host Languages

7.1. Role Attribute
7.2. State and Property Attributes
7.3. Focus Navigation
7.4. Implicit WAI-ARIA Semantics
7.5. Conflicts with Host Language Semantics 7.6. State and Property Attribute Processing

8. Conformance
8.1. Non-interference with the Host Language
8.2. All WAI-ARIA in DOM
8.3. Assistive Technology Notifications Communicated to Web Applications 8.4. Conformance Checkers

9. References
9.1. Normative References 9.2. Informative References

10. Appendices
10.1. Schemata

10.1.1. Roles Implementation
10.1.2. WAI-ARIA Attributes Module
10.1.3. XHTML plus WAI-ARIA DTD
10.1.4. SGML Open Catalog Entry for XHTML+ARIA 10.1.5. WAI-ARIA Attributes XML Schema Module 10.1.6. HTML 4.01 plus WAI-ARIA DTD

2 di 94 03/12/14 12:10

Accessible Rich Internet Applications (WAI-ARIA) 1.0 http://www.w3.org/TR/wai-aria/complete

10.2. Mapping WAI-ARIA Value types to languages
10.3. WAI-ARIA Role, State, and Property Quick Reference 10.4. Acknowledgments

10.4.1. Participants active in the PFWG at the time of publication
10.4.2. Other ARIA contributors, commenters, and previously active PFWG participants 10.4.3. Enabling funders