Dear Facebook: We Need To Talk

Facebook, honey, we need to talk. Seriously. This very instant.

I think I’ve been a good and faithful servant—I mean, user. I spend lots of time with you, usually every day, and have done so for several years. I have continued to check in with you daily despite the useless updates, the bewildering user interfaces, the sudden and unsettling amendments to your privacy statements—even your silly app, which enjoys draining my phone’s battery and sucking down data as though it were water in the desert. Through all of your confusing, outrageous shenanigans, I have done my best to navigate your bizarre design and even tolerated your overabundant ads with minimal grumbling. (I really, really enjoy grumbling, so please acknowledge the magnitude of my sacrifice. … Are you acknowledging? … Good, thank you.) In fact, Facebook, I love you so dearly and so faithfully that part of my current career depends rather heavily on interacting with you. I’m a social media specialist, Facebook, which means I have to work with you—and like it!
But, dear Facebook, you’ve shown me time and time again that you never really appreciated me. Yes, yes, you’re “free and always will be,” I know. I get it. I’m the user, not the customer. I’m the product. You sell my oh-so-exciting online life for far more than it ought to be worth, just so I can skip intrusive “suggested” posts to get to the good stuff. It’s business, this is the new normal—blah blah blah.
Still, darling, you’d think I might be worth almost enough to you, as a loyal user and frequent poster, to warrant a reasonably accessible environment. You see, Facebook dear, my eyes don’t work, and as such, you are an unpredictable and cruel companion.
One day, some complicated function works, and the next day you’ve broken it—again. Your much-lauded image description software—you know, that feature that meant we blind people would be able to “see” pictures—thinks dogs are cats and cats are dogs and any woman wearing white is a bride. It invents children that aren’t there and sometimes throws in an extra person, just to keep us all on our toes.
(“You got married? Again?”
“No no, I’m just wearing a white shirt. As you were.”)

I’ve lived in valleys of despair and soared to dizzying peaks of hope, perhaps a little naively. When you kept your mobile site clean and relatively accessible, I rejoiced. Alas, I rejoiced too soon: many of the features I wanted to use simply don’t work. Back to the sluggish, semi-inaccessible and wholly-infuriating desktop site I go, then.
I sang your praises when you introduced artificially intelligent software that would describe images, and the publicity it generated was very exciting indeed! Back to earth I drifted when I realized that not only was it laughably unreliable, but you were actually making sighted people think their days of describing pictures (very short-lived—I’d just gotten people to start doing it) were over. So, thanks and all, but please stop telling sighted people they don’t have to describe their pictures, cuz they do, maybe more than ever unless they want me to congratulate them on the new cat-dog or ask how married life is treating them.
I reveled in the simplicity of your Messenger app, reasoning that if you were going to get us all to use it by brute force if necessary, it may as well work. But, Facebook, you managed to break even that, so that I can’t scroll with any efficiency and am forced to ignore a whole lot of pointless nonsense on my cluttered screen.

This is not healthy, Facebook. At this point, I am staying for the good times, as they say. Each time you break accessibility or introduce a troublesome new feature, I grit my teeth and roll with the punches. When I struggle to perform basic aspects of my job because something on your end is mysteriously broken again, I smile through the pain and soldier on. If time is short and I don’t have an hour to fiddle with two versions of a website and an app, I call a sighted person over to help, silently cursing my dependency.

Meanwhile, you announce your access team with much fanfare and profess your commitment. You whisper (or shout, as the case may be) reassurances into my weary ear, promising that all will be well.

But you know what, Facebook? I don’t believe you.

Do I expect any of this to move you? No, of course not. You have me in a corner, and I must continue to shoulder the constant issues you create. My job and social life depend upon us getting along.
That said, dearest Facebook, I don’t have to like it.
And you know what? I don’t have to like you, either.
There, I said it. I love you, but I don’t really like you anymore.

Put your money where your mouth is. Use the same level of force to direct your accessibility team as you do to ensure that customers—I mean, users—use your ridiculous apps. If you put a fraction of the effort you pour into, say, the like button into accessibility, darling, we’d have a very different relationship, you and I.

So, Facebook, I ask only this. Until you make real, lasting strides in the direction of genuine usability and accessibility, please don’t pretend you care, because I’m done pretending I believe you.

Yours, very grudgingly,
A girl with broken eyes (and a broken heart)

Dear Web Developers: You’re Out Of Excuses

It’s been one of those days—a day that makes me want to shut down my computer and hide under a quilt to cry. It’s barely noon, and I’m already utterly fed up. If I had chocolate, I’d be binge-eating it; if I had wine, I’d be guzzling it.
Fellow disabled people will understand the kind of day I’m having: it’s the kind during which almost every single task I try to accomplish online is blocked by accessibility issues.
I encounter accessibility roadblocks all the time, though they usually have workarounds. I’m so used to them that I hardly give them much thought, and don’t waste much of my limited emotional energy on being annoyed with them. They’re a fact of life and, while I do report bugs and encourage web developers to improve, I’ve worked to embrace a positive, patient attitude when it comes to navigating the internet. Most days, I’m just grateful that I can access the internet at all. Sure, I get snarky, but generally I would rather help than condemn.
On days like these, though, I’m less philosophical. Smothering my frustration when I ran into yet another inaccessible capcha became increasingly difficult, and when I tried to report the issue using the site’s contact form, I discovered that the “submit” button wasn’t accessible either. At that point, I realized I had no chill. None. I searched for it, willing it to return, but I’m thoroughly, disproportionately discomposed.
I get it: accessibility isn’t always intuitive, and many developers are self-taught. They learn as they go along, and mistakes like these are almost inevitable. While I’m not a developer myself—I’m proud when I manage to use html correctly—I can imagine that accessibility might not be covered well in school, either. During a course on web design and online information architecture, my class received one short lesson on accessibility—just enough to explain what accessibility actually is and why it’s important, but not enough to provide insight into how it can be accomplished. There was little mention of accessibility tests, plugins, consultants, or basic handbooks. Few practical solutions were discussed. In other words, the lesson focused on awareness only, without providing a solution to the issue it raised. How useful is that? Well, it’s not useful at all.
So, yes, I understand that inclusive web design may not come naturally to a budding developer. It also might be challenging for a veteran because web accessibility has evolved considerably. As people with various disabilities speak out about what they need, accessibility becomes more comprehensive and, therefore, more complicated. I don’t pretend to know all there is to know. I’m not even close to that point yet.
Still, as in so many areas of life, ignorance is not a justifiable defence. It’s 2016, and accessibility guidelines are one click away. I’ve just performed a basic Google search, “web accessibility,” and the entire page of results is filled with helpful articles ranging from the most basic to the most advanced. Surely even beginners can take at least a few steps to ensure their websites are as inclusive as possible!
I’ve concluded that my frustration is fuelled by years of feeling like a burden when I asked developers to fix some problem or other. I was often treated like an unreasonable user who was asking for the moon, and I became accustomed to that. With notable exceptions like Apple and Buffer, my requests for improvements have often been ignored or dismissed. Several companies have lost my business entirely because I literally could not use their services anymore.
I’m growing weary of explaining that accessibility is not a privilege, but a right. I’m sick of reiterating that, no, accessibility is not about doing us a “favour.” I’m desperately tired of insisting that while ease of use isn’t mandatory, accessibility certainly is.
Developers need to add accessibility to their core values. They need to stop lumping accessibility into a category alongside perks, special features, and enhancements. They need to stop reducing it to a public relations stunt, designed only to generate glowing publicity. They need to consider it standard, not extra. Making your site accessible should be framed as the least that can be done to provide a satisfactory user experience. Companies like Apple, which include accessibility as a matter of course as often as possible, shouldn’t be as notable and praiseworthy as they are. What they are doing should not only be common, but normal. Expected. Fundamental.
So, developers, please listen: you are running out of excuses. You can’t claim ignorance; there is too much information out there for you to do that. You can’t hide behind pleas that you don’t have the time or the skill; accessibility plugins abound, and the simplest steps you can take are ones so easy to implement that even I, not tech-savvy by anyone’s standards, can figure them out. You can no longer classify accessibility as optional. Unless we’re talking about visually-based games, for example, there is no sufficient reason to leave a button unlabeled or an image undescribed. By failing to take these essential measures, you’re effectively shirking your responsibility to your users.
For now, we have workarounds. We have specialized software to help us circumvent accessibility challenges. We have extensive experience, accessibility consultants, and countless developers who are already on the right track. All is not bleak. Much of the internet is mostly, if not totally, accessible, and it’s getting better all the time. But …
I’m done making excuses for you. I refuse to apologize when I can’t access features of a website. I can’t in good conscience allow you to view my access issues as an inconvenience. I’m no longer going to defend your ignorance, your unwillingness to take the time, or your belief that I’m asking too much. Developers, I’m not asking a lot. I’m merely asking that I and fellow disabled users be able to access your website. That’s it. I just want to create an account, browse your services, and maybe even give you my money and share your content. I’m happy to help. I’ll cheerfully act as a beta tester. I don’t mind reporting bugs and offering suggestions on how to make your site better. I understand the difference between “inaccessible” and “imperfect.” When it comes to helping you make your site more inclusive, my time is yours.
Until you recognize that it’s time for change, however, I will no longer give you a pass. If you have the resources to make your website eye-catching and flashy and exciting, you definitely have the ability to make sure it’s usable, too. Karl Groves puts it more eloquently than I ever could: accessibility problems are “quality problems,” and nothing less.