We don't have any built in conditional support. There's the @first helper which works for when you only want to check if @index == 0. To do this, I'd suggest adding a helper for whatever condition you need.
Question regarding accessibility
I echo @julian's sentiments. In this project my priority is UX (user experience), and my work doesn't mean squat if users who do not have the privilege of sight can't even comprehend messages posted on forums.
I'm very interested in helping, please get the right people connected with me and I'll give it a shot!
I'd love to just hear how your users read even this thread, maybe attempt to post.
I'm sure its not great at all. That said, our project is all about evolving by user expectations. The same thing will happen in this case, I will 100% assure you.
I've just tested some access via lynx.
The most important issue is that I cannot login.
I always get
Since I'm not using lynx on a regular basis (only when I really have no X server running), I don't know how to observe the traffic more detailed.
OK, I also see that it's "read-only" in Lynx. I assume that means that people using it won't be able to post, just read the forums. Is that a bug or the desired behavior?
(I can't test it out because, as mentioned, the login doesn't work.)
Maybe that language should be revisited "your viewing experience" to "your browsing experience"
I would imagine logging in is the first of many problems we will encounter, I'd be surprised if posting would work off the shelf
We use websocket for posting, so that's an instant no-go. If the composer fell back to using xhr, that would work.
This looks like a great opportunity to improve accessibility. +1
Thanks for devoting some attention to this, appreciate it!
One question - as mentioned, some of my users typically just use email to browse mailing lists and etc. Is it possible to use nodeBB as a listserv in that way? That is, is there a way to get notifications for every new post and comment, and reply via email, etc, like you can with Yahoo groups or Google groups? That would also help with accessibility a bit.
FWIW, it's a few years later -- I was able to log in via elinks (a lynx variant used by one of our members), and though the interface was a little messy it worked. Search seemed to not work (or I wasn't using it right), but I could browse. Writing a reply to a post seemed impossible though, as I got "403 forbidden." Have not tried with JAWS or the like yet. I'm not sure if this is on the roadmap to change but here is a quick note that these are the results as of June 2018.