Tabs > Determine purpose of growing tabs example

In the accessibility audit for tabs it was noted that the growing tabs example (and story) have shortcomings since a screen reader user wouldn't be aware that a new tab has been added to the tablist.

It's unclear if this example was only to demonstrate the overflow behavior, or if it fits a real use case where tabs can be added after a page load. If it's only by way of example, then it can be removed in favor of the scroll example. If this fits with a real use case then work needs to be done to ensure that a screen reader user would understand that a new tab has been added (likely using aria-live.

Please add your thoughts and comments to help determine the direction.