Mortise Test Per Week: Ensure custom dialogs or lightboxes (including the control that opens them) follow the defined interaction pattern(s).

ARIA-09: Ensure custom dialogs or lightboxes (including the control that opens them) follow the defined interaction pattern(s).

How to test

  • Identify instances of dialogs or lightboxes (apart from alert or message dialogs).
  • Assess their semantics and interactions and confirm that they follow the applicable Dialog (Modal) pattern (https://www.w3.org/TR/wai-aria-practices/#dialog_modal).
  • Assess whether the expectations conveyed by their design match the pattern they use (i.e. that they look like what they are).
  • Identify instances of alert or message dialogs.
  • Assess their semantics and interactions and confirm that they follow the applicable Alert and Message Dialogs pattern (https://www.w3.org/TR/wai-aria-practices/#alertdialog).
  • Assess whether the expectations conveyed by their design match the pattern they use (i.e. that they look like what they are).

Exceptions

None

How to fix

Re-implement this widget to follow either the Dialog (Modal) pattern (https://www.w3.org/TR/wai-aria-practices/#dialog_modal) or the Alert and Message Dialogs pattern (https://www.w3.org/TR/wai-aria-practices/#alertdialog) that’s applicable to the design and functionality.

Related Standard: 1.3.1 A and 4.1.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 that charts and graphs do not rely on a single sensory characteristic.

NON-TEXT-CONTENT-13: Ensure that charts and graphs do not rely on a single sensory characteristic.

How to test

  • Identify instances of charts or graphs and confirm that each area of the graph or chart has more than one way to differentiate their information (e.g. combinations of color, pattern, or text).

Exceptions

  • Where the graph or chart is purely decorative.

How to fix

Use more than one sensory characteristic to differentiate different areas of graphs and charts. For example, use both color and and patterns/texture (hash, lines, crosses, dots, etc).

Related Standard: 1.3.3 A and1.4.1 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: Provide audio descriptions for all prerecorded video content, which are complete and do not skip important content.

MEDIA-05: Provide audio descriptions for all prerecorded video content, which are complete and do not skip important content.

How to test

  • Review any pre-recorded video content and assess whether the visual information in the video is available in the audio track (including on-screen text and important visual details).
  • If not, confirm that an audio description track is available which provides this information.

Exceptions

  • Where all the visual information in the video track is already available in the audio track.

How to fix

Provide audio descriptions for the video. This may mean providing an alternative version which has audio descriptions built-in to the audio track, or use a video player which supports switchable audio descriptions.

Related Standard: 1.2.5 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: If multi-point or path-based pointer gestures are used, ensure that a single-pointer non-path alternative is provided.

LANG-21: If multi-point or path-based pointer gestures are used, ensure that a single-pointer non-path alternative is provided.

How to test

  • Identify instances of functionality that requires multi-point or path-based pointer gestures.
  • Confirm that that functionality is also available by another means which does not require such gestures.

Exceptions

  • A multi-point or path-based gesture is essential (e.g. providing a signature on a touch screen).

How to fix

Provide an additional mechanism for every complex gesture (e.g. supplement pinch and zoom with keyboard accessible zoom buttons).

Related Standard: 2.5.1 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 custom sliders follow the defined interaction pattern(s).

ARIA-11: Ensure custom sliders follow the defined interaction pattern(s).

How to test

  • Identify instances of single-thumb sliders.
  • Assess their semantics and interactions and confirm that they follow the applicable Slider pattern (https://www.w3.org/TR/wai-aria-practices/#slider).
  • Assess whether the expectations conveyed by their design match the pattern they use (i.e. that they look like what they are).
  • Identify instances of multi-thumb sliders.
  • Assess their semantics and interactions and confirm that they follow the applicable Slider (Multi-Thumb) pattern (https://www.w3.org/TR/wai-aria-practices/#slidertwothumb).
  • Assess whether the expectations conveyed by their design match the pattern they use (i.e. that they look like what they are).

Exceptions

None

How to fix

Re-implement this widget to follow either the Slider pattern (https://www.w3.org/TR/wai-aria-practices/#slider) or the Slider (Multi-Thumb) pattern (https://www.w3.org/TR/wai-aria-practices/#slidertwothumb) that’s applicable to the design and functionality.

Related Standard: 1.3.1 A and 4.1.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!

Start your free trial of Tenon today!