346
edits
Accessibility/SummaryPost1.9: Difference between revisions
→The following may wait until after 3.1
| Line 68: | Line 68: | ||
<ul> | <ul> | ||
<li> Difficulty: high (need to work with standards groups & AT vendors, API design is unclear) | <li> Difficulty: high (need to work with standards groups & AT vendors, API design is unclear) | ||
<li> Note: HTML WG is looking at ways of allowing MathML inside text/html. That would lead to increase usage. | |||
<li> Impact: 508 compliance, ability to access diagrams and custom widgets, Web 2.0 accessibility | <li> Impact: 508 compliance, ability to access diagrams and custom widgets, Web 2.0 accessibility | ||
<li> Estimate: 1 month | <li> Estimate: 1 month | ||
| Line 75: | Line 76: | ||
<ul> | <ul> | ||
<li> Difficulty: extremely high (need to work with standards groups & AT vendors, API design is unclear) | <li> Difficulty: extremely high (need to work with standards groups & AT vendors, API design is unclear, keyboard navigation is always difficult in Gecko) | ||
<li> Note: HTML WG is looking at ways of allowing SVG inside text/html, which would lead to increased usage. | |||
<li> Note: Opera already implements SVG keyboard navigation, so we should look at what they have done | |||
<li> Impact: 508 compliance, ability to access diagrams and custom widgets, Web 2.0 accessibility | <li> Impact: 508 compliance, ability to access diagrams and custom widgets, Web 2.0 accessibility | ||
<li> Estimate: 2 months | <li> Estimate: ARIA work - 2 months, Keyboard navigation work - need to scope work .. wild guess is 6 weeks | ||
</ul> | </ul> | ||