Tweet
Tweet

Slide 1

Slide 1 text

Accessibility in the Real World Sommer Panage (@sommer)

Slide 2

Slide 2 text

Accessibility means using technology to overcome challeneges.

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

It looked so easy...

Slide 8

Slide 8 text

No content

Slide 9

Slide 9 text

No content

Slide 10

Slide 10 text

No content

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

The Ugly Tweetling

Slide 13

Slide 13 text

Once upon a time...

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

No content

Slide 17

Slide 17 text

According to the rules... EVERYTHING THAT ISN'T ALREADY TEXT MUST HAVE A LABEL, AND TEXT MUST BE ACCESSIBLE TO VOICEOVER.

Slide 18

Slide 18 text

No content

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

No content

Slide 21

Slide 21 text

No content

Slide 22

Slide 22 text

extension Date { private static let timestampFormatter: DateComponentsFormatter = { let formatter = DateComponentsFormatter() formatter.allowedUnits = [.day, .hour, .minute, .second] formatter.unitsStyle = .abbreviated formatter.maximumUnitCount = 1 return formatter }() var visualTimestamp: String { let now = Date() return Date.timestampFormatter.string(from: self, to: now)! } }

Slide 23

Slide 23 text

extension Date { private static let visualTimestampFormatter: DateComponentsFormatter = { let formatter = DateComponentsFormatter() formatter.allowedUnits = [.day, .hour, .minute, .second] formatter.unitsStyle = .abbreviated formatter.maximumUnitCount = 1 return formatter }() private static let audioTimestampFormatter: DateComponentsFormatter = { let formatter = DateComponentsFormatter() formatter.allowedUnits = [.day, .hour, .minute, .second] formatter.unitsStyle = .full formatter.maximumUnitCount = 1 return formatter }()

Slide 24

Slide 24 text

. . . var visualTimestamp: String { let now = Date() return Date.visualTimestampFormatter.string(from: self, to: now)! } var audioTimestamp: String { let now = Date() return Date.audioTimestampFormatter.string(from: self, to: now)! } } let myLastBirthday = Date(timeIntervalSinceNow: -6048000) myLastBirthday.visualTimestamp // 70d myLastBirthday.audioTimestamp // 70 days let sixSecondsAgo = Date(timeIntervalSinceNow: -6) sixSecondsAgo.visualTimestamp // 6d sixSecondsAgo.audioTimestamp // 6 days

Slide 25

Slide 25 text

And voila! let timestampLabel = UILabel() timestampLabel.text = tweetDate.visualTimestamp timestampLabel.accessibilityLabel = tweetDate.audioTimestamp

Slide 26

Slide 26 text

No content

Slide 27

Slide 27 text

No content

Slide 28

Slide 28 text

No content

Slide 29

Slide 29 text

No content

Slide 30

Slide 30 text

It's “accessible” but... • I cannot tell when I am on a favorite or retweet button which tweet I'd be favoriting or retweeting. • A lot of the information is useless and redundant: • Saying "profile picture" for every profile picture gets annoying • Having to swipe thru all the buttons for every tweet is annoying

Slide 31

Slide 31 text

• With swipe navigation it takes up to 9 or 10 swipes just to get thru one tweet. • It is hard to get a quick summary of the timeline by swiping thru it - want to be able to swipe thru 1 tweet at a time • This does not make for an good user experience. • And so on...

Slide 32

Slide 32 text

No content

Slide 33

Slide 33 text

No content

Slide 34

Slide 34 text

No content

Slide 35

Slide 35 text

Tradeoffs • Not everything on screen is its own accessibilityElement, but the user has a more efficient experience • Interacting with tweets requires interactions beyond basic button activation, but we optimize for reading, which is the most common use case.

Slide 36

Slide 36 text

The big questions • When synthesizing all the contents of a tweet into one string, what order does this information go in? What do I leave in and what do I take out? • How do I make the actions (retweet, like, etc.) easily accessible when they're not Accessibility Elements?

Slide 37

Slide 37 text

One string to rule them all • Look at other apps • Talk to users • Talk with other accessibility advocates • Make the call (and maybe be wrong)

Slide 38

Slide 38 text

