There’s still a lot of space to discuss feature wishes, plans, ideas. You can comment to put something specific on the agenda, or just hang out with me and give me a good rant about what we should be doing. Otherwise, you risk being drawn into my own rant, but that’s also fine.
I’m starting to write a Roadmap for OCaml.org. That will take a while and I’ll be going over the previous survey feedback, but most likely it will also require some new input on topics we haven’t talked about yet (e.g. what to do with the Community section). A survey will most likely also be part of the roadmap process to make sure we’re prioritizing properly.
Actually, I just realized I’m engaged on Monday, sorry. So, here’s what I had to say:
Accessibility, accessibility, accessibility, …
Please no moving elements by default on the front page. If you want the animated cute code windows in some of the pages deeper down, ok, I’m not going to kill you over that, but make it consistently styled so I can disable it with uBlock or similar.
Please make everything accessible by keyboard, and I mean everything, giving it not just a token effort but the same love you give to mouse interface. I’m sure there is at least one handicapped person in your life; think of them using the site.
Hey Ian, joining by phone is for sure welcome, maybe next time after that.
Thanks for championing and pushing for accessibility.
I made a few improvements compared to what things were like a year ago, but sometimes I also introduced behavior that wasn’t initially keyboard-navigable (and maybe still isn’t great, and, thus, needs to be fixed).
I think we should be doing a proper, focused effort for accessibility. That starts with adding a WCAG checker to the CI, but doesn’t end there. We need a better process for the interactive elements that ensures we get them right in the first try going forward.
Tarides is not yet hiring again, but if there were a strong frontend developer candidate with solid accessibility skills and strong motivation to build what the OCaml community needs, I think they should apply. It would help close a gap in skillset. An accessibility consultant would be the next best alternative, but it’s very likely we’d be spending resources better by learning how to do it ourselves while we build new things for the community.
Contributions in this area, like bug reports, patches, or discussions on this are immensely welcome. When we’re aware something is broken in terms of accessibility, this has a high priority to fix.
