W3C home > Mailing lists > Public > w3c-wai-au@w3.org > October to December 2006

Technique Review: HTML code view editor (Part A only)

From: Jan Richards <jan.richards@utoronto.ca>
Date: Mon, 30 Oct 2006 09:37:49 -0500
Message-ID: <45460E3D.5090003@utoronto.ca>
To: w3c-wai-au@w3.org


Back in mid-Sept I signed up for a techniques review 
Here is my first installment - from the perspective of HTML code view 
editors (Part A only):


PROPOSED changes to A.2.1 and A.2.2 already sent to AU list: 

GENERAL IDEA: Sufficient techs LABEL should be highlighted.

A.1.4: EDIT TECHNIQUE FOR Checkpoint A.1.4: Technique A.1.4-1.1 
[Sufficient]: Separating the author's display settings for fonts, 
colors, sizing (zoom), etc. from content presentation settings so that 
the content presentation settings, but not the author's display settings 
are used within the markup that is actually produced.

A.1.5 is short on examples

A.2.1: BREAK UP INTO 3 - Sufficient in combination? - Technique 
A.2.1-1.1: [1] Providing sequential keyboard access (with different 
keystrokes) for moving the focus between user interface areas (e.g., 
from the menus to the editing view to the floating toolbars, etc.) and 
editing views. [2] Also provide sequential keyboard access (with 
different keystrokes) for moving the focus within all of the controls 
within each user interface area (e.g., the menu items, the editing view 
objects, the floating toolbar controls) and editing view. [3] Also 
provide the ability to operate any control with the keyboard alone.

A.2.1: BREAK INTO 3 - Sufficient in combination? Technique A.2.1-2.1 [1] 
For sequential keyboard access, ensuring that as each control receives 
focus, no activation is made automatically that would prevent further 
sequential navigation. [2] For direct keyboard access, ensuring that as 
the control receives focus, it is only activated if the controls has 
only one setting (e.g., a particular menu item). [3] Ensuring that when 
controls with more than one setting (e.g., drop down menus) receive the 
focus no setting is automatically activated.

A.2.1: SC3: Need to modify to take into account that TAB can also be an 
authoring key - e.g. to indent

Examples lacking in A.2.1

A.2.2: Examples lacking in A.2.2

A.2.5: Technique A.2.5-1.1 would benefit from a code view example

A.2.5: Need to be clear that code views should be able to SELECT entire 
elements etc.


If people agree I will put together the actual changes to address the 


Received on Monday, 30 October 2006 14:39:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:39:54 UTC