Wednesday, June 18, 2008

My Flashes Absolutely Hilarious!

Adobe vs. Apple. No Flash for iPhone UI consistent




articulated position of Kontra on issues related to the lack of support for Flash Lite and Flash on the iPhone.

Adobe's interface strategy on the desktop has been to Avoid using native UI controls on the deployed OS in favor of Establishing and leveraging ITS own unique cross-platform UI paradigm That ITS runtime engine can deliver consistently on multiple platforms. Unfortunately

for Adobe though, Apple is in the process of establishing the first mass-market, multi-touch platform with the iPhone and has already migrated it partially to its notebooks. Clearly, Apple (which acquired FingerWorks and its patent portfolio in 2005) has greater ambitions in establishing a broader multi-touch gesture paradigm, likely to cover other devices as well

Sunday, June 15, 2008

External Flashes Great Gadget

Accessibility in Car Design



Una tuta speciale, studiata da Nissan, che aiuta a simulare (e registrare) il comportamento degli utenti della terza età nell'intento di migliorare la accessibilità dei nuovi modelli di auto in progettazione dalla casa giapponese.
E' chiaro l'intento di raccogliere frutti commerciali anche da questa fascia di utenti ma i dati raccolti saranno di aiuto nella ottimizzazione del Car Design nella sua globalità, andando ad impattare anche le altre fasce di età (e, dunque, di clienti potenziali).

Saturday, June 14, 2008

Professional Camcorders On Sale Detailed

Andy Clarke, reading time and web layout


Andy Clarke on Web Layout from Jeffrey Zeldman on Vimeo .

