I cannot reproduce this.
Please indicate at which step the process breaks down.

Chrome: 67.0.3396.99 (Official Build) (64-bit) (cohort: Stable)
NVDA: 2018.2.1

Steps to repro:
# With NVDA running, in Chrome, open a new document in docs
# Type two lines of text such as:
this is a test
this is the second line
# Press alt+t to navigate to the tools menu
# Arrow up to 'translate document' and press enter
# Tab to the list of languages
# Press 'f' several times until 'French' is selected
# Press enter
# Tab to the translate button
# Press enter
# A new document window should open with the translated text

Note: The translate button will not be available if the user already has a document with the same filename. They should choose another name.

@Reporter: Could you please respond to comment# 2, hence adding Needs-Feedback label.

Thanks!

Version of NVDA is 2018.2.1
Issue is in the last line of David's comment line:
Document was not getting translated to french earlier however now that particular problem is resolved. It does get translated.

However the current issue is in the translated content. User gets confused as a lot of non related stuff are read aloud repeatedly prior to the translated text, so the translated text is read at the last which is confusing

Video clipping attached.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

@Viswa: Friendly reminder to change the status of the bug from unconfirmed to assigned.
 If any of the information is pending for this bug, would be able to provide.

Any new info that is announced is the result of a new tab opening with the newly-translated document.
It should be a very similar experience to opening a document from Drive.
Users may have expected the text to be translated in place and thus the confusion.