Obv it's your prerogative to decide whether you'd like to make what you publish online more or less accessible, just as it's your decision how you use your livejournal. This post is just a how-to for people who have the inclination to make their posts more accessible, perhaps because they do use their livejournals as websites. I think more people these days use their LJ as an archive for their fanfiction. I know some of my stories get tens of thousands of hits over the years; I personally see value in making those pages as accessible as possible to people with differing abilities and technologies.
To be honest/in my opinion/etc I don't think it's correct in itself to say that "there is a right way and a wrong way" to code, because if using i's and b's is wrong then why would it be valid in the first place?
I don't want the inference that I'm ignoring this bit of your comment, but I don't particularly feel inclined to engage with it. Mainly because to address your point I'd have to dig back into the history and process of web development, programming and so forth in order to explain my word and presentation choice on the level you're questioning it. And I think that as a "how-to" post, I feel this makes pretty clear the options available to your non-pro, basic users who are interested in accessible publishing. Being built on the foundations of my professional skills/opinions/experiences, I am confident that this post fulfils this purpose just fine.
Basically, I don't think this is the space to get into a debate or discussion about the background of web programming, web content accessibility guidelines, and personal preference on who you want to make the content you publish online accessible to.
no subject
To be honest/in my opinion/etc I don't think it's correct in itself to say that "there is a right way and a wrong way" to code, because if using i's and b's is wrong then why would it be valid in the first place?
I don't want the inference that I'm ignoring this bit of your comment, but I don't particularly feel inclined to engage with it. Mainly because to address your point I'd have to dig back into the history and process of web development, programming and so forth in order to explain my word and presentation choice on the level you're questioning it. And I think that as a "how-to" post, I feel this makes pretty clear the options available to your non-pro, basic users who are interested in accessible publishing. Being built on the foundations of my professional skills/opinions/experiences, I am confident that this post fulfils this purpose just fine.
Basically, I don't think this is the space to get into a debate or discussion about the background of web programming, web content accessibility guidelines, and personal preference on who you want to make the content you publish online accessible to.