Getting started with accessibility standards and compliance can feel overwhelming. You may feel the need to make major changes, even doing a total reboot or rebuild.

Here’s a question for you: Have you ever been frustrated by an assemble-it-yourself furniture project? The instructions are supposed to be easy to follow, but you find yourself begging a friend to help or hiring someone to do it for you—or worse yet, abandoning the project altogether and returning the item.

Have you tried to navigate a stroller over a curb and then attempted to open a heavy door to get inside a store? (Did we mention your child is also crying and demanding lunch?) And, it’s raining.

People have got so many choices when it comes to looking for information. Google, Wikipedia, YouTube are certainly go-to sources, but libraries are very much still sought-after destinations for people.

Times are changing, exponentially faster than we may want to admit. We’re soaking in water floatation tanks to calm our nerves and planning subdivisions on Mars as one way to deal with climate change.

For many website visitors, beautiful images are vital to creating an appealing browsing experience and help to create awareness of all the services and resources available at the library. However, if a visitor is using assistive technology that reads the screen, those images can hinder the visitor’s ability to quickly.

By Ian Forrest Web accessibility isn’t easy. Sure, the fundamentals are simple enough, but most developers aren’t taught accessibility in school and it’s something that’s often taken for granted. And as web interactions become more complex, developers become even more likely to ignore accessibility — until someone.