Andy Clarke shows how comic book artists use panel size to indicate how much time a reader is supposed to spend on a particular chunk of content. He argues that web layouts can work the same way. (Later in this talk, he'll show how.)

Andy Clarke: How often do we consider the space and the time that somebody is supposed to spend, or we want somebody to spend, looking at a particular panel. So if we look at something like this, there's a conversation going on at the bottom here. 'Actually, she turned out to be quite sweet. I actually took her out a few times.' 'Seriously?' 'No.' And it carries on. So those panels are smaller because we're supposed to take less time reading them. It's this flow and this rhythm. And this is something that comic books have done for a very, very long time. And it's something that potentially we can bring into the layouts that we make for the web.

Friday, June 13, 2008

Professional Camcorders

Mac OS X Jaguar (10.2) accessibility model. Anno Domini 2002





Documentazione Ufficiale sul Model/Object in Cocoa/Carbon Applications.

Hard Drive Recovery Disk Deserves A Better Title

Opera 9.5 IU. How to waste precious space




Nuova UI per Opera. Stessi problemi di sempre.
L'ingombro verticale supera, sia nella toolbar che nella status bar, abbondantemente quella dei rivali a parità di funzionalità attivate.
Opera 9.5 : 100px di toolbar e 21px di status bar.
Firefox 3: 80px di toolbar e 17px di status bar.
Safari 3 : 75px di toolbar e 15px di status bar.
Se qualcuno in possesso di IE 7 volesse prestarsi alla comparazione, avremmo un quadro ancora più completo.

Se prendiamo in conto i dati di vendita dei monitors e dei computers, la situazione diventa alquanto concern. Are becoming more common widescreen displays (monitors and as stand-alone and as part of that notebooks are replacing desktops) that promote horizontal against the vertical space while Opera is promoting the vertical dimension in contrast against the horizontal.

On the Mac, as usual (for Opera), inconsistencies abound. If the toolbar icons can go very well on Vista (for which have been studied of course) on Leopard, do not just punch him in the rest of the UI of the OS but also, more seriously, with the rest of the IU Opera itself. Neither the color scheme or style are consistent.
Note particularly the dissonance between the icons on toolbar side which, rightly, are in gray 75% and the main toolbar.
hurry the release? Maybe.
IU Opera problems persist anyway.

Tuesday, June 10, 2008

Hard Drive Boot Disk Dvd Players And Drives

Accessibility Requirements for dummies. But only if they work in PA. For accessibility

last episode, as far as I'm concerned, the telenovela ' an accessible place in the sun'.

First, a premise.
fallibility of previous post was referring to one of the fundamental concepts of Science of the twentieth century. I apologize if I assumed that a common cultural background, obviously, is absent.
The title of the previous post so not only is consistent with the arguments but also, judging from the responses to the problem at hand. In response

go back because I would like, in conclusion of this discussion in open space, pull the threads of what has been lost on the road.

I am a down to earth. For me the important thing is that Flash designers worry for once the accessibility of its products. What I wish is that the designer development Flash animations by applying all the criteria and accessibility techniques that its platform allows. The rest will come with time.


And, as the 'platform' does not exist as a whole but has several features a seconda dell'OS si cui gira, dovremmo parlare non più di Flash in modo generico ma di Flash Player su Windows (su Mac, su Linux) e chiarire questa differenza.
Ciò non é discussione oziosa ma impatta sul lavoro quotidiano e sull'output. Inutile dare il via libera ai Devs (e qui parlo da Project Manager) sull'uso di una tecnologia sicuri della sua aderenza agli standards della accessibilità se poi, a conti fatti, è accessibile solo su di un OS. Sarebbe come dare il via libera sull'uso delle specifiche del CSS 3 che sono disponibili solo su Safari. Bello, certo. Peccato che solo gli utenti su Safari potrebbero vedere il tutto. Il resto? Si fottano .

Therefore, it is returned as a warning, the old and dear IE Required new form. Flash Player 9 for Windows required. Better accessibility, really.
We are talking about standards or did I miss something? That standard is something that only works on an OS?
Personally I have not given or will give, under these circumstances, the consent to the use of this technology going to tell the client the bale of access guaranteed. Matter of professional honesty.


It 's true that the shooting Bill Gates has always been, and often rightly, lo sport nazionale. Ma non si dovrebbe dimenticare che Microsoft, in materia di accessibilità delle applicazioni, si è mossa per prima e che solo recentemente Apple e Mozilla hanno migliorato i loro prodotti nel senso dell’accessibilità (consentendo, per esempio, agli screen reader Jaws e Window-Eyes di utilizzare Firefox). Quindi i rimproveri, se ci sono, andrebbero indirizzati ai competitors di Microsoft.


Ma vi peritate di usare tutti i sistemi operativi di cui pure discorrete oppure questo vezzo é solo a carico dei GUI designers?

VoiceOver é presente su Mac OS X da Tiger, id est dal 2005 (non proprio 'recentemente' quindi). Già you're on that page have a look at all that OS X provides for accessibility.
VoiceOver was developed in house in a gallop, just to make up for abandoning the Mac market by the only dedicated screen reader then available. ALVA Access Group in June 2003 announced its intention to abandon the software in question. In November 2003 he set out assuming Apple engineers to build a solution in house.
Panther (OS X 10.3) had just been launched (end of October 2003).
In other words, the very next version, Tiger just had VoiceOver and everything else in the system Integrated .
If we ventured to read up on platforms other than their'd all be a little better, computationally speaking.
Bertoni's position regarding the accessibility on the Mac is clearly not informed of the facts.

But, beyond what is stated above, there is also another big problem. The assumption that should be the operating system to allow

..., for example, to screen readers JAWS and Window-Eyes to use Firefox


is at least weird.
An OS exposes APIs on which the producers of SW / HW rely to build their applications. APIs are available for OS X di chiunque dato che la iscrizione alla Apple Developer Connection é gratuita . Apple non ha da permettere alcunché dato che é tutto a disposizione.
Ogni software per OS X può accedere a VoiceOver per il semplice fatto che VoiceOver é un servizio di sistema sempre attivo nel menu ' Servizi '.
Manca all'appello solo la volontà di Devs terze parti. Dove sono quelli di Jaws?

Jaws for Windows (il suo nome completo. Da non dimenticare). Jaws non funziona su Mac se non attraverso ambiente di virtualizzazione (80€ di software di virtualizzazione + Licenza Windows XP + 1GB RAM aggiuntiva to run smoothly in the machine virtualization. Sum: 240 €). Because Jaws is disabled on the Mac as citizens of the lowest category? Maybe because they do not invest in a platform with 12% market share considered, rightly, not profitable? It is perhaps telling that the disabled should be considered citizens in every respect but only if they use Windows ? In short, all are equal but some are more equal than others .

( note: the web site Jaws is the most useless can happen anywhere )


The fact that you continue to say that "A pixel is sufficient for differentiation and further" makes me think, do not take it that you do not have great practical experience with people with disabilities. Although assertions to the contrary, continues to forget the subject of accessibility: the disabled. I propose an experiment: try to turn a normal button on a form (located at a distance from another pixel) with the mouse emulator, his hands behind his back and using your mouth (with a pencil or a stick any) to interact with the keyboard. I'm not saying you can not, but maybe you will be more clear why the associations of motor disability were asked to increase these distances.


First, two concepts of two of ABC GUI Design.
Hotspot: The portion of the cursor to be positioned on a screen object before mouse click has any effect, regardless of the trigger (onMouseOver, onClick to, etc.) event.

Hot Zone: The screen objects that have the hot zones are areas where the hot moving the cursor should go to get a recording of an event on the GUI.



the first picture shows a mini navbar with two buttons as it is displayed to the user. Only 1 px visually divides the buttons.





The second image shows the hot zones are ready to capture the onMouse Events. Each button has its margin set to 10px on the horizontal axis. The effect is simple to implement with some CSS padding and margin on a tag of ul.
We have over 20 pixels of horizontal space in error. The example also shows how the offset diagonal of non-traditional full-limb motor control, is taken into account. In fact, the padding on a tag goes to cover the entire vertical dimension of the button rather than be content to surround with padding set on all the sides of the link.




The third image is the same as mini navbar would be displayed if the tables were to follow the laws set by Bertoni.

The differences are substantial. In the latter case we have a loss of consistency of the UI with buttons and highways to separate the resulting grid irretrievably lost.

said this also applies, for example, the ergonomics of a tool we use every day to comupter. The keyboard.

What we want most in all this, is that the UI remains usabilissima and consistent (as well as pleasing to the perception) for both types of users. not any sacrifices on the altar of the other . This is my country, apparently different from others, equality of treatment. Too easy to destroy the usability of a range of users to help another. Solution brief and by no means adhering to the basic principles of good UI Design.
If you hurt an arm, cut the other! seems to tell us this attitude.
How about directly using Lynx ?

Incidentally. I had disputed the claim about the connections of regulation 4. Bertoni, and suggests how to change the cards as a form button that is not a link. The form must have
button padding greater than a tool as is used in contexts where it takes you a clear choice which delivers results not recoverable. The typical example is the dialog of the installation of software. There are two contexts of human-computer interaction involving several different approaches to UI design.


I will certainly miss the experience with people with motor disabilities but on the other hand it is not that we are better in UI Design. Both said no offense. To each his own field, for goodness sake!


Back, finally!, The fundamental question and the questions I asked. The answers have
, CVD, demonstrated, as if it were needed, that the rules of accessibility are designed for the consumption of PA and, ultimately, should not be taken into account by the business sector because the rules do not consider it as a factor.
But, and this is the point, do not go telling and trumpeting the need to consider the disabled as first-class citizens like the other ? And, wonder, the first-class citizens just to go around the sites of the government? They also will not other desires, curiosity, in fact similar needs to those of other users? Or imagine their lives between home and relegated PA?
Behind the rhetoric lies in the service industry, as often happens, a turn of phrase that, to me, seems more offensive silence on the matter.
Consider them as equals, with the requisite specificity, does not mean real consider the flow of their lives on the net and not from laboratory ?

My question was specifically to make real the application of the rules of accessibility. To do this, however, there is need to start from two requirements:

  • The real needs of disabled users in the network

  • needs of the business network


find a meeting point between the two. This requires, unfortunately to no avail.

amend the rules and make them less fundamentalist taking into account both these factors do not encourage Project Managers we talk (if not commercial) to bring the blocks of code on standards available? Right now be commercially available is to die for a web application that makes business its raison d'etre. Between a ' useless to think of accessibility so this product will never be less accessible to adhere to draconian rules ' a ' do it! cost labor but Imagine delivering a product oriented business that is also affordable! 'I think that goes a big difference. At least in my eyes.

This and only this I requested. Including
who is interested only in their parish (which provides the bread and the bread and then to defend, for both) and that my assumptions are, unfortunately, accurate, I return to my personal amusements.


ps. the twenty-two rules are nonsense, however, demonstrated that those here. It would be honest rewrite changing, we're at it, the title of the original post.

Saturday, June 7, 2008

Hard Disk Drive Dvd Recorders Underwhelmed

fallible. Invitation to dialogue

I am going to respond to comments made by Marco Bertoni not a spirit of controversy, which I think useless, but to try, through the dialectic, to circumscribe a common background that can take us beyond the allegations in the absolute area of \u200b\u200bfeasibility.

A premise is a duty. I'm no 'rival' to anyone because I did not fight to excel. I would simply argue. If the discussion will prove fruitful, the better. Otherwise it will return all of its activities.

Reaffirm the need to write code that is syntactically and semantically correct and useful preliminary because it is an indictment against those who do not. What you consider a "no requirement", as the obvious need for the diagnosis of the first drug for me is the requirement for excellence in what it contains all the others. The more necessary, because sooner or later, so physicians will understand that drugs are prescribed without first visiting the patient. Some doctors, without rules and controls, are lethal. The correct structure and semantics of the content of Web accessibility are the key, you can not in any way give it up.


I'm sorry but I still disagree and for the same reason that we have seen others do not agree in ancient times.
It seems counterproductive to insist on trying to correct these effects last instead of tackling the causes. These are to be found in a mixture of mindset and business interests that should at least be able to identify and then try to aim in the communication process and legislation. A well-posed problem contains within itself the solution , someone said at the beginning of last century. Scientific spirit, of course. But much to ask to adopt a scientific criterion in a legislative act? So
as proposed, the rule takes the classic whistles for flasks. I do not know the analysis of context and I turn to the operators instead of individual action upstream on the business environment and professional that generates the effect. We continue to
look at the finger rather than turn our gaze to the one who points, then. After all, excuse the digression in other fields, I think we are masters of not addressing the causes of the problems but never limit ourselves only to the bin of the moment. Better
incinerators downstream or upstream action on the vested interests in high places and the cultural background of individuals with appropriate education for waste disposal?

repeat. The adherence to standards is not optional but is basis of the trade that is taking place. And the examination for admission to the profession.
But how do you discern the laziness and bad from professional and commercial needs of Project Management who prefer custom-made frameworks of thousands and thousands of lines of code that enable products, past, present and future, provided to large corporations?

therefore remains as unheard soundtrack, the problem of porting economic blocks consisting of code. Cui prodest?
(The commercial content of the blue sticker and it just moves to sell the product. We do not tell tales)


A private company can decide whether or not to pursue a policy of social responsibility (which, incidentally, offers a return of the image that also like the notorious commercial). None of us can criticize the choices of them. But a government in the different matter. If we agree that the government exists to serve all citizens, and if we agree that a disabled person is in effect a citizen like the others, then I do not "stop and reflect." If Google wants to use iframe as if it rains, no problem will lose a percentage of visually impaired users. Too bad for Google. But if administration discriminates against a group of users using a technology not available, this is unacceptable.


The answer confirms my claim without showing it.
argomentazone The primary is in fact given by the case of public utilities that, as I said, are rightly forced to comply with these rules.
My objection, again, gives voice to a completely different category, business, which has completely different criteria to operate. Here the fields where we both work influence, of course, our perspectives on the issue. In fact, what is said about the percentage loss customer does not take into account a basic rule business. A customer ceases to be profitable when the effort to satisfy his demands exceed the ROI from these expected . So, where is the margin? It would be worse for Google
pursue this niche. It would be commercial suicide .
Everywhere not only network, you can observe this simple principle at work. Go into any bookstore GDO (Feltrinelli, FNAC, etc.) and have a look at the catalog (both the vertical and the horizontal) and the behavior of the clerks trained ad hoc.

brutally put to annihilate an innovative service which could trigger halo effect and, therefore, to operate a cognitive lock-in to the brand with the application of Metcalfe's Law and the consequent positive impact on advertising revenue, it seems unreal but not a emerita nonsense if, as seems evident, we are still in the system called capitalism .

still believe you are starting from two different positions (not different a priori, is well understood). A business-oriented perspective and another public service oriented. Invitation to dialogue about these differences that I personally respect and recognize in their specificity. I do not know what it's worth the contrary.

course. It 'obvious that the underlining of links is useful only in blocks of text. The color-blind knows the conventions of design (menus, etc...) It 'something that, honestly, I took it for granted. No sane accessibility expert calls for an orgy of emphasis.


Bon. The notes, however, did not speak of the blocks of text, but generic links. I know what it refers to all but readers know of your requirements? Judging by the posts in forums and blogs full of zealots who call all'underline everywhere, the accessibility confused with usability (yep. someone confuses the issues of accessibility with those of the resource optimization Loading ...) etc. I know it's better to be clear on this point. It could well lead to the salvation army to obey Decalogues good but ill-equipped in independent thought.


The eyetracking research shows that pop-ups, flashing banners, advertising, etc. columns. are neatly and systematically ignored by users. The same Nielsen proposes an approach non etico: “making the ad look like content”.

Ma non capisco cosa tu veda di male nella sacrosanta regola che impone di evitare un attacco di epilessia al prossimo. Il requisito cinque dice solo questo, non proibisce banner o pubblicità. Attenzione a non fare il solito terrorismo sui requisiti.

Comunque abbiamo capito che le argomentazioni a favore della pubblicità lampeggiante e “esplosiva” sono inesistenti. Ci si chiede perché si continui a produrla. Un amico che lavora in pubblicità mi ha confessato che spesso a chiedere pop-up, animazioni e banner sono i clienti “ignoranti” e loro si adeguano. Perché contraddire un idiota che paga?


A dirla tutta non we have seen anything about insesistenza of the arguments in favor of commercials (judging from its actual use ). Neither seems to me that the answer can be inferred with a counter-argument appropriate scalable alternative proposals at the business level if not the mere statement of what I already said, namely the phenomenon of 'ad-blindness .

We have yet to find an alternative way to earn dindi through advertising. If those who branded the advertising 'explosive' have found the Holy Grail of the new Microsoft advertising is expected to check their White signed.
Pending the myth we have to make do with only three possibilities. Traditional Banners, Ad-sense-and in-context that is even worse to disguise the evil that wants to treat (as rightly noted Bertoni) in fact unusable as it would make the whole amount of information of the Internet spreading noise mixed content.

jokes aside, I still reiterate my invitation to take account of different factors, and often conflicting. If a bubble does not exist as the two positions as you will come to a strategy capable of being, together, effective and respectful of the needs of all stakeholders?


No indictment on my part, how to interpret the requirements of a regulatory requirement. Personally I have nothing against the fixed layout


You use a liquid layout (elastic).

I do not think one interpretation. It is rather, in terms of linguistic rules with a lot of reported imperative.
An invitation to the interpretation was something like
should be used, given the technical issues, adherence to the full compatibility in any web site must obey and analysis of usability, a fixed layout.

This is a decent way to communicate leaving a need space when interpretative contextualization.

According to Plato trouble me to exaggerate. These requirements are not asking for anything impossible, and are not in the wrong direction, they are just perfect as anything human. I choose to try to improve things from within.


not I never said that to be impossible (the supercelestial is not impossible, just perfect. An absolute logical type). I say apply what works for one side to everything. Pars pro toto. This is called absolutism that is what I am calling to avoid. Bertoni
I praised and continue to do so for his efforts in trying to improve in its sphere of influence, the current situation on which, as you may read elsewhere, we are in full agreement.
My notes are, of course, on the sidelines because they tend to indicate the existence of some problems and do not want to be but a 'critical ' in the classic sense, an analysis of a proposal. ' Critics' invitation to the barrier is not unilateral but the voice of the other. In this case, the needs of others.

This is no longer true with the Flash Player 9. Be careful not to give incorrect information;).
However, as I said elsewhere, it is wrong to confuse the accessibility of the Flash movie itself with the limits of the implementation of cross-platform and cross-browser plug-ins.


