| ... | ... | @@ -17,3 +17,11 @@ Developers want to use MathJax outside the DOM for testing. MathJax depends on t |
|
|
|
Authors want to know how fast MathJax should be. Authors and Developers want to track down performance bottlenecks.
|
|
|
|
|
|
|
|
We want to be able to test speed enhancements.
|
|
|
|
|
|
|
|
### Accessibility
|
|
|
|
|
|
|
|
Users want their AT tools to pick up MathJax-generated content just as well as regular MathML.
|
|
|
|
|
|
|
|
AT vendors want to use a robust API to seamlessly integrate with MathJax rendering. This currently includes User preference negotiation, Highlighting, Sync-Highlighting and copy & paste.
|
|
|
|
|
|
|
|
Open source solutions (like Benetech's prototype or possibly ChromeVox) want to integrate into MathJax to provide math speech text and other data for passive AT on mobile platforms. |
