Web accessibility is a prerequisite for digital inclusion, and it is about all people, including people with disabilities, being able to use websites and digital services, but many web developers encounter difficulties when making web applications accessible. In this thesis, I investigate the conditions and challenges web developers experience in their work by making the web accessible, especially within the public sector. The study is based on a qualitative content analysis of discussion threads from the developer forum Stack Overflow over the past six years. The focus was on the most active threads where web developers discuss problems, ambiguities, and solutions regarding accessibility on the web.

The work begins with a background on web accessibility, and the analysis identifies key factors that affect developers' work with accessibility:

1. Lack of knowledge and training in accessibility standards,

2. Lack of clear organizational support and management priorities,

3. Technical and practical barriers linked to tools, working methods and requirements specifications,

4. As well as attitudes, motivation and cultural beliefs about accessibility.

The results show that developers are often unsure of how to interpret guidelines in practice and encounter problems with screen readers, forms, and ARIA attributes. That the WCAG guidelines are experienced as complex and difficult to interpret in practice. It also appears that accessibility is rarely integrated early in the development process, which negatively affects the results.

The discussion links the results to previous studies and discusses implications for the industry. The study concludes with the conclusion that web developers need clearer guidance, more training, and organizational support to successfully make the web accessible.