Public accessibility assessment

Accessibility issues detected on lazareff.com

Evolize inspected 5 public pages on lazareff.com and detected 10 automatically identifiable accessibility findings.

10Findings detected
2WCAG criteria affected
5Pages inspected
19 Aug 2026Assessment date

Highest detected severity: Medium · 0 high-priority findings · 100% inspected-page coverage

Most widespread issueText has insufficient colour contrastDetected on 5 inspected pages
Most affected page/9 findings detected
Most represented WCAG criterionWCAG 1.4.3 — Contrast (Minimum)5 detected findings

Is lazareff.com your website?

Keep this assessment current and get notified when new accessibility issues are detected.

https://

Not your website? Scan your own site →

01 · Accessibility summary

Evolize inspected 5 public pages on lazareff.com and detected 10 accessibility findings. The most widespread issue was "Text has insufficient colour contrast", detected on 5 inspected pages. The most affected inspected page was "/", where 9 findings were detected. The assessment identified findings mapped to 2 WCAG success criterions. The sections below prioritize the broadest issues and provide technical evidence for each detected finding.

02 · Start here

These findings combine the highest severity and broadest reach detected during this assessment.

  1. Medium

    Touch targets are too small on mobile

    WCAG 2.5.8 (AA) · 5 inspected pages · 25 instances
    Why this matters

    Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

    Recommended action

    Increase the size of the touch target to at least 24x24 pixels to make it easier for users to activate by touch. Consider adding padding or increasing the font size of the interactive element.

    View technical evidence →
  2. Medium

    Text has insufficient colour contrast

    WCAG 1.4.3 (AA) · 5 inspected pages · 10 instances
    Why this matters

    Text and background colours do not meet the minimum contrast ratio, reducing legibility.

    Recommended action

    To fix this issue, increase the contrast between the text color and background color. You can do this by changing the CSS styles for the affected element, such as the span element with the aria-hidden attribute. Consider using a color contrast analyzer tool to determine the optimal colors. For example, you can change the background color or the text color to achieve a contrast ratio of at least 4.5:1 for normal text.

    View technical evidence →
  3. Medium

    Touch targets are too small on mobile

    WCAG 2.5.8 (AA) · 5 inspected pages · 5 instances
    Why this matters

    Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

    Recommended action

    Increase the size of the touch target to at least 24x24px to make it easier for users to activate by touch.

    View technical evidence →
  4. Medium

    Text has insufficient colour contrast

    WCAG 1.4.3 (AA) · 1 inspected page · 24 instances
    Why this matters

    Text and background colours do not meet the minimum contrast ratio, reducing legibility.

    Recommended action

    To improve readability, adjust the text color or background color of the element to meet the minimum contrast ratio thresholds as specified in WCAG 2.1 SC 1.4.3. Consider using a color contrast analyzer tool to determine suitable color combinations.

    View technical evidence →
  5. Medium

    Text has insufficient colour contrast

    WCAG 1.4.3 (AA) · 1 inspected page · 20 instances
    Why this matters

    Text and background colours do not meet the minimum contrast ratio, reducing legibility.

    Recommended action

    To improve readability, adjust the color of the text or background to meet the minimum contrast ratio of 4.5:1 for normal text. Consider using a color contrast analyzer tool to find a suitable combination.

    View technical evidence →

03 · WCAG criteria affected

CriterionNameLevelFindingsPagesReach
1.4.3Contrast (Minimum)AA555 / 5
2.5.8Target Size (Minimum)AA555 / 5

Absence of a criterion here does not indicate conformance with it — only that no automatically detectable issue was found for it.

Continuous monitoring

A scan shows today's exposure. Monitoring shows what changes next.

Evolize continuously reassesses public website pages, detects newly introduced or recurring accessibility findings, and tracks remediation over time.

04 · All detected findings

Medium

Text has insufficient colour contrast

WCAG 1.4.3 (AA)78 instances5 inspected pages

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Why it matters

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Recommended correction

To fix this issue, increase the contrast between the text color and background color. You can do this by changing the CSS styles for the affected element, such as the span element with the aria-hidden attribute. Consider using a color contrast analyzer tool to determine the optimal colors. For example, you can change the background color or the text color to achieve a contrast ratio of at least 4.5:1 for normal text.

