Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Self-Audit for Accessibility #7

Open
Tracked by #24
cbhernan opened this issue Jul 21, 2023 · 1 comment
Open
Tracked by #24

Self-Audit for Accessibility #7

cbhernan opened this issue Jul 21, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@cbhernan
Copy link
Collaborator

Problem

Once we have the MVP (Minimum Viable Product) in a good spot, we should revisit for accessibility (if necessary).

Proposed Solution

I've used the Wave extension to audit work for accessibility: https://chrome.google.com/webstore/detail/wave-evaluation-tool/jbbplnpkjmmeebjpijfedlgcdilocofh

These resources should also help with getting started on Accessibility and Flutter
https://docs.flutter.dev/accessibility-and-localization/accessibility
https://medium.com/@enzoftware/flutter-accessibility-getting-started-52286746314e

@cbhernan cbhernan added the enhancement New feature or request label Jul 21, 2023
@cbhernan
Copy link
Collaborator Author

cbhernan commented Apr 11, 2024

There's currently no support for header hierarchy

https://www.github.com/flutter/flutter/issues/97894

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant