European Accessibility Act EAA concerns websites from companies who deliver goods/services to consumers and/or governments.
Digital accessibility is the design and development of digital products, such as websites, apps and documents, so that they can be used by people with various disabilities, such as visual, auditory, motor or cognitive impairments. The goal is to make technology accessible to everyone, so that all users can have the same access and experience, regardless of their abilities. Digital accessibility provides access to information and services for everyone, including people with disabilities.
In The Netherlands we have to include this before the 28th of june!
My question is if there are solutions/stacks/plugins tot integrate accessibility into websites made with Rapidweaver?
thanks in advance
If you are already using Foundation 6, you are already done.
There were a couple great talks about Accessibility at the Stacks Summit last year, if you have access to the videos.
2 Likes
Awesome Joe, yes we build all our websites with Foundation6 so that is good news.
I like to watch the video’s, where and how can i watch those?
Cheers e Abs
If you attended the summit or purchased access to the videos, you can get to them here… https://academy.weavers.space/
1 Like
Dived into to the matter deeper. For example, how can you achieve keyboard operability for interactive elements like menu and links within Foundation6 ?
@joeworkman … how can you achieve keyboard operability for interactive elements like menu and links within Foundation6 ?
Foundation menus and buttons and links are navigable with simply the tab button.
There is a skip link template in the free template pack. This is useful for accessibility to assist user with assistive devices to jump directly to the main content of a page.
1 Like
I understand, but that is not what they (gov) ask for. You have to have a keyboard shortcut for each navigation button. Maybe it is an idea for a near future update, because it is a pretty hot topic right now.
Do you have a source of this requirement?
These laws and rules depend your country. Search on the internet about WCAG and you will find the page from your government about the subject. But in basics you have to have need an easy to understand navigation, that you can control with a keyboard. Just a by a TAB does not seams to be enough.
Than je need to provide a visible indicator of keyboard focus.
The different used colours must have enough contrast between text and background.
And there are a lot of more of these rules to apply now. Some like an ALT text on pictures is not to difficult to achieve, but all video’s must have now a subtitle and transcriptions.
At the moment the government start to check websites they can give big fines. I heard about a developer in Germany got fined 10.000 euro’s because of some WCAG errors in a checkout system.
They also keep developers responsible for this, and not your website client for example.
Bur let’s see. I hope @joeworkman can add some more functionality in this in Foundation6.
Then please send me the source for your country where exactly it’s stated you need a shortcut for each menu item.
For example this one: Richtlijnen - WCAG.nl
And here some more info about that the advices from the EAA are now are law by the 28th of June 2025: Nieuwe Europese toegankelijkheidswet - Digitale Overheid
If you dive into the matter you will see that it becomes very serious fro a lot of types of websites.
Hi @Blacksheep013,
I see you’re Dutch (as am I), and I’ve looked into this extensively with my legal advisor a couple of months back. To assure you:
- In the Netherlands (and the rest of the EU), you do not have to create a keyboard shortcut for each element on your page. A simple TAB to move through the fields, buttons and links, like Joe advises, is enough. This is what WCAG.nl writes about that:
Zorg dat alles te bereiken en bedienen is met het toetsenbord
(Principe 2, first bullet). no specifics on how, just that you must implement keyboard nav.
This one is more concerning though:
Zorg voor een zichtbare indicator van de toetsenbordfocus.
At the moment, you can’t highlight all elements on a page when the user tabs through it. Some browsers offer this, but that’s not enough according to my legal advisor.
2 Likes
I think the same 👍
In this case, what about Bootstrap 5 and its indication where the tab focus is currently sitting on? I think about the bold blue outline / border.
1 Like
Thank for your reply Erwin, I did the same as you. I asked around with some legal experts and colleagues. And in this keyboard matter there are doubts in what we have to do exactly. Some says a TAB would be enough, but they also say it is not 100% sure this is the case!I hope this clears up in the coming months.
I do not think they start to fine this year if the applied rules are not 100% clear.
But for the future it would be handy to have some more options in Foundation6 to choose from in this matter.
Bootstrap5… interesting thought, I will look into to that.
hmmm, good point. Bootstrap does indeed support that.
Shame the Foundry themes don’t appear to support it - which is where most of my projects live in :(
1 Like
On a sidenote, neither WCAG.nl or digitaleoverheid.nl themselves seem to support tabbing through the content on the page.
1 Like