Accessibility test digest

Synopsis

Page: __org__

URL: __url__

Score: __totalScore__

Tested by: Testaro, procedure tpProductPrice

Scored by: Testilo, procedure spProductPrice

Digested by: Testilo, procedure dpProductPrice

Introduction

This is a report on transactional accessibility. Suppose a person is visiting a website and wants to engage in some transaction with it. Is the transaction easy, predictable, and safe? If so, the website is transactionally accessible. To achieve transactional accessibility, websites can design transactions that conform to the most common and standard conventions. Then users will correctly guess what to do at each step. Users with some disabilities will especially benefit from being able to use existing knowledge and tools, without the need to discover how to do things on a website.

This transaction involves finding the price of a product. The transaction begins when a person opens the home page of a vendor of the product. The user wants to find the price at which the vendor offers the product. The test assumes that there is a standard transaction structure in such a situation:

  1. The user finds a search input on the page.
  2. The user enters a quoted query identifying the product into that input.
  3. The user presses the Enter key to submit the query.
  4. That submission takes the user to a product page.
  5. On the product page, there is a description of the product offering, containing both the full name of the product and the price at which the vendor offers the product.
  6. The elements containing the product name and price are coded with the itemprop attributes (itemprop="name" and itemprop="price", respectively) specified by the Schema.org standard for the price property.

As of this version of spProductPrice, the itemprop="priceCurrency" attribute is not considered; Schema.org recommends using USD rather than $ as the currency identifier for the United States dollar in association with that itemprop value.

Thus, instead of the user needing to figure out how this particular website discloses product prices, the user is assumed already to know how websites normally do that. Instead of exploring the site to find its method, the person uses the standard method.

Procedures

The Testaro application used its tpProductPrice testing procedure to evaluate the accessibility of this transaction on the __org__ web page at __url__ on __dateSlash__. Testaro produced a report.

The Testilo application processed the report and used the spProductPrice scoring procedure to compute a score for the transaction. The total score is __totalScore__ (where 0 is the worst and 24 is the best possible score). The scored report is appended below.

Finally, Testilo used procedure dpProductPrice to produce this digest, briefly explaining how spA11yMessage computed the scores.

Score summary

__scoreRows__
Score components

Explanation

The components of the total score are:

The precise rules of spProductPrice are found in the code itself.

Suggestions

Report

__report__