Accessible Web Applications
How we build accessible web applications to WCAG 2.1: inclusive design, screen readers, keyboard navigation, high-contrast colors and a better experience for every user.
Solution example: how we implement a project like this. It does not describe a single client project.
Accessibility as a Competitive Advantage
Initial situation & goals
Accessibility is required by law in many markets, and it is also a competitive advantage. In this solution example, we show how we design a web application, for example for a public agency, so that everyone can use it, and how that makes all users more satisfied.
The problem
Challenges
A wide range of needs
Typical starting point: different needs (physical, sensory, cognitive) each call for specific solutions.
Missing compatibility
Assistive technologies such as screen readers, captions and alternative input methods have to be supported.
Low awareness
Many people still assume that accessibility only matters to a small group.
Goals
Approach
Inclusion
Equal access to information and services for everyone.
Better usability for everyone
Accessible features such as clear navigation, high-contrast colors and alt text help all users, for example on a slow connection or a small screen.
Market advantages
The application reaches new audiences and strengthens the brand.
Building Inclusive Solutions Together
Approach
How we approach it: a clear structure and division of tasks, combined with the right tools and technologies, form the basis of the project.
Project management
Needs analysis and goals
We define user needs and clarify which standards the application has to meet.
Planning for the long term
Strategies and tools make sure future content stays accessible too.
Technologies & tools
Analysis and testing
We use common tools such as Lighthouse, WAVE and color contrast checkers to verify that the requirements are met.
Content management systems
The CMS is configured so that the content it produces is accessible.
Proven practices
We follow approaches that have worked before, so the result holds up over time.
Team & roles
UI/UX designer
Advises on accessible design decisions that look good and put users first.
Developers
Implement the relevant technologies and standards.
Project manager
Plans and coordinates the process and runs manual tests.
Client
Decides on the final design and gives feedback during the build.
Step by Step to an Inclusive Web Application
Implementation
We build an accessible web application in close collaboration with the client, so every requirement is covered and the agreed standards are met.
Core features
Clean code and semantics
Semantic HTML and ARIA attributes improve the structure and accessibility of interactive elements such as modals and dropdowns. Every component can be operated entirely by keyboard.
Responsive design and flexible layouts
The application adapts to different devices and input methods, with zoom and scaling so users can adjust it to their needs.
Colors, contrast and readability
Strong color contrast and readable fonts make content easier to see and more comfortable to read.
Media and alt text
Images get alt text. Videos and audio get captions or transcripts.
Interactive elements and feedback
Forms show clear error messages and visual feedback, and focus management makes navigation easier for keyboard users.
Testing and iterations
Automated and manual tests plus user feedback improve the application step by step.
Accessibility as an Opportunity: What We Have Learned
Lessons learned
Building an accessible website is more than meeting standards. It is a chance to make digital products usable for everyone. Our work on projects like this has taught us a few things that shape how we approach them.
Start with the users
Accessibility means understanding users' needs in depth. Direct conversations and user testing show how much real use cases matter.
Standards are the starting line
The WCAG guidelines are a solid foundation. Specific adjustments on top of them are what make an application truly inclusive.
Next steps
Training on new accessibility standards and technologies.
Building accessibility into design and development processes from the start.
Bottom line
Accessibility is not a one-time goal. It is an ongoing process that meets legal requirements and gives every user a better experience. That is why we plan for it from day one in design, development and content maintenance.
Related services
More case studies
Other projects
Headless CMS Integration
Add new channels without a rebuild: a headless CMS as the basis for a flexible omnichannel content strategy.
DigitalizationRead
SMS group 3D Configurator: Planning Industrial Plants Visually
A WebGL configurator with real-time rendering and ERP integration. It makes complex plants easier to plan, speeds up sales and is easier to use than the old tools.
3D product configuratorReadWhat are you working on?
On the first call, you tell us where things are stuck. We'll tell you honestly whether we're the right fit. 30 minutes, free.
Jens Bohl Founder and Managing Director