ahem.

I apologize but I am Mac user and Linux (debian) and use Windows daily to double-check. My problems are practical and concrete solutions require Adobe not PR.
I follow closely the developments platform without giving in to easy street number.



Confusing the output with the framework that makes it possible for delivering the output is wrong?
How do I count to view a swf without the player that makes it available?
As you have a glass of tap water without the water supply?
Without language there are words?
We can write a function without a formal syntax of programming?
And so on.

Come on.

The requirement is twenty-one, I think, the only one that was asked in a loud voice who represents the disabled persons. Nothing, "Bignami hasty" and then, but listen attentively to the demands of disabled users. We never forget who are the recipients of the benefits yielded by these requirements. People with disabilities. I assure you that a distance between pixels of a button and another for those with poor control of the pointing system is something delinquent. This is not only the visual perception of differences, but di destrezza manuale.

Se vogliamo parlare insieme di accessibilità dobbiamo sempre porci dalla parte del disabile, e cercare di capire le peculiarità di ogni disabilità.


Nope. Esiste un concetto vecchio come il bacucco (lo trovi nelle prime Apple HIG - Human Interface Guidelines) che si chiama Hotspot . Un pixel di differenziazione basta ed avanza se si ha cura del layout degli hotspot. Se poi il designer dorme e cazzeggia allegramente con i tutorials sul css, le regolette del SEO etcetera invece di studiare l'abc del GUI design, il problema non é del pixel ma del designer. Diamo una svegliata ai designer e tutto verrà di conseguenza. Limitiamo il 'designer' ai corsi regional and schools where they teach simply clicking buttons in Dreamweaver and Fireworks and here we have these results. Once again, issues of training and mindset.
What then should take the role del'utente in question is absolutely out of question. We would not be here either to discuss all this otherwise.

