[Draft] Submitting a11y fixes
Accessibility fixes should broadly follow the Open edX Product Contribution Guide process. Namely, an issue should be filed first and validated with an a11y expert that the bug exists and needs fixing, with a discussion around the appropriate way to fix the issue.
The product team should be pulled in if a proposed a11y fix alters the platform UI or UX in any way. For example, a fix that adjusts keyboard navigation without affecting anything visual does not need product input, however, a fix that requires a visual change to a Paragon component would.
Once a PR comes in that requires Product input, the flow would look like this:
