piccalilli_’s avatarpiccalilli_’s Twitter Archive—№ 25,794

            1. I’m going to try something new to encourage us all to experience the web in suboptimal ways. Every day, for a week, I’m going to add a user situation for you to test your work with in this thread. It’s inspired by this article by StuRobson alwaystwisted.com/articles/a-web-developers-new-working-week
          1. …in reply to @piccalilli_
            StuRobson Situation #1: Single Handed Saturday Use the site that you’re working on with one hand, on a mobile device. Test how responsive your click events are and importantly, how hard is it to reach elements of your site? Lastly, if you have a form: try to complete it with one hand.
        1. …in reply to @piccalilli_
          StuRobson Situation #2: Slowdown Sunday Using DevTools, throttle your connection to Slow 3G for the day. See how long it takes for the site you're working on and other sites to become useable and interactive. You’ll probably get a big shock! Remember: slow 3G is *very* common.
      1. …in reply to @piccalilli_
        Video Alt: Me reloading my site, then setting my developer tools to throttle the connection to slow 3G on the network panel.
    1. …in reply to @piccalilli_
  1. …in reply to @piccalilli_
    Situation #3: Move Slow Monday In the performance tools, you can simulate a slow processor by throttling it. You can choose 4X or 6X slowdown. Pro tip: a lot of folks have much less power on their devices that we do, so this is a good way to emulate real conditions.
    1. …in reply to @piccalilli_
      Video alt: A fancy-assed website looks smooth as heck until I set the throttling, where suddenly, it gets janky.
      1. …in reply to @piccalilli_
        Situation #4: Tabbing Tuesday You’re not allowed to use your mouse/trackpad/trackball/pointing device all day. Instead: use your keyboard to navigate the site you’re working on. Does it still work? Are there areas of the site that are hard to reach with a keyboard?
        1. …in reply to @piccalilli_
          Situation #5: What’s State Am I In Wednesday Colour is often used to determine state. There are many reasons this is problematic, but one big issue is that colourblind users can’t see state changes. Today, test your what you're working on with this: chrome.google.com/webstore/detail/colorblindly/floniaahmccleoclneebhhmnjgdfijgg
          1. …in reply to @piccalilli_
            I prefer to use iconography in support of colour changes. I outline it in this old article: css-tricks.com/small-tweaks-can-make-huge-impact-websites-accessibility/#article-header-id-5
            1. …in reply to @piccalilli_
              Situation #6: Thoughtful Thursday Today, think about how elements of the site or app you're working on could be used to abuse people or generally negatively impact people What can you do to stop it? Moderation? Code of Conduct? Design process? Put some thought into that today
              1. …in reply to @piccalilli_
                Situation #7: Firefox Friday Chromium is increasingly common now, so use Firefox for the day. It’s important to make sure the site you’re working on works there for browser diversity. Already using Firefox day-to-day? You get the day off* * please confirm with your boss