Firefox 158.0.1: safely diagnose printing crashes with a screen reader

Updated: 22 October 2026. Does Firefox close on Windows when printing or saving a web page as PDF while a screen reader or other assistive technology is running? Mozilla lists this specific crash as fixed in Firefox 158.0.1, released on 20 October 2026. [1] This guide helps affected users and small IT teams identify the right symptom and verify an approved update without switching off accessibility tools.

What is actually confirmed?

Bug 2082376 concerns the Windows accessibility interface. Its tracker marks Firefox 158 as fixed and ESR 153 as unaffected. [2] That does not make every printing problem the same bug. A blank preview, wrong margins and a browser crash are different symptoms. Do not apply the version number 158.0.1 to ESR or change update channels solely because of this article.

Prepare without losing data

Save open work before restarting. Record Windows and Firefox versions, the update channel, and the assistive software's name and version. Use a harmless local sample page or approved test document without customer data. Note the destination folder and existing PDFs to avoid overwriting them. On managed computers, installation and approval remain the responsibility of the relevant IT team.

Five steps for a safe check

  1. Identify the symptom: record whether Firefox exits, only the preview hangs, or the printed result merely looks wrong. Does it affect a physical printer, Save to PDF, or both? A crash after requesting print with assistive technology running matches Mozilla's description, but does not prove Bug 2082376.
  2. Identify the installed edition: open Help and About Firefox from the Firefox menu. Read the version and channel. Downloading an update does not apply it; Mozilla requires a restart. [3] For managed installations, use the approved software route, not third-party download portals or parallel installations.
  3. Complete the update carefully: Mozilla identifies 158.0.1 as the corrected Release version. [1] Use a newer approved maintenance release if one is offered. Save work, finish the update restart, then verify the version actually running. Do not bypass enterprise policies; record a blocked update and refer it to the responsible team.
  4. Repeat the same workflow: keep the required assistive technology running and open the approved test document. Press Ctrl+P, deliberately choose the printer or PDF destination, and save a new file with a unique name. Test the output route that originally failed. Never send confidential documents to online converters.
  5. Check the result: does Firefox stay open? Can you reopen the generated PDF, confirm the expected pages and operate the workflow with the assistive software? Check required text and navigation functions separately. Avoiding a crash does not prove that a PDF is accessible. Record version, test case and outcome.

If the problem remains

If the crash remains reproducible after updating, collect the time, output route and a minimal-data description for IT. Compare with another harmless page; Mozilla's general printing guide also suggests comparison with another browser or printer. [4] This is diagnosis, not a promise of equivalent PDF accessibility. Do not start with broad profile resets, clearing print settings or disabling accessibility tools. Do not force changes to internal Firefox preferences from old forum posts.

Acceptance and recovery

Acceptance means verifying an approved corrected version after restart and successfully completing the affected workflow with the required assistive technology. If a new problem occurs, stop testing, preserve original documents and the existing profile, and let IT approve an alternative workflow. Do not independently downgrade to an older security-sensitive version. An alternative output route is useful only after checking content and required accessibility.

Sources and scope

Source-based guidance, not a Firefox or screen-reader test performed here and not a general compatibility guarantee. The acceptance sequence is our editorial recommendation. The documented 20 October fix provides the news basis, not a claimed search surge. No purchase recommendation or affiliate links.