Apr 14

It’s infuriating to be landed in projects nowadays where basic best practices are still yet to be followed, such as those for Plain Old Semantic HTML.

To quote:

In order for a page to be POSH, it should conform to the following :

  • POSH pages should be validated, which can be done automatically via the W3C Markup Validation Service
  • All presentation should be handled by Cascading Style Sheets (CSS), not done in HTML (this means Tables should be used only for tabular data, not for page layout; similarly, spacer GIFs should never be used)
  • Emphasis tags, such as <b>, are presentational, so should be omitted; the same applies to <br>
  • All links (anchor tags) should point somewhere—a link which has an empty href attribute (linking to nowhere) should not be used
  • Class names should describe what the data is—not the way it should appear

I snagged this checklist as I finished my most recent contract last week, it really is something that needs to be drilled into every web developers head before they even think about writing anymore code:

  1. Does the page match the page design?
  2. Does the page work in all browsers defined within the projects minimum browser requirements?
  3. Are dynamic animations working?
  4. Does the page contain any hard coded values that should come from the back-end dynamically?
  5. Does it work without JavaScript?
  6. Does the page validate and conform to the W3 specifications for the document type you are using?
  7. Does the page meet WAI / WCAG (1.0/2.0) guidelines?
  • Share/Bookmark
Tagged with:
preload preload preload