Accessibility/Whitelist: Difference between revisions
Jump to navigation
Jump to search
DavidBolter (talk | contribs) (Created page with '== Problem == Our accessibilty module is intended as a solution for assistive technology (AT). Tools that are not AT invoke our engine, but need only a portion of what we provi…') |
DavidBolter (talk | contribs) No edit summary |
||
| Line 11: | Line 11: | ||
== Implementation == | == Implementation == | ||
=== Baseline | === Baseline Features === | ||
Non-AT tools: anti-spyware, auto form tools, tablet pc... | Non-AT tools: anti-spyware, auto form tools, tablet pc... | ||
| Line 19: | Line 19: | ||
{| cellspacing="1" cellpadding="1" border="1" style="width: 527px; height: 178px;" | {| cellspacing="1" cellpadding="1" border="1" style="width: 527px; height: 178px;" | ||
|- | |- | ||
! scope="col" | Required Feature | ! scope="col" | Required Feature | ||
! scope="col" | Confirmed? | ! scope="col" | Confirmed? | ||
! scope="col" | Notes | ! scope="col" | Notes | ||
|- | |- | ||
| focus events | | focus events | ||
| yes | | yes | ||
| we just know this | | we just know this | ||
|- | |- | ||
| value change events | | value change events | ||
| | | <br> | ||
| | | <br> | ||
|- | |- | ||
| | | <br> | ||
| | | <br> | ||
| | | <br> | ||
|- | |- | ||
| | | <br> | ||
| | | <br> | ||
| | | <br> | ||
|} | |} | ||
<br> And things we know they don't need: | |||
<br> | |||
{| cellspacing="1" cellpadding="1" border="1" style="width: 529px; height: 118px;" | {| cellspacing="1" cellpadding="1" border="1" style="width: 529px; height: 118px;" | ||
|- | |- | ||
! scope="col" | Unused Feature | ! scope="col" | Unused Feature | ||
! scope="col" | Confirmed? | ! scope="col" | Confirmed? | ||
! scope="col" | Notes | ! scope="col" | Notes | ||
|- | |- | ||
| text events | | text events | ||
| | | <br> | ||
| bypassing should help perf | | bypassing should help perf | ||
|- | |- | ||
| mutation events | | mutation events | ||
| | | <br> | ||
| bypassing should help perf | | bypassing should help perf | ||
|- | |- | ||
| | | <br> | ||
| | | <br> | ||
| | | <br> | ||
|- | |- | ||
| | | <br> | ||
| | | <br> | ||
| | | <br> | ||
|} | |} | ||
=== Additional Implementation Ideas === | |||
Investigate a [https://bugzilla.mozilla.org/show_bug.cgi?id=538594#c86 lossy throttle] for our event queueing and firing, for non-AT only. | |||
Revision as of 19:27, 10 June 2010
Problem
Our accessibilty module is intended as a solution for assistive technology (AT). Tools that are not AT invoke our engine, but need only a portion of what we provide (at great cpu expense).We do not want to regress our solution for AT at all. We don't want to completely break non-AT. We want to improve peformance for all cases but this topic is specifically about keeping known AT safe from any risky performance improvements.
Proposal
- Develop a list of AT that we can detect, and a method of detecting them.
- Figure out what baseline accessibility is required by non-AT.
- Manage expectations; put the word out there (blog etc)
Implementation
Baseline Features
Non-AT tools: anti-spyware, auto form tools, tablet pc...
We need to figure out the list of requirements for these tools:
| Required Feature | Confirmed? | Notes |
|---|---|---|
| focus events | yes | we just know this |
| value change events | ||
And things we know they don't need:
| Unused Feature | Confirmed? | Notes |
|---|---|---|
| text events | bypassing should help perf | |
| mutation events | bypassing should help perf | |
Additional Implementation Ideas
Investigate a lossy throttle for our event queueing and firing, for non-AT only.