Recently I visited some of our clients in Australia. We had several meetings with existing long term clients and some engaging sessions with new prospects. It is clear that accessibility is high on the agenda of the Australian public. There is a major effort to implement WCAG2.0 and the knowledge level of the Australian webmasters about the topic is impressive. A few things were striking during the long meetings that we had; online text to speech is an excellent tool to help the accessibility of a website, and most of our existing and new clients understand that and see that as one of the reasons to implement ReadSpeaker on their website. The usage statistics for the ReadSpeaker services are excellent and I was pleased to see such a large group of keen ambassadors of our solutions. During the meetings, we discovered another striking new way of using ReadSpeaker for accessibility purposes. A way that we had not envisaged before. In several of our meetings with the Australian Federal government departments, it became clear that many of the PDF and Word documents that are displayed on the government’s website are not accessible. They have been produced in times when accessibility was not an important attribute. Lay-out and design took the forefront. This has created a major task for government institutions, as all information needs to be accessible by year end 2012. Some of the more innovative departments have been using our ReadSpeaker docReader tool on their websites to read PDF documents. The perfect reading of these documents depends on their level of accessibility; the better they are tagged, the better they are read. This fact has led some departments to use ReadSpeaker in a slightly different way. It has become a gate keeper to test a document on its accessibility before it is published on a website. When someone wants to publish a document (from inside the department or from an external agency), ReadSpeaker docReader is now being implemented as a checker on the staging/testing server. Any PDF, ODF, Word document can be checked on its correct accessibility tagging by running it through the docReader tool. If it reads correctly, it is correctly tagged. This proves to be a great help for the creators of the content. In many cases these are external agencies that create these documents for the Federal government. Our clients have found an interesting way to use the ReadSpeaker products to help them test the accessibility of their own content. That is probably one of the best proofs of the alignment of ReadSpeaker to the online accessibility goals of WCAG2.0. While I was in Australia, Julia Gillard, Australia’s prime minister, launched the National Year of Reading. Australia is facing 4.5M people with literacy issues. That is a stunning 20% of the 22M population in Australia. These percentage numbers are similar in other developed countries across the globe. The ReadSpeaker technology offers a great help for these struggling readers, not only by assisting them to read and understand the content of the online texts, but also by helping them to learn to read better. Our technology of synchronized text highlighting while listening offers the capability to learn to read better over time.