Illustrate the examples from the checkpoint (logos, photos, submit buttons, etc.)
"interactive scripts have a functional equivalent..." can be described in core
and developed further in scripting specific techniques. However, this concept in general
needs to be explored further.
Not technology specific. Put info and examples here.
e.g. Mona Lisa or Beethoven's 5th. Label them as such rather than trying to describe.
Not technology-specific. Put info and examples here.
Requires development of both core techniques and technology-specific.
The non-technology aspect of this success criterion is related to types of content.
A portal site will have a different logical structure than a long document.
Since the structure must be represented in the markup, there are lots of
technology-specifics to cover.
Since the structure must be represented in the markup, there are lots of
technology-specifics to cover.
Types of models rather than types of content as with 1.3?
PDF vs CSS will separate structure from presentation differently.
Technology specific. e.g. refer to the Language section in the latest
HTML Techniques
for WCAG 2.0 draft (eeeks. no targets! pls search for "language" until a new draft
is published...apologies...).
Core techniques: provide overview. related to 1.3 and 1.5.
Tech-specifics: examples. site map, search, index, etc. Particulary related
to server-side techniques.
Checkpoints 1.3 and 1.5 "enforce" consistency through structure and markup. If these
are followed, then this criteria should be met as a side-effect.
If content types are developed in relation to checkpoints 1.3 and 1.5, will it reduce the
need for this checkpoint?
Discussion with examples will go here.
Perhaps provide some technology-specific examples.
Need technology-specific exmaples with some overview info in Core Techniques.
The success criteria for checkpoint 2.3 are an either/or. Therefore, they will likely be
handled a bit differently than the rest of the success criteria, right?
Provide core exmaple and technology specifics. e.g.
script examples
in HTML: if a has target="new" then you must...
technology-specifics: form or client-side scripting
technology-specifics: server-side
technology-specifics: server-side/form
show previous examples w/out time limit?
Technology specifics needed.
Technology-specific research needed.
Technology-specific examples.
Reliance on 1.3 and 1.5. Primary checks in core. Examples in tech-specifics.
technology-specific examples are needed.
Specifically address the different media types? Within tech-specifics address media types?
Not technology-specific.
Need to help people understand the circumstances for when to employ these.
This is the same as checkpoint 3.5. Perhaps instead of having a separate checkpoint
leave this success criteria? Either way, it requries technology-specific examples and info.
Technology-specific examples.
Information about deciding when to provide in core techniques.
In core techniques - info about how to choose.
Reference XAG - this be the "technology-specific" piece?
Technology-specific examples, refer to specifications.
Technology-specifics. e.g. Accessibility features of SMIL, SVG.
Some explantation in Core, then "tech-specifics" is UAAG and UAAG techs.
Device indie event handlers. Redundant with that?
Provide info in Core Techniques.
Technology-specifics. Primarily CSS/HTML Techniques. Will be a side benefit if
good structure is used.