Category: Mortise Test Per Week

Mortise Test Per Week: If auto-starting multimedia content or auto-starting audio is used, provide a means for users to have it muted by default, unless it ends within 3 seconds.

By Karl Groves |

MEDIA-13: If auto-starting multimedia content or auto-starting audio is used, provide a means for users to have it muted by default, unless it ends within 3 seconds.

How to test

1. Identify any auto-starting multimedia content in which the sound is not muted by default, or any auto-starting audio content, and confirm that there is a persistent control to mute this content, or that it stops within 3 seconds.

Exceptions

None

How to fix

For any page that has auto-playing or auto-updating content which lasts more than 3 seconds, provide a means for users to prevent this, or to have the content muted by default.

Related Standard: 1.4.2 A

This is one in a series of posts highlighting one of more than 270 accessibility tests in Mortise.io. Come back next week for more!

Mortise Test Per Week: Ensure text can be resized via zoom up to 200% without loss of content or functionality (including overlap of text)

By Karl Groves |

CSS-13: Ensure text can be resized via zoom up to 200% without loss of content or functionality (including overlap of text)

How to test

  • Set the device or user agent zoom to 200% and confirm there is no loss of content or functionality (including overlap of text).

Exceptions

How to fix

Use responsive design to ensure that text content reflows, to remain visible and operable within the viewport, at zoom levels up to 200 percent. Media queries defined in `em` or `rem` units respond to increases in page zoom the same as decreases in viewport size. Avoid the use of `overflow:hidden` as much as possible, so that content never becomes clipped by its container, and so that scrollbars can appear to reach content outside the viewport when necessary.

Related Standard: 1.4.4 AA

This is one in a series of posts highlighting one of more than 270 accessibility tests in Mortise.io. Come back next week for more!

Mortise Test Per Week: Avoid the use of client-side redirection (e.g. META redirect/refresh) unless the user can control or prevent this.

By Karl Groves |

NAVIGATION-09: Avoid the use of client-side redirection (e.g. META redirect/refresh) unless the user can control or prevent this.

How to test

  • Determine whether the site makes use of client-side redirects which cannot be controlled or prevented.

Exceptions

  • A mechanism to turn off such redirects or refreshes is available.
  • Redirects are performed on the server.

How to fix

Avoid the user of client-side redirects entirely, unless a mechanism is available for users to control or prevent them.

Related Standard: 3.2.5 AAA

This is one in a series of posts highlighting one of more than 270 accessibility tests in Mortise.io. Come back next week for more!

Mortise Test Per Week: Do not disable or restrict page zoom on mobile devices.

By Karl Groves |

MOBILE-03: Do not disable or restrict page zoom on mobile devices.

How to test

  • Use a mobile device or emulator, cross-referenced with devtools, to confirm that page zoom is not disabled or restricted.

Exceptions

  • Content that requires this restriction for usage or meaning (e.g. video games).

How to fix

Remove the META tag or other code that restricts page zooming.

Related Standard: 1.4.4 AA and 1.4.10 AA

This is one in a series of posts highlighting one of more than 270 accessibility tests in Mortise.io. Come back next week for more!

Mortise Test Per Week: Provide an alternative for all synchronised multimedia content (e.g. a text transcript, or a link to a downloadable transcript).

By Karl Groves |

MEDIA-15: Provide an alternative for all synchronised multimedia content (e.g. a text transcript, or a link to a downloadable transcript).

How to test

  • Identify any video content, or synchronised multimedia content (e.g. flash animations), and confirm that it has a text alternative which includes all important content.

Exceptions

None

How to fix

Provide provide a text transcript for this content, which includes all the spoken word content, as well as details of any relevant visuals (e.g. text on screen) and non-spoken audio content (e.g. such as important sound effects). The transcript should be near the video content, or there should be a clearly-marked link to it near the video content.

Related Standard: 1.2.8 AAA

This is one in a series of posts highlighting one of more than 270 accessibility tests in Mortise.io. Come back next week for more!

Start your free trial of Tenon today!

Sign up now