Web Accessibility is well known by all but, if there is a misconception of what exactly web accessibility means - http://en.wikipedia.org/wiki/Web_accessibility. Now with everyone on the same page I will get to my point (Author Accessibility). Author Accessibility is not practiced by the majority of web developers.
Author Accessibility includes the following:
1. Naming conventions
2. Correct markup
3. Author notation
1. Naming conventions - Naming conventions are a huge asset to a developer. For instance, if you name something left or the famous leftCol then when the time the content is switched over to the right side there is a mass confusion. This causes bad 'author accessibility'. A good example of good 'author accessibility' is related-content or main-content. If these get switched they will still be explaining what they are describing and keeping consistent accessibility.
2. Correct markup - Correct markup is the right markup for the job. If you have a headline followed by a sub-headline for example,
<h2>Paris growing in population</h2>
Also, remember that presentation has no part of data. So keep correct markup in mind before thinking presentation.
3. Author notation - Author notation is great in the aspect of telling other developers where certain blocks of coding start and stop as well as telling them what the blocks of coding are. Also, this practice is good for debugging an invalid page. Some times with cluttered coding or templated code the tabbing gets out of line. With author notation this would clear everything up for the author.
4. Validation - Validation needs to be set in stone so that the page is not having issues prior to an unclosed tag or etc. A majority of the time issues for layout happens because of lack of validation. This is one of the most important aspects of 'author usability'.
5. Components - Components are snippets of coding that help the present developer from reinventing the wheel each time. Components also help workload and CSS bulk.