No content

Slide 39

Slide 39 text

Where to put the actions?

Slide 40

Slide 40 text

No content

Slide 41

Slide 41 text

No content

Slide 42

Slide 42 text

The moral of the story (1/2) Accessibility is more than reading onscreen text and providing labels.

Slide 43

Slide 43 text

The moral of the story (2/2) Accessibility is about creating equal experiences rather than equal UI.

Slide 44

Slide 44 text

Caught between an AB Test and a Hard Place

Slide 45

Slide 45 text

Coordination on a single feature

Slide 46

Slide 46 text

Coordination on a single feature

Slide 47

Slide 47 text

Accessibility at a big company needs to: • Have a central point of contact and information. • Have its work distributed among all teams.

Slide 48

Slide 48 text

The accessibility hub • Place where all teams can go for "accessibility questions" • Coordination of accessibility work with PMs, designers and engineers. • Advocates with to the top of the org-chart • Educators throughout the company • Accessibility-specific features

Slide 49

Slide 49 text

The accessibility spokes • Designers coming up with VoiceOver copy • PMs budgeting time and engineering resources for accessibility work • Engineers writing the code to make a feature accessible • Top level organization members to prioritize accessibility at the org level

Slide 50

Slide 50 text

A few features works great...

Slide 51

Slide 51 text

Hundreds, not so much...

Slide 52

Slide 52 text

?!?!?!?!?!? ??? ?!?!?!?!

Slide 53

Slide 53 text

bugs...Bugs...BUGS!

Slide 54

Slide 54 text

Time for a tough choice...

Slide 55

Slide 55 text

No content

Slide 56

Slide 56 text

No content

Slide 57

Slide 57 text

So many down sides • Forces VO users to work harder than non-VO users • Does not put VO user's voices into experiments • Is unprecedented in similar apps But one up side • The vast majority of the Twitter app is accessible

Slide 58

Slide 58 text

The moral of the story Sometimes there is no (actionable) right answer; you just have to do your best. ...And sometimes you maybe get it wrong.

Slide 59

Slide 59 text

Alice in Startupland

Slide 60

Slide 60 text

Starting at the beginning at Chorus Fitness

Slide 61

Slide 61 text

Priorities from Day 1: • Dynamic Type • High color contrast ratios • Simple interactions • Properly sized tap-targets.

Slide 62

Slide 62 text

Bake accessibility in from the beginning!

Slide 63

Slide 63 text

No content

Slide 64

Slide 64 text

No content

Slide 65

Slide 65 text

No content

Slide 66

Slide 66 text

Accessibility from the beginning • Consistent dialog with designers thru each design iteration • Investing early in app-wide accessibility like Dynamic Type and colors

Slide 67

Slide 67 text

Accessibility from the beginning • Adding “no-brainer" accessibility to the code as I write it • Noting an accessibility plan for more complex UI but waiting until it's "for sure" to implement

Slide 68

Slide 68 text

Caveat - - - - - - - - Staving off some accessibility work means making sure it is clear to everyone that before we can ship there will be some extra time required to lock down any incomplete accessibility implementations.

Slide 69

Slide 69 text

But, Sommer?!?

Slide 70

Slide 70 text

Staving off some accessibility work is a compromise that allows us to move faster BECAUSE we have no users.

Slide 71

Slide 71 text

However, not having users DOES NOT mean we are not thinking about accessibility at every step.

Slide 72

Slide 72 text

No content

Slide 73

Slide 73 text

No content

Slide 74

Slide 74 text

Accessibility is more than VoiceOver and Switches: it's a bridge for all users to your content and your mission.

Slide 75

Slide 75 text

The moral of the story (1/2) Accessibility can be prioritized from the beginning in such a way that it doesn't slow down a speedy new startup (and doesn't drive the engineers bonkers).

Slide 76

Slide 76 text

The moral of the story (2/2) Small start-ups are often in the exciting position to think of accessibility questions beyond their app!

Slide 77

Slide 77 text

No content

Slide 78

Slide 78 text

Thank you so much!

Slide 79

Slide 79 text

Don't hesitate to reach out: Sommer Panage [email protected] @sommer on Twitter