Not every website and every company has a high standard for clean, accessible web solutions. We place a great deal of importance on accessibility for all users. There are many checkers and systems that verify these standards. Some services and tools are presented here.
Breakdown of the score: Your accessibility rating is a measure of how well your website performs in the automated Siteimprove accessibility checks. Our assessments are based on the WCAG success criteria, which are divided into conformance levels A, AA, or AAA. In the image (screenshot), you can see how well you performed in each category.
Plone - Accessibility first
Plone is a content management system that places special emphasis on accessibility. It meets the WCAG 2.1 guidelines (Web Content Accessibility Guidelines) and supports the creation of content that is accessible to all users – regardless of physical limitations or technology used.https://plone.org/accessibility).
Plone provides accessible templates, ARIA roles, semantically correct HTML, and good keyboard navigation by default. Images can be provided with ALT tags by default, making content accessible to screen readers. The strong focus on accessibility makes Plone one of the preferred CMS solutions for public institutions and organisations that want to provide inclusive web offerings.
✅ Recommended plugins / widgets
- accessiBe: An official app in the Webflow app directory – it promises 'Web Accessibility made simple', with daily AI analysis and automatic adjustments based on WCAG 2.1 Level AA.
- Accessibility Enabler: Widget with over 30 tools (contrast modes, screen reader aids, text adjustment etc.), which can be easily integrated into CMS systems according to the provider.
- Elfsight Accessibility Widget: A relatively lightweight approach that can be easily embedded via a code snippet, focusing on accessibility modes and widget display.Elfsight+1
- All in One Accessibility: A widget that covers many international standards – including EAA (Europe) and EN 301 549.
- Accesstive: Platform with widget, monitoring and AI audit specifically for Webflow, with a note on easy integration via script insertion.accesstive.com
🛠 Usage and implementation notes
- Installation: Most widgets only require the insertion of a JavaScript code in the "Footer Code" section of your Webflow project (Project settings → Custom Code) and subsequent publishing. Example: "Paste the code in the Footer Code section before closing </body> tag".accesstive.com+1
- Design Integration: Ensure that the widget visually matches your brand identity (e.g. colours, style) – especially if your target audience is global or if there are high brand requirements.
- Further measures needed: Important: A widget alone does not make your websitefully compliantwith all requirements (e.g. WCAG 2.1 AA, EAA, EN 301 549). You must also improve design, semantic structure, keyboard usage, focus styles, etc.Reddit+1
- Monitoring & Maintenance: Choose a system that offers regular audits, reporting or monitoring – accessibility is an ongoing process, not a one-time action.
- Legal & Documentation: If your website is relevant for Europe, you should implement aAccessibility Statementdocumenting where exceptions may exist and providing feedback mechanisms for users.
🎯 Recommendation for your company context
The following approach is recommended for your company:
- Basic Audit: First, conduct an internal audit (e.g. Webflow Audit Panel: “Accessible elements in Webflow”).
- Widget Integration: Choose, for example, accessiBe or All in One Accessibility and integrate the widget into your Webflow site.
- Technical Optimisation: Revise areas such as image alt texts, heading structure, keyboard accessibility, focus states, colour contrasts.
- Documentation: Create an accessibility statement on the website (e.g. “Our website meets …”), with feedback options for users.
- Monitoring & Reporting: Specify how regularly you will have access to reporting values (e.g. monthly/quarterly) and define responsibilities for remediation.
- Scaling: Ensure that new pages/languages are automatically captured in the widget or designed to be accessible, so that your global website remains consistent.
1. Basic Principles of Accessibility
- Content should be accessible to all people, regardless of age, disability, or device.
- The community website adheres to the WCAG 2.1 guidelines (Level AA).
- Clarity, structure, and accessibility are the focus.
2. Text Design
- Clear language: short sentences, active formulations, simple terms.
- Paragraphs: not too long, thematically clearly structured.
- Heading hierarchy: H1 for page titles, H2 for main sections, H3 for subpoints.
- Lists: use bullet points for clear structure.
- Contrasts: text colour and background must provide high contrast (e.g. dark text on a light background).
3. Images and Graphics
- Alternative texts (Alt texts): accurately describe the content of the image.
- Example: "View of the Andelsbuch marketplace in sunshine".
- No text only in images: important information must be available as text.
- Infographics: add a summary description below the graphic.
4. Videos and Multimedia
- Subtitles: all videos should be provided with subtitles.
- Transcripts: provide a text transcript for longer content.
- Audio description: optional, for important visual information.
5. Links and Navigation
- Descriptive link texts: avoid "click here", instead use, for example, "download mayor's letter".
- Tab navigation: content must be accessible via keyboard.
- Jump marks: for quick navigation between main areas.
6. Tables
- Simple tables: Clear headings in the first row.
- Summaries: Brief description of the purpose and content of the table.
7. Forms
- Labels: Each input must be labelled.
- Error messages: Clearly formulated, indicating where the error lies and how to fix it.
- Tab order: Logical and understandable.
8. Check before publication
- Automated tools: Use WAVE, Accessibility Insights or Siteimprove for checking.
- Manual check: Test pages with a screen reader and keyboard.
- Readability: Content should be understandable by people with different language and education levels.
9. Responsibilities
- Each editor checks their own content for accessibility.
- A coordinator for digital accessibility monitors compliance with the guidelines.
Further information: