Checkpoints
[WAI]
Priority 1 accessibility issues. A Web content developer must satisfy
this checkpoint. Otherwise, one or more groups will find it impossible
to access information in the document. Satisfying this checkpoint is a
basic requirement for some groups to be able to use Web documents.
1.1
Provide a text equivalent for every non-text element (e.g., via "alt",
"longdesc", or in element content). This includes: images, graphical
representations of text (including symbols), image map regions,
animations (e.g., animated GIFs), applets and programmatic objects,
ascii art, frames, scripts, images used as list bullets, spacers,
graphical buttons, sounds (played with or without user interaction),
stand-alone audio files, audio tracks of video, and video.
http://www.hipocampo.org/: (0/5)
4.1 Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions).
http://www.hipocampo.org/: (0/1)
[WAI]
Priority 2 accessibility issues. A Web content developer should satisfy
this checkpoint. Otherwise, one or more groups will find it difficult
to access information in the document. Satisfying this checkpoint will
remove significant barriers to accessing Web documents.
No checkpoint for this priority has failed to fulfill
[WAI]
Priority 3 accessibility issues. A Web content developer may address
this checkpoint. Otherwise, one or more groups will find it somewhat
difficult to access information in the document. Satisfying this
checkpoint will improve access to Web documents.
No checkpoint for this priority has failed to fulfill