Archives des Guide - Aksé

Digital accessibility: best practices and challenges to know in 2025

admin8818 — Thu, 23 Oct 2025 15:40:58 +0000

Digital accessibility: best practices and challenges to know in 2025

With the new digital accessibility law coming into effect on June 28, 2025, digital accessibility is taking center stage in the development and design of websites, SaaS, and mobile applications. As the majority of services become digital, it’s vital to ensure they are accessible to all, particularly people with disabilities. Today, we explore the fundamental principles of digital accessibility, the challenges surrounding it, and best practices for creating an inclusive digital environment.

What is digital accessibility, and why is it important?

Defining digital accessibility

Digital accessibility is about making digital content and services accessible to all users, including those with disabilities. This includes people with hearing, visual, cognitive, or motor impairments. Simply put, web accessibility aims to ensure that everyone can access information, interact with online services, and enjoy a satisfying user experience, regardless of their physical or cognitive abilities. With an aging population, it’s increasingly important to develop accessible platforms and services that enable individuals to stay connected despite experiencing cognitive and visual declines.

Accessibility challenges for users everywhere

Today, digital accessibility issues affect both social inclusion and legal compliance. it’s also a major issue in corporate CSR policies. Digital accessibility means information and services are easy to use and understand, regardless of the user’s physical or cognitive abilities. Overall, it contributes to a better user experience and helps avoid the frustration often felt by those who encounter obstacles in their user journeys.

Impact on people with disabilities

For people with disabilities, digital accessibility is much more than just an advantage; it’s a fundamental right. As we mentioned at the beginning of this article, the law on digital accessibility is becoming increasingly strict and now applies to many private companies with a turnover of more than €2 million. By making websites accessible, we enable these individuals to participate fully in society and access education, government services, employment opportunities, and financial services. Indeed, a lack of accessibility can exacerbate social exclusion and limit the life choices of people with disabilities, which highlights the crucial importance of developing websites, software, and applications that comply with accessibility standards.

How can websites be made compliant with accessibility standards?

Guidelines and standards: WCAG and RGAA

To ensure that websites comply with accessibility requirements, several guidelines and standards are in place, including the Web Content Accessibility Guidelines (WCAG) and the Référentiel général d’amélioration de l’accessibilité (RGAA) in France. These guidelines emphasize the importance of creating resources that are perceivable, navigable, and understandable for all users, including those with disabilities. The first step in complying with the law is to conduct a comprehensive audit of your website, SaaS, or application and obtain your accessibility score. You must then publish it along with your multi-year plan, which demonstrates your commitment to making your platforms 100% accessible in the coming years.

Steps to creating an accessible website

If you are starting from scratch, it’s best to seek assistance from our professionals trained in digital accessibility. Accessible web development requires strict adherence to the 50 criteria of the WCAG (A and AA). This may seem more complicated or expensive, but it actually saves time and money. The trend is clear: while accessibility legislation used to apply only to public bodies and companies with annual revenues exceeding €250 million in France, it now applies to companies with annual revenues exceeding €2 million across a wide range of industries in France. Hiring professionals who are rigorously trained in accessible web development is essential if you are launching a new website or SaaS in the coming months. Our services range from project management assistance to the complete development of your website or SaaS. Feel free to contact us!

Tools for assessing website accessibility

There are various tools available for assessing website accessibility. Automated solutions, such as accessibility validators, can help easily identify non-compliance with WCAG standards. However, these tools are no substitute for a comprehensive audit carried out by accessibility experts. They are often a first step in identifying the extent of the problems, but they are never sufficient when it comes to issuing an official rating or identifying specific solutions. To ensure compliance, an audit carried out by trained and experienced professionals is essential. Once the audit based on the 50 WCAG criteria is completed, you will receive your accessibility score and the official declaration.

What are the best practices for improving the accessibility of your digital resources?

Design principles for optimal accessibility

Developers should also pay attention to site navigation, ensuring that it’s intuitive and easy to use for all users, especially those using a keyboard. By incorporating accessible elements such as alternative descriptions for images and descriptions for tables, you not only improve accessibility for people with disabilities but also the overall user experience and the site’s search engine optimization (SEO).

Accessibility of PDF documents and other formats

PDF documents and other file formats must also be accessible. To achieve this, it’s important to ensure that they comply with accessibility guidelines, such as those outlined in the WCAG or RGAA. This includes appropriate tags, clear titles, and a logical structure, allowing screen readers to navigate the content effectively. By making these formats accessible, we ensure that essential information is available to everyone, including people with disabilities.