If news yesterday, the site of the police won as the best design usable and accessible I guess there is something wrong in the structure, but adherence to standards. If I adhere to the standards of the Code and at the same time produce an interactive flow from ass to users, we can say that the adherence to standards is not enough to ensure a damn?

Friday, June 6, 2008

.aorta.. More Condition_symptoms

Accessibility dell'iperuranio. When will the real one?

I take the occasion of an amusing article of Marco Bertoni to address some issues dear to me about the 'Law Stanca' and the problem of accessibility as it has taken shape.
Bertoni, the article mentioned, paraphrasing the main points of accessibility and allow me the use of his paraphrase to put their notes in the margins of the 'Law Stanca' addressed. How

exergue I would say that I agree with the intention of Marco Bertoni but I would have preferred a clear preface to the 'rules' in a position to clarify che ciò di cui si discorre è necessario analizzarlo caso per caso e, su tutto, non perfettamente applicabile a tutti gli ambiti del Web UI Design ma solo al campo preso di mira maggiormente dalla 'Legge Stanca' e nel quale maggiormente lavora l'autore dell'articolo, cioè le Pubbliche Amministrazioni che, per fortuna, non sono l'intero web.

Questo requisito ti chiede di scrivere codice pulito, senza errori sintattici e semanticamente corretto. Che significa? Significa che bisogna finirla con il codice spazzatura ;).


