Re: ATAG requirements on accessible authoring interfaces

Hi Roberto,

Thanks for the comments. Answers are in-line:

Roberto Scano - IWA/HWG wrote:

> Roberto Scano:
> A good work! Some points:
> 
> 1. FROM_UAAG.5 Ensure that visual displays are configurable. [Priority 
> 1] [Adapted from UAAG 4.1, 4.2, 4.3]
> Rationale: Authors with low vision may require that text be rendered at 
> a size larger than the size specified by the authoring tool's defaults. 
> authors with color blindness may need to impose or prevent certain color 
> combinations.
> 
> This could be difficoult (or impossibile) for web based authoring tools.

Actually this requirement is covered by this note at the top of the 
guideline:

"Conformance note for authoring tools with Web-based functionality: For 
the purposes of Guideline 1, Web-based functionality will be evaluated 
in the the context of the user agent(s) in which it is rendered, 
allowing user agent functionality to play a role, along with accessible 
Web page design, in satisfying the following checkpoints (NEW.2, 
From_UAAG.1, From_UAAG.2, NEW.1, EXISTING(1.5), From_UAAG.4, 
*From_UAAG.5*,..."

The point here is that a UAAG 1.0 conformant user agent will be able to 
do this (as long as the Web-based authoring tool has also followed WCAG 
as per checkpoint NEW.1), so the evaluator can make use of the 
browser-side feature as long as the browser is listed in the ATAG 2.0 
conformance profile.



> 2. From_UAAG.22 Ensure that toolbars are configurable. [Priority 3] 
> [Adapted from UAAG 11.7]
> This could go against some security level for editor. For eg, in some 
> web based plugin is possible to define an external source for show 
> particoular buttons (eg: giving to expert the possibility to edit also 
> the page with code-view and configure other users without this 
> possibility).
> So I suggest here (or eventually in the main section of the guidelines) 
> to put something about this problem.

I think it depends on how it is implemented. The success criteria don't 
say the tool must accept information from outside. It can be a 
completely closed system with configuration options.

I hope this answers your questions.

Cheers,
Jan


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

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