Discussion on usability and accessibility of product design

In the user experience of this industry, often hear, usability , accessibility, such as professional terminology, but, in fact, in many product implementations have overlooked this point! WHY?

To give a very simple example, user registration process, many interaction designers in doing this process design is unavoidable to ignore the partial availability and accessibility, it is straightforward to say that the product's application scenario does not cover a full user base, which undermines the usability and accessibility of this part of the user.

Too abstract? Don't understand? OK, then we will expand the user registration process, regaling the design of the user submitting form in the process.

See figure, this is the existing Alipay registration process in a piece of functionality, to achieve the function is very simple, individual users directly fill in the registration information, is the enterprise users, the first choice of enterprises, and then fill in the registration information, finally submit the form, complete the operation. The process has already been released online, it looks very harmonious, but otherwise ...

Where else would it be? Application scenario, yes, you are correct. The interaction designer ignores some scenarios while designing the process, not taking into account the client's lack of support for JavaScript or poor user support. Do an experiment, open Alipay's registration page, and then disable the script, you will find that no matter how, you can not point out the Enterprise class registration information! OK, now understand it, enterprise class users in this scenario is basically game over, do not have to come up with a "FT, pay treasure really TMD difficult to use Ah!" ”

Heard here, perhaps a lot of interaction designers can't sit back, "this is not the front-end development engineer to consider it?" "I think to understand this, if the simple from the perspective of front-end development, this way of implementation is understandable." What's the practice? Yes, to illustrate ...

implementation of Scenario 1: the use of CSS style set enterprise registration information container defaults to hide, when the user click the enterprise through the JS script to change the hidden properties of the container display.

Implementation Scenario 2: The initial state of the container that controls enterprise registration information through scripting is hidden, and the hidden properties of the container are displayed by scripting when the user chooses the enterprise.

Under normal circumstances, the front-end will have two implementations, put aside the accessibility, the light from the developer this level of choice, I choose the first. This program is also used in the current registration process.

Discuss these two options, each with its pros and cons, but today we're talking about usability and accessibility, so it's clear that the first option is undesirable. So why did the front-end development engineer choose her? Nature also has his reason, if the use of the second scheme, it is bound to be in the page structure after loading, and then to initialize to hide the container, when the client network is poor, will first show the content of the enterprise registration information, a few seconds later disappeared, experience a discount. But in terms of availability and accessibility, it's unassailable. Assuming that the current user environment disables scripting, then when he accesses the page, the Enterprise registration information is not hidden, it appears on the current page, there may be some deficiencies in usability, but the functionality is accessible and the whole process is sound. Compared to two situations, I think I will choose to adopt Scenario 2. Of course, if you disdain available accessibility, then the bricks hit me!

Many interaction designers take for granted that a scenario like this is very small, and perhaps the real data will surprise you! In a word, many for the user think, is the designer's minimum professional ethics!

The importance of usability and accessibility can also be found in many applications, such as voice readers, mobile browsers, and so on, which in PPK talk about JavaScript in a more detailed description, if interested, you can refer to the "PPK talk JavaScript." All in all, the semantic page structure plays a very important role in the usability and accessibility of Internet products in the future.

Speaking of which, I believe that the understanding should understand the availability and accessibility is a thing, in addition to understand, you have also seen some problems? Yes, there is definitely a problem, interactive design and front-end development process are the problems, specialization route is not a single, professional cover degree is very important!