Foundry and the European Accessibility Act

Hey everybody (and especially Elixir),

As someone just mentioned on Realmac’s forums, the EU is going forward with its Accessibility Act. Websites with certain types of content need to be complaint before 28 June 2025.

As far as I understand the legislation (I’m a webdev, not a lawyer), sites that offer services in regarding air, rail, water and bus transport need to be compliant. But so do online banking portals and e-commerce sites (webshops).

The legislation demands that sites be readable by visitors with a visual disability by offering either a way to view the text content free of clutter or offer a read-out-aloud (text-to-speech) function.

This is what the legislation mentions on which features should be present (of course not everyone will be technically possible with or applicable to websites):

" User interface and functionality design:

The product, including its user interface, shall contain features, elements and functions, that allow persons with disabilities to access, perceive, operate, understand and control the product by ensuring that:

(a) when the product provides for communication, including interpersonal communication, operation, information, control and orientation, it shall do so via more than one sensory channel; this shall include providing alternatives to vision, auditory, speech and tactile elements;

(b) when the product uses speech it shall provide alternatives to speech and vocal input for communication, operation control and orientation;

(c) when the product uses visual elements it shall provide for flexible magnification, brightness and contrast for communication, information and operation, as well as ensure interoperability with programmes and assistive devices to navigate the interface;

(d) when the product uses colour to convey information, indicate an action, require a response or identify elements, it shall provide an alternative to colour;

(e) when the product uses audible signals to convey information, indicate an action, require a response or identify elements, it shall provide an alternative to audible signals;

(f) when the product uses visual elements it shall provide for flexible ways of improving vision clarity;

(g) when the product uses audio it shall provide for user control of volume and speed, and enhanced audio features including the reduction of interfering audio signals from surrounding products and audio clarity;

(h) when the product requires manual operation and control, it shall provide for sequential control and alternatives to fine motor control, avoiding the need for simultaneous controls for manipulation, and shall use tactile discernible parts;

(i) the product shall avoid modes of operation requiring extensive reach and great strength;

(j) the product shall avoid triggering photosensitive seizures;

(k) the product shall protect the user’s privacy when he or she uses the accessibility features;

(l) the product shall provide an alternative to biometrics identification and control;

(m) the product shall ensure the consistency of the functionality and shall provide enough, and flexible amounts of, time for interaction;

(n) the product shall provide software and hardware for interfacing with the assistive technologies;

My question is: will Foundry be updated to make this easier (or even possible in some cases)?


Hi there @Erwin-Leerentveld

Most of what you’re asking about is related strictly to content – meaning the content you add to your site – along with styling and information gathering.

Foundry doesn’t have control over these things. The style you choose for your buttons, text, etc is all up to you during your design of the site. You can adjust these to be friendly to visitors with color blindness, as well as allowing you to adjust contrast to make things legible, or increase font sizes, and so on. These are all choices you make as the site’s developer and are adjustable within the settings in Foundry’s suite of stacks.

Additionally Foundry does not use any cookies or other data collection. Anything you have on your site that does this would not be Foundry-based. Foundry also provides alternatives to things like Google Fonts and such by allowing you to self-host these items. Stacks even goes as far as allowing you to opt to use local versions of things like jQuery and FontAwesome instead of the CDN versions.

As for audio – Foundry does not contain an audio player of any sort, so there’s no problem there.

Foundry also allows you to provide alt tags for images which might need them for things such as screen readers.

Foundry also already allows navigation items to be tabbed to as well when a user has this feature enabled within their browser settings.

TL;DR: Foundry provides for these requirements where needed. But the vast majority of these areas have to be addressed through your own content, styling, etc, etc.


Hi @elixirgraphics,

Thanks for the quick reply!

Now I can sleep again :slight_smile:


Well the even better news is that you wouldn’t have had to freak out for quite a while anyway. Here’s a bit from the European Accessibility Act website:

Note though I’m in the United States and don’t have a background in this act nor am I a lawyer that is equipped to give you advice on the matter.


This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.