Examples of best practices in creating accessible content

Best practices for creating accessible content include using clear, simple language, descriptive titles, and relevant links. For example, instead of using ambiguous phrases such as “click here,” it’s better to use anchor text that clearly describes the link’s destination. Additionally, creating subtitled videos and integrating audio descriptions can significantly enhance the accessibility of digital resources, making content more inclusive for all users.

Digital accessibility challenges in 2025

Technological developments and accessibility

As technologies evolve, new challenges in digital accessibility are emerging. In 2025, the integration of artificial intelligence, virtual reality, and other technological innovations could raise complex questions about accessibility. Developers and project leaders must anticipate these developments and ensure that these new technologies are designed to be inclusive.

Compliance with accessibility legislation

Compliance with accessibility legislation is another major issue. The law of February 11, 2005, stipulates that public services must be accessible to all. A European directive, specifically 2019/882, is changing the situation by making digital accessibility compliance mandatory for many companies with more than 10 employees and a turnover of over €2 million in France. This directive was transposed into French law on March 7, 2023, and will be applicable on June 28, 2025. There are an increasing number of regulatory bodies, such as Arcom and the AMF, and penalties have also increased.

Training and awareness for developers and designers

To overcome accessibility challenges, training and awareness are essential for developers, designers, and web project managers. By 2025, it will be crucial for these professionals to understand accessibility principles and be trained to integrate these standards into their daily work. At Aksé, we can support you in developing your skills and take the lead in your mission to become fully compliant.

How to conduct an accessibility audit for your website?

Accessibility audit methodology

An accessibility audit is a key step in assessing a website’s compliance. It begins with an in-depth analysis of the site’s elements, checking each aspect against WCAG and RGAA standards. The goal is to provide a comprehensive overview of the site’s accessibility and identify areas for improvement. Most importantly, you will receive a score that declares whether you are accessible, partially accessible, or not accessible. To be fully compliant with the law, you must publish your official digital accessibility statement and have a multi-year improvement plan in place to achieve 100% accessibility in the near future.

Tools and resources for conducting a WCAG audit

Several tools and resources are available to conduct an accessibility audit. Automated tools such as Axe, WAVE, or Lighthouse can quickly identify accessibility issues. However, it’s important to combine these assessments with manual testing for a more in-depth analysis. At Aksé, we utilize our own guides and checklists to enhance the accuracy and quality of our recommendations.

Interpreting the results of an accessibility audit

Interpreting the results of an accessibility audit requires an understanding of accessibility standards and expectations. By entrusting the Aksé team with your audit, you will receive a clear and comprehensive report detailing the identified issues and recommended solutions. We recommend addressing critical issues first, followed by less urgent items. Once the changes have been made, we can assist you in conducting follow-up tests to ensure that the changes have effectively improved the site’s accessibility.

Book
a discovery call

Assess the extent of your digital accessibility, development, or branding needs

Get concrete ideas for areas of improvement

Benefit from our expert advice, in-depth experience, and strategic vision in the field

Free • 45 minutes • Online

L’article Digital accessibility: best practices and challenges to know in 2025 est apparu en premier sur Aksé.

Creating accessible links: the complete guide

admin8818 — Thu, 23 Oct 2025 15:34:11 +0000

Creating accessible links: the complete guide

Why accessible links are essential

Links are at the heart of web navigation. For many users, they represent the gateway to new content or a new action. When poorly designed, they can create major obstacles. Here are a few examples, depending on the type of disability or technical context:

For blind or visually impaired people: screen readers offer a feature that lists only the links on a page. If these are not explicit, the user is faced with a succession of “click here” or “learn more” links, without knowing where they lead.
For people with reduced mobility: a clickable area that is too small or a link that is too close to another makes it challenging to use a keyboard or alternative pointing devices.
For people with cognitive impairments: ambiguous or unclear wording can cause confusion and discourage navigation.
In certain technical contexts: a poorly identified link can cause indexing or referencing problems.

In short, an accessible link is better for the overall performance of the site, its referencing, and, of course, for the inclusion of all your visitors.

Best practices to follow

1. Provide an explicit link title

A link should have a label that clearly describes its destination or action. Avoid vague phrases such as “click here” or “learn more.”

Bad example:

Pour plus d’informations, cliquez ici.

For more information, click here.

Good example:

Découvrez le détail de notre offre de formation en accessibilité.

Find out more about our accessibility training program.

This ensures the link is understandable even when read out of context by a screen reader.

However, it is possible to keep generic visual labels. This is often the case, for example, with blog article titles or product descriptions. We often see “read more” or “see more” as the visible link title. It is indeed complicated (and a little tedious) to visually customize all these links. In this case, we add an aria-label that repeats the visible title and adds context. E.g.: aria-label=“read the rest of the article on accessibility.”

2. Avoid unnecessary repetition

If several links lead to the same page, they should ideally have the same title. Conversely, if the destinations are different, the titles must be distinct.

Good example:

Be careful with titles such as “Learn More” or “Discover.” They are far too generic.

3. Make links visually identifiable

The WCAG and RGAA stipulate that colour alone should not be used to identify a link. A simple colour change is not sufficient for people who are colour blind or have reduced contrast, for example.

If the link is not obvious, i.e., highlighted, then it must be a colour that contrasts sufficiently with the rest of the text and its background. These contrasts must be at least 3:1. In addition, another indicator other than colour must be present when hovering over and focusing on the link (e.g., bold text).

4. Ensure keyboard accessibility

A link must be accessible with the Tab key, and its focus state must be visible. This means that it must have a clear outline or be highlighted when focused with the keyboard.

Example of accessible CSS style:

a:focus {
outline: 3px solid #005fcc;
outline-offset: 2px;
}

5. Use sufficiently large clickable areas

Links must be large enough to be easily activated, including by users with motor difficulties. WCAG 2.5.8 recommends a clickable area of at least 24 x 24 pixels. Although this is an AAA criterion, it should be respected as much as possible.

Therefore, an icon used as a link must have appropriate padding or margins to provide a sufficiently large clickable area.

6. Clearly differentiate between links and buttons

A link should lead to a new page or resource. A button should trigger an action on the current page (send a form, open a menu, trigger a script). This semantic distinction helps screen reader users understand the role of each element. Bad example: Open menu Ouvrir le menu Here, the user expects to be redirected to a new page, but the element triggers an action on the current page. For a screen reader, this is perceived as a link, which is misleading. Good example: View catalog Voir le catalogue In this case, the link serves its purpose: it directs the user to another page. If the expected action is to open a menu or submit a form, use a

7. Handling images and icons embedded in links

If a link is represented solely by an image, the image’s alt text must describe the destination of the link. Example: For a decorative SVG icon accompanied by text, it is preferable to hide the icon with aria-hidden=“true” and add a text alternative to the link containing the image that describes the nature of the proposed action. Example:

8. Take specific display modes into account

As with colours, links must remain visible and usable in different modes:

High contrast: check that links remain distinguishable, even when your colours are replaced by those of the system.
Dark mode: ensure that the colour of the links maintains sufficient contrast with the background.
Off-context reading: test your links in a screen reader’s list of links.

Your checklist for truly accessible links

Only use “click here,” “more,” “>>,” or “learn more” as labels.
Make sure you don’t remove underlining from links without providing an alternative visual indicator.
Ensure links aren’t too close together or too small, as this can make them difficult to click.
Use links to trigger actions that buttons should perform.
Don’t forget to manage keyboard focus status.

Conclusion

An accessible link must be understandable, identifiable, and usable by everyone. This means choosing explicit wording, ensuring sufficient contrast, making the link visible to the keyboard, and respecting the distinction between links and buttons.

These simple rules can have a profound impact on the user experience. For a blind person using a screen reader, switching from a list of “click here” to a list of clear and explicit links makes navigation infinitely smoother. For a visually impaired person, a link with enhanced contrast and a visible focus is a guarantee of comfort.

By following these principles, you make your content accessible, compliant with international standards, and more enjoyable for all users. And last but not least, you ensure your links are SEO-optimized, which is always a good thing!

Book
a discovery call

Assess the extent of your digital accessibility, development, or branding needs

Get concrete ideas for areas of improvement

Benefit from our expert advice, in-depth experience, and strategic vision in the field

Free • 45 minutes • Online

L’article Creating accessible links: the complete guide est apparu en premier sur Aksé.

Accessible Images: The Complete Guide

admin8818 — Thu, 23 Oct 2025 15:32:14 +0000

Accessible Images: The Complete Guide

Why accessible images are a major issue

