When accessibility_checks violations occur, they currently provide the view class of the incorrect view as well as its ancestors. This is useful, but often not enough.

For example, the following error message does not really help show which combobox is broken:
View violates ViewHierarchyHasAccessibilityErrors():
RootView > ui/views/window/NonClientView > ui/views/window/ClientView > View > View > View > View > views/Combobox (id 0)
- Focusable View has no accessible name or placeholder, and the name attribute does not use kAttributeExplicitlyEmpty.

A better error message would include the stack trace showing how the view was created in the first place, for example, the following error message shows exactly that the errant view was created by CardUnmaskPromptViews:

View violates ViewHierarchyHasAccessibilityErrors():
RootView > ui/views/window/NonClientView > ui/views/window/ClientView > View > View > View > View > views/Combobox (id 0)
- Focusable View has no accessible name or placeholder, and the name attribute does not use kAttributeExplicitlyEmpty.

The following stack created the inaccessible View:
#0 0x7fbff239554c base::debug::StackTrace::StackTrace()
#1 0x7fbff0236db4 views::View::View()
#2 0x7fbff01da08f views::Combobox::Combobox()
#3 0x000003cf525c autofill::CardUnmaskPromptViews::InitIfNecessary()
#4 0x000003cf5672 autofill::CardUnmaskPromptViews::GetContentsView()
#5 0x7fbff0247bb0 views::Widget::Init()
#6 0x7fbff02519fd views::DialogDelegate::CreateDialogWidget()
#7 0x000003f005db constrained_window::CreateWebModalDialogViews()
#8 0x000003f00493 constrained_window::ShowWebModalDialogViews()
#9 0x0000033b7ac3 autofill::CardUnmaskPromptControllerImpl::ShowPrompt()
#10 0x00000184e4da autofill::(anonymous namespace)::CardUnmaskPromptViewBrowserTest::ShowUi()
#11 0x00000184ef66 autofill::(anonymous namespace)::CardUnmaskPromptViewBrowserTest_DisplayUI_Test::RunTestOnMainThread()
#12 0x000002e5a2bf content::BrowserTestBase::ProxyRunTestOnMainThreadLoop()