View 78 affected elements
Component · Ref WJIY6W
Affected pagehttps://www.lazareff.com/websites/audio-addict-shop.html
Elementbutton > span[aria-hidden="true"]
Accessible name
Markup
<span aria-hidden="true">◐</span>
Affected pages/ /websites/audio-addict-shop.html /blog.html /ecrits.html /mentions-legales.html
Component · Ref KNBKN2
Affected pagehttps://www.lazareff.com/
Element.entry-card--album:nth-child(1) > .entry-card-topline > time[datetime="2005-09-26T00:00:00.000Z"]
Accessible namesept. 2005
Markup
<time datetime="2005-09-26T00:00:00.000Z">sept. 2005</time>
Component · Ref CEF7IJ
Affected pagehttps://www.lazareff.com/
Elementtime[datetime="2004-10-01T00:00:00.000Z"]
Accessible nameoct. 2004
Markup
<time datetime="2004-10-01T00:00:00.000Z">oct. 2004</time>
Component · Ref S4NXZN
Affected pagehttps://www.lazareff.com/
Element.entry-card--album:nth-child(2) > .entry-card-tags
Accessible nameconcert · Warner · James Blunt
Markup
<p class="entry-card-tags">concert · Warner · James Blunt</p>
Component · Ref PGALFR
Affected pagehttps://www.lazareff.com/
Element.entry-card--album:nth-child(1) > .entry-card-topline > span
Accessible nameDisque
Markup
<span>Disque</span>
Medium

Touch targets are too small on mobile

WCAG 2.5.8 (AA)36 instances5 inspected pages

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Why it matters

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Recommended correction

Increase the size of the touch target to at least 24x24px to make it easier for users to activate by touch.

View 36 affected elements
Component · Ref PWLZSO
Affected pagehttps://www.lazareff.com/blog.html
Elementhtml > body > div > footer > a
Accessible nameFlux RSS
Markup
<a href="/rss.xml">Flux RSS</a>
Affected pages/ /websites/audio-addict-shop.html /blog.html /ecrits.html /mentions-legales.html
Component · Ref UFOAIF
Affected pagehttps://www.lazareff.com/websites/audio-addict-shop.html
Elementhtml > body > div > header > nav > a:nth-of-type(1)
Accessible nameBlog
Markup
<a href="/blog.html">Blog</a>
Affected pages/ /websites/audio-addict-shop.html /blog.html /ecrits.html /mentions-legales.html
Component · Ref WL4KZ2
Affected pagehttps://www.lazareff.com/
Elementsection#blog > div:nth-of-type(1) > p > a
Accessible nameVoir la liste →
Markup
<a href="/blog.html">Voir la liste →</a>
Component · Ref P85WZ6
Affected pagehttps://www.lazareff.com/
Elementmain#main-content > section:nth-of-type(2) > div:nth-of-type(2) > a
Accessible nameLire le billet →
Markup
<a href="/blog/2013/06/13/lexception-culturelle-lunion-européenne-beurre-largent-beurre.html">Lire le billet →</a>
Component · Ref MP5UYH
Affected pagehttps://www.lazareff.com/mentions-legales.html
Elementmain#main-content > article > div > p:nth-of-type(2) > a:nth-of-type(2)
Accessible nameContrat Creative Commons
Markup
<a href="http://creativecommons.org/licenses/by-nc-nd/3.0/"><img src="http://i.creativecommons.org/l/by-nc-nd/3.0/88x31.png" alt="Contrat Creative Commons"></a>

05 · Most affected inspected pages

06 · About this assessment

Evolize inspects publicly accessible website pages using automated browser-based testing and deterministic accessibility rules. Automated testing can identify many reproducible technical issues but cannot determine complete WCAG or legal compliance.

  • Publicly accessible surfaces only — no credentials, private systems, or source-code access.
  • Findings apply to the pages and states successfully inspected; automated analysis may not detect every issue.
  • Results reflect the site at the scan date and may have changed since.

Evolize provides digital risk intelligence and does not provide legal advice, certify compliance, or guarantee that litigation will not occur. Methodology · Security · Example assessment

07 · Continuous monitoring

This public report captures one assessment. Evolize monitoring rescans the website, detects new and recurring findings, tracks changes over time and verifies corrections.

Is information in this report inaccurate or outdated? Request a correction or removal.