Images play a wide variety of roles on the web. They can illustrate a point, convey information, guide navigation, or enhance the attractiveness of an interface. For people who use screen readers, such as those who are blind or visually impaired, an image only exists if a text equivalent accompanies it. Without this, the voice assistant will simply announce “image” or read the file URL, which does not convey any useful information.

People who are color blind also encounter difficulties when an image relies solely on colours to deliver a message. Finally, some people with cognitive impairments benefit from clear descriptions, which make it easier for them to understand the role of the image.

Ensuring the accessibility of images enables everyone to receive the same information, and it is also a legal requirement. The WCAG (1.1.1, 1.4.5, 1.4.3) and RGAA (criteria 1.1 to 1.9) standards require that all important non-text content have an understandable alternative.

When and how to describe an image

The first question to ask is: Does the image provide the user with helpful information?

If the image is informative (such as a photo, graphic, or icon that conveys an action), it must have a relevant text alternative.
If the image is decorative (a purely visual icon, a graphic motif), it should be ignored by assistive technologies.
If the image is complex (such as a detailed diagram, infographic, or data chart), a brief summary is necessary, accompanied by a detailed description or equivalent data.
Finally, if the image contains text, it must be replaced by real HTML text, except in exceptional cases such as logos.

Here is an example of content containing decorative images:

Here, the images next to the words tomatoes, olive oil, and basil do not provide any additional information. They should therefore be ignored by assistive technologies to avoid redundancy in the reading of information for visually impaired users.

Best practices in HTML

1- Provide relevant alternative text

For an informative image, the alt attribute remains the most robust method. This text should be short and precise, describing the essentials.

The title attribute does not replace the alt attribute: it is unreliable because screen readers often ignore it.

2- Hide decorative images

A screen reader should not read a decorative image. To do this, use an empty alt attribute (alt=“”). It is also possible to add aria-hidden=“true” to reinforce the hiding.

You will have either:

Or:
or

It is important not to use alt=“” with a space, as this practice is incorrect.

3- Precision for clickable images

If an image is the only content of a link or button, the alternative text must describe the destination or action. However, if the image is accompanied by text in the same link, the image must be hidden to avoid redundancy.

Special case: SVGs

SVGs are being used increasingly to represent icons or graphics. Their accessibility depends on the context.

A decorative SVG, such as an arrow next to a button, should be excluded from the accessibility tree:

An informative SVG, such as a diagram or functional pictogram, must have a name accessible via a tag and possibly a <desc> tag. <svg role=”img” aria-labelledby=“t1 d1”> <title id=”t1″>Sales distribution by region
Île-de-France 40%, PACA 30%, AuRA 20%, others 10%.

The choice between masking and description, therefore, depends on the role of the image.

Complex images

A graph or map cannot be summarized solely in an alt attribute. This attribute must contain a summary of the key message, for example, “Sales are up 20% in 2024.” A more detailed description must then be provided in the page text or in an associated section (such as a

or data table).

The special case of maps

Maps are a prime example of complex images, since they combine geographical, topographical, and sometimes interactive information. A simple text description cannot always convey all of this rich information, but it is necessary to provide at least the essential elements.

Informative map: if the map contains useful data (e.g., election results by region or the areas covered by a service), a textual alternative must describe this information. Ideally, the image should be accompanied by a table displaying regional data or a text list enumerating the affected areas.

In the example below, filling in the Alt tag is not enough. For example, a longdesc attribute must be added, providing the URL of a page with a detailed text description. There could also be a link or button next to the image that leads to the detailed description.

Interactive map (Google Maps, floor plan, route map): the map must be ignored by assistive technologies (attribute aria-hidden=true) and a text alternative must be provided with the same level of information. For an itinerary, this means providing a text version of the directions (“Turn left onto Rue de la République, continue for 300 m, then…”); for a floor plan, a list of locations and corresponding access points must be provided.

In other words, the richer the map, the more detailed the alternative must be. The user must be able to obtain, without seeing the map, either the main message or all the data it contains, depending on the context.

Text images

The WCAG and RGAA standards prohibit the use of images containing text, except when there is no other option (e.g., for a logo). Real text, formatted with CSS, should always be preferred.

Bad practice

Good practice

When a text image cannot be replaced, it must at least comply with contrast ratios (4.5:1 for normal text and 3:1 for large text).

Here is a list of exceptions that are not affected by this ban on image text:

The text is part of a logo or brand name of an organization or company;
The text or text image is purely decorative;
The text is part of an image conveying information, but the text itself does not provide any essential information;
The text or text image is part of an interface element on which no action is possible (e.g., a button with the disabled attribute).

