I can see your point, but want to add why I recently started to add this meta-tag on most of my responsive sites:
1. images start to look blurry
2. input fields change the scale of the page and seem to confuse some users (at least in some test-cases).
On the other hand I try to improve accessability by making sites screen-reader-friendly and using high contrasts. I have also seen a lot of people using "bigger fonts" options in their browsers or on their phones, which solves this problem from my point of view.
I created an account just so I could say that as a legally blind person, I cannot use some websites without being able to zoom in. It is extremely frustrating when I encounter a site that has disabled zoom. Please don't do it!
>Sometimes you see all kinds of complicated workarounds for that, such as detecting an orientation change and temporarily blocking zooming, or detecting an attempt to zoom and then disabling the restriction temporarily so if the user repeatedly tries to pinch-zoom then subsequent ones work.
Chris_Newton's comment seems to have possible workarounds that can fix this issue. I'll trust your decision whatever you go with though, and thanks for Skeleton!
An option to increase text size in the interface is probably going to be even better than allowing zoom, since it will reflow the text and not require the user to scan left and right around the zoomed-in text.
Of course, this is how our browsers used to work before the makers decided to remove or hide that feature. I've never seen it on a mobile device. Does anyone understand the reasons behind that move? Even if you think page zoom is 'better' than text scale, surely it doesn't make sense to disable the latter altogether?
I've struggled with these issues before, and have tried then backed away from the same maximum-size solution.
Fortunately, #2 can be resolved easily by setting input,textarea{font-size:16px}. There are problems with 16px for all inputs (especially if using a custom font with different metrics than the default), but it preserves a significant usability feature. A fair trade, even if it means using system default inside of inputs.
Regarding blurry images, I favor suboptimal delivery of content over failure to deliver every time.
