Consider a process where icon-only buttons get a default accessible name

[mbgower]

This topic was first explored as part of a conversation in the Carbon Accessibility Guild. Reviewing that topic is not necessary, but may provide some background.

I will restate the problem space and suggested solution space.

1. Carbon has a lot of icon-only buttons in its library.
2. My understanding is that teams using an icon-only button have to create an accessible name.
3. Often the friendly name may be an okay accessible name, but many times it's not.
4. Leaving each time to name buttons increases the risk of poor accessible names being designated. It's also not very scalable.

I'm suggesting creating a default accessible name for each icon, which could be added to the friendly name and alias information in some libraries such as https://github.com/carbon-design-system/carbon/blob/main/packages/icons/icons.yml For future icon-only buttons, suggesting an accessible name could be part of the adoption process.

Accessible names do not need to be unique. All the alternative versions of a button will likely have the same accessible name. Teams can still override, but the default will be a vetted accessible name, good in most uses.

I'm not suggesting any prescribed technical approach here, but i would like to have an exploration on whether this is deemed a doable and useful approach.

A somewhat related discussion took place in carbon-design-system/carbon-website#2682