What to avoid at all costs

aria-label=“hidden” is not a valid value. To hide an image, aria-hidden=“true” is the correct method.
Avoid vague alt text, such as “image” or “graphic,” which conveys no useful information.
Don’t leave an empty alt text by mistake on an informative image.
Assigning a presentation role (role=“presentation”) to an interactive or focusable element will be ignored.

Conclusion

Image accessibility is based on a simple rule: each image must be treated appropriately according to its purpose or role. If it provides information, it must be described. If it is decorative, it must be hidden. If it is complex, it must be accompanied by a detailed description. And if it contains text, this text must be provided in real HTML text.

By applying these best practices, all users, regardless of their disability, can access the same information. This approach enhances the user experience for all users and meets the requirements imposed by the RGAA and WCAG.

Book
a discovery call

Assess the extent of your digital accessibility, development, or branding needs

Get concrete ideas for areas of improvement

Benefit from our expert advice, in-depth experience, and strategic vision in the field

Free • 45 minutes • Online

L’article Accessible Images: The Complete Guide est apparu en premier sur Aksé.

Accessible colour palettes: the complete guide

admin8818 — Thu, 23 Oct 2025 15:28:56 +0000

Accessible colour palettes: the complete guide

Why colour accessibility is crucial

Colour is one of the most widely used tools in web design: it attracts attention, signals action, prioritizes information, and conveys emotion. But relying solely on colour can create significant obstacles for some users.

People with colour blindness: approximately 8% of men and 0.5% of women are affected by some form of colour blindness. For them, certain combinations (such as red/green and blue/purple) become indistinguishable.
Visually impaired people: poor contrast perception makes reading difficult, especially if the text is light on a light background or dark on a dark background.
Mobile users: high brightness on a screen can reduce colour readability, even for people without visual impairments.
Elderly people: sensitivity to contrast decreases with age, making reading on screen even more difficult.

Ensuring good colour accessibility is not just about complying with the law. More importantly, it is about enabling everyone to use and understand content without ambiguity.

This is why the WCAG imposes two major rules:

Criterion 1.4.1 “Use of colour”: colour should never be the only means of conveying information.

Criteria 1.4.3 and 1.4.11 “Contrast”: there must be sufficient contrast between the text and its background.

The RGAA incorporates these obligations in its criteria 3.1, 3.2, and 3.3.

Best practices to follow

1. Never convey information solely through colour

Let’s take a typical example: a form where required fields are marked in red. For someone who is colour blind, this difference may be imperceptible.

Email (required)

Here, the word “required” is written in full, and the aria-required=“true” attribute allows assistive technologies to announce the information correctly.

Other common cases to correct:

Links differentiated only by colour: it is advisable to add underlining or an additional visual effect.
Colour-coded tables: provide a text legend, or use distinctive patterns/shapes.
Active state or error of a button: combine colour with a pictogram or text message.

2. Ensure sufficient contrast for text

The WCAG (criterion 1.4.3) imposes minimum contrast ratios:

Normal text (< 24px or 18,5px bold): 4.5:1.
Large text (≥ 24px or 18,5px bold): 3:1.

These ratios ensure that text remains legible for the majority of users, including those with low vision.

