It just irritated me that it was something that was so easy to do. I usually don't mind if it's something that simply cannot be done without JS ...yet with perhaps half an hour's work I created a version of the current IPB header that (almost!) works perfectly. In case you're wondering, it's here. There are still some issues with the positioning of the user dropdown, but I've given up on finishing it off because I've realised by doing a bit of testing here with JS off that this attitude runs right the way through IPS's products to the extent that major work needs to be done to the whole thing to bring it up to a reasonable standard. Attachments, for instance, are downright deceptive with JS off. You get the input field to upload a file, which IPB simply ignores when it's uploaded with the form, and your post goes up with no attachment. Polls, also, are completely absent. Both of these things are trivially easy to do without JS, but weren't even attempted.
I'm going to stop bothering to look for things now. I'm sure I'd find plenty more easily-avoidable issues if I looked through the whole codebase. I'll just mark that down as a point against IPB (on the off-chance that I'll need community software in the near future - yes, I realise I've been saying I might need a license soon for a couple of years now... but...
What happened to the web accessibility movement? Was it all for nothing? Should we go back to using tables for layout too, while we're at it?



Find content
Male
