Seeking feedback: Improving dev experience when working on accessibility #176237
Description
Creating an accessible app is vital—it ensures everyone, everywhere can use our products. With the growing industry focus on accessibility standards (like EAA, WCAG, and VPAT), we've seen a rise in customer-reported accessibility issues. Unfortunately, these are often discovered late in the cycle, right before a release, putting high pressure on deadlines.
We want to shift from reactive firefighting to proactive development. To do this, we need to empower developer to catch accessibility violations early in development workflow.
As the first step, we'd would to gather some feedback from Flutter developers for the following:
-
What have been your biggest pain points or notable successes with accessibility so far?
-
What tools, features, or improvements to existing debugging tools do you think would be most helpful for catching and fixing accessibility issues in Flutter?
-
Do you have any other suggestions or feedback regarding accessibility in Flutter that you'd like to share?
Please use the comment in this issue to leave your feedback.