Katie McCormick

Hi @yaili -- we have these: [[Epic]: Self-Serve Platform](https://github.com/github/accessibility/issues/492) and [[Tracking]: Self-Serve Platform](https://github.com/github/accessibility/issues/496). You can see there are some placeholder issues inside the Tracking issue, but some are also fleshed...

@yaili @vdepizzol -- We will absolutely get your reviews on these documents. I was hoping for them! Let me give a quick explanation of our driving philosophy for where things...

👋 Hi @broccolinisoup ~ What is the process for addressing breaking behavioral changes that were introduced to be accessible? We don't want to default to a less-accessible experience. cc @lesliecdubs...

Thank you @siddharthkp ! I appreciate the clear process here. When it comes to evaluating the feature changes that are causing the "draft" state, what is the process?

@broccolinisoup - This makes total sense. Thank you for clarifying, and let us know if you need the Accessibility Team to support.

cc @primer/accessibility 👀

👋 Hi @siddharthkp - Would you cc @primer/accessibility-reviewers when this is out of Draft? 🙏

👋 Hey @brunoprietog -- Feel free to pick this up and assign yourself if you like. You can cc me and the other contributors on any PRs / drafts. Would...

@brunoprietog: The current screen-reader feedback div is identified as `${this.results_id}-feedback` ID on [this line](https://github.com/github/auto-complete-element/blob/main/src/autocomplete.ts#L31). I think the majority of the work would need to be done within [`this.updateFeedbackForScreenReaders`](https://github.com/github/auto-complete-element/blob/608ab910ef29308384be74ccec90cdb12ffc473b/src/autocomplete.ts#L180) to interpret...

@keithamus - I know we have a delay on the screen reader feedback, but I'm concerned that triggering an event based on the feedback changing would announce the default phrase...