RE: ISSUE-66 Change Proposal: be more explicit about potential repair techniques

> I guess I should also ask: how do others who supported Matt's
> Change Proposal, or some compromise version, feel about this

(a) editorial: I don't think any of the proposals make any
    any changes to normative requirements for any class of
    agent or content. 

(b) Modularity: having overlapping but different recommendations
   or advice in the HTML spec and the UAAG seems counter to the
   goal of modularity of specifications and allowing independent
   evolution of the main line of HTML implementation advice vs.
   specific user agent accessibility advice.

On both these grounds, I think the original change proposal
to just remove the sentence is better.

I think as a separate issue:

An explicit reference to UAAG 1.0 and a note that WAI is working
on UAAG 2.0 with a pointer to
would be better; making UAAG 1.0 and its successors a SHOULD 
normative requirement would be even better.


Received on Wednesday, 10 March 2010 23:59:30 UTC