> The problem with these readability scores is that they don't take into
> consideration the way html works. For instance you very rarely put a
> full stop in a heading tag (eg: <h1>Hello.</h1>) but this will affect
> most of the scores as that word will now be added to the next sentence
> and make it longer then it actually is. And with lots of headings you
> actually making the page more readable. Ditto for lists as (atleast at
> my work) we don't generally put a full stop after a list item. Running
> the scores on one of our pages (http://www.accc.gov.au/content/
> index.phtml/itemId/815360) I initially get a Flesch Kincaid Grade
> Level of 24.9 (if I run it over the entire page) and 18.2 if I strip
> the html tags out. But I get a much better score of 8.3 if I add full
> stops after the correct tags before stripping the tags out. Of course
> running it over just the content I start with a reading level of 11,
> but I still end up with the 8.3 I add the full stops. I would suggest
> that the code should be modified to take this into consideration. It's
> only a few lines of extra code and I'm happy to check in my changes to
> a branch if possible.