Accessibility is a cross-role responsibility and this also means that documenting it has to be a common task. Cooperation and common grounds makes the teams efforts much more effective and it can mean a big difference when relevant documentation clarifies also the minor important decisions about specifics of accessibility.
Web is full of sticky or fixed elements and they may add to usability for some users. But if we think about variety of different users we may quickly note the possible problems for them. Covering too much screen, covering important other elements, or even blocking users totally can be prevented with proper planning and testing. This article tries to map the problems as a first step to proper awareness.
Simple reflection – accessibility is about alternatives; giving users different possibilities and respecting their preferences and needs. It’s about making things that can be accessed in multiple different ways – alternatives.
Common effort, interdisciplinary competence and early dialog can be the only best practice for assuring the accessibility of the final product. If we leave that team members live in their own roles then we are almost surely to fail and get into situations where the issues on the end prevent launching accessible products and flood the team with issues. Cooperation and dialog are key!