Check out the following comprehensive checklist on ADA Compliance with our Template Builder. We provide a breakdown of Level A and Level AA compliance.
Level A Compliance
| Success Criteria | Description | Compliance | Explanation |
| 1.1.1 – Non-text Content | Provide text alternatives for non-text content | Fully compliant | We provide the "alt" HTML property customization for all images |
| 1.2.1 – Audio-only and Video-only (Pre-recorded) | Provide an alternative to video-only and audio-only content | Fully compliant | It's up to the author |
| 1.2.2 – Captions (Pre-recorded) | Provide captions for videos with audio | Fully compliant | It's up to the author |
| 1.2.3 – Audio description or Media Alternative (Pre-recorded) | Video with an audio has a second alternative | Fully compliant | It's up to the author |
| 1.3.1 – Info and Relationships | Logical structures | Fully compliant | It's up to the author |
| 1.3.2 – Meaningful Sequence | Present content in a meaningful order | Fully compliant | It's up to the author |
| 1.3.3 – Sensory Characteristics | Use more than one sense for instructions | Fully compliant | Our messages can be used with screen readers |
| 1.4.1 – Use of Colour | Don’t use presentation that relies solely on colour | Fully compliant | It's up to the author |
| 1.4.2 – Audio Control | Don’t play audio automatically | Not applicable | We currently don't allow HTML <audio> content, but still it's up to the author |
| 2.1.1 – Keyboard | Accessible by keyboard only | Partially compliant | We don't let the user set the tabIndex HTML explicitly (only with "custom attributes") but our elements, such as buttons and images, are navigable with a keyboard |
| 2.1.2 – No Keyboard Trap | Don’t trap keyboard users | Fully compliant | We never trap the keyboard AFAIK |
| 2.4.1 – Bypass Blocks | Provide a “Skip to Content” link | Fully compliant | It's up to the author |
| 2.4.2 – Page Titled | Helpful and clear page title | Fully compliant | It's up to the author |
| 2.4.3 – Focus Order | Logical Order | Fully compliant | It's up to the author |
| 2.4.4 – Link Purpose (In Context) | Every link’s purpose is clear from its context | Fully compliant | It's up to the author |
| 2.5.1 – Pointer Gestures | Users can perform touch functions with assistive technology or one finger | Fully compliant | Our messages can be read with touch-enabled devices such as smartphones or tablets |
| 2.5.2 – Pointer Cancellation | This requirement applies to web content that interprets pointer actions | Fully compliant | There are no forced pointer actions |
| 2.5.3 – Label in Name | The name contains the text that is presented visually | Fully compliant | We provide do provide labels or text alternatives |
| 2.5.4 – Motion Actuation | Functions that are trigged by moving a device or by gesturing towards a device can also be operated by more conventional user interface components | Not applicable | We don't have movement-triggered actions |
| 3.1.1 – Language of Page | Page has a language assigned | Not compliant | At present time the user cannot set the message language; it is initially set to English |
| 3.2.1 – On Focus | Elements do not change when they receive focus | Fully compliant | |
| 3.2.2 – On Input | Elements do not change when they receive input | Fully compliant | |
| 3.3.1 – Error Identification | Clearly identify input errors | Fully compliant | We do provide basic authentication and provide clear input errors |
| 3.3.2 – Labels or Instructions | Label elements and give instructions | Fully compliant | It's up to the author |
| 4.1.1 – Parsing | No major code errors | Fully compliant | We test our code constantly |
| 4.1.2 – Name, Role, Value | Build all elements for accessibility | Fully compliant | We create standard HTML elements, with no custom ones - so any assistive technology should read its status |
Level AA Compliance
| Success Criteria | Description | Compliance | Explanation |
| 1.2.4 – Captions (Live) | Live videos have captions | Not applicable | It's up to the author |
| 1.2.5 – Audio Description (Pre-recorded) | Users have access to audio description for video content | Not compliant | We currently don't allow HTML <audio> content |
| 1.3.4 – Orientation | Requires authors not to rely on a screen orientation | Fully compliant | Our messages are responsive |
| 1.3.5 – Identify Input Purpose | Ensure common names are provided using the HTML autocomplete list | Fully compliant | Users can use <datalist> on our fields. Then it's up to the author |
| 1.4.3 – Contrast (Minimum) | Contrast ratio between text and background is at least 4.5:1 | Fully compliant | It's up to the author |
| 1.4.4 – Resize Text | Text can be resized to 200% without loss of content or function | Fully compliant | It's up to the author |
| 1.4.5 – Images of Text | Don’t use images of text | Fully compliant | It's up to the author |
| 1.4.10 – Reflow | Your website must be responsive | Fully compliant | It's up to the author |
| 1.4.11 – Non-Text Contrast | High contrast between pieces of text and their backgrounds | Fully compliant | It's up to the author |
| 1.4.12 – Text Spacing | Text spacing can be overridden to improve the reading experience | Fully compliant | It's up to the author |
| 1.4.13 – Content on Hover Focus | Ensuring content visible on hover or keyboard focus does not lead to accessibility issues | Not applicable | We don't support "hover" actions or custom keyboard focus actions. |
| 2.4.6 – Headings and Labels | Use clear headings and labels | Fully compliant |
It's up to the author |
| 2.4.7 – Focus Visible | Keyboard focus is visible and clear | Fully compliant | We use the standard HTML keyboard focus visualization |
| 3.1.2 – Language of Parts | Tell users when the language on a page changes | Not compliant | The language of our messages is forced to English |
| 3.2.3 – Consistent Navigation | Use menus consistently | Partially compliant | Our "menu" content block can be used for a consistent navigation. We currently don't support a search feature |
| 3.2.4 – Consistent Identification | Use icons and buttons consistently | Fully compliant | It's up to the author |
| 3.3.3 – Error Suggestion | Suggest fixes when users make errors | Not compliant | We do provide basic authentication and provide clear input errors, but we don't provide specific instructions on how to fix those, and custom error messages are not provided |
| 3.3.4 – Error Prevention (Legal, Financial, Data) | Reduce the risk of input errors for sensitive data | Not applicable | This criteria regards helping users with disabilities avoid serious consequences as the result of a mistake when performing an action that cannot be reversed. This depends on the data flow that the author of the message chose - thus, this is not under our control |
| 4.1.3 – Status Changes | Distances between paragraphs, rows, words and characters must be able to be increased to a certain value | Partially compliant | We only provide 4 presets for text "line-height" in text blocks; we allow arbitrary values for letter spacing and rows/paragraph, by using custom dividers |