Knowledgebase

Testing Accessibility Compliance Print

  • softwaretestingqa, software, errors, downtime, guide, howto, solution, zillionkinghost
  • 0

Verifying against standards.

WHAT STANDARDS EXIST

Published guidelines defining success criteria at several levels.

WHAT LEVEL IS COMMONLY REQUIRED

The middle level, in most regulations and procurement requirements.

WHAT THE PRINCIPLES COVER

  • Perceivable: content available to the senses available
  • Operable: usable by any input method
  • Understandable: predictable and clear
  • Robust: working with assistive technology

WHAT TO TEST AUTOMATICALLY

Contrast ratios Missing alternative text Form fields without labels Heading structure Language declaration

WHAT PROPORTION THAT COVERS

A minority of the criteria.

WHAT MUST BE TESTED MANUALLY

Keyboard operation of every function Focus order and visibility Screen reader announcement Meaningful alternative text Error identification and correction

WHY ALTERNATIVE TEXT CANNOT BE AUTOMATED

A tool can confirm it exists, not that it is useful.

WHAT TO CHECK ABOUT KEYBOARD USE

That nothing is unreachable That focus is always visible That focus is never trapped

WHAT TO TEST WITH

At least one screen reader, on its usual platform.

WHAT TO DOCUMENT

Which criteria are met, and which are not.

WHY

Procurement and regulation ask for exactly that.

WHAT TO INVOLVE

People who use assistive technology.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot