W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2005

Issues summary, GL 4.2

From: Loretta Guarino Reid <lguarino@adobe.com>
Date: Tue, 26 Apr 2005 17:22:08 -0700
To: w3c-wai-gl@w3.org
Message-id: <6.1.1.1.2.20050426163831.01cd34f0@mailsj-v1.corp.adobe.com>

		technology-supports-access issues summary

Guideline 4.2 Ensure that user interfaces are accessible or provide an
accessible alternative(s)
	http://trace.wisc.edu/bugzilla_wcag/issuereports/technology-supports-access_issues.php

This summary assumes that the proposals for GL 4.2, sent in an earlier 
message, are adopted.

Overview of Issues

+ Addressed by appropriate selection of baseline
	244, 1073, 1133, 1221, 1334, 1335
+ Close: Alternate pages
	972, 1060
+ Close: Graceful degradation
	463, 842, 855, 1419
+ Close: Overcome by events
	712, 821, 822, 899, 970, 971, 993, 1050


Appropriate selection of baseline:

	Issue 244: Keyboard access for devices that have no AT
		http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=244
	Issue 1073: Baseline support / conformance / fallbacks
		http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=1073
	Issue 1133: Use static, rather than dynamic, content for critical parts of 
the Web site
		http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=1133
	Issue 1221: lack of support for Javascript in W3C technologies
		http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=1221
	Issue 1334: Principle 4: what is meant by "current technologies"?
		http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=1334
	Issue 1335: scripting should require alternative representation
		http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=1335

These issues address concerns about what baseline WCAG2 was adopting. We 
should explain the decision to move the baseline definition out of the 
guidelines, and share the definition of baseline and (non-normative) 
guidance for choosing baselines to these submitters, and confirm that we 
can close the issues.


Alternate pages:

	Issue 972: Don't encourage separate sites
		http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=972
	Issue 1060: Do we require or permit alternative accessible pages?
		http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=1060

We no longer say anything at all about alternate pages or sites, so we can 
close these issues.

Graceful degradation:
	Issue 463: why list "required" technologies?
		http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=463
	Issue 842: 4.2.3.2 should be level 1 or 2.
		http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=842
	Issue 855: clarification on ".. can still access the resource"
		http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=855
	Issue 1419: what is a degraded but usuable experience?
		http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=1419

The definition of baseline describes graceful degradation by discussing the 
use of technologies beyond the baseline.

Overcome by events:

Issue 426: Development process v characteristics of accessible content
	http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=426


	Issue 712: what constitutes sufficiently documenting required techs?
		http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=712
	Issue 821: Reword SC L1 #2 for consistency with guideline
		http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=821
	Issue 822: Level 2 SC is too vague
		http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=822
	Issue 889: Move this guideline to principle 1
		http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=889
	Issue 970: Why single out "user interface"
		http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=970
	Issue 971: Benefit sounds redundant
		http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=971
	Issue 993: Focus on strict platform independency and flexible content delivery
		http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=993
	Issue 1050: Comments and questions for technology-supports-access
		http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=1050
	Issue 1417: GL 4.2 hard to understand
		http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=1417
	Issue 1418: what are 'accessibility conventions of the mark-up'
		http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=1418
	Issue 1336: User agents: remove all "until" clauses and assume conforming UA?
		http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=1336

The items discussed in these issues have been removed.
Received on Wednesday, 27 April 2005 00:22:17 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 23:39:37 UTC