mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
![]() Rework on the text button use case to pass [b/347102786](https://b.corp.google.com/347102786), After talking with the tester, it seems like there isn't an issue with the A11y of the text button, rather just how the test case is set up. In order for the text case to pass, there needs to be real time feedback of an action that is done by pressing the text button (think of a dialog popup, or form submission notification). So I rewrote the test case to mimic a simple form with a submit button that once submitted, will let the user know it is submitted with a snack bar notification. https://screencast.googleplex.com/cast/NTM0ODc1NDIxMDE2MDY0MHwzYWI4MTZhMS1hMA |
||
---|---|---|
.. | ||
android | ||
ios | ||
lib | ||
linux | ||
macos | ||
test | ||
web | ||
windows | ||
.metadata | ||
analysis_options.yaml | ||
pubspec.yaml | ||
README.md |
a11y_assessments
This app is used for internal testing.
Release a new version for Android
pre-requisite: This can and should only be done by a googler and you must also be in the flutter.dev play console account.
-
Follow https://docs.flutter.dev/deployment/android to create a keystore file if you don't already have one.
-
Bump the pubspec.yaml version
-
Create a key.properties file in
android/
directory following this format.
storePassword=<password>
keyPassword=<password>
keyAlias=upload
storeFile=<keystore path>
- Run
flutter build appbundle
and upload the artifact to play console
Release a new version for iOS
pre-requisite: This can and should only be done by a googler and you must also be in the FLUTTER.IO LLC developer account with iOS distribution permission.
- Bump the pubspec.yaml version
- Run
flutter build ipa
and upload the artifact to app store using transporter or other tools. For more information, see https://docs.flutter.dev/deployment/ios. - Once the app is in TestFlight, add appropriate testers to the app so they can start testing.