3 ms·

Hello. Thanks for your comments :-) Don't worry, Open Tech Calendar will never go Static - there are to many features that just won't work. However, the static

Hello. Thanks for your comments :-) Don't worry, Open Tech Calendar will never go Static - there are to many features that just won't work. However, the static site was something we tried as an experiment to make us look afresh at this problem. We may carry on with it someday, but it has already driven a bunch of code quality improvements in the main app which is great. If you are interested, could you join https://groups.google.com/forum/#!forum/openacalendar https://groups.google.com/forum/#!forum/openacalendar ? This is for the Open Source software, and we discuss features and design issues there. Very happy to have any constructive criticism discussion there! But let me try and address some points very quickly now, tho it's late and I'm off to a hackday tomorrow! (That's the Excuses in :-) ) 1. I want to recheck all font sizes - they've all been picked piecemeal. I do want to make sure the fonts are slightly large tho - while I have no problem with lower size fonts I know some people with vision problems do. For the max width, do you want it wider than 1200px? We actually have just done some design work that touches on this: https://groups.google.com/forum/#!topic/openacalendar/HvsKB3IXmag https://groups.google.com/forum/#!topic/openacalendar/HvsKB3... The image isn't really meant to be fully detailed, it's just to add a bit of texture. I was thinking of trying some different images, maybe it's time to! 2. Thanks! :-) 3. I would like to be clearer on the legal side, but I have some questions of my own about legal points and could really do with a discussion with a friendly lawyer! But rest assured I want the data to be open for all sensible uses. Anyway, hopefully this makes sense. Please do join the email list or email hello at the site domain with more points. Thanks, James

davb 10y ago
Hi, well thanks for listening :) I'll take a little look at the Google Group tomorrow and would like to give some feedback! I think the project is fantastic. I've got a couple of little follow-up comments on accessibility... One important thing to remember about visually impaired users is that they almost always have their base font size in their browser set high already, or are using a magnifier. So 150% of an already large font becomes an unusably ginormous font. While the intention is definitely good, it can have the opposite effect (I speak from experience working with both technical and non-technical family members who are partially sighted). A base size of 14-16px (depending on font), increasing to 1.5em or 2em for headers works really well, and doesn't overcompensate when visually impaired users have their own font magnifying solutions in place (as they most often do because they're needed for the vast majority of websites). And in terms of the max width, I'd definitely take it down from 1200px. Long lines are harder to read [0 (also a really good example of readable width)]. Playing with the site in Chrome dev tools, "max-width: 54em;" works really well. It stops the right-aligned/floated elements being across a wide chasm from the left-aligned elements, and it keeps line lengths at a really readable limit. And by using ems instead of pixels, if visually impaired users have a higher base font size (which doesn't scale non-text elements with sizes in pixels), it won't distort the page layout. [0] http://baymard.com/blog/line-length-readability http://baymard.com/blog/line-length-readability
- jarofgreen 10y ago
  > almost always have their base font size in their browser set high already I've come across people who don't - but still, maybe this is generally the way to go. Thanks for your detailed feedback and encouragement. I've made 2 issues at https://github.com/OpenACalendar/OpenACalendar-Web-Core/issues/649 https://github.com/OpenACalendar/OpenACalendar-Web-Core/issu... and https://github.com/OpenACalendar/OpenACalendar-Web-Core/issues/650 https://github.com/OpenACalendar/OpenACalendar-Web-Core/issu... - but if you had time to comment on the Google Group that would be great :-)

davb 10y ago

Hi, well thanks for listening :) I'll take a little look at the Google Group tomorrow and would like to give some feedback! I think the project is fantastic. I've got a couple of little follow-up comments on accessibility... One important thing to remember about visually impaired users is that they almost always have their base font size in their browser set high already, or are using a magnifier. So 150% of an already large font becomes an unusably ginormous font. While the intention is definitely good, it can have the opposite effect (I speak from experience working with both technical and non-technical family members who are partially sighted). A base size of 14-16px (depending on font), increasing to 1.5em or 2em for headers works really well, and doesn't overcompensate when visually impaired users have their own font magnifying solutions in place (as they most often do because they're needed for the vast majority of websites). And in terms of the max width, I'd definitely take it down from 1200px. Long lines are harder to read [0 (also a really good example of readable width)]. Playing with the site in Chrome dev tools, "max-width: 54em;" works really well. It stops the right-aligned/floated elements being across a wide chasm from the left-aligned elements, and it keeps line lengths at a really readable limit. And by using ems instead of pixels, if visually impaired users have a higher base font size (which doesn't scale non-text elements with sizes in pixels), it won't distort the page layout. [0] http://baymard.com/blog/line-length-readability http://baymard.com/blog/line-length-readability

jarofgreen 10y ago
> almost always have their base font size in their browser set high already I've come across people who don't - but still, maybe this is generally the way to go. Thanks for your detailed feedback and encouragement. I've made 2 issues at https://github.com/OpenACalendar/OpenACalendar-Web-Core/issues/649 https://github.com/OpenACalendar/OpenACalendar-Web-Core/issu... and https://github.com/OpenACalendar/OpenACalendar-Web-Core/issues/650 https://github.com/OpenACalendar/OpenACalendar-Web-Core/issu... - but if you had time to comment on the Google Group that would be great :-)