Skip to content

Latest commit

 

History

History
82 lines (44 loc) · 3.08 KB

accessibility-checklist.md

File metadata and controls

82 lines (44 loc) · 3.08 KB
Raw

FAST Checklist for Secure Payment Confirmation

The following evaluation is based on the FAST checklist.

Note: This checklist was created in August 2022 in preparation for Candidate Recommendation. Since that time, the Working Group made (or plans to make) two additional non-editorial changes regarding an opt-out feature and removal of a user activation requirement. January 2023 updates to this checklist take those changes into account.

If technology allows visual rendering of content

SPC does not include any features that result in rendering content in a page.

When Secure Payment Confirmation is called at authentication time, the browser displays the following information in a transaction dialog owned by the browser:

  • payeeName and/or payeeOrigin (both strings)
  • instrument displayName and icon (an image or link to an image). The specification discusses how to use the displayName as alt text for the icon.
  • Transaction total and currency (both strings).
  • Instructions for requesting that the relying party forget stored authentication credentials ("opt-out"). This feature is optional in the API; by default no opt-out experience is shown in the transaction dialog.

If technology provides author control over color

N/A

If technology provides features to accept user input

N/A

If technology provides user interaction features

  • The transaction dialog includes browser-owned buttons to cancel, proceed with Web Authentication, or (optionally) to ask that the relying party forget stored authentication credentials.
  • Accessibility considerations for WebAuthn are documented in that specification.

If technology defines document semantics

N/A

If technology provides time-based visual media

N/A

If technology provides audio

N/A

If technology allows time limits

If technology allows text content

  • The SPC transaction dialog includes both an icon and string to help the user identify the relevant payment instrument.

If technology creates objects that don't have an inherent text representation

N/A

If technology provides content fallback mechanisms, whether text or other formats

N/A

If technology provides visual graphics

N/A

If technology provides internationalization support

N/A

If technology defines accessible alternative features

N/A

If technology provides content directly for end-users

N/A

If technology defines an API

  • SPC relies on the user agent to generate a user interface (the transaction dialog). Previous review of Secure Payment Confirmation concluded there was no need to review the specification (issue 14) and the specification is largely the same since that review.

If technology defines a transmission protocol

N/A