Re: Thinking about ATAG2 Guideline A.3.1 Enhance keyboard access to authoring features

Hi all,

I'm looking forward to seeing more comments on the proposal. To kick 
things off I have a few tweaks....

1. At the moment, I'm wondering if A.3.1.2 might be interpreted such 
that a very simple paint program passes due to not having "drawing 
objects", while a vector-based tool missing only keyboard control of 
rotation would fail. So I think we need to tighten up the wording to 
apply it only to drawing interfaces supporting drawing objects.

2. Add (g) deleting existing drawing objects.

Cheers,
Jan



> Hi everyone,
> 
> I said I would send something for A.3.1...so here it is:
> 
> ISSUE:
> On a call a few weeks ago some WG members were concerned about the
> exception in A.3.1.1 ("An exception to keyboard operability is allowed
> where the underlying function requires input that depends on the path of
> the author's movement and not just the endpoints."). At the same time,
> some members were concerned about providing practical ATAG2 requirements
> in the specialized case of professional drawing tools (e.g., those often
> controlled by controllers that enter path and pressure information, such
> as a stylus). This proposal is an attempt to satisfy both concerns.
> 
> USE CASE:
> - A useful user profile to keep in mind here would be a professional
> graphic artist, who has lost steadiness in their hands due to injury, etc.
> 
> NEW DEFINITION:
> There are new terms ("Drawing functionality", "Drawing Objects") defined
> at the bottom of this message. The definition includes some examples
> that are useful to keep in mind:
> - rotating a shape in a vector graphic editor,
> - using a freehand “airbrushing” tool in a raster graphic editor,
> - resizing a div element in a WYSIWYG webpage editor,
> - adding freehand waveforms to a visual representation of audio content
> in an audio editor
> 
> NOTE ON TIMING:
> The original wording mentionned "time limits on specific keystrokes" but
> success criterion A.3.2.2 handles this. We can remind people in the
> "Intent" sections.
> 
> PROPOSAL:
> 
> A.3.1.1 Non-Drawing Keyboard Access: All functionality of the authoring
> tool, except *drawing functionality*, is operable through a keyboard
> interface (Level A):
> Note: For drawing functionality, see success criterion A.3.1.2.
> 
> A.3.1.2 Drawing Keyboard Access (Minimum): The following *drawing
> functionality* (if present) is operable through a keyboard interface
> (Level A):
> (a) inserting new drawing objects; and
> (b) selecting drawing objects; and
> (c) moving drawing objects; and
> (d) modifying the overall size of drawing objects; and
> (e) rotating drawing objects; and
> (f) adding/editing text for drawing objects
> Note: It is possible to implement keyboard access directly (e.g.,
> keyboard-driven manipulation of drawing objects) or indirectly (e.g.,
> keyboard editing of drawing object property values).
> 
> A.3.1.3 Avoiding Content Keyboard Traps: *UNCHANGED*
> 
> A.3.1.4 Drawing Keyboard Access (Intermediate): Any drawing
> functionality of the authoring tool is operable through a keyboard
> interface, except where the input depends on the path of the author's
> movement and not just the endpoints.
> Note: It is possible to implement keyboard access directly (e.g.,
> keyboard-driven manipulation of drawing objects) or indirectly (e.g.,
> keyboard editing of drawing object property values).
> 
> A.3.1.5 Keyboard Shortcuts: *UNCHANGED*
> 
> A.3.1.6 Drawing Keyboard Access (Enhanced): Any drawing functionality of
> the authoring tool is operable through a keyboard interface. (Level AAA)
> Note: It is possible to implement keyboard access directly (e.g.,
> keyboard-driven manipulation of drawing objects) or indirectly (e.g.,
> keyboard editing of drawing object property values).
> 
> A.3.1.7 Customize Keyboard Access: *UNCHANGED*
> 
> New Definitions:
> *Drawing functionality:*
> Authoring tool functionality that involves adding or modifying graphical
> representations of content (e.g., rotating a shape in a vector graphic
> editor, using a freehand “airbrushing ” tool in a raster graphic editor,
> resizing a div element in a WYSIWYG webpage editor, adding freehand
> waveforms to a visual representation of audio content in an audio
> editor). *Drawing objects* are graphical representations of content that
> remain independently selectable, in contrast to graphical
> representations that do not remain selectable (e.g., when drawing
> actions are made directly to a single raster graphic).
> 
> 
> 
> 
> Thoughts?
> 
> Cheers,
> Jan
> 
> -- 
> Jan Richards, M.Sc.
> User Interface Design Lead
> Adaptive Technology Resource Centre (ATRC)
> Faculty of Information
> University of Toronto
> 
>    Email: jan.richards@utoronto.ca
>    Web:   http://jan.atrc.utoronto.ca
>    Phone: 416-946-7060
>    Fax:   416-971-2896

Received on Friday, 13 November 2009 21:28:31 UTC