Fully Automated Web Accessibility Solution for ADA & WCAG Compliance
Ggame-changer in web accessibility, making the entire process to full compliance 100% automatic and immediate, using machine-learning and computer vision technologies. The accessibility interface is responsible for all the UI and design-related adjustments, while the AI-powered background process handles optimizations for screen-reader and for keyboard navigation (the most complex requirements). Protect your business from lawsuits, Open your website to the world!
Avoid lawsuits
Become Web Inclusive
Attract new potential customers
Boost brand perception
Show customers that you care
Automated, state-of-the-art AI technology
Automatic Screen-Reader adjustments Powered by AI
Using the contextual understanding and image recognition, hekadoc's AI scans and analyzes websites to learn what elements and functionality they include, and automatically adjusts them to users’ screen-readers.
- Alt Tags
- State Controls
- ARIA Attributes
- Icons & Buttons
- Roles & Landmarks
- Forms & Validations
Automatic Keyboard Navigation Adjustments Powered By AI
hekadoc's Contextual Understanding AI technology helps it learn and understand the structures and behaviors of the website’s elements on-the-fly, adding keyboard-only functionality to each of them.
- Dropdowns
- Menus
- Popups
- Forms
- Skip Links
- Buttons
Personal UI & Design adjustments Powered by an Interface
hekadoc's interface provides an accessibility experience that is tailored to the individual need of every user, supporting a range of UI and design adjustments from content to display.
- Content & Display
- Color & Contrast
- Stop Animations
- Forms
- Mute Sounds
- Focus & Emphasiss
How do we protect you from litigation?
WCAG 2.1 & ADA Compliance
WCAG 2.1 & ADA Compliance
Ongoing WCAG & ADA compliance even when website updates
Certification & Statement
Certification & Statement
Accessibility statement and certification of performance
Daily Compliance Monitoring
Daily Compliance Monitoring
Re-scanning and fixing accessibility issues every 24 hours
Monthly Compliance Auditing
Monthly Compliance Auditing
Who is this for and why?
Epilepsy Safe Profile
This profile enables people with epilepsy to use the website safely by eliminating the risk of seizures that result from flashing or blinking animations and risky color combinations.
Visually Impaired Profile
This profile adjusts the website so that it is accessible to the majority of visual impairments such as Degrading Eyesight, Tunnel Vision, Cataract, Glaucoma, and others.
Cognitive Disability Profile
This profile provides various assistive features to help users with cognitive disabilities such as Autism, Dyslexia, CVA, and others, to focus on the essential elements of the website more easily.
ADHD Friendly Profile
This profile significantly reduces distractions and noise, to help people with ADHD and Neurodevelopmental disorders browse, read, and focus on the essential elements of the website more easily.
Blind Users Profile (Screen-readers)
This profile adjusts the website to be compatible with screen-readers such as JAWS, NVDA, VoiceOver, and TalkBack. A screen-reader is software that is installed on the blind user’s computer and smartphone, and websites should ensure compatibility with it.
Keyboard Navigation Profile (Motor-Impaired)
This profile enables motor-impaired persons to operate the website using the keyboard Tab, Shift+Tab, and the Enter keys. Users can also use shortcuts such as “M” (menus), “H” (headings), “F” (forms), “B” (buttons), and “G” (graphics) to jump to specific elements.
Accessibility Interface
AI-Powered Processes
Foreground Application:
hekadoc's accessibility widget interface enables users with visual impairments to adjust the design and UI of your website, so it perfectly meets their accessibility needs according to the WCAG 2.1 guidelines at the AA and AAA levels.
Background Application:
hekadoc's Contextual Understanding AI technology is responsible for handling the most complex requirements - screen-reader and keyboard navigation adjustments, using machine learning and computer vision.
Key Interface Features
The interface covers much more than visuals!
Stop Animations
Epilepsy
Instantly freeze all animations, gifs, and flashing images
Virtual Keyboard
Motor Impaired
An on-screen keyboard for people who can't use a mouse
Online Dictionary
Cognitive Disorders
Allows searching for phrases, abbreviations and concepts
Quick Navigation
Motor Impaired
Let's users reach any important page with a single click.
AI Applications for Web Accessibility
Some of the most common website elements are also the biggest challenges to make accessible. Learn how our AI solves this!
Popups
Shift the focus to the popup, lock It's navigation, and enable dismissal with Esc.
WCAG 2.1 Level AA requirements for Popups
When a popup appears, the keyboard focus must lift off the main page and land back down within the first clickable element of the popup.
Navigating using the Tab key within the popup must loop back to start when reaching the last element and trying to move forward.
Users must be able to close popups with the Esc key, and the focus must go back to the element that was focused on prior to the popup. • Popups must include a “role” attribute equal to “dialog”.
Popups must include an “aria-modal” attribute equal to “true”.
Forms
Announce field requirements and validations, identify error messages and successes
WCAG 2.1 Level AA requirements for Forms
All fields must include a “LABEL” tag that is connected to the field by the “id” and the “for” attributes, or an “aria-label” attribute.
Required fields must include both visual cues (Asterix*, text or other), and the “aria-required” attribute equals true.
Fields must include the “aria-invalid” attribute to inform screen-readers whether the field is currently valid or invalid. This attribute must change dynamically according to the validations. E.g. an empty required “name” field must include aria-invalid=”true” to indicate that it’s invalid, but change to aria-invalid=”false” once the user fills it up.
When a form is submitted and errors are present, the keyboard focus must be taken to the first invalid field, and the user must receive an explanation (both visual and to the screen-reader) of what the issue is with this field.
When a form is submitted successfully, a blind user with a screen-reader should be informed of that using an alert element or via other means.
Dropdowns
Opens with arrow-down/Enter, closes with the Esc key, locks up navigation focus
WCAG 2.1 Level AA requirements for Dropdowns
Users can open dropdowns using the Enter and the arrow-down keys. Dropdowns should also be opened by focusing on the menu item.
Users can navigate within dropdowns using the up-and-down arrows, and the focus must never escape and loop within the dropdown unless it was intentionally closed.
Users can close the dropdown using the Esc key, and the keyboard focus must go back to the root menu item of this dropdown.
Icons
Identify their purpose correctly - is it search? cart? carousel navigation? review stars?
WCAG 2.1 Level AA requirements for Icons
Icons don’t really have much of a guideline, because there isn’t such a thing as an “ICON” tag or element. Icons are usually being used with links or buttons, to describe some kind of action. So, the requirements for making icons accessible is pretty much the same as making links and buttons compliant. Every icon must include a description of Its purpose or action.
Links
Label empty or insufficient link texts - identify links that open new windows
WCAG 2.1 Level AA requirements for Links
Must include text, title, or an aria-label.
Must be logically ordered within the document (a “read more” must come after the title and the paragraph of a section, for example).
Links must be reachable by keyboard navigation using the Tab key.
Links must provide a visual indicator if they are opened in a new window, and also announce that to a screen-reader using a hidden text or title.
Links must be noticeable on-page and look different than regular text.
Menus
Identify and interpret to screen-readers, navigate through the bar with the arrow keys
WCAG 2.1 Level AA requirements for Menus
Users can use the Tab key to navigate to the next element, and Shift+Tab to navigate to the previous element, and the focused element must be easily identifiable using a focus ring (outline).
Users can navigate across the menu bar itself using the left-and-right keyboard arrows. When reaching the end of the menu, and pressing the forward arrow key, the navigation should loop back to the first item.
Buttons
Identify text and link elements that behave as buttons, enable keyboard operation
WCAG 2.1 Level AA requirements for Buttons
Buttons must contain text, title, or an aria-label.
Must be an actual “BUTTON” tag or alternatively, a “role” attribute that equals to “button” is present.
Buttons must include text/aria-label/title.
Images
Provide accurate alternative texts that include embedded text as well as objects
WCAG 2.1 Level AA requirements for Images
All images must have an Alt attribute (some people call it a tag although it’s really an attribute), that properly describes the objects in the image, and if the image contains texts (like typical banners) then the embedded text must also be present in the alt attribute.
More
Skip blocks, identify landmarks, provide feedback, describe frames and more
More
Skip blocks, identify landmarks, provide feedback, describe frames and more
Ready to engage a new audience?
Start your free 14-day trial now! No contract. No Credit Card Required.
