This article had been really helpful.Thank you for sharing

Good questions :)

1. I’d say yes – it’s good for us to know you’ve been through this and how you see this being helpful, or not. Would also be good for proposals to reflect on what kind of further testing is needed, and how much time to dedicate to that.
2. That’s debatable – either yes, more of this in different places. Or we change how we do colors to start with, so we only change the colors in one place and it reflects everywhere.

See for example the concept of design tokens, and how the Spectrum design system uses this for colors.

@janehughes might have more to say about all of this!

Thank you. I had been going through the admin interface. I had seen the styleguide specifically.I shall be exploring it further

hello,
I was going through a few articles and was wondering if we can use -
CSS Custom properties while using the @ media (for high contrast active). This will allow using of variables in multiple places according to the requirement for different compenents. Creating a basic CSS Custom properties for a range of colors and widths and sizes, we can utilize the same at different places , making the code much organized and easily accesible.
Apart from this, I have noticed that a web browser plays a crucial role into deciding for a display mode, Are we using windows high contrast mode only or will we consider Forced color display mpde too as it is available on most browsers including chrome whereas high contrast is supported only on edge (little unsure about the availibilty though)

if we can use CSS Custom properties while using the @ media (for high contrast active)

It’s definitely possible. What you’re proposing seems like a very promising approach to me, definitely worth having on your proposal. Most likely we’d start the project by doing further research to validate this as an approach.

Are we using windows high contrast mode only or will we consider Forced color display mpde too

As far as I understand, "forced-colors" and Windows High Contrast Mode (WHCM) / Contrast themes are the same thing currently. "forced colors" is what it’s called in W3C specifications because it’s a concept that can be applied across lots of browsers / operating systems, but WHCM is currently the implementation.

Also as far as I understand, WHCM works in all browsers on Windows, although with differences (Firefox’s implementation is simpler). We’ll definitely want to consider supporting all variants of "forced colors" themes, though WHCM on Edge is the one that’s the most common.

I think I convyed the high contrast and forced color part in wrong way. I meant if we shall consider forced color display mode (i.e using forced-color) OR legacy high contrast (i.e -ms-high-contrast)
I am suggesting if we can use the display mode that works for most browsers( forced-color) and yet create one more css for other browsers like (-ms-high contrast) internet explorer or safari where forced color doesnt work properly. These Css files could be downloaded or put inside a package(this i am still debating on how to implement) and be used during the wagtail installation by user who have exceptional browsers.

Hi @AAC2001, welcome :) Please have a look at our Google Summer of Code 2022 wiki page, and for this project in particular, look at the links we shared above. If you have further questions let us know.

Hello, @thibaudcolas Nice to talk with you :) would please provide me in which process I have to prepare proposal pdf which was asking to submit.

• Reason
• I am FREASHER to this. so, actually I didn't have any projects and internships before . So,please help me in this.
• Just tell me how to prepare that's enough . After that , I will prepare .
• I think you will help to me in this.

THANKING YOU,

Sure, please see this post: https://wagtailcms.slack.com/archives/CTL4SFX29/p1649101509755349.