Accessibility and web performance are not features, they?re the baseline

• Accessibility, performance

4 min. (877 words)

accessibility-and-web-performance-are-not-features,-they?re-the-baseline

This week I’ve been brooding about web performance and accessibility. It all began when Ethan Marcotte made a lot of great notes about the accessibility issues that are common with AMP:

In the recordings above, I’m trying to navigate through the AMP Story. And as I do, VoiceOver describes a page that’s impossible to understand: the arrows to go back or forward are simply announced as “button”; most images are missing text equivalents, which is why the screen reader spells out each and every character of their filenames; and when a story’s content is visible on screen, it’s almost impossible to access. I’d like to say that this one AMP Story was an outlier, but each of the nine demos listed on the AMP Stories website sound just as incomprehensible in VoiceOver.

Ethan continues to argue that these issues are so common in AMP that accessibility must not be a priority at all:

Since the beginning, Google has insisted AMP is the best solution for the web’s performance problem. And Google’s used its market dominance to force publishers to adopt the framework, going so far as to suggest that AMP’s the only format you need to publish pages on the web. But we’ve reached a point where AMP may “solve” the web’s performance issues by supercharging the web’s accessibility problem, excluding even more people from accessing the content they deserve.

I’ve been thinking a lot about this lately — about how accessibility work is often seen as an additional feature that can be tacked onto a project later — rather than accessibility work being a core principle or standard of working on the web.

And I’ve seen this sentiment expressed time and time again, in the frameworks, on Twitter, in the design process, in the development process, and so much so that arguing about the importance of accessibility can get pretty exhausting. Because at some point we’re not arguing about the importance of accessibility but the importance of front-end development itself as a series of worthy skills to have. Skills that can’t be replaced.

Similarly, this post by Craig Mod, on why software should be lightning fast, had me thinking along the same lines:

I love fast software. That is, software speedy both in function and interface. Software with minimal to no lag between wanting to activate or manipulate something and the thing happening. Lightness.

Later in the piece, Mod describes fast software as being the very definition of good software and argues that every action on a computer — whether that’s a website or an app — should feel as if you’re moving without any latency whatsoever. And I couldn’t agree more; every loading screen and wait time is in some degree a mark of failure.

Alex Russell made a similar point not so long ago when he looked at the performance of mobile phones and examined how everyone experiences the web in a very different way:

The takeaway here is that you literally can’t afford desktop or iPhone levels of JS if you’re trying to make good web experiences for anyone but the world’s richest users, and that likely means re-evaluating your toolchain.

I’m sort of a jerk when it comes to this stuff. I don’t think a website can be good until it’s fast. The kind of fast that takes your breath away. As fast as human thought, or even faster. And so my point here is that web performance isn’t something we should aspire to, it should be the standard. The status quo. The baseline that our work is judged by. It ought to be un-shippable until the thing is fast.

The good news is that it’s easier than ever to ship a website with these base requirements of unparalleled speed and accessibility! We have Page Speed Insights, and Web Page Test, not to mention the ability to have Lighthouse perform audits with every commit in GitHub automatically as we work. Ire Aderinokun showed us how to do this not so long ago by setting up a performance budget and learning how to stick to it.

The tools to make our websites fast and accessible are here but we’re not using them. And that’s what makes me mad.

While I’m on this rant — and before I get off my particularly high horse — I think it’s important to make note of Deb Chachra’s argument that “any sufficiently advanced negligence is indistinguishable from malice.” With that in mind, it’s not just bad software design and development if a website is slow. Performance and accessibility aren’t features that can linger at the bottom of a Jira board to be considered later when it’s convenient.

Instead we must start to see inaccessible and slow websites for what they are: a form of cruelty. And if we want to build a web that is truly a World Wide Web, a place for all and everyone, a web that is accessible and fast for as many people as possible, and one that will outlive us all, then first we must make our websites something else altogether; we must make them kind.

25 comments

  1. Today, I went to the beach with my children. I found a sea shell
    and gave it to my 4 year old daughter and said “You can hear the ocean if you put this to your ear.”
    She put the shell to her ear and screamed. There was a
    hermit crab inside and it pinched her ear. She never wants to go back!
    LoL I know this is entirely off topic but I had to tell someone!

  7. Hello there! This is kind of off topic but I need
    some help from an established blog. Is it hard to set up your own blog?
    I’m not very techincal but I can figure things out pretty
    quick. I’m thinking about creating my own but I’m not sure where to begin. Do you have any tips or suggestions?
    Thanks

    Also visit my page kannikar.com

  8. Hi there, just became alert to your blog through Google, and found that it’s really informative.
    I’m gonna watch out for brussels. I will be grateful if you continue this in future.

    Lots of people will be benefited from your writing.
    Cheers!

    Here is my homepage … tsw1.home.pl

  9. Howdy! I could have sworn I?ve visited this site before but after browsing
    through many of the posts I realized it?s new to me.
    Regardless, I?m definitely happy I found it and I?ll
    be bookmarking it and checking back often!

    Have a look at my blog post – chengdian.cc

  11. Hi, i read your blog from time to time and i own a similar one and i was just wondering if you get
    a lot of spam responses? If so how do you reduce it, any plugin or anything
    you can advise? I get so much lately it’s driving me crazy
    so any help is very much appreciated.

    Here is my web blog 918kiss 2 jackpot

  12. My developer is trying to convince me to move to .net from PHP.

    I have always disliked the idea because of the costs.
    But he’s tryiong none the less. I’ve been using Movable-type on numerous websites for about
    a year and am nervous about switching to another platform.
    I have heard good things about blogengine.net. Is there a way I
    can transfer all my wordpress content into it? Any kind of help would be really appreciated!

    Also visit my blog post … test id ntc33 (xe88-my.com)

  13. I blog quite often and I truly thank you for your information. The article has truly peaked my interest.
    I am going to take a note of your site and keep checking for
    new details about once a week. I opted in for your Feed as well.

    My homepage – ok388 slot game

  17. hello!,I really like your writing so a lot! percentage we be in contact
    extra about your article on AOL? I need an expert in this area to
    solve my problem. Maybe that is you! Looking forward to peer you.

    Also visit my blog: vetearii.free.fr

  18. Hi there! Do you use Twitter? I’d like to follow you if that would be okay.
    I’m definitely enjoying your blog and look forward to new updates.

  23. I am really loving the theme/design of your weblog. Do
    you ever run into any internet browser compatibility problems?
    A small number of my blog visitors have complained about my site not operating correctly in Explorer
    but looks great in Opera. Do you have any recommendations to
    help fix this issue?

    my blog; http://vetearii.free.fr/modules.php?name=Your_Account&op=userinfo&username=JonsonDemetrius

Leave a Reply

Your email address will not be published.