Practicing web accessibility
Successful web design begins with semantic HTML and WCAG compliance, emphasizing inclusive content and user needs. Redesigns should start with accessibility audits, prioritizing critical issues, high-impact content, and reusable components to ensure sustainable accessibility improvements.
Planning for success
A Solid foundation
The foundation for any website should be semantic HTML, with CSS for visual presentation, and JavaScript as needed for additional functional behaviour. Design and develop using the non-proprietary standards and technical specifications that define the World Wide Web.
WCAG 2.1 and 2.2
Ontario’s legal standards for web accessibility are based on the WCAG 2.0, which was published in December 2008. WCAG 2.1 became a W3C recommendation in June 2018 and WCAG 2.2 was released in 2023. These are backwards compatible with previous versions, which means that compliance with the WCAG 2.1 also achieves compliance with the WCAG 2.0. We highly recommend that every designer read the latest version of the full WCAG Overview.
Mindset
Design for the needs of the widest possible range of users throughout the process.
Content considerations
As early as possible in the process, assess the content that is going to populate the new website. Accessibility issues often start with the content and language usage. Digital documents that are linked or embedded in the website should be considered as part of the content as well.
Testimonial
The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect.
Tim Berners-Lee, creator of the World Wide Web
Redesigns & renovations
Many web design projects are some form of redesign or renovation. Before any serious work has started, ask the client if there is any content that can be decommissioned and removed altogether. This saves everyone time and money.
Next, perform an accessibility audit. Consider classifying issues into the following four categories.
- Critical. A serious problem that will prevent people with disabilities from using the site.
- Serious. A very frustrating problem that might prevent people with disabilities from using the site.
- Moderate. A mildly frustrating problem that will not likely prevent people with disabilities from using the site.
- Minor. An accessibility issue that is unlikely to cause problems for anyone.
Once accessibility issues are identified and classified, look at addressing critical issues in the site templates and reusable components. Focus on the elements that have the highest degree of usage and the most serious accessibility issues. Also consider prioritizing any forms or mechanisms that enable users to either provide feedback or ask for assistance.
The next phase of work might focus on individual pages and content. Use traffic analysis tools to identify the most visited content, and the paths that users take both within pages and throughout the site. Prioritize the most critical issues on the content with the highest impact.