Hi, at June 2025 new websites have to be WCAG 2.2 conform, at least for larger companies. It still might be helpful to set up new websites to meet these requirements as close as possible.
→ I did not check every documentation, but from your experience, does Blocs have the in-built support for aria labels and such?
I know much depends on contrast of colors and other things not necessarily in the responsibility of Norm.
Thank you 
@Norm Could you please add some information about this?
Hey @Fuellemann sorry I missed this.
Regrading aria labels, we add them to various parts of the UI generated by Blocs, elements with more complex structures such as the navigation and carousels.
But you can add your own using the Custom Data Attributes.
As for colour contrast, we have the Colour Impairment controls in canvas settings to test contrasts against various colour impairments.
I hope that helps.
Hi I am “fighting” with this problems. I made same pages - and now I have a lot of troubles. There are missing text at links (where should be placed), neighbor links to same url (? I don’t understand that).
Is it planned, that are ready templates with WCAG Features in Blocs App Store?
Did you try the custom attributes as mentioned above? 
I will try a new page with this attributes
Neighbour links are usually alerts and not errors, they are flagged in an audit but you can document their reason for being there e.g. Sign Up Now might appear in a menu, but you might also place it in a call to action elsewhere in a page. That is an alert only, you could probably be best adding an aria label in custom attributes stating this for a screen reader.
Missing text links is a bit of a pain, it happens in the social media icons group bric, I couldn’t remedy that with custom attributes so rebuilt it instead from scratch using buttons.
What’s needed for the follow Bric I’ll add it in an update to the Bric.
Thanks @Norm luckily I hid and selected do not publish so I just reinstated and published to get the WAVE report, here are the problems as screenshots.
As you can see the link not having a discernable name. I put an ARIA label in and tried that, but it didn’t satisfy the outcome.
It’s interesting though, apart from these few niggles Blocs is very efficient, much more efficient and compliant in code generation than other systems I’ve used. Without wanting to create a riot and a digital brawl, another system I’ve used is a bit like the Wild West with accessibility compliance, with too many variables involved, with elements created by different individuals that render them unusable due to the accessibility requirements not being integrated. These requirements I believe are not encased in US law, therefore are not high on the agenda it would seem. I’ve got a couple of websites I’m going to have to recreate in Blocs to meet guidelines so they are no longer on the other system. Apart from trying to now minimise US software where I can due to potential future problems that could be caused with digital tarrifs (you never know now what could happen, be prepared 
), accessibility is strengthening that belief, using Blocs and Volt keeping it UK/EU means that these aspects of accessibility will be more focussed. In a nutshell, a few niggles here and there, but Blocs is very good at meeting legislation, and great that we can discuss with devs on here when discovered. I wonder how this will pan out for other non UK/EU no code systems and also for the mighty Worpress.
Edit: One thing that needs to be considered with code generated for a link name is that it can’t be generic such as Link, Read More, etc it has to be descriptive and useful otherwise it still flags as an error. Another exmple is in the Nav bar for the logo, if it is just kept at the default Logo it flags up, but because this is user editable it can be sorted and made unique such as ‘Logo image for company name’.
I am also very interested in this area of design / development.
Maybe we could share tools, tips, solutions used within Blocs, etc. here ?
I am digesting this.
For all german users, please see this article regarding the requirements as well as the exceptions for accessibility by June 28th, 2025:
Good idea, maybe a thread dedicated to it. The regulations affects many of us, but many folk are not yet up to speed with it. It is a good thing as accessibility has often been overlooked, but is now just as important from a regulation sense as GDPR. I know many folk use the Lighthouse test and can score highly on it and think that covers it. It’s quite easy to score 100% for accessibility on that. I’m may be drawing on assumption here, but with it being American it may not be looking for UK/EU regulations. as I say I might be wrong on that but WAVE picks up many errors that need fixing or addressing that Lighthouse doesn’t.
Yes Shall we create one? I am Germany so this affects my clients. It has been mentioned before but blocs exports pretty nice code. Also it seems that if we follow the basic requirements wave scores are better then expected - alt Tags, proper titles, H1-H5. I would like to dive a bit deeper into these regulations and find appropriate solutions.
I am thinking about buying this course.
https://www.udemy.com/course/web-accessibility/?couponCode=MINICPCP70425#reviews
@BAM All of those you mention are great, but to be honest one of the best ways to learn and become more familar is to run each page throughh WAVE see what errors and alerts you get, they have great reference material, where it tells you the problem, then goes in to more detail and shows you the code that is causing the problem.
You can also, if need step by step explanation of something use Chat GPT or Claude AI to investigate the code, copy and paste code in to them, they can be really nifty at generating code snippets for you if something becomes quite difficult to solve as a workaround if it is something out of your control to remedy.
For anyone interested.
