On Mon, Feb 1, 2016 at 04:33 am, Jason White <[email protected]> wrote: To be fair to the technical support person, if it wasn't their bug but Adobe's, then there might not have been any other practical work-around until Adobe fixed it in an update. "Just don't do the action that triggers the bug until it's fixed" seems to me to be good advice.
Amen!! Even the FS Tech Support rep knows that this is a workaround, and a bad one, not a solution. But when an issue is being triggered due to software interactions that are beyond your control and not of your own making there's nothing to do except identify a workaround and/or either asking the person experiencing the problem to report it to the other vendor or do so yourself. I've not been front line technical support for a company like FS, but have done help desk type stuff a lot and am front line technical support of a sort in my private business. There are times when you know what's wrong and it's completely beyond your power to make the fix and it's really frustrating. What's really frustrating for the end user, though, is you can never really know when these statements are real versus "passing the buck" and both happen. I've been in a JAWS 17 installation failure vortex where I really can't decide who's dead on accurate versus trying to pass the buck at both FS and Microsoft Accessibility. Brian
