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

SC Needing Attention

From: Kelly Ford <Kelly.Ford@microsoft.com>
Date: Mon, 14 Nov 2011 20:59:40 +0000
To: WAI-ua <w3c-wai-ua@w3.org>
Message-ID: <FDD93DBB2C16D643AABC1A7111D149F32E17A6B8@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
Hello,

>From our previous reviews, the below SC were items we felt needed work that do not have open actions.  If you feel strongly about taking one of these on, please let me know by EOD Tuesday.  Otherwise I'll make a bbest guess on assignments with Jim and Jeanne.

Thanks to Jim for the spreadsheet tracking all these reviews.


#

level

wording

comments

111

a

Configurable Default Rendering: The user can specify which types of alternative content to render by default.

needs work - handle wrong

112

a

Browse and Render: When a rendered element has alternative content, the user can render alternatives according to the following: * synchronized alternatives for time-based media (e.g. captions, audio descriptions, sign language) can be rendered at the same time as their associated audio tracks and visual tracks, * and non-synchronized alternatives (e.g. short text alternatives, long descriptions) can be rendered as replacements for the original rendered content.

address the ability to have the alternative content presented to you without replacing the default verison, e.g. display title or alt text in pop-up or tooltip?

124

aaa

Broken Alternative Content:  The user can be notified when the user agent cannot render alternative content (e.g. when captions are broken).

this sounds like what people curse about MSWord, predicting what you want to do. or what it thinks you mean

131

a

 Highlighted Items: The user can globally specify that the following be highlighted so that each class is uniquely distinguished. It is not the intention that all recognized enabled elements be uniquely distinguished, just that they be distinguished from disabled elements. a. selection, b. active keyboard focus (indicated by focus cursors and/or text cursors), c. recognized enabled elements, d. presence of alternative content, e. recently visited links

review, too many options, should say "these could include". should remove f. presence of alternative content

133

aa

Highlighted Input Controls: The user can have the following highlighted when they are recognized: (a) enabled controls that take input (e.g. push buttons, radio buttons, check boxes, and text input fields, but not groupings or static text and images) regardless of whether they are read-write or read-only, and (b) elements with scripted input handlers (e.g. images or text ranges that have onClick or onKeyPress events) regardless of whether the current state allows them to operate.

review, reword, add auditory

1111

a

Access Relationships: The user can access explicitly-defined relationships based on the user's position in content (e.g. show form control's label, show label's form control, show a cell's table headers).

check action item, otherwise YES

1112

aaa

Extended Link Information: The user agent provides for each link:  * link title, * technology type (of the linked Web resource), * internal/external: (whether the link is internal to the resource e.g. the link is to a target in the same Web page)

mail thread

211

a

Keyboard Operation: All functionality can be operated via the keyboard using sequential or direct keyboard commands that do not require specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints (e.g. free hand drawing). This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.

working on bluedog term

216

a

Separate Selection from Activation: The user can specify that selection is separate from activation (e.g. navigating through a set of radio buttons without changing which is the active/selected option)

complicated.

224

aa

Options for Wrapping in Navigation: When user interaction with web content causes focus wrapping at the@@, the user can prevent wrapping or the user can receive feedback when wrapping



275





jeanne has action ?moved? Not in document

342

a

Avoid Side Effects of Navigation: The user can move the keyboard focus without causing the user agent to take any further action, other than the presentation of information (e.g. scrolling or pop-ups that do not change the focus or selection).



415

a

Write Access: If the user agent keeps an internal representation of the user content in terms of element structure, relationships between elements, element meaning, or some combination thereof, it must expose this internal representation via an appropriate means (normally by using the platform accessibility architecture or a programmatically available DOM).



521

a

Web-Based Accessible (Level A) : User agent user interfaces that are rendered using Web standard technologies conform to WCAG Level "A".



522

aa

Web-Based Accessible (Level AA) : User agent user interfaces that are rendered using Web standard technologies conform to WCAG Level "AA".



523

aaa

Web-Based Accessible (Level AAA) : User agent user interfaces that are rendered using Web standard technologies conform to WCAG Level "AAA".



542

a

Handle Unrendered Technologies: If the user agent does not render a technology, the user can choose a way to handle content in that technology (e.g. by launching another application or by saving it to disk).
Received on Monday, 14 November 2011 21:00:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 14 November 2011 21:00:19 GMT