Accessibility Audit Summary

The following is a summary of the most recent accessibility audit performed on www.eleaseloop.com on June 24, 2025, using EqualWeb’s automated WCAG scanner. The audit benchmarked conformance against WCAG 2.1 AA guidelines and reviewed 23 distinct pages of the site.

Overall Compliance Metrics

• Accessibility score (no widget): 82.8 / 100
• Total errors detected: 109
• Pages scanned: 23
• Applicable standard: WCAG 2.1 AA
• Lawsuit risk level: Low

Summary of Non-Conformities by WCAG Success Criteria

🔴 1. Non-text Content – WCAG 2.1 SC 1.1.1 (Level A)

At least 24 failures were identified due to missing alt text or inaccessible <svg> elements lacking aria-label or meaningful labels. This includes:

• 22 failures involving inline SVG icons without accessible names or roles.
• Examples include selectors like: #app > div:nth-child(3) > div:nth-child(2) > span > svg
• Intercom elements also fail to provide a label for launcher icons, violating role="img" requirements.

🟠 2. Contrast Issues – WCAG 2.1 SC 1.4.3 / 1.4.6 / 1.4.11 (Level AA)

There are 41 documented contrast failures:

• Text placed over background images fails to meet the minimum 4.5:1 contrast ratio for body text, and 3:1 for large-scale text.
• Fails techniques G18 and G145 for contrast compliance.
• Affected elements include: #new_user_form, .desc blocks, and call-to-action links in the login and sign-up forms.

🟠 3. Missing Bypass Blocks – WCAG 2.1 SC 2.4.1 (Level A)

Five violations were found where no "skip to main content" or landmark navigation is implemented:

• None of the scanned pages contain a functional skip link.
• Fails technique G1, G123, and G124.

🟠 4. Iframes Missing Titles – WCAG 2.1 SC 2.4.1 / Technique H64 (Level A)

• Four iframe elements detected with missing or empty title attributes.
• Selectors include: html > body > div:nth-child(19) > iframe and iframe:nth-child(17).

🟠 5. Duplicate ID Attributes – WCAG 2.1 SC 4.1.1 (Level A)

• Failure of technique F77: Duplicate id="hs-script-loader" present on multiple DOM nodes.
• Impacts assistive technology navigation and violates DOM specification rules.

🟠 6. Role, Name, Value Accessibility – WCAG 2.1 SC 4.1.2 (Level A)

• 38 elements fail to provide programmatically determinable names or roles.
• Includes anchor tags with valid href but no link text: <a href="#"></a>, <a href="/users/auth/google"></a>
• Violates technique H91.

🟠 7. Heading Structure and Labeling – WCAG 2.1 SC 2.4.6 (Level AA)

• Footer and other sections lack <h1>-<h6> headings.
• Fails technique H69: Required to aid assistive tech navigation.

🟠 8. Form Field Accessibility – WCAG 2.1 SC 3.3.2 (Level A)

• 8 form fields are missing labels or aria-label attributes.
• Examples: First name, last name, password fields on #new_user_form.

Remediation Roadmap

The following detailed actions are required to bring www.eleaseloop.com into full compliance with WCAG 2.1 AA. Each issue references specific Success Criteria and techniques outlined by the W3C Web Content Accessibility Guidelines.
These actions will be implemented out by 31s of December 2027 with a new audit ran to validate full compliance.

1. Non-text Content – SC 1.1.1 (Level A)
   
   • Add meaningful alt text to all informative <img> elements.
   • Use alt="" and role="presentation" for decorative images.
   • Ensure inline <svg> icons include role="img" and accessible labels using aria-label or aria-labelledby.
   • Refactor Intercom launcher icons and similar UI components to include appropriate ARIA naming.
2. Color Contrast – SC 1.4.3 / 1.4.6 / 1.4.11 (Level AA)
   
   • Identify all text elements placed over images or background gradients.
   • Adjust foreground/background colors to ensure:
     • Minimum 4.5:1 contrast for body text (G18)
     • Minimum 3:1 for large-scale text (G145)
   • Prioritize fixing contrast in areas like .desc blocks, form buttons, and login/sign-up links.
3. Bypass Blocks – SC 2.4.1 (Level A)
   
   • Implement a skip to content link at the top of every page.
   • Ensure the skip link targets a <main id="main-content"> region and is visible on focus.
   • Verify compliance with techniques G1, G123, and G124 to aid keyboard users.
4. Iframes Missing Titles – SC 2.4.1 (Level A), H64
   
   • Add descriptive title attributes to all <iframe> elements.
   • Title should clearly convey purpose (e.g., "Location map", "Chat interface").
5. Duplicate ID Attributes – SC 4.1.1 (Level A), F77
   
   • Eliminate duplicated id="hs-script-loader" or dynamically generate unique IDs where necessary.
   • Use classes or data attributes instead of IDs for styling or JS targeting when repeatable elements are required.
6. Role, Name, Value – SC 4.1.2 (Level A), H91
   
   • Ensure all <a> elements include visible text, aria-label, or accessible content.
   • Remove or fix empty links like <a href="#"></a> to provide semantic purpose.
   • Refactor social and OAuth links (e.g., Google login) to be screen-reader compatible.
7. Heading Structure and Labeling – SC 2.4.6 (Level AA), H69
   
   • Ensure all page sections (header, footer, sidebars) begin with appropriate <h2>-<h4> tags.
   • Use headings to establish logical document structure. Avoid skipping levels (e.g., from <h1> to <h4>).
8. Form Field Accessibility – SC 3.3.2 (Level A), H44 / H65
   
   • Add visible <label for="..."> elements to all input fields.
   • Ensure form fields like #user_first_name, #user_last_name, and #user_password are explicitly labeled.
   • Avoid using placeholders as the sole means of conveying field purpose.

All remediations should be validated through a combination of automated tools (e.g., axe-core, Lighthouse) and manual testing with assistive technologies (e.g., NVDA, VoiceOver). Compliance should be reviewed periodically as part of ongoing digital accessibility maintenance.

This report was generated using automated WCAG scanning tools. Additional manual testing (keyboard navigation, screen reader flow, cognitive accessibility) is recommended to ensure full conformance with the European Accessibility Act (EEA) and WCAG 2.1 AA.