Re: [w3c/payment-request] Section for A11Y Considerations (#450)

(Sorry, I thought I had said this when it was timely :( Apparently not.)

> From @chaals' reference to HTML AAM [1] I am gathering that the idea would be to map the data flowing through the system (e.g., address, currency, amount, and so forth) to familiar platform-specific accessibility APIs.

Not at all. The idea would be to say, as noted in @marcoscaceres' comments on the PR, that it is vital that the data presented is accessible to users. Pushing them to an accessibility API is not going to achieve that for most users, and is quite possibly unnecessary even for the few users who can potentially benefit from it.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-request/pull/450#issuecomment-328848527