Il primo requisito è un non requisito dato che scrivere codice senza errori sintattici fa parte delle best practices. E' come dire a doctor must see a patient before prescribing a drug any. Ethics and conduct that does not need to be confirmed. The fact remains that the opposite happens and logically prior to the formal validity of the standard. In short, the rule states a requirement but not an indictment. An indictment against those, many who have been trained not to move with the times.
In the latter case, you are talking to the wind in those who do not care what his training or his own free market needs even more reason not to seize this invitation from imposed. In short, to whom is this indictment?

But, and this is il punto che svilupperò più approfonditamente in altro post, non è sempre colpa del coder il risultato che vediamo . Spesso, molto spesso, viene ordinato di riusare porzioni di codice per ottimizzare sul tempo e quindi sul margine di guadagno. Il problema é quindi non di chi scrive il codice ma delle sezioni commerciali che obbligano a tempistiche strettissime promettendo mari e monti nei canonici 7 giorni della Creazione. Solo quando si sarà parlato non ai coders ma ai 'Commerciali' si riuscirà ad ottenere qualcosa. Ma, si sa, il 'Commerciale' conosce solo una lingua. La domanda è quindi, quale vantaggio economico può bring large blocks of code to migrate towards accessibility?
In short, the point at issue is a false problem that does not identify its target precisely. To be redone.

