Meeting minutes
Publication status
<Jem> mck: touchbase with daniel and shawn next week to finish all the coordination for the publication.
<Jem> ..contacting them email about publication schedule
<Jem> howard: I can get ready for the publication on sept 11 and 12 for publication
High contrast PR
<Jem> w3c/
<Jem> github: w3c/
<Jem> jongund: I have questions about strategies
<Jem> high contrast setting for users - neither of those does not have the info. only info is about forced color one.
<Jem> ...window OS is the only one which support css forced color one uing media query
<Jem> .. it is called as window themes for changing settings for system colors
<Jem> those system colors are not consistent through browsers.
<Jem> the most incidious setting is "transparent" setting in google browser and it does put white to white font.
<Jem> The examples are mentioned in the table, computed color is "transparent" in https://
<Jem> mck: color contrast will be different by OS system and themes the users choose.
<Jem> w3c/
<Jem> jongund: color contrast seems like moving target.
<Jem> mck: let's talk about the framework how to lead the discuss the color contrast topic.
<Jem> ...there are three common OS settings and only window OS is the one we can tell how to use. Two OS color setting is complex and complicated.
<Jem> .. here in APG , we can discuss how to enhance the color contrast better by showing different color contrast info such as computed colors and more.
<Jem> mck: we can think about pro and con of invert color vs forced colors.
<Jem> ... not making any changes to the existing doc and making the documentation for pros and cons. then include the guideline for high color contrast.
<Jem> from users' point
<Jem> once we know user's perspective, then we can frame that and connect the data Jon collected.