Issue 678991  has been merged into this issue.

Possibly related, possible dupe of  bug 777051 

 Issue 777051  has been merged into this issue.

I decided to dupe out 777051 since these bugs are similar enough. 

Repro steps for another way of looking at this:
What steps will reproduce the problem?
(1) Enable JAWS, open Chrome
(2) use ctrl + t to create at least one new tab and one
(3) Use ctrl + 1, ctrl + 2, etc. to select tabs 

What is the expected result? Title of the tab is read

What happens instead? Title of the tab is NOT read, just the number is spoken

NVDA reads the title of each tab whereas JAWS does not. 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/3700a46c532af05ed573ee417e2437c398352fcb

commit 3700a46c532af05ed573ee417e2437c398352fcb
Author: Aaron Leventhal <aleventhal@chromium.org>
Date: Mon Jan 22 16:30:58 2018

Remove spurious focus event in UI during tab switching

Do not advance focus to the IconLabelBubbleView when switching tabs as
this causes screen readers to read the contents of that view, and in the
case of JAWS, causes it to also not read the new focus within the tab.

The spurious focus event was caused by the following line:
SetFocusBehavior(FocusBehavior::NEVER);
This resulted in a call to View::AdvanceFocusIfNecessary().

This CL cleans up the code path that occurs when we are emptying the
content area prior to attaching new content, including only the
necessary lines of code that would have run, need to run and
are not harmful to accessibility.

Bug:  791757 , 777051 
Change-Id: I81cfd39710e0bb0beaeb8a571ce3b899e9b71d7e
Reviewed-on: https://chromium-review.googlesource.com/868475
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: Trent Apted <tapted@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#530878}
[modify] https://crrev.com/3700a46c532af05ed573ee417e2437c398352fcb/chrome/browser/ui/views/frame/browser_view.cc
[modify] https://crrev.com/3700a46c532af05ed573ee417e2437c398352fcb/chrome/browser/ui/views/frame/browser_view_focus_uitest.cc

Hello testing team, please verify with screen readers on all platforms as well as both Ctrl+Tab and Ctrl+digit, Ctrl+W to close, etc.

Chrome: 66.0.3349.0 (Official Build) canary (64-bit) (cohort: Clang-64)
NVDA 2017.4
JAWS 2018

# Open two tabs with different content
# Focus the omnibox on one tab
# Press ctrl+tab a few times using NVDA or JAWS
# Notice that NVDA and JAWS don't announce page title on the tab where the omnibox has focus

Expected: Page title should always be announced when tab receives focus

Actual: Omnibox title is announced instead of page title if the omnibox is focused

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/3dfddc05c6fea9d96313e62a8093d84823bec87c

commit 3dfddc05c6fea9d96313e62a8093d84823bec87c
Author: Aaron Leventhal <aleventhal@chromium.org>
Date: Fri Mar 09 16:10:08 2018

Focus event to indicate context if UI focused after tab switch

When switching to a tab that has the Omnibox or other UI focused,
screen readers do not read the title of the document being navigated to.

For the case where a tab is switched, and the UI is about to be focused,
fire an extra focus event on the widget's root view so that the document
title is read before the UI focus.

TBR: tsepez@chromium.org
Bug:  791757 
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I19a91eaac1c24dfd04ab3458a41aaa0c512a8739
Reviewed-on: https://chromium-review.googlesource.com/938778
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542131}
[modify] https://crrev.com/3dfddc05c6fea9d96313e62a8093d84823bec87c/chrome/browser/ui/views/frame/browser_view.cc
[modify] https://crrev.com/3dfddc05c6fea9d96313e62a8093d84823bec87c/chrome/browser/ui/views/tab_contents/chrome_web_contents_view_delegate_views.cc
[modify] https://crrev.com/3dfddc05c6fea9d96313e62a8093d84823bec87c/chrome/browser/ui/views/tab_contents/chrome_web_contents_view_delegate_views.h
[modify] https://crrev.com/3dfddc05c6fea9d96313e62a8093d84823bec87c/chrome/browser/ui/views/tab_contents/chrome_web_contents_view_focus_helper.cc
[modify] https://crrev.com/3dfddc05c6fea9d96313e62a8093d84823bec87c/chrome/browser/ui/views/tab_contents/chrome_web_contents_view_focus_helper.h
[modify] https://crrev.com/3dfddc05c6fea9d96313e62a8093d84823bec87c/chrome/common/extensions/api/automation.idl
[modify] https://crrev.com/3dfddc05c6fea9d96313e62a8093d84823bec87c/chrome/renderer/extensions/automation_ax_tree_wrapper.cc
[modify] https://crrev.com/3dfddc05c6fea9d96313e62a8093d84823bec87c/third_party/closure_compiler/externs/automation.js
[modify] https://crrev.com/3dfddc05c6fea9d96313e62a8093d84823bec87c/ui/accessibility/ax_enum_util.cc
[modify] https://crrev.com/3dfddc05c6fea9d96313e62a8093d84823bec87c/ui/accessibility/ax_enums.mojom
[modify] https://crrev.com/3dfddc05c6fea9d96313e62a8093d84823bec87c/ui/accessibility/platform/ax_platform_node_auralinux.cc
[modify] https://crrev.com/3dfddc05c6fea9d96313e62a8093d84823bec87c/ui/accessibility/platform/ax_platform_node_mac.mm
[modify] https://crrev.com/3dfddc05c6fea9d96313e62a8093d84823bec87c/ui/accessibility/platform/ax_platform_node_win.cc
[modify] https://crrev.com/3dfddc05c6fea9d96313e62a8093d84823bec87c/ui/views/accessibility/native_view_accessibility_base.cc

@dsexton, all 4 combinations of switching between tabs should be addressed, 2 types of focus in first tab times 2 types of focus in second tab. (tab with focus in content or location bar) then switching to (new tab with focus in content or location bar). 

Great work!