How Do You Integrate AI-Powered Chatbots Into Our Existing Website to Improve Customer Service?

Introduction

Web accessibility — building websites that are usable by people with disabilities — is both a moral imperative and, in many jurisdictions, a legal requirement. For Swiss businesses, the topic is increasingly relevant: the revised Swiss Disability Discrimination Act (BehiG) and European accessibility standards are raising expectations, and an accessible website is also a better website for all users. In this article, we explain what web accessibility means, what the key requirements are, and how Swiss businesses can implement it in practice.

Problem

Many websites unintentionally exclude users with disabilities through poor design and development choices.

Common Accessibility Barriers

• Images without alternative text (alt attributes) are invisible to screen reader users.
• Poor colour contrast makes text difficult or impossible to read for users with visual impairments.
• Keyboard-only navigation is impossible on many sites, excluding users who cannot use a mouse.
• Videos without captions or transcripts exclude deaf and hard-of-hearing users.
• Complex, confusing forms create barriers for users with cognitive disabilities.

Legal and Reputational Risk

• Swiss public sector websites are required to meet WCAG 2.1 Level AA standards under Swiss legislation.
• The EU Web Accessibility Directive applies to public sector bodies operating in EU member states and influences best practices more broadly.
• Inaccessible websites expose businesses to reputational risk and potential legal challenges.
• Switzerland has approximately 1.7 million people with some form of disability — an inaccessible website unnecessarily excludes a significant portion of the potential customer base.

Misconceptions About Accessibility

• Many businesses believe accessibility is expensive to implement or will compromise visual design — both misconceptions.
• Accessibility is often treated as an afterthought rather than integrated from the start of a project.
• There is a widespread lack of awareness about what accessibility actually entails and how to test for it.

Solution

Web accessibility is best approached as a practice built into the design and development process from the outset.

1. Follow WCAG Guidelines

• The Web Content Accessibility Guidelines (WCAG) 2.1 provide a comprehensive framework organised around four principles: Perceivable, Operable, Understandable, and Robust (POUR).
• Level AA is the generally accepted standard for commercial websites and is referenced by most accessibility legislation.
• Focus initially on the most impactful criteria: sufficient colour contrast, keyboard navigability, meaningful alt text, and accessible forms.

2. Accessible Design

• Use a colour contrast ratio of at least 4.5:1 for body text and 3:1 for large text and UI components.
• Design clear focus indicators so keyboard users can always see which element is currently active.
• Ensure interactive elements are large enough to be easily tapped on touch screens (minimum 44x44 pixels).
• Avoid relying solely on colour to convey information — use additional visual cues such as icons or text labels.

3. Accessible Development

• Use semantic HTML elements correctly — headings, lists, landmarks, buttons, and links should all convey their meaning through the HTML structure.
• Implement ARIA (Accessible Rich Internet Applications) attributes where necessary to supplement HTML semantics for complex UI components.
• Ensure all functionality is operable via keyboard alone, with a logical focus order.
• Test with real screen readers (NVDA, JAWS, VoiceOver) as part of the development process.

4. Testing and Validation

• Use automated tools such as Axe, Lighthouse, or WAVE to catch common accessibility issues quickly.
• Supplement automated testing with manual keyboard navigation testing and screen reader testing.
• Involve users with disabilities in usability testing where possible — this provides insights that automated tools cannot.
• Conduct regular accessibility audits, particularly after significant content or design changes.

Benefits

Accessibility improvements benefit all users, not just those with disabilities.

• An accessible website reaches a broader audience, including Switzerland's 1.7 million people with disabilities.
• Accessibility improvements often align with general usability best practices, making the site better for everyone.
• Better semantic HTML and clear structure improve search engine indexability, contributing to SEO performance.
• Demonstrating commitment to accessibility enhances brand reputation and signals corporate social responsibility.
• Building accessibly from the start is significantly cheaper than retrofitting accessibility later.

Practical Example

A Swiss government agency undertook a full accessibility audit of their public information website. The audit identified 47 distinct WCAG violations, including poor colour contrast on a widely used information panel, missing alt text on over 200 images, and a contact form that was completely unusable via keyboard. After a targeted remediation project, the site achieved WCAG 2.1 Level AA compliance. The agency reported a measurable increase in time on site and a reduction in support enquiries from users who had previously struggled to find information.

Conclusion

Web accessibility is not optional — it is a fundamental aspect of building websites that work for everyone. For Swiss businesses, the combination of evolving legal requirements, a significant population of users with disabilities, and the general usability benefits of accessibility makes it a priority worth investing in. The most effective approach is to treat accessibility as a core quality criterion from the very beginning of any web project, rather than as a compliance checkbox to be addressed at the end.