Correct example: black text (#000000) on a white background (#FFFFFF) → contrast 21:1.

Incorrect example: light gray text (#999999) on a white background (#FFFFFF) → contrast 2.5:1.

Tools such as WebAIM’s Contrast Checker or the “Colour Contrast Analyzer” extension allow you to test combinations quickly.

3. Ensure sufficient contrast for interactive elements

Interactive elements, such as buttons, form fields, or interactive pictograms, must also have sufficient contrast with their background.

WCAG and RGAA require a contrast of at least 3:1 between the interactive element and its background.

See the example below, which features a blue-outlined form field on a grey background. The top one has sufficient contrast, with the blue colour (#0051FF) on the gray background (#EDEBEB). The bottom one is insufficient, as the blue (#AEC7FF) is too light compared to the grey background.

4. Check the accessibility of interactive states

Links and buttons must remain identifiable at all stages: normal state, hover, keyboard focus, and click (active). Other visual cues, such as underlining or border thickness, must reinforce colour changes. The contrast of these interactive elements must meet a minimum ratio of 3:1, regardless of their state.

5. Ensure readability in different display modes

Not all users see your site under the same conditions. Some activate specific display modes, which can completely transform the colours of an interface.

High contrast mode (Windows, Linux, browser extensions)

In this mode, the colours defined by CSS can be replaced by those chosen by the user. The background can be set to black and the text white, or vice versa. Background images, gradients, and drop shadows are often disabled. Consequence: if the text relies on a background image to be readable, it will disappear. If an icon is only displayed in light colours on a light background, it may be invisible.

Dark mode or custom themes (dark mode/high contrast custom)

More and more systems (iOS, Android, macOS, Windows) and browsers offer a “dark mode.” If your site is not designed to handle these switches, dark text may become unreadable on a dark background.

User colour customization

Some visually impaired users set their own colour combinations (e.g., yellow text on a black background). This means that your default styles must be flexible enough to adapt. Best practices:

Avoid using background images or gradients to convey essential information.
Check that icons and buttons remain visible when the background changes (use borders, symbols, or high contrast).
Ensure that the interface remains functional even when the system contrast is enabled. For example, test the page with Windows high contrast mode.
Use CSS media queries (prefers-contrast, prefers-colour-scheme) to offer a version adapted for dark mode or high contrast. Example:

@media (prefers-colour-scheme: dark) { body { background: #000; colour: #fff; } }

Common mistakes

Using colour alone to indicate an error in a form.
Choosing “trendy” palettes without checking the contrasts. Styles change, but the constraints remain the same.
Forgetting to test icons and pictograms: a yellow icon on a white background may be invisible to many users.
Removing underlining from links without adding another visual indicator.

Colours and contrasts are essential elements of digital accessibility. They ensure that content remains readable and understandable, regardless of the user’s visual impairment, lighting environment, or age.

To design an accessible website or application, there are three simple principles to remember: never rely solely on colour, ensure sufficient contrast for all text and interactive elements, and test interfaces in different display contexts.

Doing this work upfront prevents many problems and provides all users with a clear, enjoyable, and equitable browsing experience.

Book
a discovery call

Assess the extent of your digital accessibility, development, or branding needs

Get concrete ideas for areas of improvement

Benefit from our expert advice, in-depth experience, and strategic vision in the field

Free • 45 minutes • Online

L’article Accessible colour palettes: the complete guide est apparu en premier sur Aksé.

Archives des Guide - Aksé

Digital accessibility: best practices and challenges to know in 2025

Digital accessibility: best practices and challenges to know in 2025

What is digital accessibility, and why is it important?

Defining digital accessibility

Accessibility challenges for users everywhere

Impact on people with disabilities

How can websites be made compliant with accessibility standards?

Guidelines and standards: WCAG and RGAA

Steps to creating an accessible website

Tools for assessing website accessibility

What are the best practices for improving the accessibility of your digital resources?

Design principles for optimal accessibility

Accessibility of PDF documents and other formats

Examples of best practices in creating accessible content

Digital accessibility challenges in 2025

Technological developments and accessibility

Compliance with accessibility legislation

Training and awareness for developers and designers

How to conduct an accessibility audit for your website?

Accessibility audit methodology

Tools and resources for conducting a WCAG audit

Interpreting the results of an accessibility audit

Book a discovery call

Creating accessible links: the complete guide

Creating accessible links: the complete guide

Why accessible links are essential

Best practices to follow

1. Provide an explicit link title

2. Avoid unnecessary repetition

3. Make links visually identifiable

4. Ensure keyboard accessibility

5. Use sufficiently large clickable areas

6. Clearly differentiate between links and buttons

7. Handling images and icons embedded in links

8. Take specific display modes into account

Your checklist for truly accessible links

Conclusion

Book a discovery call

Accessible Images: The Complete Guide

Accessible Images: The Complete Guide

Why accessible images are a major issue

When and how to describe an image

Best practices in HTML

1- Provide relevant alternative text

2- Hide decorative images

3- Precision for clickable images

Special case: SVGs

Complex images

The special case of maps

Text images

50% off this weekend

What to avoid at all costs

Conclusion

Book a discovery call

Accessible colour palettes: the complete guide

Accessible colour palettes: the complete guide

Why colour accessibility is crucial

Best practices to follow

1. Never convey information solely through colour

2. Ensure sufficient contrast for text

3. Ensure sufficient contrast for interactive elements

4. Check the accessibility of interactive states

5. Ensure readability in different display modes

Common mistakes

Book a discovery call

Book
a discovery call

Book
a discovery call

Book
a discovery call

Book
a discovery call