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:
- The user finds a search input on the page.
- The user enters a quoted query identifying the product into that input.
- The user presses the Enter key to submit the query.
- That submission takes the user to a product page.
- 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.
- The elements containing the product name and price are coded with the
itemprop
attributes (itemprop="name"
anditemprop="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
Explanation
The components of the total score are:
pageLoad
: 2 points if it was possible to visit the pagepageFast
: 2 points if the page loaded within 4 seconds, or 1 point if it loaded within 6 secondssearchInput
: 1 point if the page contained a search inputsearchType
: 2 points if the search input consisted of aninput
element with atype="search"
attribute rather than anaria-label
orplaceholder
attribute with a value containingsearch
.searchWork
: 2 points if it was possible to submit the search query by pressing the Enter keysearchFast
: 3 points if the product page loaded within 3 seconds, 2 points if within 5 seconds, or 1 point if within 7 secondsnameInPage
: 2 points if the product name was on the product pagenameInNode
: 2 points if the product name was the value of a text node on the product pagenameProp
: 3 points if the element containing that text node had anitemprop="name"
attributeprice
: 1 point if a price appeared in the text content of the product pagepriceProximity
: 4 points if the parent element of the product-name element has a price in its text content and has a descendant element with anitemprop="price"
attribute, or 3 if this is true for a grandparent element, or 2 if true for a great-grandparent element, or 1 if true for a great-great-grandparent element.
The precise rules of spProductPrice
are found in the code itself.
Suggestions
-
__suggestions__
Report
__report__