With 10 years of experience in speech enabling the web, it is more than time to broaden the scope than just making content speak on the web and in mobile phones. In these 10 years, as you all know, the web has gone through a number of dramatic changes. From being all about information, it is now about transaction, interaction and socializing. How can web based speech enabling improve these areas? To start with, text is still the problem to a lot of people. Statistics about reading difficulties for example have not changed just because the web has moved forward. Actually, the more that day to day activities get online, the greater the digital divide gets. Exclusion rather than inclusion. That doesn’t feel so 2010. Sure, speech enabling the web is not the answer to all questions and is not the answer to all prayers, but it sure is a means in reducing the digital divide. On-line banking and other financial services, government and company e-Services, E-commerce, surveys etc all interact with the users with some kind of online form where they can exercise various tasks whenever they like. Apart from being very convenient for the user, it is also a cost saver for the organization offering these services. Automated processes, case handling systems, online customer support services make a large number of organizations more efficient. However, have they made all necessary efforts to make the front end as usable and accessible as possible? Not making a form accessible and usable is as wise as putting a 1,76 meter tall and 0,48 meter wide door 50 centimeters from the ground as the only entrance to the supermarket. With average height, width and gymnastic skills you can come in, and if not, you don’t. Since we know that speech enabling does help a lot of people, we developed a prototype of what came to be ReadSpeaker formReader. We implemented it on a few forms (e-services) at a municipality website in Sweden. We also gathered a test group with people from different disability groups (plus a few elderly and some non-native speaking persons). After the test phase, we did as we normally do when developing a new product, we went back to the drawing table incorporating the results from the user tests. Speech enabling forms helps. To be able to have audio prompts that tell you what to fill in and a voice that reads back what you have written/chosen proves to be very useful. With more people being able to fill out the forms themselves, and fill them in accurately (thanks to the “proof listening”), the organization offering the service gets a better value for their investment. And since formReader works pretty much like a screen reader, the requirements on the forms are the same. Meaning that they should be properly coded according W3C/WCAG guidelines. During the implementation of the formReader on the municipality website, a couple of easily solvable accessibility issues became very obvious and were easily corrected by the municipality web developers. So the result was, regardless if you chose to activate formReader or not, a better and more accessible web form. CSUN2010_ReadSpeaker_formReader_Presentation