Working on a web app for creating accessible color palettes. ๐ It gives you precise control of the hue/saturation/lightness curves of each swatch and lets you easily check the WCAG contrast of color pairings. #Accessibility#a11y#WCAG#design
@colmtuite@OnnenMusic It's mostly devs who don't design that are overly excited about it because OKLCH looks like an automated solution to pick colors without a designer? All palettes I look at tweak chroma + hue as the lightness of a color changes, so lightness changes only isn't going to look great?
@meodai Is https://t.co/b4iiDjMIAo relevant for the tools list? It's an accessible color palette creator that uses HSLuv along with WCAG2 and APCA contrast checking. :)
@AdhamDannaway Any thoughts on if you need both heading and paragraph text, or if one is enough? I often see modals that repeat the same phrase like this and it feels redundant. Why not something like this with a heading and no paragraph?
"Save post to drafts?
[Save post] [Discard post]"
@PureRinFunction@PureRinFunction Woo, thanks! Let me know if you've got any feedback on features you'd like to see next or just to chat about palette design. ๐
@lukasoppermann@lukasoppermann Thanks Lukas! ๐ Getting all the small parts right and figuring out the control point UI for curve editing was more work than I expected. Most tools focus on autogenerating colors but I really wanted something that let me easily customize everything.
Great #tool to generate #accessible#colorScales https://t.co/RfcdGOiG39 I built something similar at work, but never got around polishing it enough to open source it. Great to see @seanw_org did. โค๏ธ
Quick dark mode exploration using the accessible color palette editor I'm working on. ๐ The colors pass WCAG and APCA contrast checks. I'll link to the palette editor below if you want to try and have any feedback! ๐งต #accessibility#a11y
My Chrome extension is 50% off the 1st year for Black Friday! https://t.co/B3z8ItTQw5 ๐ Checkbot tests 100s of pages at once for SEO, speed & security issues like broken URLs, duplicate titles, bad HTML, insecure pages & 50+ more checks. #buildinpublic#seo#webdev#blackfriday
My Chrome extension is 50% off the 1st year for Black Friday! https://t.co/B3z8ItTQw5 ๐ Checkbot tests 100s of pages at once for SEO, speed & security issues like broken URLs, duplicate titles, bad HTML, insecure pages & 50+ more checks. #buildinpublic#seo#webdev#blackfriday
@hypeddev@DesignTokens "colorSpace": "srgb", "components": [1, 0, 1]
[1, 0, 1] means full red, no green, full blue within sRGB color space. It depends what color space you specify and the ranges for the color space. For sRGB, valid values are between 0 and 1.
@vponamariov I always go with B now, sentence case, same as e.g. Google and Apple. I think people go with B to try to look professional and important, but it comes across as stuffy and old-fashioned now. There's multiple styles of B (https://t.co/1oStLl6meH) so it's hard to be consistent too.
@adamwathan The separation that's useful in practice: content goes in a database or Markdown/YAML/JSON files. There's no point separating HTML + CSS.
I've never seen a redesign where the pull-request diff was only to CSS files lol. It's like nobody wants to admit it's a pipe dream. โจ
@adamwathan My feelings from misunderstandings about Tailwind is you need to push "reuse styles via templates instead of CSS classes", "HTML and CSS always change together so there's no way to separate concerns there", and "inline styles are more verbose and can't do media queries".
@asidorenko_ So my understanding is Typescript works as normal, but not for these kinds of problems where you try to access server-only stuff from the client code.
@zander_supafast It's worth mentioning some common exceptions here though e.g. chat/post and search inputs. I can't think of any sites that show visible labels for these, so it looks odd if you include one, and for these cases you're not likely to forget what the field was for.