Showing posts with label software quality. Show all posts
Showing posts with label software quality. Show all posts

2011-03-01

Acrobat Pro #Fail: Why Software Standards Matter for Accessibility

Acrobat Pro Resolution-dependent Window
Acrobat Pro 9 -- not just the Reader, but the commercial off-the-shelf product -- is a mainstay product of Adobe. Adobe is a publicly held company with more than 7,000 employees. It's Fortune rank in 2009 was 601. It is reasonable to expect that Adobe has in place solid standards for its products. These standards make Adobe products similar across platforms, consistent with each other, and consistent with platform-specific standards -- that is, Windows, Apple or Linux platforms. 

For these reasons, coupled with the maturity of Acrobat 9 Pro, when a customer contacted me with a Windows problem, the working assumption is that the user had accidentally clicked on some setting.  The symptom was that a dialog box used to control automatic insertion of headers and footers, such as Bates numbering, was partly off screen. There was no scroll bar for this dialog box, which had apparently been coded using the Multiple Document Interface (MDI) standard.  Unlike some daughter windows in Acrobat, this window could not be maximized, minimized or resized. The standard Microsoft Windows "Move" command worked, but the "Size" commands did nothing. As a result, the user couldn't see all the settings available, nor even click OK to invoke what few settings were visible.

A little casual research showed that my customer was not alone.  There is no solution for customers who use 800 x 600 resolution, single monitor displays. The "fix" is to increase resolution.

Not only is this a major nuisance, but for visually impaired and some netbook users, it creates a serious obstacle. Adding to the annoyance factor are the abundant comments in various forums which show that this problem must be known to Adobe. I don't know whether it's been "fixed" in Acrobat Pro X, which specifies a minimum resolution of 1024 x 576 (a bit odd, but there are a few netbooks that use this resolution), but the analyst producing requirements for the Acrobat Pro developer team should have either specified that all dialog boxes must operate within 800 x 600, or alternatively, since this is by today's standards a low resolution, provide an Acrobat startup warning that the resolution was below the minimum required.


Update I cross-posted this message to the aforementioned Adobe forum, and a user requested an explanation. One was received. In essence, no patch for the V9 problem was ever produced, but Adobe did address the problem in version X. The message as relayed by user cyberbiker1 follows. I'm not fully convinced that the accessibility issue has been addressed:
 "Unfortunately the 9.4.2 patch did not address anything relating to screen resolution.  The system requirements for Acrobat 9 on Windows operating systems includes a minimum resolution of 1024x768.  Simply put, Acrobat 9 and previous versions weren't designed for netbooks.  During the Acrobat 9 development cycle, netbooks were in their infancy. Acrobat X however, was designed with netbooks in mind, supporting a minimum resolution of 1024x576."

2009-01-28

Question Software Maintenance? You bet.

A cover story in Information Week (January 26, 2009) poses the radical question, "What if I don't pay maintenance?" Or, at least, what if I go to a third party for software maintenance instead of the manufacturer? Oracle and SAP are moving to an annual maintenance fee of 22%. The software life cycle cost has been growing steadily since the "standard" rate of 18% was exceeded by some major players. What irks many who might otherwise be willing to pony up is that customers have little control over how the maintenance revenues are spent. Author Mary Hayes Weier suggests the alternatives include open source, SaaS, third party support, renegotiation, or moving to self-service maintenance. Whether any of these are feasible for your scenario is unclear, but it is clear that few companies offer much transparency about where your maintenance revenues are being spent -- though those same firms will be the first to make claims to Wall Street about how those revenues account for bottom line results.

2008-08-10

MS05-051 "broke" Vista: HRESULT was 8007043c eventsystemobj.cpp

I pride myself on keeping my most critical Vista box well patched and happy (from a Microsoft point of view). I plan to use Vista for many years -- I even bought the "retail" version.

Imagine my surprise when I noticed that it was no longer accepting peer to peer network connections. "Hmm, I guess I'll try rebooting," I frowned. But Mr. Ultimate Vista refused to start up. It displayed the Vista logo, then, without any message or notice, rebooted itself again. This would have gone on indefinitely if I had not intervened.

I booted into safe mode, (luckily that worked!) looked at the System log (not a minor accomplishment, since some of the other log flavors were not viewable due to "could not connect" errors). The error that got my attention was "The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043c from line 45 of d:\rtm\com\complus\src\events\tier1\eventsystemobj.cpp." And a probably related message, "System log:The following boot-start or system-start driver(s) failed to load: ACPIaswSPspldrWanarpv6." Deeper frown.

I looked at the Reliability Monitor, and it showed nothing unusual for the past couple of months.

A TechNet forum post suggested a closer look at the Microsoft KB entry that is the title of this post. In short, the problem is with permissions policies -- apparently some critical Windows applications were locked out from the Registration directory.

This is an understandable "bug." What is less understandable is how this problem escaped the automated test tool sniffers one imagines that Microsoft has at its disposal. After all, the easiest problem for a test script to detect is a boot failure.

Before the era of web- or email-enabled newsgroup / forum posts, my system could have been down for days as I sorted this out.

One other thing: the Microsoft warrantee for Vista is 90 days after it's activated.