|
The HiSoftware
Potential Screen
Movement and
Flickering Report
allows AccVerify or
AccMonitor users to
locate elements on
pages that can cause
the potential to
make the screen move
or flicker. This
report can be
downloaded and used
as is or you can
customize it to
match your exact
organization
requirements.
Note the default
checks may need to
be edited slightly
to match your
organizations
policies.
This custom report
can be downloaded
for use with
AccVerify,
AccRepair, and
AccMonitor. Simply
extract the files
into the C:\Program
Files\HISC\AccVerify
Pro\Test Suites or
C:\Program
Files\HISC\AccMonitor\Test
Suites directories
to use. For those
using the custom
check development
environment, you can
store in any folder
as long as all files
are in the same
folder.
-
Download the
Potential Screen
Movement and
Flickering
Report (ZIP
file)
-
Download other
Custom Reports
Checkpoints and
detail of this
report follow:
-
1. Detect page
elements that
might cause the
page to link or
flicker.
Blinking and
flickering items
on pages can
cause seizures
in users with
photosensitive
epilepsy. The
Section 508
1194.22
standards
Checkpoint J
states to avoid
flickering
between 2 and 55
flashes per
second. The
WCAG 1.0
Guidelines
Checkpoint 7.1
states to avoid
flickering
between 4 and 59
flashes per
second with a
peak sensitivity
of 20 flashes
per second.
Note: You can
adjust these
values in the
XML Custom Check
File, via the
Custom Check
Editor. You can
add words or
images
extensions to
validate.
Example you may
wish to add the
word logo, some
people argue
that logo is a
bad word to have
in alternative
text.
Specific Quality
Checks for Potential
Screen Movement and
Flickering Report
-Descriptions
The following
section describes
what checkpoints are
being run with this
content quality
assurance checklist
for your content
management needs.
The checkpoints are
described as well as
information on why
these checks are
important.
1.1 Validate that
the objects found in
the page do not
cause flickering.
When an object,
defined by the
<OBJECT> element is
found in your page,
then you need to
perform a manual
check to make sure
that the page does
not flicker. The
Section 508 1194.22
standards Checkpoint
J states to
avoid flickering
between 2 and 55
flashes per second.
The
WCAG 1.0 Guidelines
Checkpoint 7.1
states to avoid
flickering between 4
and 59 flashes per
second with a peak
sensitivity of 20
flashes per second.
1.2 Validate that
the applets found in
the page do not
cause flickering.
When an applet,
defined by the
<APPLET> element is
found in your page,
then you need to
perform a manual
check to make sure
that the page does
not flicker. The
Section 508 1194.22
standards Checkpoint
J states to
avoid flickering
between 2 and 55
flashes per second.
The
WCAG 1.0 Guidelines
Checkpoint 7.1
states to avoid
flickering between 4
and 59 flashes per
second with a peak
sensitivity of 20
flashes per second.
1.3 Validate that
script found in the
page does not cause
flickering.
When script, defined
by the <SCRIPT>
element is found in
your page, then you
need to perform a
manual check to make
sure that the page
does not flicker.
The
Section 508 1194.22
standards Checkpoint
J states to
avoid flickering
between 2 and 55
flashes per second.
The
WCAG 1.0 Guidelines
Checkpoint 7.1
states to avoid
flickering between 4
and 59 flashes per
second with a peak
sensitivity of 20
flashes per second.
1.4 Validate that
the <BLINK> element
is not found in your
page
The <BLINK> element
should not be used
in your page. The
Section 508 1194.22
standards Checkpoint
J states to
avoid flickering
between 2 and 55
flashes per second.
The
WCAG 1.0 Guidelines
Checkpoint 7.1
states to avoid
flickering between 4
and 59 flashes per
second with a peak
sensitivity of 20
flashes per second.
1.5 Validate that
the <MARQUEE>
element is not found
in your page.
The <MARQUEE>
element should not
be used in your
page. Scrolling text
can cause problems
for some users. The
Section 508 1194.22
standards Checkpoint
J states to
avoid flickering
between 2 and 55
flashes per second.
The
WCAG 1.0 Guidelines
Checkpoint 7.1
states to avoid
flickering between 4
and 59 flashes per
second with a peak
sensitivity of 20
flashes per second.
1.6 Validate that
the embedded content
found in the page
does not cause
flickering.
When an object,
defined by the
<EMBED> element is
found in your page,
then you need to
perform a manual
check to make sure
that the page does
not flicker. The
Section 508 1194.22
standards Checkpoint
J states to
avoid flickering
between 2 and 55
flashes per second.
The
WCAG 1.0 Guidelines
Checkpoint 7.1
states to avoid
flickering between 4
and 59 flashes per
second with a peak
sensitivity of 20
flashes per second.
1.7 Validate any
<param element that
has a multimedia
extension present.
Many times,
multimedia files are
placed inside of
objects, or embedded
elements in the
page. These objects
take parameters to
refer to the file to
play, along with
other settings. This
checkpoint looks for
the <param element
and if found, looks
for a listing of
common multimedia
extensions in the
value attribute.
The
Section 508 1194.22
standards Checkpoint
J states to
avoid flickering
between 2 and 55
flashes per second.
The
WCAG 1.0 Guidelines
Checkpoint 7.1
states to avoid
flickering between 4
and 59 flashes per
second with a peak
sensitivity of 20
flashes per second.
1.8 Validate any
multimedia files
referenced by
linking.
If you have a
hyperlink to a file
with a multimedia
extension, you can
test that file to
see if it flickers
or blinks at the
user. Hyperlinks are
defined by the <a
href> element and
attribute. The
Section 508 1194.22
standards Checkpoint
J states to
avoid flickering
between 2 and 55
flashes per second.
The
WCAG 1.0 Guidelines
Checkpoint 7.1
states to avoid
flickering between 4
and 59 flashes per
second with a peak
sensitivity of 20
flashes per second.
1.9 Validate any SVG
files referenced by
the <IMG tag do not
flicker or blink.
If you have
referenced an SVG
file within an <IMG
tag, confirm that it
is not causing the
page to blink or
flicker at the
user. The
Section 508 1194.22
standards Checkpoint
J states to
avoid flickering
between 2 and 55
flashes per second.
The
WCAG 1.0 Guidelines
Checkpoint 7.1
states to avoid
flickering between 4
and 59 flashes per
second with a peak
sensitivity of 20
flashes per second.
1.10 Validate any
<Embed> element that
has a multimedia
extension present in
the src attribute.
Many times,
multimedia files are
placed inside of
objects, or embedded
elements in the
page. These objects
take parameters to
refer to the file to
play, along with
other settings. This
checkpoint looks for
the <embed> element
and if found, looks
for a listing of
common multimedia
extensions in the
src attribute. The
Section 508 1194.22
standards Checkpoint
J states to
avoid flickering
between 2 and 55
flashes per second.
The
WCAG 1.0 Guidelines
Checkpoint 7.1
states to avoid
flickering between 4
and 59 flashes per
second with a peak
sensitivity of 20
flashes per second.
1.11 Validate that
any animated gif
images found in the
page do not cause
flickering.
When animated GIF
images are found in
the page, you need
to perform a manual
check to make sure
that the page does
not flicker. The
Section 508 1194.22
standards Checkpoint
J states to
avoid flickering
between 2 and 55
flashes per second.
The
WCAG 1.0 Guidelines
Checkpoint 7.1
states to avoid
flickering between 4
and 59 flashes per
second with a peak
sensitivity of 20
flashes per second.
|