Fwd: UAAG Comments

For Information.


-------- Original Message --------
Subject:  UAAG Comments
Date:  Fri, 31 Jan 2014 10:48:44 +0000
From:  Simon Harper <simon.harper@manchester.ac.uk>
To:  public-uaag2-comments@w3.org <public-uaag2-comments@w3.org>



Hi guys, no the whole I think this is very good. But here are a few comments...

Missing 'an' in the sentence after the comma


         1.1.3 Replace Non-Text Content:

The user can request a placeholder that incorporates recognized
<http://www.w3.org/TR/UAAG20/#def-recognize> text alternative content instead of
recognized non-text content, until explicit user request to render the non-text content.
(Level A)


1.4.2 and 1.4.3 need a space between the : and (

1.8.14 is a good idea but I think we need to make it clear that persistence is not
guaranteed if the page elements have changed  and there needs to be some way to notify
people that the marked content has changed or been lost. Also typo space required between
. And (


         1.8.14 Provide Webpage Bookmarks:

The user can mark items in a webpage, then use shortcuts to navigate back to marked items.
The user can specify whether a navigation mark disappears after a session, or is
persistent across sessions.(Level AAA)


For 1.10.1 are we assuming that close elements will be close in the DOM. I'd think this
would be hard based on the visual rendering, and would require some idea of the semantics
of the association. I'd also think that a label to a form element could be close in  DOM
for distant in the visual rendering based on the CSS, how is this handled?

For the understandability principle, then isn't this a little all encompassing. There is
nothing about simple language usage or graphic usage for people with a learning
disability. So my question is understandable to whom?

Finally, 4.1.7 is about making API Calls be timely such that delays aren't perceived by
users, but this is difficult if the software interfaced to us not timely, people may the
perceive a delay. I think this needs to be a little more explicit.

Cheers

-- 
Si.

PS I check my email at 08:00 <x-apple-data-detectors://26> and 17:00 GMT
<x-apple-data-detectors://27>. If you require a faster
response please include the word 'fast' in the subject line.

=======================
Simon Harper
My Business Card   - http://simon.harper.name/about/card/
Schedule a Meeting - http://doodle.com/simon.harper.name

University of Manchester (UK)
Web Ergonomics Lab - Information Management Group
http://wel.cs.manchester.ac.uk <http://wel.cs.manchester.ac.uk/>

-- 
Too brief? Slow response? There is a reason - see the Email Charter. <http://emailcharter.org>

------------------------------------------------------------------------------------------

Simon Harper
My Business Card <http://simon.harper.name/about/card/>
Schedule a Meeting <http://doodle.com/simon.harper.name>

University of Manchester (UK)
Web Ergonomics Lab <http://wel.cs.manchester.ac.uk>
Information Management Group

------------------------------------------------------------------------------------------
Find me on:

   * ORC-ID <http://orcid.org/0000-0001-9301-5049>
   * Google <http://scholar.google.co.uk/citations?user=SQEdResAAAAJ>
   * ACM Bibliometrics <http://dl.acm.org/author_page.cfm?id=81100139139>
   * Research Gate <https://www.researchgate.net/profile/Simon_Harper/>

   * Bitbucket (sharpic) <https://bitbucket.org/sharpic>
   * GitHub (sharpic) <https://github.com/sharpic>