To achieve the effect of resizing for mobile devices, I have only used so far
Width = device width, start scale = 1 That did not work out a problem.
I discovered recently
user scalable = no as an option for the meta viewport. At first I thought it was an abbreviation for the attitude
maximum width = 1, minimum width = 1however, it comes along in my viewa big advantage:
That allows them [the web browser] To eliminate the dreaded 300 ms delay on touch events that the browser needs to wait to see if your single touch is a double touch.
Brilliant, I thought. Some basic tests on my and some fellow cell phones actually seem to pick up the delay of 300 ms, leading to a much faster feel.
scalable by the user Some more rings. The general consensus seems to be that along with it
maximum / minimum widthis "harmful" to accessibility. Some excerpts from articles or written contributions this year:
"And although initial scale = 1 is quite useful, the maximum scale is bad news for accessibility."
"Mostly these harmful explanations are absolutely not necessary:
Maximum scale = 1, scalable by the user = no"
What interests me is that both these references refer to two or three year old articles as well as the respective arguments:
Setting maximum-scale = 1.0 disables the feature to use pinch zoom on mobile devices, forcing users to view your page in a specific way.
[…] However, there are many cases where the user may need to zoom in: small font (at least for the needs of the user), checking details on a photo, etc
This parameter removes the ability to zoom in or out, and is even worse than the maximum scale. If there is a very special reason to use them (for example, you are programming a web application and you need to avoid increasing the form input)
While I understand some of the concerns raised, I wonder if some of the arguments refer to things that are not or should not be a problem.
For example, if it is alleged that the ability to zoom input fields is eliminated, one could argue that if a user needs to enlarge form fields on a mobile-optimized website, there is another problem that should be fully resolved by users to be asked to enlarge in the first place.
The font size that I can accept is a problem, although a workaround could be to include font size controls (used to display them more often).
That's possible in that sense
user scalable = no (or max / min width) is not quite as horrible as it sounds, and with some thought / planning in terms of accessibility, could it be safe to use it and take advantage of the benefits it brings?
For a fair argument and a small confession, I'm probably thinking a lot more about mobile phone sizes than about tablet sizes. For mobile phones, I feel that things are magnified often enough (most things are set to only 100% width), the same is not always true for tablets I admit. I also do not suffer from anything that interferes with my accessibility, so I'm probably naive about some of the issues that other people face.