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)
(Implementing UAAG)
Line 77: Line 77:
 
===Overall (Implementing)===
 
===Overall (Implementing)===
 
<ul>
 
<ul>
 
+
<li style="padding-bottom:0.5em;">comment <span style="color:#808080;">{name}</span></li>
<li style="padding-bottom:0.5em;">Would it be possible to use structuring elements such as H5s to indicate sections like Intent of SC, Examples and resources? While comparing to the structure of [http://www.w3.org/WAI/GL/2011/WD-UNDERSTANDING-WCAG20-20110621/complete.html#contents Understanding WCAG 2.0], is there a W3C graphical design that could make each guideline document look similar? <span style="color:#808080;">{Sylvie, 14 June}</span></li>
+
 
+
<li style="padding-bottom:0.5em;">Ditto Sylvie's comment. <span style="color:#808080;">{Paul, 17 June}</span></li>
+
 
+
<li style="padding-bottom:0.5em;"> Examples: change some of the names to be more diverse <span style="color:#808080;">{Shawn, 3 June}</span></li>
+
 
+
<li style="padding-bottom:0.5em;"> CSS to add more space between chunks of text, especially more space above new SC. Also, increase leading throughout. <span style="color:#808080;">{Shawn, 3 June}</span></li>
+
 
+
<li style="padding-bottom:0.5em;"> change "Return to Guideline" to @@ <span style="color:#808080;">{Shawn, 3 June}</span></li>
+
 
+
 
</ul>
 
</ul>
  
 
===Introduction (Implementing)===
 
===Introduction (Implementing)===
 
<ul>
 
<ul>
 +
<li style="padding-bottom:0.5em;">comment <span style="color:#808080;">{name}</span></li>
 +
</ul>
  
 
</ul>
 
  
 
===Definition of User Agent (Implementing)===
 
===Definition of User Agent (Implementing)===
 
<ul>
 
<ul>
 
+
<li style="padding-bottom:0.5em;">comment <span style="color:#808080;">{name}</span></li>
<li style="padding-bottom:0.5em;">
+
Third paragraph: the link to "What Qualifies as a User Agent" is followed by the name of the current document in brackets, isn't this redundant? 
+
<span style="color:#808080;">{Bim 14 June}</span></li>
+
<li style="padding-bottom:0.5em;">I think Wayne's comment from "Modality Independence Principle" from above is appropriate here. I like that they use easy-to-follow if-then conditions, but examples are needed for clarity. <span style="color:#808080;">{Paul, 17 June}</span></li>
+
 
</ul>
 
</ul>
  
 
===Implementing Guideline 1.1 - Provide access to alternative content.===
 
===Implementing Guideline 1.1 - Provide access to alternative content.===
 
<ul>
 
<ul>
 
+
<li style="padding-bottom:0.5em;">comment <span style="color:#808080;">{name}</span></li>
<li style="padding-bottom:0.5em;">Link to definition of metadata would be helpful <span style="color:#808080;">{Howard, 18 June}</span></li>
+
<li style="padding-bottom:0.5em;">Several occurences in this guideline and may be elsewhere through the doc: in Intent of success criterion X, the document says that non text content is unusable, or <em>"painful"</em>. I have never seen this term elsewhere in W3C docs and wonder if it is appropriate. <br />Another example in intent of SC 1.2: <blockquote>"Some users with visual disabilities may wish to hide images in order to avoid those that are painful (such as those with high contrast)."</blockquote> <span style="color:#808080;">{Sylvie, 14 June}</span></li>
+
<li style="padding-bottom:0.5em;">In 1.1.3 Configurable Alternative Content Defaults, first example: <blockquote>"Sally is blind. In the browser's preferences dialog box, Sally specifies that she wants alt text displayed in place of images, and that the document should reflow to allow the entire alt text to be displayed rather than truncated."</blockquote> As screen readers retrieve the alt text content is it necessary for a blind user to request that the browser displays alt text rather than images? May be the example should be rewritten to reflect real use of alt text by blind users? <span style="color:#808080;">{Sylvie, 14 June}</span></li>
+
<li style="padding-bottom:0.5em;">In Examples of Success Criterion 1.1.6, the disability of the users is not always specified, (e.g. Maximilian or Tom. <span style="color:#808080;">{Sylvie, 14 June}</span></li>
+
<li style="padding-bottom:0.5em;">Agree with Sylvie's comments above <span style="color:#808080;">{Howard, 18 June}</span></li>
+
 
</ul>
 
</ul>
  
 
===Implementing Guideline 1.2 - Repair missing content.===
 
===Implementing Guideline 1.2 - Repair missing content.===
 
<ul>
 
<ul>
 
+
<li style="padding-bottom:0.5em;">comment <span style="color:#808080;">{name}</span></li>
<li style="padding-bottom:0.5em;">Why is a link to "Website Accessibility Conformance Evaluation Methodology" a resource for this particular guideline. I followed the link which brought me to the very top of the <em>Evaluation Methodology</em> Document but I had no idea what I should be looking for or which section to look at. (WCAG-EM) 1.0 <span style="color:#808080;">{Howard, 18 June}</span></li>
+
<li style="padding-bottom:0.5em;">I think an example of what's stated <em>not to do</em> in a & b would be helpful. Otherwise, I'm not exactly sure what those instructions are warning against. <span style="color:#808080;">{Howard, 18 June}</span></li>
+
<li style="padding-bottom:0.5em;">Examples of Success Criterion 1.2.2, first example:<br />The example talks about Franck who is called George in the next sentence. ^Try to check that the names remain the same in each example, in order to avoid confusing the reader. <span style="color:#808080;">{Sylvie, 14 June}</span></li>
+
 
</ul>
 
</ul>
  
 
===Implementing Guideline 1.3 - Provide highlighting for selection, keyboard focus, enabled elements, visited links.===
 
===Implementing Guideline 1.3 - Provide highlighting for selection, keyboard focus, enabled elements, visited links.===
 
<ul>
 
<ul>
 
+
<li style="padding-bottom:0.5em;">comment <span style="color:#808080;">{name}</span></li>
 
+
<li style="padding-bottom:0.5em;">more white space is needed above Section 1.3.2 and now that I'm looking at this more closely, greater line space is needed throughout between paragraphs and bullet items and above subheadings.<span style="color:#808080;">{Howard, 18 June}</span></li>
+
<li style="padding-bottom:0.5em;">It would be nice to know that more info is available in "Examples of Success Criterion 1.3.1:" for note items 1 & 2. I don't know if there's a way to indicate this without cluttering up the screen. <span style="color:#808080;">{Howard, 18 June}</span></li>
+
<li style="padding-bottom:0.5em;">missing word: In second bullet item under "Examples of Success Criterion 1.3.1": "so he tell where" should be "so he can tell where" <span style="color:#808080;">{Howard, 18 June}</span></li>
+
<li style="padding-bottom:0.5em;">1st example under "Examples of Success Criterion 1.3.1:". When you refer to "website that uses styles to override visited link color", do you mean font style - such as italic in lieu of a "visited link color." If so, I think you should refer to it specifically as "font style" because style in a css file can include color. In any case, the current sentence is too ambiguous.<span style="color:#808080;">{Howard, 18 June}</span></li>
+
<li style="padding-bottom:0.5em;">missing word: Second sentence: "they working" should be "they are working" <span style="color:#808080;">{Howard, 18 June}</span></li>
+
<li style="padding-bottom:0.5em;">Should "hover" be included in the list of 1.3.1 classes where highlighting is user controlled? Or would this be the same as "selection"? <span style="color:#808080;">{Howard, 18 June}</span></li>
+
 
+
<li style="padding-bottom:0.5em;">SC 1.3.1 has three notes. I wonder if it is worth numbering them in note 1, note 2 ... or may be it does not make sense? <span style="color:#808080;">{Sylvie, 14 June}</span></li>
+
 
</ul>
 
</ul>
  
 
===Implementing Guideline 1.4 - Provide text configuration.===
 
===Implementing Guideline 1.4 - Provide text configuration.===
 
<ul>
 
<ul>
 
+
<li style="padding-bottom:0.5em;">comment <span style="color:#808080;">{name}</span></li>
<li style="padding-bottom:0.5em;">Typo: not sure whether we should indicate them in EOWG ^comments: Summary contains one word "<em>the</em>" that should not be there: <blockquote>"The user can control text font, color, and size (1.4.1), including whether all text should be the shown the same size (1.4.2).</blockquote><span style="color:#808080;">{Sylvie, 14 June}</span></li>
+
 
</ul>
 
</ul>
  
 
===Implementing Guideline 1.6 - Provide synthesized speech configuration.===
 
===Implementing Guideline 1.6 - Provide synthesized speech configuration.===
 
<ul>
 
<ul>
 
+
<li style="padding-bottom:0.5em;">comment <span style="color:#808080;">{name}</span></li>
<li style="padding-bottom:0.5em;">grammar/style: "and synthesizer speech characteristics <em>like</em> emphasis (1.6.3) and features <em>like</em> spelling (1.6.4)."  "like" should be replaced with "such as" if meaning here <em>includes</em> features such as "emphasis" and "spelling". If the features are similar to "emphasis" and "spelling" but different, then "like" would be used.<span style="color:#808080;">{Howard, 20 June}</span></li>
+
 
+
 
</ul>
 
</ul>
  
 
===Implementing Guideline 1.7 - Enable Configuration of User Stylesheets.===
 
===Implementing Guideline 1.7 - Enable Configuration of User Stylesheets.===
 
<ul>
 
<ul>
 
+
<li style="padding-bottom:0.5em;">comment <span style="color:#808080;">{name}</span></li>
<li style="padding-bottom:0.5em;">3rd bullet under "Examples of Success Criterion". 2nd occurrence of word "text" should be removed.  <span style="color:#808080;">{Howard, 20 June}</span></li>
+
<li style="padding-bottom:0.5em;">similar problem with 4th bullet under "Examples of Success Criterion".  "text easiest to read text if text is highlighted" should be changed to:  "text easiest to read if it is highlighted"  <span style="color:#808080;">{Howard, 20 June}</span></li>
+
<li style="padding-bottom:0.5em;">I wonder if it would be useful to explain acronyms such as in last "Examples of Success Criterion 1.7.1, 1.7.2 & 1.7.3". <br /><blockquote>"Mattias has ADHD and finds text easiest to read text·...</blockquote>explain what is ADHD? Is it clear to any reader? <span style="color:#808080;">{Sylvie, 14 June}</span></li>
+
 
</ul>
 
</ul>
  
 
===Implementing Guideline 1.8 - Help users to use and orient within windows and viewports.===
 
===Implementing Guideline 1.8 - Help users to use and orient within windows and viewports.===
 
<ul>
 
<ul>
 
+
<li style="padding-bottom:0.5em;">comment <span style="color:#808080;">{name}</span></li>
<li style="padding-bottom:0.5em;">Mentioned this above - need more line spacing between end of paragraphs and headings for readability. <span style="color:#808080;">{Howard, 20 June}</span></li>
+
<li style="padding-bottom:0.5em;">Summary is long on this item. Readability would be improved if it was broken up into bullet items. <span style="color:#808080;">{Howard, 20 June}</span></li>
+
<li style="padding-bottom:0.5em;">The meaning of this heading in not clear. Does "use" refer to "windows & viewport" as in "help users to use windows and viewports"? Suggest something like "Help users to orient within, and control, windows and viewports" <span style="color:#808080;">{Howard, 20 June}</span></li>
+
<li style="padding-bottom:0.5em;">In "Examples of Success Criteria 1.8.8, 1.8.9 & 1.8.10:", first example talking about Justin, there is a word repetition: "The word remains selected remains the same so he doesn't have to reorient or find it on the page." <br />Second example talks about George who uses a screen reader. In other examples, the text talks about Jorge, not sure if this is the same person as the names are written differently.<span style="color:#808080;">{Sylvie, 17 June}</span></li>
+
 
</ul>
 
</ul>
  
 
===Implementing Guidelines 1.9 and 1.10===
 
===Implementing Guidelines 1.9 and 1.10===
 
<ul>
 
<ul>
 
+
<li style="padding-bottom:0.5em;">comment <span style="color:#808080;">{name}</span></li>
<li style="padding-bottom:0.5em;">For 1.9 should "or" in header ("The user can view the source of content (1.9.2), or an outline view of important elements. (1.9.1).") be "and/or" or simply "and"? Current wording seems to imply you should only do one or the other. <span style="color:#808080;">{Howard, 20 June}</span></li>
+
<li style="padding-bottom:0.5em;">The examples of Success Criterion 1.9.2 talk about users who display the source code of a page to find out what an untagged image is for or to modify style sheets. I am not sure that these examples are realistic as users need to have knowledge of code to have a look at lines of source codes. Either the group should explain that these users have already good knowledge of page coding, or the examples should be rewritten. @@Eowg thoughts on this are welcome. See for example the users' reactions in Jaws 14 who can set their screen reader to start reading on a specific place (h, div, and so on) on the page or ignore iframes (like facebook iframes). They are disturbed by the use of code to set this. <br />Same comment for example of success criterion 1.10.2, where the user "selects the text he's interested in, opens the browser's debug window, which shows him that the selected text is an element with class "story" inside a paragraph inside a DIV with class "Premiere". He then knows the combination of classes and element types to specify in the user style sheet.".<span style="color:#808080;">{Sylvie, 17 June}</span></li>
+
 
</ul>
 
</ul>
  
 
===Implementing Guideline 1.10 - Provide element information. ===
 
===Implementing Guideline 1.10 - Provide element information. ===
 
<ul>
 
<ul>
 +
<li style="padding-bottom:0.5em;">comment <span style="color:#808080;">{name}</span></li>
 +
</ul>
  
<li style="padding-bottom:0.5em;">I know what you're saying in the summary but I wonder if there's a better phrase than "content relationship" - perhaps "content hierarchy" or "content metadata" or "parent/sibling relationships."  <span style="color:#808080;">{Howard, 20 June}</span></li>
+
===Other comments on implementing UAAG ===
 
+
<ul>
 +
<li style="padding-bottom:0.5em;">comment <span style="color:#808080;">{name}</span></li>
 
</ul>
 
</ul>
  
 
 
===Other comments on implementing UAAG ===
 
* SC 2.1.2: example 1: Two names have been used for first example: Amal and Alan. <span style="color:#808080;">{Sylvie, 17 June}</span>
 
* SC 2.1.4: last example refers to a specific device and screeen reader (Iphone and Voiceover). Is it ok to do that, or should the document remain device and screen reader neutral? <blockquote>"Ari uses Voiceover on his iPhone to navigate a webpage. He selects an item and is able to activate the element using gestures. This requires sufficient screen real estate to perform gestures without changing focus."</blockquote> <span style="color:#808080;">{Sylvie, 17 June}</span>
 
 
===typos in implementing UAAG===
 
===typos in implementing UAAG===
* In "Examples of Success Criterion 2.4.1:"
+
<ul>
** Example 2: "Betty, who has low vision, is attempting to create a user stylesheet for a site. She need to know", instead of "she needs to know".
+
<li style="padding-bottom:0.5em;">comment <span style="color:#808080;">{name}</span></li>
** 5th example: "Agnes uses the search function to seach through the captions": write search through the captions. <span style="color:#808080;">{Sylvie, 17 June}</span>  
+
</ul>
* In Examples of Success Criterion 2.4.3: "Jules is low vision and uses a magnified screen." Better write: "Jules has low vision and uses a magnified screen." <span style="color:#808080;">{Sylvie, 17 June}</span>
+
* In last example of SC 2.7.3: "At those times he users his browser's user preference profiles to load a different configuration that’s optimized for the keyboard." Write: "He uses his keyboard"<span style="color:#808080;">{Sylvie, 17 June}</span>
+
* In Intent of SC 2.7.4 the following sentence repeats a word twice and is not understandable to me: "The user agent can accomplish this in multiple including including detecting and implementing the platform accessibility settings, providing an external file to modify, providing access to settings from a separate utility program, providing accessibility options in the installation program, or providing command-line switches to change the user agent's behavior." <span style="color:#808080;">{Sylvie, 17 June}</span>
+
* In the 4th example of SC 2.7.4, there seems to be a word missing: "Justin has an attention deficit disorder. He is setting up his new e-book reader and is interrupted while setting the default font colors, then finds he accidentally set his background and font color to white on white. <span style="color:#808080;">{Sylvie, 17 June}</span>
+
* In Examples for SC 2.8.1:
+
** Third example about Caraway: "In programs she uses a lot she removes toolbars that she doesn't use in order to reduce the probably that the speech program will interpret text input as a toolbar command and click something Caraway does not intend." May be they mean probability?
+
** Last example about Jennifer: "she turns on the built-in voice application so she so she can quickly find her way around Linda's phone." So she is repeated twice.<span style="color:#808080;">{Sylvie, 17 June}</span>  
+
* there is only one title of 2.8.2 reset Toolbar configuration, and no text in it. <span style="color:#808080;">{Sylvie, 17 June}</span>  
+
* In the first examples of Success Criterion 2.11.1: one word repeated: "Jill is blind. She browses browses the web using a screen reader to listen to the text of web pages." <span style="color:#808080;">{Sylvie, 17 June}</span>
+
* In Intent of Success Criterion 2.11.2 : last sentence of the note before examples: placholder instead of placeholder.<span style="color:#808080;">{Sylvie, 17 June}</span>
+
* Examples of SC 2.11.2:
+
** second example word repetition: "When he is ready to he is ready to hear it, he navigates to the placeholder".
+
** third example, a sentence that is not easy to understand: "Evan has configured his mobile phone to so any audio or video file displays a placeholder with a triangle "play" icon."<span style="color:#808080;">{Sylvie, 17 June}</span>
+

Revision as of 17:30, 22 November 2013

Nav: EOWG wiki main page

Drafts:

Previous comments: UAAG review June 2013

UAAG

Overall

  • comment {name}

Abstract

  • comment {name}

Introduction

  • comment {name}

Overview

  • comment {name}

UAAG 2.0 Layers of Guidance

  • comment {name}

UAAG 2.0 Supporting Documents

  • comment {name}

Components of Web Accessibility

  • comment {name}

Levels of Conformance

  • comment {name}

Definition of User Agent

  • comment {name}

Modality Independence Principle

  • comment {name}

Relationship with WCAG 2.0

  • comment {name}

Relationship with ATAG 2.0

  • comment {name}

Implementing UAAG

Overall (Implementing)

  • comment {name}

Introduction (Implementing)

  • comment {name}


Definition of User Agent (Implementing)

  • comment {name}

Implementing Guideline 1.1 - Provide access to alternative content.

  • comment {name}

Implementing Guideline 1.2 - Repair missing content.

  • comment {name}

Implementing Guideline 1.3 - Provide highlighting for selection, keyboard focus, enabled elements, visited links.

  • comment {name}

Implementing Guideline 1.4 - Provide text configuration.

  • comment {name}

Implementing Guideline 1.6 - Provide synthesized speech configuration.

  • comment {name}

Implementing Guideline 1.7 - Enable Configuration of User Stylesheets.

  • comment {name}

Implementing Guideline 1.8 - Help users to use and orient within windows and viewports.

  • comment {name}

Implementing Guidelines 1.9 and 1.10

  • comment {name}

Implementing Guideline 1.10 - Provide element information.

  • comment {name}

Other comments on implementing UAAG

  • comment {name}

typos in implementing UAAG

  • comment {name}