on a favorite or retweet button which tweet I'd be favoriting or retweeting. • A lot of the information is useless and redundant: • Saying "proﬁle picture" for every proﬁle picture gets annoying • Having to swipe thru all the buttons for every tweet is annoying
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...
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?
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-speciﬁc features
• 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