As part of my work on our current HTTPS Indicator UI study (issue 803138 and  issue 803501 ), some regressions around the accessibility labels for the visual elements of our security indicators came up ( issue 812034 ).

tapted@ discussed (https://crrev.com/c/917282) a potential longer term solution of having ToolbarModelImpl::GetSecureVerboseText() explicitly set the accessibility label:

> Would it would be more robust to pass a `base::string16* accessibility_label` to 
> ToolbarModelImpl::GetSecureVerboseText()? or have it return a std::pair?  the 
> logic matches for now, but when the logic in GetSecureVerboseText changes again, 
> it will be easy for these to get out of sync.

This seems like a good idea to investigate further, although the specific code in question (c/b/ui/cocoa/location_bar/page_info_bubble_decoration.mm) will likely be going away with the mac views work. However, this could still be a good way to generalize how the security indicators get labeled for accessibility purposes, e.g. making it easier to give more descriptive labels for screen-readers.