This requirement forbids you to use frames. Let

: frames are ugly. They both web nineties. And makes a nuisance to screen readers. Old stuff and harmful words. And what about the inline frame (iframe )?...


Gmail uses an iframe to sea. Why? Why am I required to operate the web application and constribuiscono to decrease the waiting time increases, consequently, the usability globale della stessa. Aderire, senza residuo, alla norma porterebbe una usabilità minore e a funzionalità problematiche da implementare e fornire.
Certo, possiamo ben usare noi il DOM traversal +Ajax e ottenere quanto é da ottenere con divs ma, nondimeno, non mi sentirei di escludere apriori gli iframes quando possono dare una mano a gestire dei servizi risolvendo problematiche di HTTP request .
Se per aderire ad una regola frettolosa devo rinunciare ad offrire una piena usabilità della web application mi sa che occorre fermarsi a riflettere.

Se elimini la sottolineatura per i collegamenti e li differenzi dal testo normale solo grazie al colore, puoi creare notevoli problemi a chi è affetto da cecità ai colori, che non sarà in grado di distinguerli. Questo è un esempio per chiarire che non devi usare solo il colore per assegnare significato all’informazione.


L'informazione è data, in un layout, dalla differenziazione all'interno della griglia. In altre parole, il posizionamento fornisce informazione sulla funzionalità. Basta osservare una qualsiasi GUI su windows o Mac o Linux o Symbian o... per rendersi conto che gli strumenti sono suddivisi e posizionati in modo consistente per fornire una differenziazione percettiva immediata in base alla loro localizzazione. La stessa consistenza that must be achieved at the level of usability, even on the web. So it would be more appropriate to say not to fiddle with the positioning of the elements of the User Interface, and follow the conventions as the first rule. The rest is as redundancy. A page full of links where the menu is confused with the content of the page, even if it would not be chock full of underline immediately perceived in its primary function. With all due respect the good intentions.

