Tuesday, March 29, 2011

What's coming next, and in what order...

A couple of days again I had a chance to bring together the "What's Coming Next" document for Project metalmouth. After completing the "Tidy up" part which, I'm sure, is a re-occuring activity in most projects it is now time to move on - in fact I called it "Moving toward a more complete off-screen model...".

However, the thought struck me today that it would be most useful to implement the next items in the off-screen model in a sequence which would benefit actual users the most - but how?

It will need a lot more thinking about...

As always, if you are using the extension or just like the intensions behind the project (I already like you and think your wonderful) I would ask you to get involved in the project (especially user testing, feature requests, etc...) - otherwise, maybe just providing a link to the project website (http://code.google.com/p/metalmouth/) so that others may more easily find it.

2 comments:

  1. You should maybe consider detailing how to launch the program with the flags mentioned, as most users my self included won't know how to do this. Also, are you considering putting in keystrokes for read to end, navigating headings, etc? Tabbing to the desired option seems a bit clunky for users coming from screen readers such as nvda.

    ReplyDelete
  2. Hi, many thanks for your comment.

    My instructions on the "Getting
    started: Step-by-step guidance on getting started..." web page (found
    at http://code.google.com/p/metalmouth/wiki/GettingStarted) were not
    as clear as they should have been.

    I have now updated step two in the
    step-by-step sequence to include information from google on how to
    start the Chrome browser in the desired way. In addition, I have been
    in touch with one of the chrome.experimental.tts developers who
    suggests that this API might be taken out of experimental in the very
    near future (I will seek an update) - which would mean that you would
    no longer need to do step two (sooner the better I say)...

    With regard to keystrokes - I had initially used HTML accesskeys, but took them out as they were starting to get a little clumsy. Instead, I had tried to simplify what appeared in the toolbar.

    However, I think I now have a more user friendly approach for keystrokes which I shall detail in the "Whats coming next" web page (found at http://code.google.com/p/metalmouth/wiki/WhatsComingNext) - and try and implement next...

    Thanks once again...

    ReplyDelete