Currently we have >1000 open issues all under the single component UI>Accessibility. I've taken the time to sort them into more specific components.

Here are the temporary labels I applied:

NewComponent-Accessibility-ChromeVox
NewComponent-Accessibility-Compatibility
NewComponent-Accessibility-Features
NewComponent-Accessibility-Browser
NewComponent-Accessibility-Internals
NewComponent-Accessibility-Blink
NewComponent-Accessibility-DevTools
NewComponent-Accessibility-PDF

Here are the corresponding 8 new components I'd like to add with a brief description of each.

Suggestions welcome - this seems like a great time to suggest other names or locations for any of these. If the names for any of these are unclear, please check out the issues using the temporary labels, above.

Internals>Accessibility
(Out-of-process iframes, test infrastructure, failing tests, crashes, refactoring, etc.)

Blink>Accessibility
(ARIA, AOM, HTML, SVG, CSS, anything else Blink)

Internals>Plugins>PDF>Accessibility
(PDF plug-in accessibility)

Platform>DevTools>Accessibility
(DevTools accessibility)

UI>Accessibility>ChromeVox
(The ChromeVox screen reader on Chrome OS)

UI>Accessibility>Compatibility
(Making Chrome compatible with software like JAWS, NVDA, VoiceOver, TalkBack, Android Switch Access, etc.)

UI>Accessibility>Features
(Browser features and Chrome OS features/feature requests like Select-to-speak, Switch access, Magnification, High Contrast Mode, Caret Browsing, Stop Animation)

UI>Browser>Accessibility
(Toolbars, Bookmarks, Sign In Page, History, Settings, WebUI, etc.)