Client
Raiffeisen banka
Turning accessibility barriers into clear next steps
Accessibility
EN 301 549
WCAG 2.2
Intro
The findings remain confidential, but the audit process and methodology can still be shared.
Due to the confidential nature of the audits, I cannot show specific findings, screens, or client data. This case study focuses on my audit process, report structure, and how I turn accessibility barriers into clear, actionable recommendations.
Due to the confidential nature of the audits, I cannot show specific findings, screens, or client data. This case study focuses on my audit process, report structure, and how I turn accessibility barriers into clear, actionable recommendations.
I conducted a full accessibility audit for several clients including Raiffeisen Bank’s website, focusing on WCAG-based evaluation, practical recommendations and support.
I conducted a full accessibility audit for several clients including Raiffeisen Bank’s website, focusing on WCAG-based evaluation, practical recommendations and support.
Context
Accessibility audits turn uncertainty into a clear plan.
The goal of the audit was to evaluate the website against EN 301 549 and WCAG requirements. Although the required standard included WCAG 2.1, I tested against WCAG 2.2 to help the client be better prepared for future accessibility expectations.
The goal of the audit was to evaluate the website against EN 301 549 and WCAG requirements. Although the required standard included WCAG 2.1, I tested against WCAG 2.2 to help the client be better prepared for future accessibility expectations.
Accessibility audits are often misunderstood as a simple automated scan. In reality, automated tools can only support the process. Many issues require manual review, context, assistive technology testing, and an understanding of how barriers affect real users.
Accessibility audits are often misunderstood as a simple automated scan. In reality, automated tools can only support the process. Many issues require manual review, context, assistive technology testing, and an understanding of how barriers affect real users.
The audit focused on a representative sample of the website. The sample was selected to cover the most important pages and a variety of content types, so the audit could reveal barriers across different parts of the experience.
The audit focused on a representative sample of the website. The sample was selected to cover the most important pages and a variety of content types, so the audit could reveal barriers across different parts of the experience.
Process
Choosing a meaningful audit sample
The audit started with selecting a representative sample of pages that covered the most important content and interaction patterns across the website.
The audit started with selecting a representative sample of pages that covered the most important content and interaction patterns across the website.
The size of the sample depended on the scale and complexity of the website, but the goal was always the same: to review the areas where accessibility barriers were most likely to affect users.
The size of the sample depended on the scale and complexity of the website, but the goal was always the same: to review the areas where accessibility barriers were most likely to affect users.
Testing manually, with tools as support
I used automated tools as a starting point, not as the final source of truth. Their results helped highlight potential problems, but each finding had to be manually checked to confirm whether it was valid, avoid false positives, and understand the real impact on users.
I used automated tools as a starting point, not as the final source of truth. Their results helped highlight potential problems, but each finding had to be manually checked to confirm whether it was valid, avoid false positives, and understand the real impact on users.
Each accessibility criterion was reviewed manually, with assistive technologies as support, because automated testing can only detect a limited part of accessibility issues.
Each accessibility criterion was reviewed manually, with assistive technologies as support, because automated testing can only detect a limited part of accessibility issues.
Turning findings into practical recommendations
The most important part of the audit was making the findings useful for the client and their team.
The most important part of the audit was making the findings useful for the client and their team.
For each issue, I documented where it appeared, what the problem was, which criteria it violated, and why it mattered for users. I also prepared detailed recommendations for developers, including examples of possible solutions and implementation guidance.
For each issue, I documented where it appeared, what the problem was, which criteria it violated, and why it mattered for users. I also prepared detailed recommendations for developers, including examples of possible solutions and implementation guidance.
Report
A report designed for action
The report was structured to help the client understand both the overall accessibility state and the specific issues that needed attention. It was designed to be useful not only for stakeholders, but also for the developers responsible for fixing the issues.
The report was structured to help the client understand both the overall accessibility state and the specific issues that needed attention. It was designed to be useful not only for stakeholders, but also for the developers responsible for fixing the issues.
For each finding, I documented the location, problem description, affected criteria, user impact, screenshots, and detailed recommendations for developers.
For each finding, I documented the location, problem description, affected criteria, user impact, screenshots, and detailed recommendations for developers.
The final report included both a high-level evaluation and detailed page-level findings. I presented the results to the client and provided follow-up consultations where needed.
The final report included both a high-level evaluation and detailed page-level findings. I presented the results to the client and provided follow-up consultations where needed.
Result
Overview of accessibility barriers and a practical path toward fixing them.
The audit provided a structured overview of accessibility issues across the selected website sample. It helped the client understand which barriers were present, why they mattered, and how they could be addressed.
The audit provided a structured overview of accessibility issues across the selected website sample. It helped the client understand which barriers were present, why they mattered, and how they could be addressed.
The report also created practical input for development work, supported prioritization of fixes, and improved the team’s understanding of accessibility.
The report also created practical input for development work, supported prioritization of fixes, and improved the team’s understanding of accessibility.
Accessibility audits are not just about finding issues. They are about helping teams understand the impact of those issues and giving them clear, practical steps to fix them.
This project reminded me that a good design system is not the most complex one. It is the one people can actually use, trust, and maintain over time.