[Design] accessibility built-in not added-on.

[Jeremy McGee (Bassett)]

As well as the accessibility issues Allen discusses, it will also be
important to ensure that localization and translation capabilities are
included in the core product. 

Together with more obvious solutions like resourcing all strings, the
subtleties include

* sort orders and collation sequences
* support for multi-byte character sets
* support for non-Roman character sets, including Chinese and Arabic
* support for right-to-left text - and display layouts

In some of these areas, existing email and PIM clients do
satisfactorily. In others they most certainly don't. 

These features can be very expensive and time-consuming to build in to a
finished product. Even if the initial releases are in U.S. English only,
building a localizable framework means that other (third party?
commercial?) organizations can build out localized versions. 

Oh, and adding to Allen's comment, a voice-driven version would be
really very cool. But that's perhaps another product.

-- Jeremy