Headings and labels need to describe the content they are identifying in the content. This means when you have a H1 is should describe the page as a whole. Labels need to describe the data they are collecting. Seems simple. And usually it is. Let’s look at some examples of when it isn’t as clear.
Comments closedIn the physical world we understand that not everyone can climb 20 flights of stairs, so under the ADA we created rules to overcome these situations. Buildings now have commitments they need to make during construction to include ramps and elevators to access areas that someone might not be able to climb stairs. This is an example of multiple ways. Let’s review how that translates to digital spaces.
Comments closedIf you are anything like me, you don’t want your data sold to third parties. You probably run ad blockers. Maybe a VPN. Some governments are trying to help by requiring the site to declare what cookies are used and providing the user to opt out. But the current method of displaying this information tends to have some serious accessibility issues. I have another way of thinking about them I’d like to propose.
Leave a CommentI’ve been encountering a pattern lately of developers trying to do things right when it comes to live regions, but not understanding how they essentially work. This tip is to provide a super high level on how they function.
Leave a CommentLinks are what make the internet the world wide web. The original idea was that the internet is a set of digital documents. The link allows you to move between them. To make them as effective as they can be, we want to make them clear in what they do. Often though, the simple link doesn’t provide a clear purpose. Let’s look at what it takes to pass 2.4.4 Link Purpose (in Context).
Comments closedI’ve been doing accessibility work long enough that I can confidently say, you cannot avoid lawsuits about accessibility. What you can do is minimize your risk. If you do not have an accessibility effort going on in your company, start one. This guide will help you prioritize where you should be looking first. If you have a program going, this can help focus your efforts into where most lawsuits look first.
1 CommentThe internet today far exceeds what we initially thought it could be. We’ve advanced so far that we can replicate desktop applications running in the browser. Cloud-based software is everywhere. We’ve crafted frameworks to speed up development and solve the hard parts of server-client communication.
But the same problem keeps happening. We keep rebuilding interactive components using custom coding. And we forget all the things we need to do to make them accessible.
Today I’m looking at a why we should be using more native HTML controls and fewer custom ones. I’ll show you what is included if you use a native control.
Comments closedWalking into a library you are faced with thousands of books to read. Each one has a title, and they’re grouped together in like topics. You’re looking for a book on how to develop accessible websites, so you head to the internet section. As you walk into the aisle, all the books are pages out with spines to the back of the shelf.
1 CommentYou’ve seen the warnings before TV shows and movies. “This show contains flashing lights.” This warning on visual media also applies web sites and apps. Guideline 2.3.1 addresses this by implementing a requirement that reduces the potential for severe damage. Let’s discuss why.
1 CommentSEO folks, come at me. The overall product card has gotten cluttered with too many calls to action. It’s killing the point of the interface.
Ecommerce sites have a mind-boggling amount of links. Especially if you are a large company selling diverse things. Just to get to the product list, we first navigate through a mega menu. We do this to choose a category on most eCom sites. Then on the category page, we have to deal with a bunch of filters. If we’re lucky they will be in accordions and we can close them to skip.
1 Comment
