Accessibility as a Service

Accessibility Concerns for Content Staff

Content creators have an overarching objective: Coming up with eye-grabbing, attention-stealing content that entices and informs their website visitors.

Something that tends to be overlooked is making sure that their published content is fully accessible according to Web Content Accessibility Guidelines (WCAG). From the readability of written content to the formatting of images, tables, and other multimedia components, achieving accessibility can seem daunting to creators who are far removed from web development or HTML coding.

Continue reading “Accessibility Concerns for Content Staff”

Mortise Test Per Week: No non-emergency interruptions, or interruptions can be prevented or postponed by the user.

TIMEOUTS-04: No non-emergency interruptions, or interruptions can be prevented or postponed by the user.

How to test

  • Identify instances of content which is automatically updated, and confirm that there is a mechanism to turn off or postpone the updates.

Exceptions

  • Real-world emergencies, such as a hurricane warning.

How to fix

Consider making automated content updates optional: provide a user control for turning content updating on and off. Otherwise, provide a means to temporarily turn off automated content updates, either for a specified time or at the user’s discretion.

Related Standard: 2.2.4 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: Visible labels at least partially match accessible names, ideally the beginnings of the strings.

KEYBOARD-11: Visible labels at least partially match accessible names, ideally the beginnings of the strings.

How to test

  • Identify each instance of an interactive control which has a visible label.
  • Use devtools or a screen reader to ensure that the accessible name at least partially matches the visible text.

Exceptions

  • Where a visible text label does not exist for a component.

How to fix

Ensure that the visible label matches, or at least partially matches, the accessible name. If the match is only partial, then it’s preferable that the visible label matches the start of the accessible name. Form fields can be given accessible labels which are partly different from their visible label using the `aria-label` attribute. However it is almost always best to allow the visible text to function as the accessible label, rather than using ARIA.

Related Standard: 2.5.3 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: Automatic timeouts can be extended, except where caveats apply.

TIMEOUTS-02: Automatic timeouts can be extended, except where caveats apply.

How to test

  • Identify instances of timeouts which occur automatically or due to user inactivity, and confirm that the user has a means of turning off, adjusting or extending the timeouts.

Exceptions

  • Where non-extendable timeouts are required (e.g. realtime auctions and some online games).
  • Where extending the time limit would invalidate the activity (e.g. an exam).
  • Where incomplete user data is preserved for at least 20 hours.

How to fix

Consider removing any time limits on the input of user data. Otherwise, provide an explicit means of turning off, adjusting or extending the time limit.

Related Standard: 2.2.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: Notification content does not disappear automatically.

TIMEOUTS-05: Notification content does not disappear automatically.

How to test

  • Identify instances of notification content (e.g. toast banners), and confirm that they do not disappear automatically.
  • Exceptions

    • The user has the ability to turn of the auto-disappearing behaviour.
    • The notifications are part of a real-time event or are essential to the activity.

    How to fix

    Consider removing any time limits on notification content, and have it permanently displayed with a manual close button. Otherwise, provide a means for users to turn off the auto-disappearing behaviour.

    Related Standard: 2.2.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!

    Start your free trial of Tenon today!