Menu
ICA Congress Barcelona 2025 is committed to making it website accessible, in accordance with Royal Decree 1112/2018, of 7 September, on the accessibility of public-sector websites and applications for mobile devices (hereafter, Royal Decree 1112/2018, of 7 September), with which the Directive (EU) 2016/2102 of the European Parliament and Council is transposed.
This accessibility declaration applies to ICA Barcelona 2025 (the subdomains of this website shall have their own declaration).
This declaration was prepared on 24/10/2024.
Last revision of the declaration: 24/10/2024.
This website is compliant with Royal Decree 1112/2018, of 7 September having passed an external accessibility audit carried out with the Accessibility Checker tool. The following aspects were tested and considered as Accepted, based on WCAG 2.2, the international standards by WC3 . These standards are accepted by ADA and Section 508, EEA and EN 301 549 , and other worldwide accessibility legislations.
1. Uses ARIA roles only on compatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page.
2. `button`, `link`, and `menuitem` elements have accessible names
When an element doesn’t have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers.
3. ARIA attributes are used as specified for the element’s role
Some ARIA attributes are only allowed on an element under certain conditions.
4. Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology.
5. Elements with `role=”dialog”` or `role=”alertdialog”` have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements.
6. `[aria-hidden=”true”]` is not present on the document “
7. `[aria-hidden=”true”]` elements do not contain focusable descendents
Focusable descendents within an `[aria-hidden=”true”]` element prevent those interactive elements from being available to users of assistive technologies like screen readers.
8. Elements use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies.
9. `[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers.
10. `[role]` values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions.
11. `[aria-*]` attributes have valid values
Assistive technologies, like screen readers, can’t interpret ARIA attributes with invalid values.
12. `[aria-*]` attributes are valid and not misspelled
Assistive technologies, like screen readers, can’t interpret ARIA attributes with invalid names.
13. Buttons have an accessible name
When a button doesn’t have an accessible name, screen readers announce it as “button”, making it unusable for users who rely on screen readers.
14. Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read.
15. Document has a `<title>` element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search.
16. `<frame>` or `<iframe>` elements have a title
Screen reader users rely on frame titles to describe the contents of frames.
17. Heading elements appear in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies.
18. `<html>` element has a `[lang]` attribute
If a page doesn’t specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn’t actually in the default language, then the screen reader might not announce the page’s text correctly.
19. Identical links have the same purpose.
Links with the same destination should have the same description, to help users understand the link’s purpose and decide whether to follow it.
20. Image elements have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute.
21. Image elements do not have `[alt]` attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice.
22. Links have a discernible name
Link text
23. Links are distinguishable without relying on color.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision.
24. `[user-scalable=”no”]` is not used in the `<meta name=”viewport”>` element and the `[maximum-scale]` attribute is not less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page.
25. No element has a `[tabindex]` value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies.
26. Touch targets have sufficient size and spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets.
27. `<video>` elements contain a `<track>` element with `[kind=”captions”]`
When a video provides a caption it is easier for deaf and hearing impaired users to access its information.
You may send communications regarding the accessibility requirements (Article 10.2.a) of Royal Decree 1112/2018 of September 7, through the following mailbox.
For example:
Fill out the form below, and we will be in touch shortly.