Some of you may remember that my first dedicated service for the RapidWeaver community was Classic to Elements, helping users move their existing websites into RapidWeaver Elements.
Now I am taking the next step.
I have launched a new Web Accessibility Services offer at https://einfach-gute-webseiten.de/en/web-accessibility-services/ for websites built with RapidWeaver Elements and have attached a sample audit report at the end.
I can audit an existing Elements website against WCAG 2.2 Level A and AA, document the findings, implement the necessary fixes and retest the finished website. Accessibility can also be included when planning and building a new Elements website.
Why does this matter? Apart from the obvious answer that everybody should be able to use a website, there are three particularly good reasons:
1. Reach more people
An accessible website works better for people using keyboards, screen readers, enlarged text or reduced-motion settings. It also helps visitors with temporary limitations, older devices or simply a bad day and one hand occupied by coffee.
2. Prepare for legal requirements
Accessibility is no longer a distant “maybe someday” topic. The European Accessibility Act has applied since 28 June 2025 to certain products and consumer services, including areas such as e-commerce. The exact obligations depend on the business, service and country, so this is not legal advice, but waiting until somebody sends an official-looking letter is probably not the most relaxing project plan.
3. Build a technically better website
Accessibility work often uncovers issues that otherwise remain hidden: unclear navigation, weak focus indicators, inaccessible forms, poor mobile reflow, missing language information or components that work with a mouse but not with a keyboard. Fixing these points usually makes the website more robust and easier for everyone to use.
And one more thing: can AI understand your website?
People are increasingly discovering businesses through AI assistants as well as traditional search engines. That means a website should not only look good to humans. Its purpose, services, language and relationships should also be understandable to machines.
This is now part of my offer too. I can improve the semantic structure of an Elements website, create consistent metadata and structured JSON-LD data, check canonical and language signals, and prepare sitemap.xml, robots.txt and an optional llms.txt overview. These measures make the website easier for search engines and compatible AI agents to interpret and navigate.
There is no magic “make AI recommend me” switch, unfortunately. If there were, it would probably be hidden next to the button that makes every client send all their content on time. But a clear technical structure gives search engines and AI systems much better information to work with.
I have used my own English homepage and service page as a practical test case. The work included automated and manual WCAG testing, keyboard and focus checks, 320-pixel reflow testing, form validation, media and reduced-motion checks, and a detailed accessible PDF audit report.
You can see the English service here:
https://einfach-gute-webseiten.de/en/web-accessibility-services/
Example WCAG 2.2 audit report:
wcag-audit-report-homepage-en-2026-08-15.pdf (283.6 KB)
So the journey continues: first Classic to Elements, and now Elements to accessible Elements. The second slogan may still need a little work 
If you have an Elements website and would like to know where it currently stands, feel free to contact me. I offer an initial assessment and then prepare an individual fixed-price proposal.