How to incorporate accessibility into development
Building accessibility into your development process
Prioritise accessibility in development
Follow coding practices that prioritise accessibility and inclusivity in the development of your digital building logbooks. Ensure seamless integration of assistive technologies and APIs, enhancing the overall user experience for homeowners across Europe.
Follow Web Content Accessibility Guidelines (WCAG)
Web Content Accessibility Guidelines (WCAG) is developed through the W3C process in cooperation with individuals and organizations around the world, with a goal of providing a single shared standard for web content accessibility that meets the needs of individuals, organizations, and governments internationally.
Easy Check – A first review of web accessibility
These checks cover just a few accessibility issues and are designed to be quick and easy, rather than definitive. A web page could seem to pass these checks, yet still have significant accessibility barriers. More robust assessment is needed to evaluate accessibility comprehensively.
It’s useful to pilot tools with teams on smaller-scale projects to observe their application in real-life scenarios (e.g., screenreaders).
Ideally, every potential issue would be resolved prior to launch. However, teams facing significant time or resource limitations may find it beneficial to initially focus on critical areas that could hinder access. Providing clear examples of these priority areas helps in focusing efforts where they are most needed.
It can also be helpful to identify target areas or key touchpoints that commonly cause exclusion and always check those first (e.g. forms, videos, instructions). Other touchpoints that aren’t directly ‘gate-keeping’ access to certain services or products can be addressed later and be part of future iterations.
