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.


UAAG review January 2014

From Education & Outreach
Jump to: navigation, search

Nav: EOWG wiki main page

This is an archive of previous review used for comments submitted 31 January 2014
(EOWG: Put new comments in the " UAAG review page.)


This is an archive of previous review used for comments submitted 31 January 2014
(EOWG: Put new comments in the " UAAG review< page.)

EOWG: See Notes under Technical Document Review for info on reviewing and commenting.

Drafts:

Note: These comments are from individuals and have not been reviewed by all EOWG participants.

UAAG

Overall

  • [closed] classification by priority level ? On Guideline 1.4, one can find success criteria with level AA, followed by success criteria level AAA followed by success criteria level AA. See 1.4.4, 1.4.5, 1.4.6. Would it be more logical to classify by priority levels or is there a ground for this classification? {Sylvie, 24 January}
    • EOWG 24 Jan telecon: decided OK to group by topic and not levels.
  • I have read the document and it is fine. I have no comments at this time {Anthony}
  • Comment {Name}

Implementing UAAG

Overall (Implementing)

  • {Question for EOWG}: Examples of users: in some cases, the "disability" of the user is not specified, whereas it is indicated in most of the examples. May be it will not be clear, for the reader, why it is necessary to implement the success criterion for the specified user. See for example, Binh in success criterion 1.3.1, or Maximilian in 1.1.6. {Sylvie, 17 January}
    • I'm OK submitting comment as is{Shawn}
    • Agree to submit the comment as it is {Sharron}
    • +1 {Andrew}
    • Comment {Name}
  • Typos: through document, "webpage" instead of "web page"{Sylvie, 17 January}
  • In Examples of Success Criterion 2.4.1: In Agnes example: Time line: is the spelling of this word timeline or time line or both? {Sylvie, 23 January}
  • The table of contents only has 'Guideline N' as the link - suggest also linking the guideline name (also applies to the TR) {Andrew, 31 January}
  • comment {name}

Abstract (Implementing)

  • In the second paragraph, the last word "guideline" is singular whereas the other terms are plural, so it is not clear to which guideline last part of the sentence refers.
    "This document provides explanation of the intent of UAAG 2.0 success criteria, examples of implementation of the guidelines, best practice recommendations and additional resources for the guideline.
    {Sylvie, 10 January 2014}
  • Suggest to substitute "each" for "the" guideline. So it will say "...additional resources for each guideline." {Sharron}

Examples of Success Criterion 1.8.2

  • {Question for EOWG} Example 2 is not clear. Why and how George should scroll?
    George uses a screen reader. He is showing a sighted colleague how to complete a registration form that's contained within a viewport. The form exceeds the vertical bounds of the viewport, requiring George to scroll vertically to view the complete form content. When George completes each form entry, if the next form is not already visible in the viewport, it scrolls into view.
    {Sylvie, 17 January}
    • I'm OK submitting comment as is{Shawn}
    • Agree to submit this comment as it is {Sharron}
    • Agree to submit {Andrew}
  • comment {name}

Examples of Success Criterion 2.3.4

  • In first example, there are some strange sign that I cannot identify, may be that have sense graphically but not in braille and nothing is pronounced by speech synsethiser. Here is what I can read: "notices that the menu item has a "⌘" label (e.g. "Copy ⌘+C")." Clarifications would be welcome! {Sylvie, 23 January
  • comment {name}

Examples of Success Criterion 2.4.1

  • {Question for EOWG}: The 4th example on Sam is not clear. I am not sure that many blind users disable images in their browsers as images do not need to be disabled to hear their alt attribute spoken by screen readers. think about how realistic this example is.
    Sam is a screen reader user. He has images off and the alternative content for images  is revealed. He wants to send the flow chart image on the page to a collegue. Sam searches for the word "flowchart" that he heard spoken as part of the 'alt' text for the image. He then uses the context menu to select the address of the image and sends it to a colleague.
    {Sylvie, 23 January}
    • I'm OK submitting comment as is{Shawn}
    • Agree{Sharron}
    • Agree to submit {Andrew}
  • comment {name}

Examples of Success Criterion 2.5.2

  • In third example on Celia, it could be useful to add a comma after "document": "When looking for any particular section of the document she finds it easier to scan through headings". {Sylvie, 23 January}
  • {Question for EOWG}: I don't understand the meaning of 4th example that talks about blindness, speech command and heading navigation. There should be more explanations on this concept.
    Armand is blind. When he uses the speech input to locate a web page on his smartphone, Armand navigates from heading to heading using touch commands.
    {Sylvie, 23 January}
    • I'm OK submitting comment as is{Shawn}
    • Agree{Sharron}
  • comment {name}