Closed Issues

Apply the following changes to selected issues:

There are 90 closed issues listed in the system.

ID State Title Raised on Product Open Actions
ISSUE-2 (edit) CLOSED Remove 'chrome' from all checkpoints...entire document 2008-10-16 0
ISSUE-8 (edit) CLOSED Weave into conceptual intro - Teirs of configurability: wizard, menus, xml listing (firefox) 2008-10-20 0
ISSUE-12 (edit) CLOSED 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-17 (edit) CLOSED Editors need to set standards for SC handles, and review document for consistency of handles. 2008-10-21 0
ISSUE-20 (edit) CLOSED 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-22 (edit) CLOSED In Guideline 2.7 the closing Note discusses Japanese and Chinese. This may need to be preserved in Techniques. 2008-10-21 0
ISSUE-23 (edit) CLOSED Draft a proposal for a rewording of 2.10 Timely Exchanges through APIs to make it more clear. 2008-10-21 0
ISSUE-26 (edit) CLOSED WAI glossary, coordinate between WCAG, ATAG, UAAG 2008-12-18 0
ISSUE-27 (edit) CLOSED 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-29 (edit) CLOSED 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-33 (edit) CLOSED 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-34 (edit) CLOSED 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-37 (edit) CLOSED 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-39 (edit) CLOSED Need to work on the definition of 'important' so it can be used as an objective measure. 2009-07-30 0
ISSUE-41 (edit) CLOSED 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-42 (edit) CLOSED Move tests for User Agent into Guideline 1 Techniques 2009-09-03 0
ISSUE-43 (edit) CLOSED Review UAAG20 and ISO 9241-171 remove duplicate items 2009-09-10 0
ISSUE-44 (edit) CLOSED Cross referencing text search, structured navigation, with media info 2009-09-17 0
ISSUE-46 (edit) CLOSED 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 (edit) CLOSED HTML5 Comment UAWG06 scrolling elements into view. We need to add a requirement to override automatic scrolling 2009-10-08 0
ISSUE-49 (edit) CLOSED 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-51 (edit) CLOSED Think about concepts around user notification, do we have it covered -- all the state information 2009-11-05 0
ISSUE-53 (edit) CLOSED Need definition of 'browser extension' 2009-11-05 0
ISSUE-56 (edit) CLOSED Definition of important or structural elements are vague, rewrite 2009-11-06 0
ISSUE-57 (edit) CLOSED Create low priority search - regular expressions, word forms, colors, text attribute - bold etc. 2009-11-06 0
ISSUE-58 (edit) CLOSED 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-59 (edit) CLOSED Are there other Undo or errors that UAAG needs to consider? Do we need new SC? 2009-11-06 0
ISSUE-60 (edit) CLOSED Need a requirement for out of the box installation present options for interface 2009-11-07 0
ISSUE-63 (edit) CLOSED Mechanism to expand marque (or other element) to read the content within - scroll bars, etc 2009-12-10 0
ISSUE-64 (edit) CLOSED The UA should allow the user to perform on CSS images and background images any action they could perform on normal, foreground images. Same with extra text e.g. bullets and numbering. UA should have access to CSS DOM or its generated content. 2009-12-10 0
ISSUE-69 (edit) CLOSED Guidelines for keyboard and mouse navigation in complex, nested scrollable areas and content 2010-05-27 0
ISSUE-71 (edit) CLOSED Do we need to define how we reach our level ratings? 2010-06-24 0
ISSUE-73 (edit) CLOSED Bug 8743 (auditory icons clashing with AT) is a UA issue; UAAG should highlight user control over such events 2010-09-09 0
ISSUE-75 (edit) CLOSED For 1.4.1 "Render content according to specification" to explicitly exempt cases where user preferences request overriding aspects. 2010-10-28 0
ISSUE-76 (edit) CLOSED Do we need to encourage display of alt text and images at the same time. 2010-11-09 0
ISSUE-77 (edit) CLOSED Revisit repair text 1.2.1 (minutes 9nov2010) 2010-11-09 0
ISSUE-78 (edit) CLOSED 1.8.1 needs attention - confusing and meaning is unclear. 2010-11-09 0
ISSUE-79 (edit) CLOSED Need a consise term forvisible portion of viewport. 2010-11-09 0
ISSUE-80 (edit) CLOSED Talk about 1.8.4 later, greg to create clarification 2010-11-09 0
ISSUE-81 (edit) CLOSED Review section 2.9 to see if it should apply to UI as well as content. 2011-02-03 0
ISSUE-82 (edit) CLOSED In the conformance section, should we allow browsers to use extensions to claim conformance. 2011-02-03 0
ISSUE-83 (edit) CLOSED Navigate by element and semantic role (<div role="heading" aria-level="2">) 2011-04-14 0
ISSUE-84 (edit) CLOSED Ensure that our documents reflect the global concerns of native controls, recognized controls and overall give people clear guidance. 2011-04-21 0
ISSUE-85 (edit) CLOSED We need to think about this (f a user agent conforms to UAAG 2.0 then there may be the problem if the ARIA overrides this) more. 2011-04-28 0
ISSUE-86 (edit) CLOSED Ensure aria role, state, etc should be in the glossary. 2011-05-26 0
ISSUE-87 (edit) CLOSED Need some SC about reflow of content when alternatives put in the document. 2011-06-23 0
ISSUE-88 (edit) CLOSED Make a resolution for 1.10.3 and 2.5.7 (merge/separate). 2011-08-18 0
ISSUE-89 (edit) CLOSED Does UAAG20 apply to mobile browsers 2011-08-24 0
ISSUE-90 (edit) CLOSED UAAG needs to address situation where keyboard shortcuts really means Navigation mechanism. 2011-10-27 0
ISSUE-97 (edit) CLOSED Further discussion needed on mobile apps being UAs or not. Are they covered totally by WCAG 2013-02-14 0
ISSUE-99 (edit) CLOSED Sample code does not include @alt, which is bad practice. 2014-01-13 0
ISSUE-1 (edit) CLOSED 4.4.1 define - general flash and red flash thresholds 2008-10-16 UAAG 2.0 Guidelines 0
ISSUE-3 (edit) CLOSED 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 UAAG 2.0 Guidelines 0
ISSUE-4 (edit) CLOSED Move 4.5.3 to Level AA 2008-10-16 UAAG 2.0 Guidelines 0
ISSUE-5 (edit) CLOSED 4.5.4 remove quotes around wizard 2008-10-16 UAAG 2.0 Guidelines 0
ISSUE-6 (edit) CLOSED 4.5.4 remove (at least) --- no change in meaning 2008-10-16 UAAG 2.0 Guidelines 0
ISSUE-7 (edit) CLOSED 4.6.4 reword 2008-10-16 UAAG 2.0 Guidelines 0
ISSUE-9 (edit) CLOSED Save Intro Configurability section for a potential Understanding document 2008-10-20 UAAG 2.0 Guidelines 0
ISSUE-10 (edit) CLOSED Reorganization of Introduction 2008-10-20 UAAG 2.0 Guidelines 0
ISSUE-11 (edit) CLOSED Do we need a rationale layer at the guideline (or any level) 2008-10-20 UAAG 2.0 Guidelines 0
ISSUE-13 (edit) CLOSED A list of the core principles of the essential accessibility features 2008-10-20 UAAG 2.0 Guidelines 0
ISSUE-14 (edit) CLOSED Include in the conformance claim 2008-10-20 UAAG 2.0 Guidelines 0
ISSUE-15 (edit) CLOSED That we add to the Techniques document: media player controls must be keyboard accessibile and available programmatically 2008-10-20 UAAG 2.0 Guidelines 0
ISSUE-16 (edit) CLOSED Relook at the phrasing of Principle 3 to ensure clarity. 2008-10-21 UAAG 2.0 Guidelines 0
ISSUE-18 (edit) CLOSED Background Image toggle (4.9) has concerns about identifying decorative vs. no -decorative images. 2008-10-21 UAAG 2.0 Guidelines 0
ISSUE-19 (edit) CLOSED Including ageing issues in UAAG 2008-10-21 UAAG 2.0 Guidelines 0
ISSUE-21 (edit) CLOSED Re-evaluate Principle 2 to see if name, role,state, value, and description are complete and sufficient for minimum accessibility 2008-10-21 UAAG 2.0 Guidelines 0
ISSUE-24 (edit)
CLOSED User agent definition 2008-10-21 UAAG 2.0 Guidelines 0
ISSUE-25 (edit) CLOSED Resolve "to" and "via" to describe how information is delived to API or other applications. 2008-12-04 UAAG 2.0 Guidelines 0
ISSUE-28 (edit) CLOSED Rieview 2.1.6 Properties and the validity and reasoning for including the 6 items 2008-12-18 UAAG 2.0 Guidelines 0
ISSUE-30 (edit) CLOSED Someone needs to read through the entire document and identify words/phrases that need a definition. 2009-01-22 UAAG 2.0 Guidelines 0
ISSUE-31 (edit) CLOSED Future Formats - do we need to investigate these? 2009-02-05 UAAG 2.0 Guidelines 0
ISSUE-32 (edit) CLOSED 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 UAAG 2.0 Guidelines 0
ISSUE-35 (edit) CLOSED Think about interactions between user agents and AT around viewport creation and responsibilities. 2009-04-09 UAAG 2.0 Guidelines 0
ISSUE-36 (edit) CLOSED Keyboard efficiency, for screenreaders and speech users. cognitive load from GL comments (micorsoft wordding) 2009-05-14 UAAG 2.0 Guidelines 0
ISSUE-38 (edit) CLOSED Review "the user has the option to be able to navigate via the keyboard" 2009-07-30 UAAG 2.0 Guidelines 0
ISSUE-40 (edit) CLOSED 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 UAAG 2.0 Guidelines 0
ISSUE-45 (edit) CLOSED There is some concern about the mixing/over-ride of app-supplied key 2009-09-24 UAAG 2.0 Guidelines 0
ISSUE-48 (edit) CLOSED HTML5 Comment UAWG07 focus APIs. We need to add a requirement to override automatic change of focus 2009-10-08 UAAG 2.0 Guidelines 0
ISSUE-50 (edit) CLOSED 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 UAAG 2.0 Guidelines 0
ISSUE-52 (edit) CLOSED 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 UAAG 2.0 Guidelines 0
ISSUE-54 (edit) CLOSED Do we have a SC to support OS conventions for cut copy paste etc 2009-11-05 UAAG 2.0 Guidelines 0
ISSUE-55 (edit) CLOSED 4.1.7 seems ambiguious, apply only to UI toolbars, menus; or apply also to content - groups of radio buttons 2009-11-05 UAAG 2.0 Guidelines 0
ISSUE-61 (edit) CLOSED Settle on one term for "time-based media" (4.9.3), "animation" (4.9.7), and "video" (4.9.6) 2009-12-10 UAAG 2.0 Guidelines 0
ISSUE-62 (edit) CLOSED Editorial checks -- review document for 'recognize', 'and/or', initialisms (UA, acromyns, etc.) 2009-12-10 UAAG 2.0 Guidelines 0
ISSUE-65 (edit) CLOSED Review the document for consistency of the use of option: option, ability, by default, on/off, or always. 2010-02-25 UAAG 2.0 Guidelines 0
ISSUE-66 (edit) CLOSED Editorial--review document for normalization of terms that match new definition 2010-02-26 UAAG 2.0 Guidelines 0
ISSUE-68 (edit) CLOSED UAAG harmonization with ISO 2010-05-13 UAAG 2.0 Guidelines 0
ISSUE-70 (edit) CLOSED Resolution of 3.10.10 pending on definition review in action-240 viewports, scrollbars and overflow 2010-06-03 UAAG 2.0 Guidelines 0
ISSUE-72 (edit) CLOSED Ensure UAAG docus have fully updated references to the various accessibility APIs. 2010-08-03 UAAG 2.0 Guidelines 0

Raise an issue .

Jim Allan <>, Kelly Ford <>, Chairs, Jeanne F Spellman <>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: issues.php,v 1.16 2014-02-12 10:09:00 dom Exp $