Important note: This Wiki page is edited by participants of the EOWG. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.


Difference between revisions of "UAAG review"

From Education & Outreach
Jump to: navigation, search
(Abstract)
(Overview)
Line 35: Line 35:
 
<ul>
 
<ul>
 
<li style="padding-bottom:0.5em;">comment <span style="color:#808080;">{name}</span></li>
 
<li style="padding-bottom:0.5em;">comment <span style="color:#808080;">{name}</span></li>
<li style="padding-bottom:0.5em;">comment <span style="color:#808080;">{Sylvie, June 13} May be the Working Group can bring more clarifications on the second sentence of follwoing paragraph, give an example of features concerned:<br />"Some UAAG 2.0 requirements may have security implications, such as communicating through Application Program Interfaces (API), or allowing programmatic read and write access to content and user interface control. UAAG 2.0 assumes that features required by UAAG 2.0 will be built on top of an underlying security architecture. "</span></li>
+
<li style="padding-bottom:0.5em;">May be the Working Group can bring more clarifications on the second sentence of follwoing paragraph, give an example of features concerned:<br />"Some UAAG 2.0 requirements may have security implications, such as communicating through Application Program Interfaces (API), or allowing programmatic read and write access to content and user interface control. UAAG 2.0 assumes that features required by UAAG 2.0 will be built on top of an underlying security architecture. " <span style="color:#808080;">{Sylvie, June 13} </span></li>
 
</ul>
 
</ul>
  

Revision as of 11:33, 13 June 2013

Nav: EOWG wiki main page

Drafts:


UAAG

Overall

  • comment {name}
  • Carefully consider what information should be in UAAG proper, and what should be in Implementing UAAG. Once UAAG is done, it cannot be changed; however, Implementing can be updated. Therefore, it might be wise to move some of the information from the Into of UAAG to Implementing. {Shawn, 3 June}

Abstract

Abstract

  • comment {name}
  • Second sentence in abstract:
    "User agents include browsers and other types of software that retrieve and render Web content."
    It may be useful to indicate what "other types of software" is meant in addition to browsers.{Sylvie, June 13}

Introduction

  • comment {name}

Overview

  • comment {name}
  • May be the Working Group can bring more clarifications on the second sentence of follwoing paragraph, give an example of features concerned:
    "Some UAAG 2.0 requirements may have security implications, such as communicating through Application Program Interfaces (API), or allowing programmatic read and write access to content and user interface control. UAAG 2.0 assumes that features required by UAAG 2.0 will be built on top of an underlying security architecture. " {Sylvie, June 13}

UAAG 2.0 Layers of Guidance

  • comment {Wayne} The Principles bullet should read, "At the top layer,"... Omitting the word layer caused me to trip while reading Principles 4 and 5 are new and need more than just naming. The meaning of facilitate programmatic access and comply with specifications and conventions is not clear, and a brief description does not appear for a very long time. Please give each a brief description when they first appear.
  • comment {Sylvie June 13} The three different levels of conformance are not obvious to read, in particular level A. The way it is written, it makes believe that there is a highest level whereas the highest level is called A. therefore, it may be helpful to write that the lowest level is called A and the highest is called AAA.
    Text concerned: "Three levels of conformance meet the needs of different groups and different situations: A (lowest), AA, and AAA (highest).

UAAG 2.0 Supporting Documents

  • comment {name}

Components of Web Accessibility

  • comment {name}

Levels of Conformance

  • comment {name}
  • comment {Sylvie, June 13} I don't understand one of the "Factors that were considered in the process of determining the level to a success criterion", fourth bullet:
    "implementation difficulty – ranging from deterministic to inferential"

Definition of User Agent

  • comment {name}

Modality Independence Principle

  • comment {name}

Relationship with WCAG 2.0

  • comment {name}
  • comment {Sylvie, June 13} The relationship between UAAG and WCAG is not very clear: when the application is considered to be a user agent and when not. As WCAG applies in both cases, why is it mentionned here?

Relationship with ATAG 2.0

  • comment {name}


Implementing UAAG

Overall (Implementing)

  • comment {name}
  • Examples: change some of the names to be more diverse {Shawn, 3 June}
  • CSS to add more space between chunks of text, especially more space above new SC. Also, increase leading throughout. {Shawn, 3 June}
  • change "Return to Guideline" to @@ {Shawn, 3 June}

Introduction (Implementing)

  • comment {name}

Definition of User Agent (Implementing)

  • comment {name}