This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1226 - Compound list of issues from ATutor developer
Summary: Compound list of issues from ATutor developer
Status: NEW
Alias: None
Product: ATAG
Classification: Unclassified
Component: ATAG 2.0 (show other bugs)
Version: 2.0
Hardware: All All
: P5 critical
Target Milestone: CR
Deadline: 2018-06-30
Assignee: Jan Richards
QA Contact: Matt May
URL: http://lists.w3.org/Archives/Public/w...
Whiteboard:
Keywords: a11y
Depends on:
Blocks:
 
Reported: 2005-04-07 20:50 UTC by Jan Richards
Modified: 2018-06-28 19:25 UTC (History)
1 user (show)

See Also:


Attachments

Description Jan Richards 2005-04-07 20:50:18 UTC
(1) In checkpoint 1.5, for Web-based tools can the search be browser's find 
function? What if only some browsers support "find".

(2) In checkpoint 2.3, what if information is required from the user? Can the 
pre-corrected markup be put in anyway?

(3) In checkpoint 3.1, success criteria 2 is confusing.

(4) In checkpoint 3.2, does success criteria 2 require that a checker be 
launched automatically?

(5) In checkpoint 3.7, the success criteria could be interpretted as covering 
all functionality (in principle, almost anything can affect accessibility).