Accessibility
What Is in This Accessibility Report?
Mendix is an application development platform. This report covers accessibility conformance for web applications created using Mendix Studio Pro.
Who Is Responsible For Accessibility?
Specific accessibility issues reported to Mendix will be treated as bugs. Since not all success criteria can be used with all types of content and Mendix is an application development platform that supports user interface development, several guidelines require certain implementation and content from developers to achieve success. Compliance to accessibility standards is the responsibility of the application developers using the platform.
| Example | Mendix Platform | Developer |
|---|---|---|
| Header usage | Provides the options to specify headings (for example H1–H6). |
Responsible for applying correctly, for example by only using an H1, logical ordering, or header once. |
alt tags for images |
Provides option to a set multi-lingual alt text for images. |
Must provide logical alt text. |
| Contrast | Provides a default theme with enough contrast and option to configure the colors. | Must keep enough contrast when changing the colors. |
| Visual widgets | Provides visual widgets which are not accessible by definition, for example Charts or Maps. | Developers should take into account the limitation of visual widgets with respect to accessibility and provide a valid alternative like a textual representation. |
| Keyboard tab order | All UI components have option to include or exclude from keyboard tab index. | Developers should make sure forms and webpages are keyboard accessible. A logical tab and focus order should be created. |
How Does Mendix Support Accessibility?
Mendix supports the following guidelines:
- Web Content Accessibility Guidelines (WCAG) 2.1 levels A and AA (for more information, click here)
- Section 508 of the American Federal Communications Act as published in 2017 (for more information, click here)
For a simplified overview of WCAG guidelines, see these Simplified WCAG Checklists. Although they address WCAG 2.0 guidelines, these checklists provide simply written solutions for improving accessibility.
How Does Mendix Support WCAG 2.1?
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content (Level A) Also applies to: 2017 Section 508
|
Supports | The Mendix Platform uses standard HTML and WAI-ARIA techniques for providing text equivalents of non-text elements. This includes the use of alt attributes for images and the use of aria-label or aria-describedby attributes for input elements. On top of this, the Mendix Platform offers generic support for configuring additional attributes on widgets.
The Mendix Platform enables developers to define a text-only representation when needed for accessibility. Some purely decorative elements that have no functional or informational purpose may not have a text alternative. |
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) Also applies to: 2017 Section 508
|
Not applicable | The Mendix Platform does not include audio or video content by default. However, developers can include video content in user interfaces that are created with Mendix. In such cases, developers can include alternative representations (such as text transcripts) that present equivalent information to the videos. |
| 1.2.2 Captions (Prerecorded) (Level A) Also applies to: 2017 Section 508
|
Not Applicable | The Mendix Platform does not include audio or video content by default. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Also applies to: 2017 Section 508
|
Not Applicable | The Mendix Platform does not use synchronized media. |
| 1.3.1 Info and Relationships (Level A) Also applies to: 2017 Section 508
|
Supports | The Mendix Platform uses semantically-correct markup so that information, structure, and relationships can be understood independent of presentation.
Note that the Mendix Platform does not enforce a structure, hence it is the responsibility of the developer to confirm to a correct structure and use the correct widgets and settings. For example, a container widget has different render mode settings. Combining them improperly could confuse assistive technologies. If a |
| 1.3.2 Meaningful Sequence (Level A) Also applies to: 2017 Section 508
|
Supports | The Mendix Platform generates semantically-correct markup to allow assistive technologies to interpret the meaning of content and controls.
Developers are responsible for creating a meaningful and logical structure when building a page. |
| 1.3.3 Sensory Characteristics (Level A) Also applies to: 2017 Section 508
|
Supports | The Mendix Platform does not depend on sensory characteristics such as shape, size, visual location, orientation, or sound to understand the content.
The Mendix Platform also uses WAI-ARIA techniques and correct DOM structure to ensure that those relationships are available to assistive technologies. Mendix provides options for defining text alternatives if needed. |
| 1.4.1 Use of Color (Level A) Also applies to: 2017 Section 508
|
Supports | Colors are only used as a decorative or supplemental attribute of user interface elements. A textual representation can always be used as the primary approach for displaying information.
Developers are responsible for how they use colors in their applications. Mendix provides options for defining text alternatives if needed. |
| 1.4.2 Audio Control (Level A) Also applies to: 2017 Section 508
|
Not Applicable | The Mendix Platform does not include audio or video content by default. |
| 2.1.1 Keyboard (Level A) Also applies to: 2017 Section 508
|
Supports | Applications built with the the Mendix Platform are web-based applications that support standard keyboard navigation and input functions. This includes features like using the Tab key to move between selectable UI components, pressing the arrow keys to navigate between elements (if applicable), and enabling a developer to configure the behavior when pressing the {Enter} key on text inputs. |
| 2.1.2 No Keyboard Trap (Level A) Also applies to: 2017 Section 508
|
Supports | Applications built with the Mendix Platform are web-based applications that support standard keyboard navigation. Mendix ensures that keyboard users cannot be trapped in a subset of content. |
| 2.1.4 Character Key Shortcuts (Level A) | Not Applicable | The Mendix Platform does not offer an option for character-key shortcuts |
| 2.2.1 Timing Adjustable (Level A) Also applies to: 2017 Section 508
|
Not Applicable | The Mendix Platform does not offer an option for time-controlled content. |
| 2.2.2 Pause, Stop, Hide (Level A) Also applies to: 2017 Section 508
|
Not Applicable | The Mendix Platform does not include moving, blinking, scrolling, or auto-updating information. |
| 2.3.1 Three Flashes or Below Threshold (Level A) Also applies to: 2017 Section 508
|
Not Applicable | The Mendix Platform does not use flashing interface elements. |
| 2.4.1 Bypass Blocks (Level A) Also applies to: 2017 Section 508
|
Supports | The Mendix Platform offers the capability to add actions to links that bypasses blocks by scrolling or setting focus to other elements. In addition, Mendix containers provide render modes which can be used as input for assistive technologies.
For example, a container can be rendered as a |
| 2.4.2 Page Titled (Level A) Also applies to: 2017 Section 508
|
Supports | The Mendix Platform allows developers to provide page titles for all pages. |
| 2.4.3 Focus Order (Level A) Also applies to: 2017 Section 508
|
Supports | The Mendix Platform uses a logical tab order through interactive elements such as links and form controls. Developers can control the focus order by changing the tab index of widgets. |
| 2.4.4 Link Purpose (In Context) (Level A) Also applies to: 2017 Section 508
|
Supports | The Mendix Platform allows developers to configure link titles or textual links and provides options to define an alt text for image links. |
| 2.5.1 Pointer Gestures (Level A) | Supports | The Mendix Platform does not rely on path-based gestures, multipoint gestures, or single-point activation for spatial positioning and manipulation. It also does not require complex gestures, |
| 2.5.2 Pointer Cancellation (Level A) | Supports | The Mendix Platform does not use down-events to execute functions. |
| 2.5.3 Label in Name (Level A) | Support with Exceptions | The Mendix Platforms offers support for configuring additional attributes like aria-labelledby on widgets.
The Mendix Platform does not offer the option to provide hidden span elements inside buttons or links. |
| 2.5.4 Motion Actuation (Level A) | Supports | The Mendix Platform offers several capabilities to trigger functions and is not limited to only device or user motion. |
| 3.1.1 Language of Page (Level A) Also applies to: 2017 Section 508
|
Supports | The Mendix Platform sets the language attribute (lang) on the HTML element to specify the default language of the page based on the current language.
Mendix supports both left-to-right and right-to-left writing directions. |
| 3.2.1 On Focus (Level A) Also applies to: 2017 Section 508
|
Supports | By default, UI components of the Mendix Platform do not initiate a change of context when they receive focus.
Developers can configure onEnter and onLeave events, but should employ this option carefully. |
| 3.2.2 On Input (Level A)
Also applies to:
|
Supports | By default, UI components of the Mendix Platform do not initiate a change of context when they receive input.
Note that it is possible for developers to deviate from this behavior when input is received and a different UX is preferred. |
| 3.3.1 Error Identification (Level A) Also applies to: 2017 Section 508
|
Supports | The Mendix Platform offers several options to display error and validation messages. These messages can be shown directly to the related input field if applicable.
Additionally, the Mendix Platform uses |
| 3.3.2 Labels or Instructions (Level A) Also applies to: 2017 Section 508
|
Supports | The Mendix Platform provides capabilities for specifying labels and instructions for user input fields. Developers can add descriptions for two common cases: to explain if a field is required, or to provide instructions about the expected format.
The Mendix Platform uses standard HTML and WAI-ARIA attributes to associate labels and instructions to user interface elements. This includes the use of |
| 4.1.1 Parsing (Level A) Also applies to: 2017 Section 508
|
Supports | The Mendix Platform creates correct markup for all pages. This markup is automatically generated based on the application model. |
| 4.1.2 Name, Role, Value (Level A) Also applies to: 2017 Section 508
|
Supports | The Mendix Platform uses standard HTML and WAI-ARIA attributes to describe the identity, operation, and state of user interface elements to assistive technologies. On top of this, the Mendix Platform offers generic support for configuring additional attributes on widgets. |
4.2 Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) (Level AA) Also applies to: 2017 Section 508
|
Not Applicable | The Mendix Platform does not use synchronized media. |
| 1.2.5 Audio Description (Prerecorded) (Level AA) Also applies to: 2017 Section 508
|
Not Applicable | The Mendix Platform does not use synchronized media. |
| 1.3.4 Orientation (Level AA) | Supports | The Mendix Platform supports responsive design by default which gives support for orientation, for example portrait or landscape. |
| 1.3.5 Identify Input Purpose (AA) | Supports | The Mendix Platforms offers generic support for configuring the autocomplete attribute on widgets. |
| 1.4.3 Contrast (Minimum) (Level AA) Also applies to: 2017 Section 508
|
Supports | The Mendix Platform provides a default theme with enough contrast in colors.
The Mendix Platform provides the option to configure colors. When making changes to the default color scheme, it is the responsibility of developers to keep a high enough contrast ratio. |
| 1.4.4 Resize text (Level AA) Also applies to: 2017 Section 508
|
Supports | Mendix-based web applications support standard browser zoom capabilities built into modern web browsers and operating systems. |
| 1.4.5 Images of Text (Level AA) Also applies to: 2017 Section 508
|
Supports | The Mendix Platform does not use images of text by default.
Developers may choose to include images of text in pages that they create with Mendix. In this case the Mendix offers the capability to provide an |
| 1.4.10 Reflow (Level AA) | Supports | The Mendix Platform enables developers to design responsive pages which include the option to provide content presented without loss of information or functionality, and without requiring scrolling in two dimensions. Developers have control of the content of a page and can add CSS media queries to adjust visibility and dimensions. |
| 1.4.11 Non-Text Contrast (Level AA) | Supports | The Mendix Platform provides a default theme with enough contrast in colors.
The Mendix Platform provides the option to configure colors. When making changes to the default color scheme, it is the responsibility of developers to keep a high enough contrast ratio. |
| 1.4.12 Text Spacing (Level AA) | Not applicable | The Mendix Platform offers the capability to configure the content, layout, and styling of pages.
As developers control the content, layout, and styling of pages, they are responsible for meeting this requirement. |
| 1.4.13 Content on Hover or Focus (Level AA) | Supports | By default, the Mendix Platform does not show content based on focus or hover events. However, the developer can change the behavior of Mendix widgets to show content on focus or hover and can hide when losing focus or hovering away. In this case the developer is responsible for meeting this requirement. |
| 2.4.5 Multiple Ways (Level AA) Also applies to: 2017 Section 508
|
Supports | The Mendix Platform provides capabilities for incorporating navigation menus, links, and search functions in user interfaces built with Mendix. It is the developer’s responsibility to incorporate these how they see fit. |
| 2.4.6 Headings and Labels (Level AA) Also applies to: 2017 Section 508
|
Supports | The Mendix Platform uses semantically-correct markup for interface elements, including headings (H1–H6) and labels. |
| 2.4.7 Focus Visible (Level AA) Also applies to: 2017 Section 508
|
Supports | The Mendix Platform provides a default theme that makes focus visible. Developers can adjust this to the needs of the application by changing or adding CSS or SASS. |
| 3.1.2 Language of Parts (Level AA) Also applies to: 2017 Section 508
|
Not applicable | Mendix does not provide the option to provide text or data in multiple languages on the same page.
The Mendix Platform sets the language attribute ( |
| 3.2.3 Consistent Navigation (Level AA) Also applies to: 2017 Section 508
|
Supports | The Mendix Platform uses navigation layouts to provide consistent navigation. |
| 3.2.4 Consistent Identification (Level AA) Also applies to: 2017 Section 508
|
Supports | The Mendix Platform provides a standard component library which a developer can use to create a consistent user interface and user experience. When creating a user interface it is the developer’s responsibility to create and maintain consistent component usage. |
| 3.3.3 Error Suggestion (Level AA) Also applies to: 2017 Section 508
|
Supports | The Mendix Platform offers several options to display error or validation messages. The text of these messages can be fully configured, and the messages can be shown directly to the related input field if applicable. It is the responsibility of the developer to provide clear guidance to the user in these messages. |
| 3.3.4 Error Prevention (Legal, Financial, Data) ((Level AA) Also applies to: 2017 Section 508
|
Supports | The Mendix Platform provides capabilities for developers to build their user interfaces for error prevention, namely validation messages and custom workflow checks in microflows and nanoflows.
By default, the Mendix Platform checks whether the data type of user-inputted data is valid using built-in domain model checks. In addition, developers can create tailor-made mechanisms (pages and microflows) for reviewing, confirming, and correcting before submission. |
| 4.1.3 Status Messages (Level AA) | Supports | The Mendix Platform provides the capability to show or hide status messages without losing the focus. |
4.3 Success Criteria, Level AAA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.6 Sign Language (Prerecorded) (Level AAA) | Not Applicable | The Mendix Platform does not include audio or video content by default. |
| 1.2.7 Extended Audio Description (Prerecorded) (Level AAA) | Not Applicable | The Mendix Platform does not include audio or video content by default. |
| 1.2.8 Media Alternative (Prerecorded) (Level AAA) | Not Applicable | The Mendix Platform does not include audio or video content by default. |
| 1.2.9 Audio-only (Live) (Level AAA) | Not Applicable | The Mendix Platform does not include audio or video content by default. |
| 1.3.6 Identify Purpose (Level AAA) | Supports with Exceptions | The Mendix Platforms offers support for adding the aria landmarks main and nav.
The Mendix Platform does not offer support for adding the aria landmarks |
| 1.4.6 Contrast (Enhanced) (Level AAA) | Supports | The Mendix Platform provides a default theme with enough contrast in colors the option to configure colors. |
| 1.4.7 Low or No Background Audio (Level AAA) | Not Applicable | The Mendix Platform does not include audio or video content by default. |
| 1.4.8 Visual Presentation (Level AAA) | Supports with Exceptions | The Mendix Platform does not provide a tool for user to select the foreground and background colors or to set the line spacing.
Developers have control on the layout of pages and can design the pages to have no text blocks wider than 80 characters, make sure the text is not justified to both sides of the web page, and that text can be resized up to 200% without requiring the user to scroll horizontally. |
| 1.4.9 Images of Text (No Exception) (Level AAA) | Not Applicable | The Mendix Platform does not use images of text by default. |
| 2.1.3 Keyboard (No Exception) (Level AAA) | Supports | Pages built using UI components (widgets) in the Mendix Platform can be used fully with the keyboard. |
| 2.2.3 No Timing (Level AAA) | Not Applicable | The Mendix Platform does not offer an option for time-controlled content. |
| 2.2.4 Interruptions (Level AAA) | Not Applicable | The Mendix Platform does not create interruptions by default.
Please note that developers can create interruptions. In those cases the developer can set the focus to the close button for example. |
| 2.2.5 Re-authenticating (Level AAA) | Not Applicable | The Mendix Platform does not log out the user automatically. |
| 2.2.6 Timeouts (Level AAA) | Not Applicable | The Mendix Platform does not use timeouts. |
| 2.3.2 Three Flashes (Level AAA) | Not Applicable | The Mendix Platform does not provide flashing content. |
| 2.3.3 Animation from Interactions (Level AAA) | Not Applicable | The Mendix Platform does not provide animations. |
| 2.4.8 Location (Level AAA) | Supports | The Mendix Platforms offers the capabilities to create bread crumbs by using buttons or links. |
| 2.4.9 Link Purpose (Link Only) (Level AAA) | Supports | The Mendix Platform offers the option to configure the caption of a link or button, and in the case of images provide an alt text. |
| 2.4.10 Section Headings (Level AAA) | Supports | The Mendix Platform offers support for different headings like H1 to H6, paragraphs, and the option to use fieldsets. |
| 2.5.5 Target Size (Level AAA) | Supports with Exceptions | The default styling of the Mendix Platform does not always meet this requirement because of aesthetic reasons. However, the styling can be fully adjusted to meet this requirement. |
| 2.5.6 Concurrent Input Mechanisms (Level AAA) | Supports | The Mendix Platform offers the capability to interact with the application via different input mechanisms which can be concurrently used. |
| 3.1.3 Unusual Words (Level AAA) | Supports | The Mendix Platform does not provide unusual words for default texts and offers the option to customize and configure captions and texts. |
| 3.1.4 Abbreviations (Level AAA) | Supports | The Mendix Platform does not provide abbreviations and offers the option to customize and configure captions and texts.
However, it is the responsibility of the developer to not provide abbreviations. |
| 3.1.5 Reading Level (Level AAA) | Supports | The Mendix Platform provides the option to customize and configure captions and texts. |
| 3.1.6 Pronunciation (Level AAA) | Supports | The Mendix Platform provides the option to customize and configure captions and texts. |
| 3.2.5 Change on Request (Level AAA) | Supports | The Mendix Platform does not provide elements which automatically update by default, open links in the same windows, or auto-submit forms. |
| 3.3.5 Help (Level AAA) | Supports | The Mendix Platform provides several capabilities to add help texts to pages using labels and texts. |
| 3.3.6 Error Prevention (All) (Level AAA) | Supports | The Mendix Platform provides capabilities for developers to build their user interfaces for error prevention, namely validation messages and custom workflow checks in microflows and nanoflows.
By default, the Mendix Platform checks whether the data type of user-inputted data is valid using built-in domain model checks. In addition, developers can create tailor-made mechanisms (pages and microflows) for reviewing, confirming, and correcting before submission. |