preload

Accessibility Testing Requirements – Understandable – Input Assistance

Posted by Albert Gareev on Oct 27, 2014 | Categories: AccessibilityReviews

In the series of reviews I’m looking at WCAG level A / AA (Web Content Accessibility Guidelines) requirements from testing perspective.

Common Definitions

Human Testing

  • Brief – “You know as you see it” – quick scanning is sufficient to check and make a judgment. This does not include effort of logging defects.
  • Detailed – Either interaction (execution of tests) with the functionality is necessary or detailed review/analysis must be done in order to verify a requirement.

Tool-Assisted Checking

  • Not Available – Tools cannot help in checking for the specified requirement or they help very insignificantly.
  • Partial – Tools provide significant help in checking for the specified requirement, either by saving time in parsing content source or through visualization. Human does the verification and judgment.
  • Full – Tools capable of locating and verifying the specified requirement. Brief review of checking results is sufficient to make a judgment.

Understandable – Input Assistance

Help users avoid and correct mistakes.

This can be completely covered with proper functional testing.

Error Identification

Required form elements or form elements that require a specific format, value, or length provide this information within the element’s label (or if a label is not provided, within the elements title attribute).

Human Testing – Detailed

Tool-Assisted Checking – Not Available

This is part of functional testing.

However, if requirements are generic, testers to step beyond and investigate in details for each input control.

Form Validation Errors

If utilized, form validation errors are presented in an efficient, intuitive, and accessible manner. The error is clearly identified, quick access to the problematic element is provided, and user is allowed to easily fix the error and resubmit the form.

Human Testing – Detailed

Tool-Assisted Checking – Not Available

This is part of functional testing.

However, if requirements are generic, testers to step beyond and investigate in details for each input control.

Labels or Instructions

Sufficient labels, cues, and instructions for required interactive elements are provided via instructions, examples, properly positioned form labels, and/or fieldsets/legends.

Human Testing – Detailed

Tool-Assisted Checking – Not Available

This is part of functional testing.

However, if requirements are generic, testers to step beyond and investigate in details for each input control.

Error suggestion

If an input error is detected (via client-side or server-side validation), provide suggestions for fixing the input in a timely and accessible manner.

Human Testing – Detailed

Tool-Assisted Checking – Not Available

This is part of functional testing.

However, if requirements are generic, testers to step beyond and investigate in details for each input control.

Error prevention (Legal, Financial, Data)

If the user can change or delete legal, financial, or test data, the changes/deletions can be reversed, verified, or confirmed.

Human Testing – Detailed

Tool-Assisted Checking – Not Available

This is part of functional testing.

This needs to be properly addressed by design.

QA can cover this with functional testing and raise concerns on where the requirement is not fulfilled.


  • Leave a Reply

    * Required
    ** Your Email is never shared

Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported
This work by Albert Gareev is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported.