Imagine you are really excited about doing something online, such as buying that shiny new gadget, those concert tickets you\u2019ve been waiting for, or those plane tickets that finally came down in price so you can go on that much-needed vacation you\u2019ve been waiting for. Today is the day when you can finally make that purchase. You hop online using your device of choice, log in, open up your preferred web browser, navigate to the site, and\u2026<\/p>\n\n\n\n
You can\u2019t read any of the buttons or links. The images are just black squares, and all the text looks exactly the same\u2014no larger text for headings, no bold or italic font, nothing. The page is just a wall of text with random black squares where images should go. Blank buttons permeate the page, their purpose a mystery that could bring success or epic failure as you roll the dice on activating them.<\/p>\n\n\n\n
This nightmarish scenario is all too familiar for those of us who are Blind or visually impaired and rely on assistive technology (AT) to perform daily digital tasks. <\/p>\n\n\n\n
Those customers who don\u2019t need assistive technology to access the web would snatch up those tickets, the last of those gadgets, or the last cheap plane ticket while those who need to use assistive technology are still pressing all the blank, unlabeled buttons to see what they do, arrowing around the page frantically, smashing their keyboards against the wall, etc.<\/p>\n\n\n\n
To make this scenario even worse, this is all easily avoidable and fixable. <\/p>\n\n\n\n
Assistive technology, such as a screen reader, is designed to understand standard HTML. That means that if AT can\u2019t interpret a button, link, or other standard HTML element, someone has broken it, so AT users can\u2019t use a web page as intended.<\/p>\n\n\n\n
What\u2019s more, even if some developer made an element inaccessible, we have a sort of digital duct tape to fix such issues. Enter ARIA.<\/p>\n\n\n\n
ARIA gives us handy HTML attributes we can put as duct tape over the leaky pipes and broken support struts that make up a web page. Oh, and this duct tape is invisible to everyone except those who use AT.<\/p>\n\n\n\n
I have been using a screen reader for almost thirty years and have really seen some stuff (no pun intended). <\/p>\n\n\n\n
Like nearly all screen reader users, I have been that person in the mentioned scenario many times. <\/p>\n\n\n\n
It did use to be way worse decades ago of course; pages would need to refresh when you are in the middle of reading a lengthy article for school, throwing your screen reader focus all the way back to the top of the page, searching for a \u201cdownload\u201d or \u201csubmit\u201d button in vain because the aforementioned element is an animated image with a JavaScript function that is only looking for mouse clicks.<\/p>\n\n\n\n
Another accessibility problem I used to see all the time was a web page that did not have any headings. <\/p>\n\n\n\n
Screen reader users rely on headings to provide structure to a page. You can quickly jump around a page that has properly marked-up headings. Without them, you have to press up and down arrow keys ad nauseum until you find what you are looking for. <\/p>\n\n\n\n
Mostly, it is the websites not owned by a large group, such as personal pages that may not have headings. If I get to a web page and I hear my screen reader say \u201cno headings available\u201d when I press the \u2018H\u2019 key, I\u2019m noping out of there in a hurry. <\/p>\n\n\n\n
Luckily, the rise of CMS (Content Management System, like WordPress) has helped with this since their templates typically have headings, albeit not in a logical order, but they at least have headings.<\/p>\n\n\n\n
Now imagine a team of dedicated, talented accessibility engineers whose continuing mission is to seek out inaccessible content, explore strange, new websites, and boldly go where no team of accessibility engineers has gone before. <\/p>\n\n\n\n
Such a team would share their values of equitability, access for all, and expertise in making the digital world accessible. <\/p>\n\n\n\n
Imagine a world where no one has difficulty using a digital environment due to their ability. Imagine a world where typing just a few keys to label a button for screen reader users or putting a simple <h1> tag on a heading makes a world of difference in someone else\u2019s life. Imagine that doing such a simple thing allows that person to purchase that fancy, new gadget, those much sought-after concert tickets, or that plane ticket to that dream vacation.<\/p>\n","protected":false},"excerpt":{"rendered":"
Imagine you are really excited about doing something online, such as buying that shiny new gadget, those concert tickets you\u2019ve been waiting for, or those plane tickets that finally came […]<\/p>\n","protected":false},"author":33,"featured_media":93761,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[14],"tags":[66,55,80],"class_list":["post-93760","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-accessibility","tag-accessibility-testing","tag-web-accessibility"],"acf":[],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t