1] Component Name: SelectToSpeak

Guideline 1 (Clarity): Component name should be descriptive beyond the core
project team
(i.e. please avoid using non-industry standard abbreviations, code words,
project names, etc...)

Guideline 2 (Permanence): Component names should describe features/
functions and not team names, code locations, etc..., which are more
subject to change and make the hierarchy less predictable for people
triaging issues.
The name of the feature is Select-To-Speak

Guideline 3 (Specific): Components are meant to explicitly track functional
work areas.  If you are trying to track a Proj(ect) or an on-going effort
(e.g. Hotlist-Conops), please instead request a label for a (Proj- or
Hotlist-)
Select-to-Speak is a feature just like Chromevox. At this point it has enough crbugs to warrant its own component.

Guideline 4 (Discoverable/ Predictable): Components should be parented
where people would logically expect to find them (i.e. follow product
decomposition when naming versus team decomposition)
This is the product name, and it's an accessibility feature

2] Parent Component (e.g. Blink, UI>Browser, etc...): UI>Accessibility

Note: We generally avoid creating new component namespaces, unless there is
a new hierarchy that needs to be expressed.  Please try and use existing
components as parents.

3] Description of Component: The Accessibility feature Select-to-Speak on Chrome OS

4] Admin/ Owner: katie@chromium.org

5] Please specify what triage practices will be followed for the component
(i.e. what team will do it and how frequently).
The Chrome Accessibility team will triage these bugs similarly to the rest of UI>Accessibility. Specifically, the Select-to-Speak owner (katie@chromium.org) will go through the bugs list bi-weekly to make sure all bugs are triaged.