Accessibility refers to the inclusive measures done on websites to make it possible for everyone to enjoy the web. ONE BILLION PEOPLE (or 15% of the world population) suffers from some disability (source: https://www.worldbank.org/en/topic/disability) so the problem is highly significant to all websites. It is not only the right thing to do, but also a lost monetary opportunity to not take measures for high accessibility.
At Leadoo we believe everyone should have the same possibility to enjoy the web. Interactive bot elements, such as the InpageBot are a great way to enhance accessibility to relevant information on your website.
But more importantly, accessibility is about technical implementations that help screen readers read the page, people navigate with a keyboard instead of a mouse and people with colorblindness see the information.
Leadoo’s bots and other technologies have the following improvements to remove barriers thus complying with WCAG and WAI-ARIA (where applicable):
ARIA labels and roles for UI components – imperative for screen readers and web browsers to ensure keyboard navigation
Base themes adjusted for color contrast – Color contrast or WCAG is a mathematically easy thing to check. Leadoo’s basic themes have been improved for better contrast but more importantly, you can create your own themes and ensure every page and every bot uses the theme you choose.
Keyboard-accessible UI components – we’ve added keyboard shortcuts for multi-line inputs and chat inputs and we’ve ensured and enhanced to calendar widget to be keyboard accessible.
Image alts for non-visual description – all images include alt tags that help screen readers know what the image is about. E.g. closing down a chatbot.
ARIA-live areas for constantly updating information (livechat, bot flow)
Hover/focus states for UI inputs, buttons and links – we’ve also disabled state on not-yet-ready components that are still in the DOM tree
Input placeholders for example content
Input labels with “required” status indicators
And probably many more that already worked out of the box. We’ve also used external parties to test our different bot solutions and are working closely with our larger customers with their own accessibility experts to ensure Leadoo works on the specific technologies they use.
Accessibility is not a one-time thing – technology evolves and so do needs and what is possible to do. At Leadoo we feel everyone should have the same chances to enjoy the web and we are committed to improving accessibility in our technologies.
Evaluation of Leadoo’s Visual Bot
About the Evaluation
Report CreatorIn-house evaluation.Evaluation CommissionerLeadoo Tech LeadEvaluation dateTue May 07 2024
Executive Summary
While Leadoo’s visual bot is not a web page per se, it helps users on the website find relevant information faster. At the same time it complies to standards, implements assistive attributes and does not include bloated DOM structures of heavy JavaScript usage – which results in compliant accessibility for its part and possibly even enhancing the accessibility of the overall site.
Scope of the Evaluation
Website nameLeadoo Visual BotScope of the websiteThe Leadoo Visual Bot’s webcontent. Used https://bot.leadoo.com/bot/visual.html?code=58901085 as an example.WCAG Version2.1Conformance targetAAAccessibility support baselineEvergreen browsers as of May 2024.Additional evaluation requirementsNot provided
Detailed Audit Results
Summary
Reported on 50 of 50 WCAG 2.1 AA Success Criteria.
33 Passed
0 Failed
8 Cannot tell
9 Not present
0 Not checked
All Results
1 Perceivable
1.1 Text Alternatives
Success Criterion
Result
Observations
1.1.1: Non-text Content
Entire sampleResult: Passed
Entire sampleObservations:All visual elements have a text associated with them.
1.2 Time-based Media
Success Criterion
Result
Observations
1.2.1: Audio-only and Video-only (Prerecorded)
Entire sampleResult: Passed
Entire sampleObservations:In Leadoo Visual Bots it is possible to add text together with video & audio to describe the content. However, captions etc have to be created by the author of the video/audio (see next point).
1.2.2: Captions (Prerecorded)
Entire sampleResult: Cannot tell
Entire sampleObservations:Up to the creator of the video/audio.
1.2.3: Audio Description or Media Alternative (Prerecorded)
Entire sampleResult: Cannot tell
Entire sampleObservations:Possible in Leadoo, but up to the creator of the bot & media.
1.2.4: Captions (Live)
Entire sampleResult: Cannot tell
Entire sampleObservations:Up to the creator of the media.
1.2.5: Audio Description (Prerecorded)
Entire sampleResult: Cannot tell
Entire sampleObservations:Up to the creator of the media.
1.3 Adaptable
Success Criterion
Result
Observations
1.3.1: Info and Relationships
Entire sampleResult: Passed
Entire sampleObservations:Both true visually as well as technically in the DOM tree.
1.3.2: Meaningful Sequence
Entire sampleResult: Passed
Entire sampleObservations:Tested with screenreader & tabbing order.
1.3.3: Sensory Characteristics
Entire sampleResult: Passed
1.3.4: Orientation
Entire sampleResult: Passed
1.3.5: Identify Input Purpose
Entire sampleResult: Passed
Entire sampleObservations:Leadoo has predefined input types which maximizes the possibility of compliance in meaningful input types.
1.4 Distinguishable
Success Criterion
Result
Observations
1.4.1: Use of Color
Entire sampleResult: Passed
Entire sampleObservations:Text is the primary way to convey information.
1.4.2: Audio Control
Entire sampleResult: Not present
1.4.3: Contrast (Minimum)
Entire sampleResult: Cannot tell
Entire sampleObservations:The use of themes in bot solutions ensures that custom non-compliant solutions aren’t used. But this is up to the customer’s own theme and color palette. If this color palette has for instance low contrast then technically it can be used in Leadoo’s case as well.
1.4.4: Resize text
Entire sampleResult: Passed
Entire sampleObservations:Using the browser’s native zoom works.
1.4.5: Images of Text
Entire sampleResult: Passed
Entire sampleObservations:Text is the primary way to convey information and the only meaningful reason for using Leadoo Visual Bots.
1.4.10: Reflow
Entire sampleResult: Passed
1.4.11: Non-text Contrast
Entire sampleResult: Cannot tell
Entire sampleObservations:By default yes, but can be changed by the customer according to their visual theme.
1.4.12: Text Spacing
Entire sampleResult: Passed
1.4.13: Content on Hover or Focus
Entire sampleResult: Passed
2 Operable
2.1 Keyboard Accessible
Success Criterion
Result
Observations
2.1.1: Keyboard
Entire sampleResult: Passed
2.1.2: No Keyboard Trap
Entire sampleResult: Passed
2.1.4: Character Key Shortcuts
Entire sampleResult: Not present
2.2 Enough Time
Success Criterion
Result
Observations
2.2.1: Timing Adjustable
Entire sampleResult: Not present
2.2.2: Pause, Stop, Hide
Entire sampleResult: Not present
2.3 Seizures and Physical Reactions
Success Criterion
Result
Observations
2.3.1: Three Flashes or Below Threshold
Entire sampleResult: Passed
2.4 Navigable
Success Criterion
Result
Observations
2.4.1: Bypass Blocks
Entire sampleResult: Not present
2.4.2: Page Titled
Entire sampleResult: Not present
Entire sampleObservations:The website that Leadoo Visual Bots are added to need to comply with page title requirements.
2.4.3: Focus Order
Entire sampleResult: Passed
Entire sampleObservations:Leadoo bots can be navigated sequentially alone and as a part of a website.
2.4.4: Link Purpose (In Context)
Entire sampleResult: Cannot tell
Entire sampleObservations:Implementation issue. Technologically Leadoo Visual Bots support this.
2.4.5: Multiple Ways
Entire sampleResult: Not present
Entire sampleObservations:No applicable for Leadoo bots.
2.4.6: Headings and Labels
Entire sampleResult: Passed
2.4.7: Focus Visible
Entire sampleResult: Passed
2.5 Input Modalities
Success Criterion
Result
Observations
2.5.1: Pointer Gestures
Entire sampleResult: Passed
2.5.2: Pointer Cancellation
Entire sampleResult: Passed
2.5.3: Label in Name
Entire sampleResult: Passed
Entire sampleObservations:By default this is the primary use-case of Leadoo’s Visual bots.
2.5.4: Motion Actuation
Entire sampleResult: Not present
3 Understandable
3.1 Readable
Success Criterion
Result
Observations
3.1.1: Language of Page
Entire sampleResult: Passed
Entire sampleObservations:Html lang defined in bots.
3.1.2: Language of Parts
Entire sampleResult: Passed
3.2 Predictable
Success Criterion
Result
Observations
3.2.1: On Focus
Entire sampleResult: Passed
3.2.2: On Input
Entire sampleResult: Passed
Entire sampleObservations:By nature Leadoo’s Visual Bots consist of buttons that navigate within a sub context to the next desired logical state.
3.2.3: Consistent Navigation
Entire sampleResult: Cannot tell
Entire sampleObservations:Leadoo is not a webpage but a subset of it.
3.2.4: Consistent Identification
Entire sampleResult: Passed
3.3 Input Assistance
Success Criterion
Result
Observations
3.3.1: Error Identification
Entire sampleResult: Passed
3.3.2: Labels or Instructions
Entire sampleResult: Passed
3.3.3: Error Suggestion
Entire sampleResult: Passed
Entire sampleObservations:Email, phonenumber etc have default error messages that instruct users.
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept”, you consent to the use of ALL the cookies.
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.