Accessibility Statement
Our Commitment
IncluSend LLC is committed to ensuring that Melaa is accessible to all users, including people with disabilities. We believe that every educator should be able to use our platform to support multilingual learners, regardless of ability.
Standards
Melaa is designed and developed to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. We also strive to meet the accessibility requirements set forth by Colorado HB21-1110, which requires state and local government websites to meet WCAG 2.2 Level AA standards.
Accessibility Features
We have implemented the following accessibility features throughout Melaa:
Keyboard Navigation
- Skip-to-content link on every page to bypass repetitive navigation
- Visible focus indicators on all interactive elements
- All primary navigation, forms, and controls are operable via keyboard alone
Screen Reader Support
- Semantic HTML structure with proper heading hierarchy
- ARIA roles and labels where native semantics are insufficient (e.g.,
role="switch"witharia-checkedon toggles,aria-labelon icon buttons) - Live regions (
aria-live="polite") for dynamic content updates such as AI chat responses and form status messages - Descriptive alt text on all meaningful images
Color and Visual Design
- Color contrast ratios of 4.5:1 or higher for normal text
- Focus-visible outlines that meet contrast requirements
- Support for
prefers-reduced-motionto disable animations - Information is never conveyed by color alone-status indicators include text labels
Forms
- All form inputs have associated labels via
<label>withhtmlFor - Autocomplete hints on name, email, and organization fields in our contact and request forms
- Error messages are clearly identified and associated with their fields
Modals and Dialogs
- Modal dialogs use
role="dialog"andaria-modal="true" - Escape key closes modals
- Close buttons include
aria-label="Close dialog"
Responsive Design
- Content reflows at 320px viewport width without horizontal scrolling
- Content is readable and functional at 200% browser zoom
- Touch targets meet 24x24 CSS pixel minimum size
Known Limitations
We are aware of the following accessibility gaps and are actively working to address them:
- Modal dialogs: Our dialogs use
role="dialog"witharia-modal="true", close on the Escape key, and trap keyboard focus while open. We are completing an audit to confirm every dialog across the app meets this bar. - Animated content: The homepage product demo is a CSS/JavaScript animation that automatically stops for visitors who enable the "reduce motion" setting in their operating system. It does not yet offer an on-page play/pause control for visitors who have not set that preference; we plan to add one.
- Data table captions: Public-facing tables (including the VPAT and subprocessor tables) now include
<caption>elements andscopeattributes. Some in-app admin data tables still do not include a<caption>; we plan to add descriptive captions to those. - AI-generated content: The AI Thought Partner generates instructional recommendations in markdown format. While we render this content with semantic HTML, the structure of AI-generated responses may vary and may not always follow an ideal heading hierarchy.
Voluntary Product Accessibility Template (VPAT)
The following VPAT Version 2.5 documents Melaa's conformance with WCAG 2.2 Level AA as of July 5, 2026.
Product Information
Product:Melaa (melaa.app)Version:1.0Report Date:July 5, 2026Company:IncluSend LLCContact:support@melaa.app
Applicable Standards
- WCAG 2.2 (Level AA) - Included
- Revised Section 508 - Included (WCAG 2.2 mapping)
- EN 301 549 - Not evaluated
Conformance Terms
- Supports: At least one method meets the criterion without known defects.
- Partially Supports: Some functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
WCAG 2.2 - Level A
| Criteria | Level | Remarks |
|---|---|---|
| 1.1.1 Non-text Content | Supports | All images include alt text. Decorative images use empty alt attributes. |
| 1.2.1–1.2.3 Audio/Video | N/A | Application does not include audio or video content. |
| 1.3.1 Info and Relationships | Supports | Semantic HTML: headings hierarchy, form labels, landmark regions, lists, and tables with headers. |
| 1.3.2 Meaningful Sequence | Supports | Logical reading order. DOM order matches visual presentation. |
| 1.3.3 Sensory Characteristics | Supports | Instructions do not rely solely on shape, size, visual location, or sound. |
| 1.4.1 Use of Color | Supports | Color is not the sole means of conveying information. Status indicators use text labels. |
| 2.1.1 Keyboard | Supports | All navigation and form controls are keyboard accessible. |
| 2.1.2 No Keyboard Trap | Partial | Most components navigate freely. Gap: some modal dialogs do not implement focus trapping. |
| 2.2.1 Timing Adjustable | Supports | No time limits imposed. Session uses standard auth token refresh. |
| 2.2.2 Pause, Stop, Hide | Partial | Loading indicators auto-stop, and the homepage product demo (a CSS/JS animation, not a GIF) pauses under prefers-reduced-motion. Gap: it does not yet offer an on-page pause control for visitors who have not enabled reduced motion. |
| 2.4.1 Bypass Blocks | Supports | Skip-to-content link on all pages. |
| 2.4.2 Page Titled | Supports | All pages have unique, descriptive titles via Next.js metadata. |
| 2.4.3 Focus Order | Supports | Focus order follows logical sequence consistent with content structure. |
| 2.4.4 Link Purpose | Supports | Link text is descriptive or provides context through surrounding content. |
| 2.5.1–2.5.4 Pointer/Motion | Supports | Single-point activation only. Standard up-event behavior. No motion-triggered features. |
| 3.1.1 Language of Page | Supports | lang="en" set on root HTML element. |
| 3.2.1–3.2.2 On Focus/Input | Supports | No unexpected context changes on focus or input. Submission requires explicit action. |
| 3.3.1 Error Identification | Supports | Validation errors displayed as visible, descriptive text messages. |
| 3.3.2 Labels or Instructions | Supports | All form inputs have associated labels. Required fields are indicated. |
| 4.1.2 Name, Role, Value | Supports | Standard HTML elements. Toggle switches use role="switch" and aria-checked. |
WCAG 2.2 - Level AA
| Criteria | Level | Remarks |
|---|---|---|
| 1.2.4–1.2.5 Captions/Audio Desc. | N/A | No live or prerecorded audio/video content. |
| 1.3.4 Orientation | Supports | Content is not restricted to a single display orientation. |
| 1.3.5 Identify Input Purpose | Supports | Input fields use appropriate type and autocomplete attributes. |
| 1.4.3 Contrast (Minimum) | Supports | Text meets the 4.5:1 ratio. Body: #211826 on #ffffff. Secondary body text: #4a3f4d on #ffffff (exceeds 4.5:1). |
| 1.4.4 Resize Text | Supports | Text resizable to 200% without loss of content or functionality. |
| 1.4.5 Images of Text | Supports | No images of text (except the product logo, which is exempt). |
| 1.4.10 Reflow | Supports | Content reflows at 320px without horizontal scrolling. |
| 1.4.11 Non-text Contrast | Supports | UI components meet 3:1 contrast against adjacent colors. |
| 1.4.12 Text Spacing | Supports | Content remains readable with modified text spacing. No clipping or overlap. |
| 1.4.13 Content on Hover/Focus | Supports | Hover content is dismissible, hoverable, and persistent. |
| 2.4.5 Multiple Ways | Supports | Navigation via top menu, skip link, direct URL, and sidebar. |
| 2.4.6 Headings and Labels | Supports | Headings describe sections. Labels describe input purpose. |
| 2.4.7 Focus Visible | Supports | Browser default focus indicators preserved. Custom styles applied where defaults are overridden. |
| 2.4.11 Focus Not Obscured | Supports | Focused elements are not hidden by fixed headers or other content. |
| 2.5.7 Dragging Movements | Supports | No drag-based interactions required. All functionality uses single-point actions. |
| 2.5.8 Target Size (Minimum) | Supports | Interactive targets meet 24x24 CSS pixel minimum. |
| 3.1.2 Language of Parts | Supports | Content is in English. No mixed-language content. |
| 3.2.3–3.2.4 Consistency | Supports | Consistent navigation order and component identification throughout. |
| 3.3.3 Error Suggestion | Supports | Correction suggestions provided for detected input errors. |
| 3.3.4 Error Prevention | Supports | Destructive actions require confirmation. Data is reviewable before submission. |
| 3.3.7 Redundant Entry | Supports | Previously entered information is auto-populated where applicable. |
| 3.3.8 Accessible Auth | Supports | Sign-in is single sign-on only (Google, Microsoft, ClassLink) - no password or memory/transcription test is required. |
Testing Methodology
- Manual: Keyboard-only navigation, screen reader testing (VoiceOver on macOS)
- Automated: Lighthouse accessibility audit, axe-core browser extension
- Color: WebAIM Contrast Checker
- Responsive: Tested at 320px, 768px, 1024px, and 1440px viewports
Reporting Accessibility Issues
We take accessibility feedback seriously. If you encounter any barriers while using Melaa, please let us know so we can address them. You can report accessibility issues through our contact page or by emailing us directly. Please include a description of the issue, the page where you encountered it, and the assistive technology you were using (if applicable).
Contact Us
If you have questions or concerns about accessibility, please contact us: