Baseline assignments:
Enter in the Status column the category to which each technique belongs for your baseline. Categories are:
Enter any additional comments in the Comments column.
| Num | Technique | SC | Graphical | Future | ||
|---|---|---|---|---|---|---|
| Status | Comments | Status | Comments | |||
| 1.1 | Avoid javascript: URIs for form actions. | GL 4.1 Level 1 SC 1 | O | although the technique really is a best practice |
O | Optional but still a good idea |
| 1.2 | Avoid using images with onclick="form.submit()" as submit buttons. | GL 2.1 Level 1 SC 1 | S | although tech. could show adding an onkeydown handler to catch enter key |
O | Optional but still a good idea |
| 2.1 | Avoid javascript: URIs. Attach events using DOM event attributes. | GL 4.2 Level 1 SC 1 | O | O | Optional but still a good idea | |
| 2.2 | Avoid document.write() and innerHTML(). | GL 4.2 Level 1 SC 1 | O | avoid document.write() since it won't work in XHTML; well placed document.write() and use of innerHTML do seem to work in most graphical UAs and ATs |
O | Optional but still a good idea |
| 2.3 | Avoid changing focus on the user. | GL 2.1 Level 1 SC 1 | O | most current UA and ATs do okay with focus() (plus I need it for the DHTML roadmap :-) |
S | |
| 2.4 | Avoid device-dependent events, or use both keyboard- and mouse-based functions. | GL 2.1 Level 2 SC 1 | S | S | ||
| 2.5 | Use the onactivate event in place of onclick. | GL 2.1 Level 2 SC 1 | NR | this technique is currently wrong |
S | |
| 2.6 | This task wille describe an accessible method for interactive menus, also known as "DHTML menus". | GL 1.1 Level 1 SC 1 | S | hopefully when completed |
S | Honestly, not enough information in technique to make a call. |