Re: Comments on ATAG 2.0

Hi Andrew,

My comments are in-line:

Ronksley, Andrew wrote:
>  
> So everyone has it for the conference call, here are my notes from reviewing the guidelines:
>  
> 1: More of an editing comment - it feels like the "Applicability Notes" would be better placed before the guidelines they relate to along with the "Rationale". This way, readers are made aware straight away whether a guideline is relevant to them or not.

Makes sense to me. Other opinions?


> 2: The rationale for guideline A.2.1 uses the word "enhancement" - what does this mean?

e.g., changing the foreground and background colors for readability...so 
maybe "color enhancement"?


> 3: Can I check my understanding of the difference between A.2.3.4 and A.2.3.7 is that A.2.3.4 applies only to the properties font, style, colour and size whereas A.2.3.7 must make any text presentation properties available via the platform - is that correct?

Any "editable" properties. So for instance if the tool doesn't let the 
author change the space between letters, then the spacing doesn't need 
to be communicated. It's all about enabling the quasi-preview 
functionality of WYSIWYG editing views.


> 4: Another editing comment - guideline A.2.4.1 - there is no space after the brackets are closed around the word "views".

Thanks for spotting that - I will make the correction.


> 5: Guideline B2.2.8 - I don't understand what "resource discovery by end users" means? Is this tied in with recording the accessibility of pre-authored content, e.g. templates?

Basically it means that the status information (what tests passed and 
failed) can be encoded and used in systems that match user preferences 
with resources. E.g. a page might contain a video with audio. The video 
has audio descriptions, but no captions. As such it is not WCAG Level A 
conformant, but for a person who is blind, it would work quite well.

As you say, it is related to the accessibility of pre-authored content. 
Though in that case I think it makes more sense to align with the WCAG 
levels for example.


Cheers,
Jan

>  
> Thanks.
> Regards,
> Andrew.
> 
> 

-- 
Jan Richards, M.Sc.
User Interface Design Specialist
Adaptive Technology Resource Centre (ATRC)
Faculty of Information Studies
University of Toronto

   Email: jan.richards@utoronto.ca
   Web:   http://jan.atrc.utoronto.ca
   Phone: 416-946-7060
   Fax:   416-971-2896

Received on Wednesday, 14 May 2008 17:46:59 UTC