This rule fosters the reading of the rules as a mere check list to which I have written previously . The truth is that the good old Web designer should be primarily a designer and know by heart the rules of good design that is not fuck with Photoshop (or Fireworks or whatever) but the study of space, communication analysis, redundancy noticed, transmission channel, perception, semiotics, etc.. Only when the 'web designers' are equipped with the skills that each designer will be worth it for granted insist on these minutiae, but it will be useless because the problem will still exist.
Before the structure then the details. The information structure is more detail without noise. Noise stressed but still noise.

If you like the animated gifs and flashing messages ... well ... you know ... happy ... But you're very close to the frequency of flashing, or you risk serious damage to those who suffer from photosensitive epilepsy. In addition to annoy us all.


And bread to those who work for whoever pays the web application without advertising?
In short, this is one of the rules to be taken cum grano salis. It fits very well to certain types of web site (type ' but who we are, but how many we are, but then we do it? "We write a letter? ') but certainly not all. It might be good in an ideal world but in the real world primary business is advertising . Like or less so. Amen.

Norma then be discarded if not in the presence of institutional sites, and personal websites Portfolio Web Site. The rest continue to ignore it for the simple reason given above. If the proponents of the law Stanca would sign monthly allowance paid by the latter to compensation for economic losses suffered by the removal of the banners we might see some results. For now the only hope of seeing the banners animazioncelle decrease is given by the finding that users are now ad-blinds. If so we will see a reverse trend is due not to respect the rules of accessibility, but the replacement of banners with something more effective in terms of achieving economic goals.

You must make sure that the text can be resized (enlarged). Even with Internet Explorer 6 and earlier (menu View> Text Size).
When the character is maximized there should be no overlap between the different parts of the page. Even resizing the window.
You must use a liquid layout (elastic).


the indictment against the fixed layout respond with three arguments:

  • Technical problems (for those not familiar, the Visual Design Lead at Google).

  • control by the Layout Designer.

  • Problems di leggibilità della informazione


Le norme sulla Accessibilità dovrebbero essere studiate in base alla situazione reale e non al mondo dell'iperuranio. Perchè il legislatore non mette un pò del suo zelo nello scrivere una lettera ufficiale a Microsoft invitandola a rispettare gli standards invece di legiferare a vuoto in direzione sbagliata?

Un liquid layout non è ipso facto accessibile (perchè mai dovrebbe esserlo?) e spesso si preferisce, per le tre obiezioni di cui sopra, optare per una soluzione fixed che è vantaggiosa in termini strettamente economici e di controllo del layout. Affermare che il fixed layout è da scartare a priori è quanto meno affrettata come proposizione (voglio esser buono e non pensar male circa le competenze nel campo del supporto browser agli standards dei consulenti interpellati in vista della Legge).
Per inciso, lo stesso ALA usa un fixed layout e nemmeno centrato. Se Zeldman in persona opta per questa via qualche dubbio da parte del 'legislatore' ce lo possiamo attendere. O no?

Immaginiamo poi un bel caso di un layout liquido a due colonne ove le colonne di testo della content area si estenderanno per il 90% della viewport. Dobbiamo ricordare l'abc della usabilità circa il numero di caratteri massimo su di una riga visualizzabile a video dall'occhio human?
Imagine the same case on a monitor 1600px horizontal resolution. A disaster of usability


A lot 'of people surf with scripting disabled. You have to do with it for a reason. So you have to ensure that your pages are usable even by those who have disabled scripts, applets, or other 2.0 stuff.

