Reporter submitted the following additional info: The bug referenced in both of those reports has been closed. In fact there is actually a solution to this now if you follow the trail of reports and then then search on the new configuration option. A better place to be directing people (like me) that open bugs of this nature would be the following set of links:
http://kb.mozillazine.org/Ui.key.generalAccessKey http://kb.mozillazine.org/Ui.key.chromeAccess http://kb.mozillazine.org/Ui.key.contentAccess