Re: Orca Firefox 3 and inline html editors

[Benjamin Hawkes-Lewis <bhawkeslewis googlemail com>]

There are several ways this could be tackled, and they are perhaps best
used in combination:

1. Persuade the webmasters or HTML editor developers to add the relevant
ARIA classes so that AT-SPI would be able to tell Orca that the user was
in an editing area.

2. Look for tell-tale signs of common HTML editor widgets. This may be a
lot easier once IAccessible2 gives Orca better DOM access. If it would
be possible to notify Orca that you are in an editable control given
such tell-tale signs, we could look into compiling a list of tell-tale
signs for common editors. If tell-tale signs do not exist, ask
developers to add them. So the question is, if we spotted a particular
class or id, for example, would Orca be able to assume it's an editable
control?

3. Specific scripts for URIs that match a given expression may be
especially important for homebrew or customized editor widgets.

4. Having a key-sequence to notify Orca that you are in an editable
control doesn't sound like such a bad idea, but there may well be
technical obstacles to this that are not obvious to me.

--
Benjamin Hawkes-Lewis