But the legislature is not neutral. If for religious reasons (' our bold) you can not do without your script inaccessible, then by an explanation of the features (that 15% of users will be lost) and, as a requirement Three provide alternative text equivalent.

You wanted the script? And now ride.

scripts but I'm not the devil. Just read PPK to understand that with a little 'expertise can do whatever you want.


Of course the 'script' (but then that means 'script'? Even php, ruby, python scripts are and need to stay where they are. In the body of the DOM) are not the devil. Equally certain is that this is a problem to be tackled with great care and parsimony of summary judgments by the witch-hunt that saw the carrier is leading the web applications (or RIA if you prefer) to be eligible candidates substitutes delle Desktop Applications. Il libello citato è importante (non il migliore in materia) e pieno di indicazioni utili ma in applicazioni complesse (tipo Yahoo Mail) vi è poco da accusare di religiosità fondamentalista in modo aprioristico e generico. Il codice JavaScript è in line perchè ha da essere inline. Se a questo punto le strade tra usabilitá ed accessibilitá divergono occorre affrontare il problema con occhio attento al rispetto di entrambe le necessitá e non sacrificare la usabilità sull'altare della accessibilità.

Devi garantire che le funzionalità (per esempio un menu) e le informazioni (il testo) presenti negli script, negli applet, nelle animazioni Flash siano direttamente accessibili alle tecnologie assistive.

Questo significa che devi installare uno screen reader e provare a navigare all’interno della tua animazione Flash. Se qualche “esperto” ti ha detto che Flash non puà essere accessibile, mandalo al diavolo e digli di leggersi la letteratura in merito e questi articoli.


Ironia della sorte, il famigerato articolo linkato è in Flash e non supporta il mouse scroll risultando quindi non usabile dagli utenti 'normali'. Vi è poi scritto a chiare lettere che Accessibilità con Flash è sinonimo di accessibilità Flash Windows .

All accessible Flash content must be tested on the Microsoft Windows platform. While there
Have Been recent improvements to the Apple Macintosh OS 10.4
release (Tiger), Including Called VoiceOver screen reader built in, the
Flash Player does not support this screen reader.


In other words, Mac and Linux takes you there in my pocket. Now, a technology it says when it adheres to standards-compliant, in all areas where you use , to the latter. Flash can, with a lot of work to be accessible only on Windows but it can not be called outright accessible unless you go back to the old 'IE Required' below disguise. One moment a user with respect to part, and which does not hurt, on the platform that deliberately ignores the most beautifully and standards that are not his. Better JavaScript inline compatible on all platforms that Flash on Windows only. Whatever one may say the 'experts'.

Ah. This is my favorite. I have also helped to correct an error in the first version of the statement.

You should always consider the fact that for those who have difficulty in controlling the pointing device is very difficult to select the link or right button if they are too close together. Imagine the frustration when after a huge effort to beat you click the wrong button. When you whistle your ears, think about the curses that will send users to this habit of sticking around. Will be the case for lack of affection?

The solution is simple: distance properly form buttons, form fields, and lists of links, in general, all active objects on the page.

I would add that even more than the default line spacing is better. But I know that not everyone agrees: There 's obviously people on the walls of text which is often seen in the horrific portals of many companies and Italian public administrations.


perceptual differentiation and not to enlarge the area indefinitely. Here is the problem.



If you look at the GUI of the Finder of Mac OS X, as famous example, we will see an icon in the toolbar and another is 1px of space, but all is well differentiated visually. You do not need a space that forces the user to travel with your mouse to move from one tool to another with the result of reducing its productivity and diminish the usability of all, it should be instead a remarkable differentiation.
Amazon, for its part, uses a 1px solid border with an arrow to do redundancy.



classic examples to show how the rules are far from an actual grip on reality.

is in this attitude that the hasty Bignami Stanca Law is that we must then seek the causes of accessibility as a mere label and list of commandments to be observed .

I repeat, calling for a change of mindset, which alone can ensure the successful progress in the studies in this area so controversial. Collaboration and dialogue by all the professionals concerned and not the ivory tower of the 'specialists'.
Decalogues but no discussion.

Tuesday, June 3, 2008

New York State Drivers License Template

Touch User Interface. A look at laboratory culturedcode

First steps of the iPhone version of Things , good GTD application for OS X.
First steps into the world of Touch User Interface Design. Many problems, different solutions.



The first impressions of culturedcode the difficulties of developing an application that interact in different behavioral patterns from the traditional Desktop Applications and that, nevertheless, it is proposed not to mourn the 'convenience' of the latter .