I agree with Jamie.
An application shouldn't special case anything wrt it's accessibility
API implementation depending on such a screen reader present flag.
It doesn't matter who is asking for the information for what ever reason.
Someone asks for information, so he should get it.
When we
An important feature of web browser today is the ability to navigate rich
content editable areas. This feature is standardized in HTML 5. IBM,
Mozilla, and other members of the open community have been working hard on
addressing keyboard navigation. Alex Surkov, Mozilla, is creating a
document
Hi Alex,
This is just a first pass:
Starting with this link:
https://wiki.mozilla.org/Accessibility/RichContentKeyboardBehaviour
In ARIA widgets you say that ARIA is all about screen readers. That is not
true. Most AT solutions: Voice recognition technology, alternate input
devices,
