Re: Creating Web Payments logo

Please also keep in mind during the design the new contrast requirements
from W3C spec WCAG 2.1** and ensure the design has good contrast within
itself to be distinguishable in low light on small screens. See
Understanding
<https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast.html>1.4.11
Non-text Contrast
<https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast.html>.

** Success Criterion 1.4.11 Non-text Contrast (Level AA)
The visual presentation of the following have a contrast ratio of at least
3:1 against adjacent color(s):

User Interface Components
Visual information required to identify user interface components and
states, except for inactive components or where the appearance of the
component is determined by the user agent and not modified by the author;

Graphical Objects
Parts of graphics required to understand the content, except when a
particular presentation of graphics is essential to the information being
conveyed.

** katie **

*Katie Haritos-Shea*

*Principal ICT Accessibility Architect, **Board Member and W3C Advisory
Committee Rep for Knowbility *

*WCAG/Section 508/ADA/AODA/QA/FinServ/FinTech/Privacy,* *IAAP CPACC+WAS = *
*CPWA* <http://www.accessibilityassociation.org/cpwacertificants>

*Cell: **703-371-5545 <703-371-5545>** |* *ryladog@gmail.com
<ryladog@gmail.com>* *| **Oakton, VA **|* *LinkedIn Profile
<http://www.linkedin.com/in/katieharitosshea/>*

People may forget exactly what it was that you said or did, but they will
never forget how you made them feel.......

Our scars remind us of where we have been........they do not have to
dictate where we are going.


On Thu, Jul 12, 2018 at 4:13 AM, Eiji Kitamura <agektmr@google.com> wrote:

> ​​
> Hi all,
>
> Not sure if I posted the link previously but Ian kindly raised an issue on
> GitHub where we can discuss about the logo.
> https://github.com/w3c/webpayments/issues/250
>
> I've just added a new comment. Please join the discussion.
> (Sorry if I didn't post the link before)
>
> Thanks
>
>
> On Wed, Jun 27, 2018 at 5:35 PM Eiji Kitamura <agektmr@google.com> wrote:
>
>> Hi all,
>>
>> I'm Eiji, a developer advocate at Google working on the open web focusing
>> on payments and identity from Tokyo Japan.
>>
>> As Payment Handler is becoming a good shape and being shipped on Chrome ,
>> I think it's good time to determine web payments' official logo. I heard
>> there were efforts to create one in the past but didn't come to a
>> conclusion.
>>
>> I'd like to hear your opinion on
>> - if we should do it
>> - how we should do it
>>
>> Luckily, Ian has already come up with set of expectations to the logo
>> https://github.com/w3c/webpayments/wiki/Brand
>>
>> Let's follow that. And on top of what he suggested, I think:
>> - Web payments logo can represent this effort and it will be far easier
>> for people to identify a payment solution is one of web payments even they
>> have never seen it before..
>> - The logo can be a symbol across web, merchant and payment industries
>> and will unite us together.
>>
>> I'm thinking if we can use the logo for
>> - Generic payment button (launches Payment Request UI instead of specific
>> payment app directly)
>> - A sticker on a technical documentation that means the technology is
>> based on web payments
>>
>> If there are enough interest, I'd like to determine how we should move
>> things forward.
>> Let first tell us what you think.
>>
>> Thanks.
>>
>> P.S. There's a Web Payments slack and some of us have been discussing
>> about this for sometime. Please feel free to join.
>> https://join.slack.com/t/webpayments/shared_invite/
>> enQtMjQyNDI4Mjg4NjQ2LWIyYjAyMDE1MGM1YTNiYjM4NzI4OThhYzlhZjk2
>> M2RmMDQyODk1ZWY4MzQ2ZGMxZTY0MmMxOWYzNzY3YzNlMDg
>>
>>
>> --
>> Eiji Kitamura | Developer Advocate | google.com/+agektmr |
>>  +81-80-1150-6480
>>
>
>
> --
> Eiji Kitamura | Developer Advocate | google.com/+agektmr |
>  +81-80-1150-6480
>