Why Accessibility Matters
Complying with accessibility standards like WCAG is only the first step; you also need to build capacity to maintain accessibility, especially as standards evolve and new technologies or solutions arise.
Ultimately, you don’t want to treat web accessibility as a technical feature, but an underlying framework of your library website. Otherwise, you’ll be at higher risk of suffering from accessibility gaps, particularly when standards evolve or web technologies change. The best way to mitigate such risks is by investing in a dedicated team that treats online accessibility for public libraries as its core mission.
Libraries may treat accessibility as one aspect of their digital strategy. They may, for example, invest in a tool like a screen reader and then check accessibility off their checklist.
However, accessibility is more than just a collection of features; it’s a thought process that must shape your digital strategy from end to end.
Not every public library has the bandwidth to invest in such internal infrastructure when there are more urgent, competing priorities. The next best option is to work with a partner that treats online or web accessibility in public libraries as its primary mission. This approach offers a dual benefit: First, you get the necessary infrastructure to achieve your accessibility needs. Second, if your partner works with other public libraries, the solutions you get will draw on the data and insights of a larger pool of users—larger than what you could access alone.
Next Steps
Accessibility is a crucial piece, but it's only one piece among many. Your online library project needs to account for web design, security, content management, catalog integration, and a range of other factors as well. To get a full understanding of how to direct your online library project, see our complete web development guide (written specifically for public libraries!).
.svg)
