Accessibility test digest
Synopsis
Page: __org__
URL: __url__
Score: __totalScore__
Tested by: Testaro, procedure tpA11yMessage
Scored by: Testilo, procedure spA11yMessage
Digested by: Testilo, procedure dpA11yMessage
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 learning how to report a web-page issue. The transaction begins when a person opens a web page and notices an accessibility issue on the page. The user wants to report that issue to whoever is responsible for the website. The test assumes that there is a standard transaction structure in such a situation:
- The user finds an accessibility link on the page.
- The user clicks that link.
- That link takes the user to an accessibility page.
- On the accessibility page, there is a link for sending an email message about accessibility, and there is another link for making a telephone call about accessibility.
Thus, instead of the user needing to figure out how this particular website accepts accessibility issue reports, the user is assumed already to know how websites normally accept such reports. So, instead of exploring the site to find its method, the person uses the standard method.
Procedures
The Testaro application used its tpA11yMessage
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 spA11yMessage
scoring procedure to compute a score for the transaction. The total score is __totalScore__ (where 0 is the worst and 23 is the best possible score). The scored report is appended below.
Finally, Testilo used procedure dpA11yMessage
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 secondsa11yLink
: 1 point if the page contained a link whose name includedaccessibility
a11yLinkWork
: 2 points if clicking the link produced a new pagea11yLinkFast
: 2 points if the new page loaded within 3 seconds, or 1 point if it loaded within 5 secondsa11yPageTitle
: 1 point if the new page had a titlea11yTitleGood
: 2 points if the title includedaccessibility
a11yPageH1
: 1 point if the new page had 1 level-1 headinga11yH1Good
: 2 points if that heading includedaccessibility
mailLink
: 2 points if the new page contained any email (mailto:
) linkmailLinkName
: 2 points if the name of an email link includedaccessibility
, or 1 point if the context of an email link (i.e. the text content of its parent element) includedaccessibility
telLink
: 2 points if the new page contained any telephone (tel:
) linktelLinkName
: 2 points if the name of a telephone link includedaccessibility
, or 1 point if the context of a telephone link includedaccessibility
The precise rules of spA11yMessage
are found in the code itself.
Suggestions
-
__suggestions__
Report
__report__