Universal accessibility

Make ensures universal design for all newsletters

How we approach accessibility for users with reading difficulties.

Get a more focused way of working with a native mobile app built for modern teams and a smoother experience.

A woman typing on a Mac keyboard

We present content based on four main principles:

Perceivable

Information and user interface components must be presented in a way that is perceivable to all users.

  1. Text alternative (alt text) for all non-text content

  2. The content remains understandable even without CSS

  3. Highlighted elements will flash only once.

  4. Text can be scaled up to 200% without loss of functionality.

  5. Multiple concurrent methods are used to deliver functionality

Easy to operate

User interface elements and navigation must be accessible to everyone.

  1. Mark headings with <h1> to <h6> for easy navigation

  2. A minimum 5:1 contrast ratio between foreground and background

  3. All features are fully accessible using both keyboard and mouse

  4. The content is presented in a logical order

  5. The purpose and function of links are clearly indicated by the link text

Easy to understand

The content and usability of the website must be accessible to everyone.

  1. The language of the content is specified in the code

  2. Required form fields must be indicated with text

  3. In case of invalid input, the user is notified with both color and text

  4. Predictable navigation across pages

  5. Identical functions are designed consistently across all pages.

Robust

The content must be compatible with assistive technologies.

  1. The content is reliably interpreted by user agents and assistive technologies.

  2. The website is validated and the code is correct.

  3. Extended HTML semantics (ARIA) are used where they improve accessibility.

  4. Custom components have their name and role defined in the code

  5. Status notifications are sent to assistive devices

Overview of accessibility status (WCAG)

Overview of accessibility status (WCAG)

Our implementation of WCAG applies to the public-facing parts of our online solution, including users of our customers' services. This includes newsletters, web versions of newsletters, and form pages. For your business, this means a wider reach, the ability to offer more self-service options, and a larger pool of potential users.

Our implementation of WCAG applies to the public-facing parts of our online solution, including users of our customers' services. This includes newsletters, web versions of newsletters, and form pages. For your business, this means a wider reach, the ability to offer more self-service options, and a larger pool of potential users.

Principle 1

Perceivable

Information and user interfaces are presented so that everyone can see or hear the content.

1.1 Text Alternatives

Fulfilled

Provide text alternatives for non-text content so that it can be converted into other formats people need, such as large print, braille, speech, symbols, or simplified language.

1.1.1 Non-text Content

1.2 Time-based media

Fulfilled

Provide alternatives for time-based media.

1.2.1 Audio-only and video-only (pre-recorded) · 1.2.2 Captions (pre-recorded)

1.3 Customizable

Fulfilled

Create content that can be presented in different ways without losing information or structure.

1.3.1 Info and relationships · 1.3.2 Meaningful sequence · 1.3.3 Sensory characteristics · 1.3.4 Orientation · 1.3.5 Identify input purpose

1.4 Separable

Partial

Make it easier for users to see and hear content, including separating the foreground from the background.

1.4.1 Use of color · 1.4.2 Audio control · 1.4.3 Contrast (minimum) · 1.4.4 Resize text · 1.4.5 Images of text · 1.4.10 Reflow · 1.4.11 Non-text contrast · 1.4.12 Text spacing · 1.4.13 Content on hover or focus

All except 1.4.2 Audio Control, which is not applicable to our content.

Principle 2

Easy to operate

User interface elements and navigation are accessible to everyone.

2.1 Keyboard accessible

Fulfilled

Make all functionality accessible via keyboard.

2.1.1 Keyboard · 2.1.2 No keyboard trap · 2.1.4 Character key shortcuts

2.2 Sufficient time

Fulfilled

Provide users with sufficient time to read and interact with content.

2.2.1 Adjustable speed · 2.2.2 Pause, stop, hide

2.3 Seizures and physical reactions

Fulfilled

Do not design content in a way that is known to cause seizures.

2.3.1 Maximum threshold of three flashes

2.4 Navigable

Fulfilled

Enables users to navigate, find content, and understand their current location.

2.4.1 Bypass Blocks · 2.4.2 Page Titled · 2.4.3 Focus Order · 2.4.4 Link Purpose (In Context) · 2.4.5 Multiple Ways · 2.4.6 Headings and Labels · 2.4.7 Focus Visible

2.5 Input Methods

Partial

Make it easier for users to operate functionality using input methods other than just a keyboard.

2.5.1 Pointer gestures · 2.5.2 Pointer cancellation · 2.5.3 Label in name · 2.5.4 Motion actuation

All except 2.5.4 Motion Actuation, which is not applicable to our content.

Principle 3

Easy to understand

The website's content and usability are accessible to everyone.

3.1 Readable

Fulfilled

It must be possible to understand the information and operation of the user interface.

3.1.1 Language of the page · 3.1.2 Language of parts of content

3.2 Predictable

Fulfilled

Ensure that web pages are presented and function in a predictable manner.

3.2.1 Focus · 3.2.2 On Focus/Input · 3.2.3 Consistent navigation · 3.2.4 Consistent identification

3.3 Input assistance

Partial

Help users avoid and correct errors.

3.3.1 Error identification · 3.3.2 Labels or instructions · 3.3.3 Error suggestions · 3.3.4 Error prevention

All except 3.3.4 Error Prevention, which is not applicable to our content.

Principle 4

Robust

The content is compatible with assistive devices and technologies.

4.1 Compatible

Fulfilled

Ensure the best possible compatibility with current and future user agents, including assistive technology.

4.1.1 Parsing · 4.1.2 Name, role, value · 4.1.3 Status messages

Known accessibility limitations

VML is used in Outlook to create buttons and graphics, but screen readers like JAWS do not support VML and ignore attributes such as alt, aria-label, and role. We therefore always supplement VML-based buttons with text links and correct ARIA attributes, ensuring they display correctly in Outlook and remain accessible in other email clients.

Frequently asked questions about universal design

Answers to frequently asked questions about universal design and WCAG in Make.

Stian Pedersen

Stian Pedersen

Technical Account Manager

Schedule a demo

Let us walk you through Make and explain how the system works, with no obligation.

Book an appointment

Prefer email? You can reach us at

support@make.as

Stian Pedersen

Stian Pedersen

Technical Account Manager

Schedule a demo

Let us walk you through Make and explain how the system works, with no obligation.

Book an appointment

Prefer email? You can reach us at

support@make.as

Stian Pedersen

Stian Pedersen

Technical Account Manager

Schedule a demo

Let us walk you through Make and explain how the system works, with no obligation.

Book an appointment

Prefer email? You can reach us at

support@make.as

Frequently asked questions about universal design

Answers to frequently asked questions about universal design and WCAG in Make.

  • What is universal design (UU)?

  • What is the WCAG standard?

  • Which parts of Make are accessible?

  • Are you following all of the success criteria?

  • What are the four main principles you operate by?

  • Are there any known limitations?