amazonv: (Default)
[personal profile] amazonv
Micro Interactions, More like Micro Aggressions
Type: Breakout
Track: Design
For a Neurotypical person, an attention-grabbing, movement driven feature can be a friendly nudge alerting to a new enhancement or a welcomed hint that a chat is available if they have questions. Unfortunately for someone with attention-related disabilities, or Neurodivergent, that distraction can and often is the end of the road for a task. With the popularity of micro-interactions on the rise as mobile technology continues to grow, the barriers they create for people with attention-related and other cognitive disabilities rise along with it. In this talk Shell Little will discuss the difficult place we are at with these standard-less patterns that help some and block others using a variety of examples including in-the-wild patterns with a focus on mobile-based micro-interactions, all to answer the question ‘what is micro enough?’.
 
>> We're going to get started soon.  Thanks for your patience.  We'll get kicked off here shortly.
Hello to everyone that's already in the chat from all over the world.  That's really exciting.
Once again thank you, everyone, who is trickling in here.  We're going to get started in three minutes.  I'm Travis Marsca.  From Deque.  There are some questions about the availability of the slides.  Are those going to be available?
>> Yes.  I plan on making them available after the event.  I'm slow at getting slides out.  They will be.
>> No problem.  I wanted to be able to answer that.  We're about two minutes from start time.  Let's go ahead and go over a few things.  Again thanks, everyone, for joining.  My name is Travis.  I'll be your moderator.  We have Shell Little your speaker today.  Just a couple of housekeeping items to go over today's session will be recorded.  You'll have access to that as attendees as soon as it is available.  The slides once they are available to us and we make sure they are access will be up on the session page.  Just a little bit about the user interface that you are interacting with.  Just to the right of your video stream you'll see the Slido component for Q & A and chat.  A lot of you are already interacting in the chat.  For questions that you want us to get to at the end will be -- I strongly recommend the uploading feature so we can get an uploading feature to get an idea of what the most popular questions are.  We've got a lot of people here.  I'm sure there are going to be a ton of questions.  That will help me get the right questions asked.  If you would prefer to use captions, that should be depending on the size of your monitor below your video screen.  You have to scroll.  I encourage you to interact with that and adjust the font size and things like that to your liking.  I think that's about it.  Feel free to interact with each other in the chat.  If you have questions that you would like to be asked, use the Q & A portion of Slido.  There's also a couple of settings there if you want to filter by most popular or most recent based on your preference.  And right half past I'm going to hand it over to your speaker and go off camera.  Thanks, everyone, for joining.  Shell, take it away.
>> I think you are muted.
>> I can just give a talk to myself in the house.  Thanks.  If you are looking at microinteractions at the right place.  Without further ado, I know there were other talks that you could go to.  I know it is late on the east coast.  I appreciate that.  I want to note that.  I really do.  Let me start my timer.  And we're off.  Cool.  All right.  So when I give talks I typically like to have a road map.  This is setting expectations for the talk.  On the screen I have my road map.  The first bullet point is intro, microadepressions, number three is standards, and number four is microinteractions, and then the last can conclusion.  On the collide numbers, 1, 2, 3 are quite close together.  A little bit after is four and 50% of the road map is going to be for microinteractions.  It to set those expectations.  Let's get going with the introductions.  I'm Shell Little.  I'm very active on Twitter.  I don't check my LinkedIn.  I work for Wells Fargo for the retail side of the bank.  I work in corporate.  If you go out and get a credit card, you are not working with my stuff.  In my job I'm on the accessible user experience team where I'm in the design and mobile lead.  I have a lot of cognitive disability and evangelism feels weird.  I live in Seattle.  I'm partnered.  My kids all have tails.  If you know me, I have ADHD.  If you don't know -- it is who I am as a person.  On top of having ADHD I have a lot of other really words that go with how my rain works.  I have a large set of words to show how overwhelming to have all of different names.  I have a traumatic brain jury, chronic migraines, nerve damage, time blindness, brain fog.  There's a lot of stuff that goes when you have a cognitive disability.  It is all bun thing and a myriad of others.  I like to say I'm neurodivergent.  What does that mean?  It is not cognitive challenged.  I am not challenged by my brain.  I'm challenged by Sod oku.  It is not cognitive defects.  I didn't come off of the line defective.  Not special needs.  They are what everybody has and everybody needs.  Let's remove those.  Now to move on to defining the term that means having a brain that functions in is way that's different than the dominant societal standard of normal.  Normal is relative.  We have statistics.  This is going by a neurodivergent activist.  Whenever I give a talk I have to talk about spoon theory.  You really can't understand what it is like having a cognitive disability unless you understand what spoon theory is.  Let's jump in to talking about spoon theory.  To define it, if you haven't heard it before, it is a metaphor created by Christine used to describe the daily amount of mental or physical energy a person has and the toll of being disabled has on energy.  Basically your spoons are a measurement.  They can only hold a finite amount of stuff.  They are a universal tool.  Being a disabled person living in an ableist world it takes more spoons to exist.  Not only does it take more spoons to exist as an disabled American an ableist world, you also get less spoons back from sleep.  It is all about -- it is a balancing game.  That's what we do as disabled people is we balance energy.  We balance our spoons.  On the screen right now I have a chart.  I'm going to tell a quick story.  We're going to pretend that you have ten spoons.  The first line is for someone that's not disabled.  It takes one spoon to get out of the bed.  That takes one spoon.  They work all day.  Job is pretty hard.  It takes three spoons out of them.  Next transit back home another spoon.  When they get home at night, they have four spoons left to pay bills, make cool, grocery shop.  Pick up the kids.  When they rest, they are back to ten.  Now let's talk about somebody who has chronic pain.  Potentially nerve damage.  Morning routine showers suck and hurt when you have water running over parts of your body that have nerve damage, it hurts.  Getting up and getting move can be difficult.  Transit is difficult.  Someone bumps into them on the bus.  They are uncomfortable and jammed.  Feeling anxious.  Work it is hard for them to get food.  All of their co-worker's go out.  They are having a high-pain day and maybe they have to order food or go out of their way.  Transit home.  They had a rough day.  Instead of just taking transit home, they pay for a Lyft to go home.  To save spoons they had to spend money.  Next when they are home, they don't have any spoons left.  They have one left after the day.  Unfortunately they don't have spoons to pay bills or do laundry.  And they have to order out.  So again they have to spend more money to save spoons.  Because they had a high-pain day, they get 7 spoons when they rest.  Being disabled is expensive.  It is hard to take care of yourself and make sure you are giving yourself everything that you need.  Ability is a sliding scale.  What you can do in the morning and what you can do at night are little things.  I had two into graphics on the screen what you can do in the morning versus when you get home and you are drained after being bombarded with the cognitive strain and the lights and sounds and feels and the tastes of, you know, being outside and smelling the air.  It can be a lot for people with cognitive disabilities.  What you can do at the end of the day is quite different.  My barriers come from purposeful design.  My barriers come from the design decisions.  The biggest one for me is movement.  In the morning something that's bothersome is a poke.  At night it can feel like a slap.  I'm trying to pay bills.  In morning.  It is easier especially medication windows rather than at night.  To quote Jamie knight from a couple of hours ago, distraction is a process that builds on barriers such as memory and decision making.  Distractions can quickly stack into an unrecoverable barrier.  All righty.  Let's move into microaggressions.  When we have the barriers, we're being pulled and pushed.  It is draining us of spoons.  Microaggressions come into the play.  It is a statement, action, or incident regarded as indirect, subtle, or intentional discrimination regardless of intent.  Doesn't matter if you meant it or if you were trying to be nice.  Microaggressions is a common part these days.  When which is hard when you are part of the group of people.  I have a screen shot on it of a woman of color who is being just bit by mosquitoes.
The concept they push forward that I enjoy is microaggression is like mosquito bites.  It is not just one.  It is the fact that you get them all day.  It is totals up.  People grabbing at you and touching your wheelchair and grabbing your cane.  One is not the end of the world.  It is a systemic problem that builds until sometimes you explode.  In the disability space, you are so brave.  I'm just getting coffee.  I'm outside.  I didn't do anything brave.  I'm just ordered Starbucks.  You are too beautiful to be stuck in the wheelchair.  The person who delivers that believes it is a compliment.  It is one I get a lot.  They learn about my cognitive disabilities.  You are so articulate.  Thanks.  I have heard of friends who have disclosed and been told you are really smart for having cognitive disabilities.  Those kinds of comments are examples of verbal microaggressions.  They say you are welcome here and you are not understand here.  Who you are and what you represent is something that people don't get.  An example on the microaggression on the web is clubhouse.  There's an app called clubhouse.  People have been buzzing about it.  It is an audio-based app that has no room for any sort of the asistive technology in their minds for captioning or nothing for transcripts, and also the fonts are not adjustable.  So if you have low vision.  And according to clubhouse, it is done by design.  So they want to be elite and exclude on purpose.  You are not welcome here.  Another one microaggressions on the web when people use overlays that are not accessible.  You can not slap on Java script and call it accessible.  They went to the web site that's using overlay.  The screen reader is not working.  They are not welcome on the site.  Even though the person who got this is using an overlay thinks they are doing the right thing, it is still a microaggression.  I have screen shot just for a random sample.  For people with cognitive disabilities, the Internet can be a downright hostile place.  I know we talk about vestibular and people with seizures.  The Internet can be scary.  There's a type of microaggression that I would like to talk about.  So I gave a talk it was two years ago now.  2020 didn't exist.  But basically things that are to trick and manipulate users.  People with cognitive disabilities, especially people who are low on spoons are very susceptible and high risk.  It is considered a microadepression.  Hostile or hijacking patterns.  Pick me.  Pick me.  People with cognitive disabilities do fall prey to that kind of pattern.  Unavoidable motion and flashing content.  People with ADHD and attention-related and people with autism speak about how difficult the web can be because of those things.  Protection from cognitive microaggressions.  Read only mode.  Ad blocker.  Eric Bailey wrote a really great article for reader mode the button to meet.  It is a great one and has a ton of resources built into it.  People use things like ad blockers.  And so on the screen right now I have a screen shot.  We see her using an ad blocker.  I need an ad blocker to use the site.  Am I just not welcome here?  On the screen right now I have a tweet from a person saying sometimes I do want to turn off the ad blocker when a site that I like.  I want to support, usually I have to turn it back on.  The ads are too distracting.  I didn't have allocated space.  It slows everything down.  There's multiple reasons why people use ad blockers.  They are just not welcome on the sites.  Are they are doing on time?  Crushing it.  Sweet.  Next up we're going to talk about standards.  WCAG.  I have a love/hate.  If you know me personally, I have a lot of feelings.  I respect how far we've been able to come.  We need to go forward.  WCAG we only have a couple of standards.  A lot of them are AAA.  Cognitive disabilities are really complicated.  The biggest thing I like to tell people a fix for one cognitive disability is barrier for another.  And that's really true.  You can't do a one-size.  Fits all which is why inclusive design is so important.  Because you could be unintentionally creating barriers when you think you are fixing it for one user group.  Thinking holistically is important.  That's what standards are for.  They give you a testable solution or guidance.  It is really difficult to write standards for things that are so nebulous.  Looking at WCAG2.is my favorite.  I said I would get a tattoo of 2.2.2 on my body.  I guess I'm really overdue for that.  It is basically at the criterion that says moving stuff that starts automatically, last longer than five seconds, presented in parallel to other content has to have a way to be paused, stopped, or hidden.  Caveat being unless it is essential.  And the other animation related criterion is animation from interaction.  It is similar to pause, stop, hide.  Motion animation triggered by interaction can be disabled unless it is essential.  How relevant it is in the United States depending on your organization.  We always strive and push for AAA.  It is tough to test for.  When it comes to the standards there's just gaps.  That's just how it is.  Especially when -- anything that's essential to the function is exactly the rule.  But essential depends on who you ask.  If I'm trying to pay my bills, it is essential that I pay my bills.  If you ask the company they are paying bills, they might want me to sign up for a new service.  It is a new things, and they want new users.  For them me paying bills is a secondary.  They want me to sign up for the thing.  Next for the gaps can be paused.  Equals is it possible to do so.  Not you can continue and complete your task.  Can it be?  If that thing pops in your face and you have moving ads.  If you can close it, it passes.  Unfortunately with cognitive, it is the slap.  You are done.  There goes your train of thought and working member that you were holding on to that little bit of information in your hands gone.  Like I was saying dismissible animations and auto play.  You can dismiss them eventually.  I like to say where WCAG stops that's where the cognitive barriers start.  That a difficult place to be.  We don't have standards for microinteractions.  We bareically -- people barely respect pause, stop, hide as it is.  To ask and push us further to talk about microinteractions, I would really like for us to great at some point.  Which is why I wrote this talk.  All right.  We're at section four.  This is the bulk of the talk.  I'm going to jump into talking about microinteractions now.  Awesome.  Defining microinteractions.  It is any single task-based engagement with a device.  That's from Carrie Cousins.  It is a pretty, nice, simplified expression of what is microinteraction is.  Depending on who you ask, people have different opinions.  From UX design their definition is microinteractions are used to communicate meaningful feedback to users because a user has to constantly know what's happening when an action is performed.  So it is the dance between the user and the device or the -- or the computer.  When it comes to communication.  So from -- I never said their name out loud.  An end group, you know who I'm talking about.  I'm so sorry.  They had a good article about microinteractions and breaking it down.  There are microinteractions that are user based and microinteractions that are system-based.  Animations and things that happen when you interaction with the web site or web app or application.  It is either you are initiating them or the system is initiating them.  Basically they come in different forms.  Talking microinteractions in terms of the motion.  Next up is feedback and metaphor and navigation and signifier and attention grabbing and attention hijacking.  There are for things like communicating space changes and metaphors of navigation.  They are for the types of thing.
These are really important to people with cognitive disabilities.  I have sensory processing disorder.  I get tunnel vision.  When I need to do an action and the device is giving me proper feedback and it's done in a tasteful way, it really, really helps.  That's the tough thing.  What is too much and what is not enough for them.  Let's get going on breaking down the different uses of microinteractions.  First off feedback.  An animation is used to communication an action that has been recognized by the system.  It is feedback.  It lets you know the thing that you just did worked.  On the screen I have an interaction of what Spotify has on their like button.  You can like a song and it adds to the like play list.  For those of us who are sighted, keep focus on that.  The interaction, the heart when you toggle it off shakes.  When you toggle it back on, there's an animation of little hearts coming off of it and circles going outward.  It shows the user what be you just did worked.  It also has cute animations to say you liked it.  It is just a great example of what feedback is.  Next up is state change.  That's an important thing to communicate to the user.  It is used to communicate the action has been recognized by the system.  I forget to change the slide screen text.  Something has changed.  Something is different.  You need to be aware of it.  The example that I have on the screen right now is Twitter.  They have a blue button that's sticky on the bottom righthand of the application.  When you are on your feed it is a plus sign with a quill to write a Twitter.  When you toggle over to the messages, the button moves and switches over to the message icon.  Create a new message.  You can Twitter something to you are going to message someone.  To handle that, they have an action button.  I'm going to push play on that.  We'll check it out.  How it works is the button spins and toggles back and forth between the different settings and versions.  That's a state change.  We're going to move on.  Thank you.  Cool.  Spatial metaphors.  This is really important for people with cognitive disabilities as well.  Having animation to communicate the thing and mode is coming from the action button.  Those kinds of communications are really important.  On the screen right now I have just a menu from Google.  Just hitting a menu.  It is supplemental cues for the direction they are moving within a process.  Think about the phones when you swipe from left to right.  You have a cube effect.  It is just giving that feeling of transition.  I'm going to push play.  It is just a menu.  Like a hamburger menu expanding with animation.  Nothing too fancy.  It just goes out.  And it goes back in.  It is communicated the user the menu lives over here.  Which is important.  Awesome.  Next is signifier it teaches them how to act.  It shows them if you pull this, I'm going to do something, if you swipe this, I'm going to go away.  Thinking about Tinner and Bumble and you are able to swipe a card.  I have Apple music.  When you select the song it allows you to pull down and dismiss.  It gives the user that feedback to say I'm dismissible.  Last but not least attention hijacking.  This is a dark pattern.  Often times it is used for evil.  If you did not get Eric's talk today, it ties into the content for looking out for the dark patterns like attention hijacking.  It is a landing page of the video editing app.  I'm going to push play.  It is chaos.  Everything is moving.  There's an edit button that toggles.  It flips like a card over and has animation inside of it.  There's a crown that represents their premium shaking and moving.  Then at the -- they have some content sections below for creative videos.  They are all moving as well.  I'm going to push play.  It is pandemonium.  Getting on the page and trying to figure out what you are trying to do is difficult.  It is shining and moving and live edit.  It is so much.  That crown moving and bumping is like pick me.  Please pay me money.
Awesome.  Let's tie this into the cognitive accessibility part.  Cool.  Just checking time.  What makes a cognitively accessible microinteraction?  That's a great question.  After doing research, all I can say, it is complicated.  It is tough.  There are some things that you can look out for.  There are some points that you can takeaway when you are having to find a way to communicate to users that's good, because you are trying to communicate something important to them.  It is not too much.  So the points that I would like to talk about in the cognitive accessibility microinteraction stuff is relevance to task, size, location, speed, and intrusiveness.  Which is a word that I like.  So when it comes to relevant of task, asking yourself as a designer is the task that I'm asking at the user to do in the work flow or am I pulling them to the banners or to the rails on the side?  Is it relevant to what they are doing right then and there?  Is it something the user wants the system to know?  We have the new feature you'll probably never use.  We want you to know, because we worked really hard on it.  Those kinds of interactions can be jarring when you are trying to get something done.  When it comes to relevance of task, who determines what the task is when there are so many different things you can do.  Are you really going to pay your bills or check your credit score?  What are you trying to accomplish?  I had the thing that if I could look at.  Your task has changed.  Remembering you are not your user.  Access lab has a really great resource about tweets and stuff.  I snagged a couple from them.  One of them says assuming ADHD counts, it is hard to locate content or overly busy pages and animations are a nightmare of distraction.  In terms of distraction is it relevant to flow and task?  Is it user initiated or system initiated?  That changes a lot.  If it is something the system is doing rather than the user doing it, it changes the feeling of the interaction.  System initiated stuff, you are being pulled.  You are being yanked.  You are being called.  There's a bell ringing on the corner.  You are being pulled away.  You don't know where it is.  On the screen it has a channel point where you are able to watch and support a streamer and rack up channel points.  The screen box next to the channel box shakes until you act on it.  You have to click it and select it in order to claim your points.  It passes pause, stop, hide, because you have doing something with it.  What if you don't want to collect them?  I have another tweet on the screen.  Anything that moves without me initiating that movement is so distracting.  I'll be unable to read what I same to do on the site.  Basically the attention grabbing is to effective I can't use the site.  Is any of the stuff that happened relevant to your task at hand?  I highly doubt it.  Another example for wondered is the system applying to the action or you just being on the page?  I have a really bad screen shot.  I was angry.  I was on Jera.  This is a menu on the side.  They have a purple button or badge.  It has a ring around it that pulses.  It goes in and out.  I could not dismiss it.  I was trying to work on the ticket that was critical.  I've got the thing buzzing over here.  I really don't care about custom channels.  I'm trying to answer the ticket.  By moving it pulled the distraction and made it harder.  ADHD if there's a subtle animation running, I cannot focus.  Biggest offender is blog.intercom.com.  This is another I snagged.  Those kind of concepts.  Is it interaction something to help the user or pulling them away for something else.  That thing you were working on six weeks ago it is overdue or notifications, toast, things like that.  Not everybody wants those.  Next up is size.  Animation shouldn't take up more than one third of the screen size.  On the screen right now I have a lovely example of the restaurant web site.  It is not one third of the page.  It is everywhere.  This can be so jarring and it can make you ill.  I got dizzy taking the screen shot myself.  It wasn't great.  Animations cannot take up that much of the screen.  The thing is animations add up.  To size.  If you want to look for really bad experiences, go on mobile and look up any recipe.  Recipe sites are riddled with madness.  The screen shot has a banner that has pancakes and fluffy Greek yogurt.  Next is an ad for the car I don't want to drive.  You have the add choice maybe if you click that it will show the X button.  Maybe it won't.  Then there's part of the article.  Above is a pop-up add for makeup and beslow the Verizon.  Every single thing on there moving.  At the best part is on the right hand is to heart button to save it.  A heart button and you have to see it is updating.  Hearts shoot out.  It is a lot.  This web site is basically useless at this point.  Next up is location.  So how far are you from pulling the user from their task?  On the screen right now I have an add to cart and shopping cart.  I'm going to switch to the next screen which is animated.  When you -- in the example when you select add to cart the button shrinks and jumps over into the cart.  And badge comes up.  This is an example of right there with the user.  They are doing it.  It is showing them the thing that you just did has been simply add to the cart.  I've seen ones that go up and across the screen.  If you are adding 30 things to the cart, maybe the animation is not so great.  In general things like this that are in your proximity and work flow can be beneficial to users.  Next up is in terms of location is the animation and context with the content.  Is it a full overlay forcing the user to watch the screen and add.  It is not really in context.  It is annoying and jarring.  It takes you away from your task.  If you were holding on to the number or something, that's gone.  It is not in content or in parallel with the content.  So, you know, if you have to have something moving, out of context is way better.  Next is speed.  When it comes to showing, it is too fast.  The button pressed that changes state.  If the user moves too fast, they won't understand.  We had UXR for doing authentication processes.  We got feedback from the users the authentication was too fast.  They didn't believe it was working.  Because of that we slowed it down a little bit.  So users could think.  It is really thinking about logging us in.  It is really checking that security.  Because it moved too fast they were unable to see the load, and they didn't believe it worked.  On the flip side they will use that connection you are showing them with the microinteractions.  If you push the button to expand something and it is over ten seconds, user might forget they pressed that button or which one?  I can't remember.  In general the rule for hydrointeractions is typically one second.  300 or 400 milliseconds to give an instantaneous response.  This thing you did worked.  I'm loading the page.  One second still gives them a seamless experience.  There's a sense of delay.  The thing is thinking.  Ten seconds versus what I already would feel like five seconds.  They are praying to the Gods it is going to work and not going to crash and go through.  Studies have shown that anything plus ten seconds or anything user memory is way too long.  Keep that in mind.  Last but not least on the section.  I know I'm running short on time is intrusiveness.  Going back to the example of the switch thing.  Is it endless until the user interactions?  How easy is it dismissed?  If you have to be a hacker to put your hood up and sunglasses on.  I don't know.  Sometimes they have a hammer in their hand of people who are hacking.  You shouldn't have to be a stock photo hacker to figure out how to get your animation to stop moving.  Intrusiveness is how much effort?  Anything that interferes with my ability to see at the high contrast and highlights as I read makes the page harder to read.  A lot of custom UI widgets seem to interfere with this.  They are hovering over things and moving and popping.  Imagine if there are links in the text.  When they hover over the links, they are moving and popping.  Maybe it looks cool.  For this person that's a barrier.  On the screen right now I have an example of -- I think it is Word Press.  It has a save function.  Auto saves.  And it auto saves.  And it auto saves.  So you are constantly seeing the save drafts and then the second you stop typing the cloud icon toggles.  It is moving so I can't stop it.  There's a flashing animation of the auto saving.  It says saving and then flashes and says saved.  It does it over and over and over.  A user has no way to stop that animation.  Tweet on the screen says I'm so glad you can hide media preview on Twitter iOS app.  As a person showing ADHD symptoms, it is a lot less distracting.  Twitter has it, Pinterest has it, and giving them that option to not have auto play.  For settings this is the recommendation slide.  This is a big one.  Use logic.  Sometimes stopping animation is good.  Other times simple things like turning off auto play is giving you the setting to do that outside of the preferred motion on the computer level on your site like Twitter or Instagram -- not Instagram, like Pinterest.  In the reduced motion sense fading is so much less intrusive than sliding in.  Things like being able to turn off animation on hover is really important.  Limit the user required dismissal of animations.  Those better be tied to the cuff.  Allow ad blockers.  We have to stop.  We're in a war right now between how annoying can we make our ads and how much people will download ad blockers.  It is just spinning.  Let me run through my last couple of conclusion slides.  Listen to, hire, and ask disabled people.  Shouldn't be hard.  But it is really is these day.  Nothing about us without us.  Nothing should be done without asking and bringing people in and paying them for their time.  Ability is a sliding scale.  Design with that in mind.  What bugs them and bothers them at 10 could like me bothers them Google did a thing and I couldn't e-mail anybody.  Ability changes.  Microadepressions exist on the web and they tell disabled users they are not welcome.  Takeaway number four, standards are never going to be enough.  They are just the start.  Let's take the standards that we have apply them where we can and push them further.  Second to last microinteractions and animations add a lot of accessibility for cognitive disabilities.  We're talking about pairing things, complex interactions, pushing buttons and getting that live feedback right there knowing what I did worked.  Those kinds of interactions have a lot of plus for cognitive disabilities.  On the flip side the microinteractions if abused can create barriers with users of cognitive disables.  I have one more slide.  Surprise.  Number seven.  Give your users settings.  Give them settings.  They know what they need better than anybody else.  Give them the ability to decide how they want to have receive notifications.  If they have toast, they don't want to see that right now.  They toggle that off.  Their badge still updates.  Imagine if Twitter hit you with a toast notification every time.  How overwhelming.  That's it for me.  That's it for me.  Thank you for your time.  I'm a little over.  Thank you for your time.  Thank you.
>> Thank you so much.  You did great.  We've got eight or so minutes left to take some questions.  Let's jump into that.
>> Yeah.  Sure.
>> Thanks for everybody that's been participating and submitting questions and uploading them, et cetera.  We'll get right to it.  Here's one that says what advice would you give to someone with the cognitive disability when they feel invalidated bit fact that people don't perceive their differences or don't believe them because they use all of the spoons putting up a socially acceptable front?
>> Masking is exhausting.  I feel this person.  It is tough.  Empathy -- the hardest part about being in the marginalized community is unfortunately because of the systems that's been built around us based off of racism and sexism and ableism, we are forced to be the teachers.
It is not our job to teach people to be inclusive.  Unfortunately that is where we get pigeon holed into.
>> More spoons.
>> Yeah.  More spoons basically.  What my recommendation would be is lean on the disability community.  On Twitter -- I don't know if they are a Twitter user.  There's a fantastic, robust, brilliant disability community that has resources and articles that explain.  Black girl lost keys has a fantastic blog.  It talks about how difficult it is.  Things like rejection dysphoria can be enough to end your day.  See what they have to save spoons.
>> Great.  Thanks, Shell.  Here's one that I was reading through earlier.  I think it is about session timeouts.  Do you have any strategies for conveying countdown it is or eminent timeouts that don't hijack a users focus or create unnecessary stress assuming there's some security requirement that requires the app to that have type of timeout?
>> Yeah.  I'm so against timers.  I hate them so much.  I have on my screen right now the time and I have the seconds hidden.  There are very few instances where users are going to benefit from seconds.  Ordinariered tickets and stock prices.  Those things change rapidly.  When we're talking about timeouts giving if the user the warning and you have five minutes rather than four minutes.  A giant ass timer on the screen.  Just do away with seconds.  You've increased the accessment for cognitive a ton.
>> Don't introduce anxiety.  I'm going to break my uploading rule.  This just crept in.  Do you have any recommendations for who to follow on Twitter to learn more about cognitive disabilities?  Aside from this one right here at the bottom of our screen.
>> I typically have a ton of people to recommend.
>> You haven't submitted your slides yet.
>> I'm going to tweet out a list.
>> That was anonymous.  Start by following Shell.  Sometimes I completely miss important conveyed by the microinteractions.
It is called bright girl blindness.  It is eye tracking software.  Users don't see them anymore, because we've learned to block them out.  Same with carousels.  Time and time again nobody interactions and nobody cares about carousels.
>> It is a bunch of people fighting.
>> Different spaces.  All I'm saying is there's research out there that shows people don't look at those.  I think that is a conversation that they don't want to have anyway.  Inviting them to realize that there are users who want -- who don't mind ads and have to block them because they move.  It is a downward spiral.  The ads get more aggressive and they get even more ad blockers and they get more aggressive.  There's a lot of great resources.  Niemann Marcus to look into the spiral and know the non-moving ads are more likely because people aren't block them.
>> Interesting.  Unfortunately we're at time.  Thank you, everybody, so much.  Thank you, Shell.  Again the slides will be made available.  I suggest everybody follow Shell on Twitter.  She tweets a lot of cool stuff.  You promised that list of people to follow.
>> I wrote it down.  Thank you so much for attending.  I appreciate your time and attention.  I hope everybody has a great rest of the day.  I'll let you continue the signout.
>> That's all.  The AV guys will tell us when we can go off air.
>> All right.

Profile

amazonv: (Default)
amazonv

December 2025

S M T W T F S
 123456
789101112 13
14 15 16 17 18 19 20
21 22 2324252627
282930 31   

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jan. 10th, 2026 12:04 am
Powered by Dreamwidth Studios