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

Expose accessibility on iOS #1664

Closed
Hixie opened this Issue Feb 8, 2016 · 3 comments

Comments

Projects
None yet
4 participants
@Hixie
Copy link
Contributor

Hixie commented Feb 8, 2016

No description provided.

@Hixie Hixie added this to the Flutter 1.0 milestone Feb 8, 2016

@chinmaygarde chinmaygarde self-assigned this Feb 8, 2016

@Hixie Hixie added a: accessibility and removed engine labels Feb 9, 2016

@chinmaygarde chinmaygarde removed their assignment Feb 29, 2016

@tvolkert tvolkert added the priority:P1 label Mar 4, 2016

@tvolkert tvolkert modified the milestones: Next, Flutter 1.0 Mar 4, 2016

@tvolkert tvolkert removed the priority:P1 label Mar 4, 2016

@abarth

This comment has been minimized.

Copy link
Contributor

abarth commented Mar 9, 2016

Todd said he was going to look at this issue.

@tvolkert

This comment has been minimized.

Copy link
Contributor

tvolkert commented Apr 22, 2016

flutter/engine#2594 wires up basic knowledge of our widget tree exposed as accessible elements.

Sub-tasks that need doing:

  • Communicate when a view is modal
  • Default actions
  • Incrementing and decrementing adjustable elements
  • Scroll gestures
  • Escape gesture and semantic escapes

tvolkert added a commit to flutter/engine that referenced this issue May 6, 2016

Move node implementation to Objective C (#2652)
* Move node implementation to Objective C

This changes AccessibilityBridge::Node (C++) to be AccessibilityNode (objc)
in order to have the nodes returned directly as ui accessibility elements.
This buys us a few things:

1) We can now return an element tree instead of a flat list, thus negating
   the need to maintain a global rect and global translation
2) We use less memory since we don't need to instantiate both nodes and
   their ensuing accessibility elements
3) accessibility elements can now implement the methods necessary to respond
   to events like user scrolling

flutter/flutter#1664

tvolkert added a commit to flutter/engine that referenced this issue May 6, 2016

tvolkert added a commit to flutter/engine that referenced this issue May 9, 2016

Wire up accessibility scrolling (#2664)
* Wire up accessibility scrolling

flutter/flutter#1664
@tvolkert

This comment has been minimized.

Copy link
Contributor

tvolkert commented May 9, 2016

Calling this done for v1. I filed separate issues for the remaining tasks needed before we can call Flutter apps on iOS 100% accessible:

#3814
#3815
#3816
#3817
#3819
#3821

@tvolkert tvolkert closed this May 9, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment