3.1.1 Retain Information For Personalization

JavaScript: Reading the updated version [1], I think that the phrase 
need here is "do not rely on" [2] JavaScript variables for state 
information. Use it when it's working but do not rely on it.

Hidden Form Elements: Perhaps say something about keeping the strings 
short. Some applications generate random IDs that are very long, much 
longer than a page of mobile markup.

HTML5 Local Storage API [3]: Perhaps say that this is only a working 
draft, and probably still will be when MWABP reaches Rec ("Implementors 
should be aware that this specification is not stable. Implementors who 
are not taking part in the discussions are likely to find the 
specification changing out from under them in incompatible ways"). Is 
this compatible with the use of XHTML in the Delivery Context?

Perhaps a table might be useful here to compare the features of each 
technique, to help people choose.

regards,

Alan



[1] 
http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#bp-personalization-retain
[2] http://www.w3.org/TR/WCAG20/#reliedupondef
[3] 
http://www.w3.org/TR/html5/structured-client-side-storage.html#structured-client-side-storage



-- 
Alan Chuter
Departamento de Usabilidad y Accesibilidad
Consultor
Technosite - Grupo Fundosa
Fundación ONCE
Tfno.: 91 121 03 30
Fax: 91 375 70 51
achuter@technosite.es
http://www.technosite.es

Received on Monday, 16 February 2009 12:40:51 UTC