Add implementation of UIAccessibilityContainer Protocol

[JanenePappas]

Addresses #31, to add accessibility; creates accessible element consisting of the title and description when a new message is shown and notifies the framework to read the message

[JanenePappas]

@terryworona You would prefer just the accessible element instance and not the usual pattern of keeping a collection? Certainly can do it that way. Will modify and re-submit.

The accessibility frame is actually irrelevant (found after more testing after your comment). I'll remove it since the user can't tap on it anyway.

[terryworona]

I'm not really saying to do it one way or another, just curious why it's a collection if we only really have a single element to keep track of; I guess a collection scales better for (potential) future changes.

[cdzombak]

If this does remain a collection, this property doesn't need to be publicly exposed regardless.

[cdzombak]

(And definitely doesn't need to be mutable.)

[JanenePappas]

I've submitted an updated push for keeping a single element. I would agree that a collection is definitely more scalable, however.

[cdzombak]

👍

[terryworona]

This looks good. I'll pull it in later tonight or tomorrow. Thanks for the contrib.

[JanenePappas]

Great, thanks Terry. Happy to add something to the project.

Janene

On Mar 31, 2014, at 8:04 PM, terryworona notifications@github.com wrote:

This looks good. I'll pull it in later tonight or tomorrow. Thanks for the contrib.

—
Reply to this email directly or view it on GitHub.

[terryworona]

I pulled it in today and made some cleanup changes.

I'm a bit of a novice when it comes to accessibility; but I tested it on device and the voice doesn't exactly work (the message is cut off when I tap the button to present it). Am I missing something?

[JanenePappas]

The changes are structured to initiate the voice-over immediately when the banner is presented. It does not cut out unless the user taps on it, as tapping on the banner is set to dismiss it in itemSelected. If you do nothing, does it complete reading of the message?

[terryworona]

The voice over begins, but is then cut off by another voice over describing the button that was pressed to show the message; this is all within the demo app.

You mind checking out the demo project in master to see if you can reproduce?

[JanenePappas]

Will do.

[terryworona]

Sweet. Go ahead and pull now, I just checked in a last minute change! Thanks!

[JanenePappas]

It appears the demo's view controller is affecting accessibility. I've put your version of TWMessageBarManager in my app and it works correctly. Researching more.