This Wiki page is edited by participants of the WCAG Working Group. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.

Difference between revisions of "Post WCAG 2"

From WCAG WG
Jump to: navigation, search
(Adding Dynamic Content)
Line 52: Line 52:
 
* Document a series of techniques about CSS media queries and layout module to provide more flexible layout mechanisms that meet WCAG more elegantly.
 
* Document a series of techniques about CSS media queries and layout module to provide more flexible layout mechanisms that meet WCAG more elegantly.
 
* Need techniques about CSS spriting issues. Cynthia has a PFWG action to submit some.
 
* Need techniques about CSS spriting issues. Cynthia has a PFWG action to submit some.
 +
 +
== Misc ==
 +
 +
* Sometimes WCAG has a requirement but a "mirror image" requirement that is also an issue isn't as clearly covered. E.g., things that look like headings have to be marked as headings, but things marked as headings don't have to look like headings.

Revision as of 20:18, 20 June 2013

Notes about things we might want to do post WCAG 2.0.

Metadata

Comments from Liddy Nevile:

(1) Any resource that is not described with metadata must be accessed in order to discover what it is about and how it works and can be accessed. This places a burden on users at selection time, if it is being accessed other than because it is already known to be what the user wants, and so it makes access to the resource less flexible and potentially distracting (as is the case when it is not what the user wants but they have had to retrieve it to discover this).

(2) When the means of accessibility is not a static, conformant page but rather a dynamic compilation of components, as is common with Web 2.0, and as may be achieved by a service that provides resources to match a user's personal needs and preferences (using components that in themselves and in isolation may not be fully conformant), without appropriate metadata, the service agent can not know what components to compile to suit the user. In this case, such a service that potentially provides a higher than usual form of accessibility would be denied. It seems odd to allow this situation to exist.

Change of context after timeout

On 30 September 2010 we discussed the question of a survey that pops up after a delay when a page loads. This was determined to be a failure of 3.2.5 Change on Request and 2.2.4 Interruptions, both AAA. It was considered almost but not quite a failure of 3.2.1 On Focus (which is Level A). The feeling is that it should be a failure at AA, but the SC as they exist didn't cover the situation. Two issues need to be more clearly addressed in the future:

  • Should loading of a page be covered by the same provisions that 3.2.5 has for focusing a component?
  • A change of context that happens after a timeout creates a greater problem with respect to interruptions and disorientation than a change of context that happens immediately, yet appears to be permitted as a loophole because the wording of the SC is specific to changes that happen immediately.

Keyboard Navigation

  • Focus order vs programmatically determined reading order vs visual presentation order;
  • what keyboard users want/expect from initial focus placement,
  • strategies and standards for navigating around a page in ways other than tabbing through all controls
  • possible standards and conventions for keyboard access
  • User Agent and AT support that is needed to improve this experience for HTML and DHTML

Low Vision Support

See Wayne Dick's public comments and follow-up comments about his need for

  • modification of font-family based on element (tag) type,
  • enlargement of letter, word and line spacing for text and
  • variable enlargement linked to element type.

Adding Dynamic Content

If a user action causes new content to be added, especially outside the user's current viewport, the user needs to know both that the content changed and where the changes are located. This is particularly an issue for blind users when content is added before the current location. ARIA live regions may be a solution to this in some situations.

See Survey of LC 2744

Techniques

  • We will consider including information that more clearly associates failures with the technologies they relate to in future versions of the Techniques document. Issue 2678
  • Document a series of techniques about CSS media queries and layout module to provide more flexible layout mechanisms that meet WCAG more elegantly.
  • Need techniques about CSS spriting issues. Cynthia has a PFWG action to submit some.

Misc

  • Sometimes WCAG has a requirement but a "mirror image" requirement that is also an issue isn't as clearly covered. E.g., things that look like headings have to be marked as headings, but things marked as headings don't have to look like headings.