You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Accessibility] Three finger scrolling does not announce new content #64924
Unassign myself since i don't have time to work on this. Maybe able to solve by providing UIScrollViewAccessibilityDelegate to the FlutterScrollableSemanticsObject
This issue is marked P1 but has had no recent status updates.
The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub.
Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks!
Activity
goderbauer commentedon Sep 9, 2020
When clicking on the links I get "You're not authorized to access this page."
What kind of announcement is expected?
mehmetf commentedon Sep 9, 2020
Odd. I used to be able to access these. Asked for access.
chunhtai commentedon Jan 24, 2022
Unassign myself since i don't have time to work on this. Maybe able to solve by providing UIScrollViewAccessibilityDelegate to the FlutterScrollableSemanticsObject
https://developer.apple.com/documentation/uikit/uiscrollviewaccessibilitydelegate?language=objc
838 commentedon Nov 15, 2022
Any plan to look at this issue in future? 🙂
flutter-triage-bot commentedon Nov 27, 2023
This issue is marked P1 but has had no recent status updates.
The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub.
Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks!