ISSUE-41 |
OPEN |
We do want the ability, need to research how it is done today - to know if search of alternative, embedded, or plugin content is acceptable to make it a requirement. |
2009-08-20 |
|
0 |
| ISSUE-40 |
OPEN |
We do want the ability, need to research how it is done today - to know if it is acceptable to make it a requirement. |
2009-08-20 |
|
0 |
| ISSUE-42 |
OPEN |
Move tests for User Agent into Guideline 1 Techniques |
2009-09-03 |
|
0 |
| ISSUE-43 |
OPEN |
Review UAAG20 and ISO 9241-171 remove duplicate items |
2009-09-10 |
|
0 |
| ISSUE-45 |
OPEN |
There is some concern about the mixing/over-ride of app-supplied key |
2009-09-24 |
|
0 |
| ISSUE-44 |
OPEN |
Cross referencing text search, structured navigation, with media info |
2009-09-17 |
|
0 |
| ISSUE-39 |
OPEN |
Need to work on the definition of 'important' so it can be used as an objective measure. |
2009-07-30 |
|
0 |
| ISSUE-38 |
OPEN |
Review "the user has the option to be able to navigate via the keyboard" |
2009-07-30 |
|
0 |
| ISSUE-33 |
OPEN |
API include the following in techniques or understanding document. \"Implementing APIs that are independent of a particular operating environment (as are the W3C DOM Level 2 specifications) may reduce implementation costs for multi-platform user agents a |
2009-02-12 |
|
0 |
| ISSUE-32 |
OPEN |
In the definition of platform accessibility architecture, the final sentence refers to the need for a DOM. Make sure this concept is clearly covered by Principle 2 |
2009-02-12 |
|
0 |
| ISSUE-34 |
OPEN |
Take definition of configure, control, user option from the 21 January Editor's draft and move it to Techniques document. |
2009-02-19 |
|
0 |
| ISSUE-35 |
OPEN |
Think about interactions between user agents and AT around viewport creation and responsibilities. |
2009-04-09 |
|
0 |
| ISSUE-37 |
OPEN |
UA definition - Adobe AIR, Google Gears, UA behavior, stand alone web app that may or may not actually connect to the web. Is an html rendering tool that never goes on the web a user agent. |
2009-06-18 |
|
0 |
| ISSUE-36 |
OPEN |
Keyboard efficiency, for screenreaders and speech users. cognitive load from GL comments (micorsoft wordding) |
2009-05-14 |
|
0 |
| ISSUE-46 |
OPEN |
HTML5 comment UAWG16 on 4.10 Forms asks that the author be able to style the errors in form submission. We should add to UAAG 2.0 thta the user should be able to style error messages. |
2009-10-08 |
|
0 |
| ISSUE-47 |
OPEN |
HTML5 Comment UAWG06 scrolling elements into view. We need to add a requirement to override automatic scrolling |
2009-10-08 |
|
0 |
| ISSUE-56 |
OPEN |
Definition of important or structural elements are vague, rewrite |
2009-11-06 |
|
0 |
| ISSUE-55 |
OPEN |
4.1.7 seems ambiguious, apply only to UI toolbars, menus; or apply also to content - groups of radio buttons |
2009-11-05 |
|
0 |
| ISSUE-57 |
OPEN |
Create low priority search - regular expressions, word forms, colors, text attribute - bold etc. |
2009-11-06 |
|
0 |
| ISSUE-58 |
OPEN |
Searching from base UA through embedded UAs (time based object, svg, etc). how is user to know difference between natively rendered video (html5) and embedded video (quicktime). should the base UA query the embedded UA for its search results. |
2009-11-06 |
|
0 |
| ISSUE-60 |
OPEN |
Need a requirement for out of the box installation present options for interface |
2009-11-07 |
|
0 |
| ISSUE-59 |
OPEN |
Are there other Undo or errors that UAAG needs to consider? Do we need new SC? |
2009-11-06 |
|
0 |
| ISSUE-54 |
OPEN |
Do we have a SC to support OS conventions for cut copy paste etc |
2009-11-05 |
|
0 |
| ISSUE-53 |
OPEN |
Need definition of 'browser extension' |
2009-11-05 |
|
0 |
| ISSUE-49 |
OPEN |
It might be good for an SC to specifically require UA to allow the user to use any style sheet, including print-oriented style sheets, on the screen. That would allow them to take advantage of simplified layouts created for printing. |
2009-11-05 |
|
0 |
| ISSUE-48 |
OPEN |
HTML5 Comment UAWG07 focus APIs. We need to add a requirement to override automatic change of focus |
2009-10-08 |
|
0 |
| ISSUE-50 |
OPEN |
When working through our docuemnt we need to be sure that examples and success criteria reflect our true intnet. Namely, if text appears in the UA from any source we want the user to have control over as many of the attributes of that text as possible. |
2009-11-05 |
|
0 |
| ISSUE-51 |
OPEN |
Think about concepts around user notification, do we have it covered -- all the state information |
2009-11-05 |
|
0 |
| ISSUE-52 |
OPEN |
In 4.1.2 how to make a keystroke cascade, trickle down from UA interface, extensions, accesskeys, scripts. if ALT F opens file menu, but the script need the ALT F how UA provide mechanism to pass the ALF F to the script and not open the menu |
2009-11-05 |
|
0 |
| ISSUE-31 |
OPEN |
Future Formats - do we need to investigate these? |
2009-02-05 |
|
0 |
| ISSUE-30 |
OPEN |
Someone needs to read through the entire document and identify words/phrases that need a definition. |
2009-01-22 |
|
0 |
| ISSUE-11 |
OPEN |
Do we need a rationale layer at the guideline (or any level) |
2008-10-20 |
|
0 |
| ISSUE-10 |
OPEN |
Reorganization of Introduction |
2008-10-20 |
|
0 |
| ISSUE-12 |
OPEN |
Build into the Conformance statement that the developer needs to cite the operating environment features that support the conformance claim (e.g. using the OS audio controls) |
2008-10-20 |
|
0 |
| ISSUE-13 |
OPEN |
A list of the core principles of the essential accessibility features |
2008-10-20 |
UAAG 2.0 Guidelines |
0 |
| ISSUE-15 |
OPEN |
That we add to the Techniques document: media player controls must be keyboard accessibile and available programmatically |
2008-10-20 |
|
0 |
| ISSUE-14 |
OPEN |
Include in the conformance claim |
2008-10-20 |
UAAG 2.0 Guidelines |
0 |
| ISSUE-9 |
OPEN |
Save Intro Configurability section for a potential Understanding document |
2008-10-20 |
UAAG 2.0 Guidelines |
0 |
| ISSUE-8 |
OPEN |
Weave into conceptual intro - Teirs of configurability: wizard, menus, xml listing (firefox) |
2008-10-20 |
|
0 |
| ISSUE-4 |
OPEN |
Move 4.5.3 to Level AA |
2008-10-16 |
|
0 |
| ISSUE-3 |
OPEN |
4.4.1 and 4.4.2 - do we just link to definition that include all info from wcag, or add short note in explanation with link to definitions and techniques |
2008-10-16 |
|
0 |
| ISSUE-5 |
OPEN |
4.5.4 remove quotes around wizard |
2008-10-16 |
|
0 |
| ISSUE-6 |
OPEN |
4.5.4 remove (at least) --- no change in meaning |
2008-10-16 |
|
0 |
| ISSUE-7 |
OPEN |
4.6.4 reword |
2008-10-16 |
|
0 |
| ISSUE-1 |
OPEN |
4.4.1 define - general flash and red flash thresholds |
2008-10-16 |
|
0 |
| ISSUE-16 |
OPEN |
Relook at the phrasing of Principle 3 to ensure clarity. |
2008-10-21 |
|
0 |
| ISSUE-26 |
OPEN |
WAI glossary, coordinate between WCAG, ATAG, UAAG |
2008-12-18 |
|
0 |
| ISSUE-25 |
OPEN |
Resolve "to" and "via" to describe how information is delived to API or other applications. |
2008-12-04 |
|
0 |
| ISSUE-27 |
OPEN |
Rationale / explanation for 2.1.6 for say font-family needed for future developers (how are we considering capturing this kind of thing) |
2008-12-18 |
|
0 |
| ISSUE-28 |
OPEN |
Rieview 2.1.6 Properties and the validity and reasoning for including the 6 items |
2008-12-18 |
|
0 |
| ISSUE-29 |
OPEN |
Flag (a) the bounding dimensions and coordinates of rendered graphical objects, (b) font family of text, (c) font size of text, (d) foreground color of text, (e) background color of text., (f) change state/value notifications. DON'T WANT TO MOVE TO REC WI |
2008-12-18 |
|
0 |
ISSUE-24
ua-def |
OPEN |
User agent definition |
2008-10-21 |
|
0 |
| ISSUE-17 |
OPEN |
Editors need to set standards for SC handles, and review document for consistency of handles. |
2008-10-21 |
|
0 |
| ISSUE-19 |
OPEN |
Including ageing issues in UAAG |
2008-10-21 |
|
0 |
| ISSUE-18 |
OPEN |
Background Image toggle (4.9) has concerns about identifying decorative vs. no -decorative images. |
2008-10-21 |
|
0 |
| ISSUE-20 |
OPEN |
Take a look at user requirements for mobile users with disabilities and see if there are additional requirements needed in UAAG. |
2008-10-21 |
|
0 |
| ISSUE-21 |
OPEN |
Re-evaluate Principle 2 to see if name, role,state, value, and description are complete and sufficient for minimum accessibility |
2008-10-21 |
|
0 |
| ISSUE-22 |
OPEN |
In Guideline 2.7 the closing Note discusses Japanese and Chinese. This may need to be preserved in Techniques. |
2008-10-21 |
|
0 |
| ISSUE-2 |
CLOSED |
Remove 'chrome' from all checkpoints...entire document |
2008-10-16 |
|
0 |
| ISSUE-23 |
CLOSED |
Draft a proposal for a rewording of 2.10 Timely Exchanges through APIs to make it more clear. |
2008-10-21 |
|
0 |