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.
0 comments:
Post a Comment