CSUN musings

Presentation went very well. Thanks all! for being on the Working Group. It
was an honor to speak about and a representative for our efforts! 

Jeanne and I rewrote the presentation several times. I read UAAG20 at least
3 times and WCAG a few also, and ARIA and the security last call. Amidst all
the reading and talking with lots of folks things popped up. 

1. should UA control rendering of tooltips - what happens on other
platforms. Do non-Windows platforms also use an OS widget to render the
@title or whatever else that may be rendered using 'tooltip'. I have helped
many folks who are confused that scaling/zooming web pages has no effect on
tooltips. 

2. should UA flag the state of High Contrast in the OS so that javascript
'knows' and can adjust the rendering of Web2 widgets (sliders etc)

3. should the UA keep a dynamic current keybinding list of what the user has
set in the UA and Content. This would be different than the help or
documentation which would only list the default UA settings. 

4. proposed Success Criteria 4.1.2 order of precedence - User has the option
to change order of precedence of keybinding (UA, javascript, accesskey,
etc.) AAA (does not exist, does it need to be added?)

5. content vs UI - security information appears in UI address bar but it is
generated by meta information in content. 
this is fuzzy- where do we draw the line. Address bar is UA component, but
author can add information (images). Security Certificate information
appears there. We have talked about it before. I don't recall what we
decided. 

6. aria landmarks, they should be part of in-page structured navigation
list. Do they show up as links? Are there keybindings? Can the UA discover
them and reveal them to the user. 

7. UAAG20 lets the user change bindings, but we have no restore default
keybindings. A new SC or just rewrite the existing to include restore to
default?

8. CSS content injection - css spec this content should not appear in the
DOM. How can the UA communicate CSS info to accessibility api? Should there
be a CSS DOM. If author's insert content via CSS it will fail WCAG. I don't
want that it must pass WCAG to be a fall back for everything. 

9. where is the boundary between content and function. This is by line
between WCAG and UAAG. Because there is currently no UA that renders @title
from the keyboard ARIA has example code (five lines of HTML and JavaScript)
to make something that looks like a tooltip show up from the keyboard for
aria widgets. But it is not a title attribute. So millions of authors have
to write this example code and ship it across the net because UAs don't
render @title from the keyboard. Hopefully they write it correctly. Having
the example code for this and other functions included as assets in
authoring tools is not the answer. UAs should render @title from the
keyboard!  This is a function! Authors should not have to write functions.
Are there other things like this?

10. rendering @title from keyboard. There should be a delay just like the
mouse functions for the tooltip to appear. Should this delay be user
settable?  Scenario: user tabbing through content every tab causes tool tip
to appear and disappear for every item. Very annoying.  

11. need to update those places where we have "can recognize". Flash
animations, embedded audio, etc. these are all examples of nested user
agents (the base/parent UA is a compound document). The base UA cannot
recognize the content. But, the user agent that is rendering the embedded
content does recognize the content and can control it. Can recognize should
be removed for those instances. 

12. How can a user quickly move to nested user agents to stop
jumping/flashing/noise content. Do we need an api or browser function to
jump to nested user agents for quick navigation. Should navigation to
embedded UAs be added to the structured navigation SC?

13. If/when video is native to the UA should Search also include searching
the native media (captions). 

14. Should search pass onto other embedded UAs (mathml or svg, etc.). the
content is on the base page. The markup language changed from html to svg
and back to html. Should inpage search include all content regardless of
markup? Maybe this is a non-issue. Just thought I would bring it up.

15. Keybindings and other inaccessible practices yet to be discovered that
JAVASCRIPT allows authors to do. Should we recommend that UAs have an api or
some mechanism for JavaScript parser (or JS authoring methods) that would
communicate bindings, and other important accessibility information to the
browser so it can pass it on to the accessibility api?

Jim Allan, Accessibility Coordinator & Webmaster
Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
"We shape our tools and thereafter our tools shape us." McLuhan, 1964

Received on Wednesday, 25 March 2009 22:45:49 UTC