surveys icon indicating copy to clipboard operation
surveys copied to clipboard

CSS2022: How can we improve?

Open SachaG opened this issue 2 years ago • 2 comments

Some relevant comments from the "how can we improve" question.

(All comments: https://gist.github.com/SachaG/5d78c795b2e21f1585dac33458290c5d )

  • Respect prefers-color-scheme (light), and improve contrast of focus states for checkboxes.
  • MDN links to explanations of features would be helpful.
  • Don‘t use the matchup type of question.
  • Buttons don't look like buttons
  • Mark any skipped open-end questions as complete so I don't have to go back and write n/a :)
  • Less Frameworks, more actual CSS. Also pay some respect to the standards body. Neither the W3C nor the CSSWG were listed as options for resources to learn CSS from.
  • Indicate progress (x out of y or progress bar)
  • The background and font color makes my eyes a bit dizzy
  • Better outreach to represent more demographics and more transparency about what actually happens with the data once collected
  • The radio buttons and checkboxes have to get tapped twice on a touch experience. As the CSS survey, I expect better.
  • Use ranking instead of elimination tournament
  • There are so many features listed that are basically not supported in browsers, so why are you asking about them?
  • Prefer an option not to answer on some race, salary, disability
  • Salary question is missing Prefer not to say option
  • Maybe add a free form comment at the end of each section for general comments about the section. For example, I had no defined space to complain about css is js!
  • I’d love a summary page of the answers I gave so I have a list of CSS properties and YouTube videos to go learn about!
  • Ask about more common css, such as if you use float a lot still vs better layout techniques.
  • Use less US-centric race and ethnicity categories
  • Use same range for each salary level groups
  • maybe it is fun to also ask for everybody's favourite CSS feature of that year
  • there were some ui bugs. the padding kept squeezing the content between the radio buttons and the comment icon upon each item selection
  • I don't know why the next button redirects me to the GitHub repository
  • Light theme option
  • With bad internet connections, my survey progress is lost and I have to start over. Would be better if progress is also saved locally.
  • Gather information on survey respondents’ role and title at work, eg Designer vs Frontend Developer vs Manager/Director
  • better font and color. Dark mode hurts my eyes. If there's a light mode, I didn't see it (not discoverable/accessible) when filling out the survey. And even though the font has serif, it's still hard to read. Too much animation on the page, disorienting, reminds me of 90s-era web sites (crazy colors, crazy animations).
  • Carry the idea of comments completely on each possible answer.
  • make your next page button links work, I got to the broken link pages by editing the url
  • A combobox for the country input instead of a select. Separate "working" and "studying" time periods.
  • Improve the checkbox. Its difficult to select.
  • "Know of but can't/won't use because of compatibility concerns" as an option on the individual feature questions would be way better than one catch all near the end"
  • auto-scroll on answer
  • make labels of radios clickable please!
  • Maybe less questions about the bleeding-edge proposed specs and more about normal every useful css features
  • Add options for students in about me section
  • spend some money in ad campaigns to get more people to participate. More results, more accurate numbers to real cases.
  • send me a copy of the questions that I answered
  • On clicking multiple times at a option, the box shrinks in width and breaks the answer line.
  • You asked which properties I don’t use because of compatibility, but I can answer that better on the pages I’m answering about usage
  • Adding a "save and finish later" option
  • The Race & Ethnicity section only appeals to American people and disregards actual ethnicity.
  • take into account that people use css non-professionally (it's not my job), so i want to point out that my company is not actually a company but a universit
  • list Native American, Pacific Islander, or Indigenous Australian grouped is honestly disrespectful to all three cultures.
  • Sign-in form had zero labeling: an empty text input with a blank button on the left; a blank button on the right. Labels would have helped me not have to use the dev tools to figure out what did what.
  • Don't treat empty custom fields as unfilled answers, I need that 100% in every category lol
  • Maybe a question about whether someone writes production CSS anymore? I haven't committed code to prod in over a decade, I went down more of the designer path.
  • Didn't really understand why "Not in a company" wasn't an option; I'm a student, I work with CSS as a hobby (and a passion!)

SachaG avatar Nov 01 '22 11:11 SachaG

Some things addressed in the CSS 2023 edition:

  • MDN links to explanations of features would be helpful.
    • Added Reading List
  • Don‘t use the matchup type of question.
    • Replaced matchups with "top N" questions
  • Less Frameworks, more actual CSS. Also pay some respect to the standards body. Neither the W3C nor the CSSWG were listed as options for resources to learn CSS from.
    • Survey is less library-focused overall; added CSSWG
  • Indicate progress (x out of y or progress bar)
    • Added progress bar

SachaG avatar Jun 05 '23 03:06 SachaG

Visual summary: https://lookerstudio.google.com/c/reporting/8a8bdc30-d03d-4f60-b422-660dc3bf56b5/page/7DCUD

shhaine avatar Jun 14 '23 05:06 shhaine