Hi George, we added some JavaScript to the page to block the right click menu in Chrome: https://gist.github.com/huertanix/01c06b0f92b57e279271.

Thanks for any suggestion.

Hi Steven,

Unfortunately, I cannot give you a specific model that will meet your needs as our own mounts are all stationary. However, I think that what you are looking for will be a mount that can tilt up to 45 degrees. That should be a sufficient range for your needs, but given the size of the PC you may not be able to get it to tilt the full range as it will hit the wall. Perhaps someone can build a stud for you that will let you set the mount a few inches from the wall, allowing people to tilt it completely.

Additionally, you want to ensure that it can handle the weight of the PC at all angles and one that uses four mounting screws to adhere to the wall itself is highly advisable. In the past I’ve found that some mounts tend to tilt downward with the weight of the PC/TV, but often it is hard to tell when shopping for them, so it may be best to try out a few models.

I am converting a non-functioning mechanical display to a touch screen display. After reading Brian Weirich article, I have ordered a HP ProOne 400 and it will be here in a few days. I plan to mount the ProOne to a desktop that will allow easy wheelchair access.

Now I need some advise on a mount that will easily tilt forward to facilitate wheelchair access and tilt back for easy viewing by someone that is standing. I saw an article on this, but can’t find now. Any suggestions would be appreciated.

Assigned User Access mode was something that we tried in the beginning, but was unfortunately ruled out for a number of reasons. The core problem of achieving the clean, locked down experience we wanted with Assigned User Access was that these webpages were intended to be viewed in Google Chrome. When using Chrome as a Windows 8 app, which is required for Assigned User Access, issues arose with disabling pinch-to-zoom, viewing the right click menu, the URL bar being accessible, and a few other minor things that thankfully faded from memory.

Each of these problems COULD be addressed in this mode, but the process quickly degenerated into a game of break-fix Whack a Mole, which, besides being frustrating, was sucking up Developer and Sysadmin time. I ended up drawing out the path to resolution for both methods and found that disabling Explorer.exe and running Chrome with the switches described proved to be the path of least resistance that provided the experience we needed.