- From: Marcos Cáceres <notifications@github.com>
- Date: Thu, 25 Aug 2016 21:01:30 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
Received on Friday, 26 August 2016 04:02:08 UTC
I don't have an opinion re: accessibility, but I do share @annevk's concerns about RFC2119 terms in non-normative text: It can lead to unintentional confusion, particularly because a lot of people (both devs and implementers) end up relying on notes to understand the spec text so they can take the "should" as RFC2119 SHOULD and so on. -- 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/browser-payment-api/issues/240#issuecomment-242624535
Received on Friday, 26 August 2016 04:02:08 UTC