Thread Subject: Re: teitac-websoftware Digest, Vol 7, Issue 30

From: Therese Wiley
Date: Fri, Apr 13 2007 9:35 AM

• Return to this mailing list's archives
• View all messages in this thread
• Next message in thread: None
• Previous message in thread: None
• Messages sorted by: Author | Thread | Date

Please reference:

UNIFORM FEDERAL ACCESSIBILITY STANDARDS
The flashing frequency of visual alarm devices shall be less than 5 Hz. If
such ... (b) The Architectural and Transportation Barriers Compliance
Board ...
www.access-board.gov/ufas/ufas-html/ufas.htm

Thanks.

Therese E. Wiley
USDA-National Agricultural Statistics Service (NASS)
NASS Disability Employment Program Manager
I.T. Specialist, Information Technology Division
202-720-7892
202-720-9909 (fax)




= EMAIL ADDRESS REMOVED =
Sent by: = EMAIL ADDRESS REMOVED =
04/13/2007 10:52 AM
Please respond to
= EMAIL ADDRESS REMOVED =


To
= EMAIL ADDRESS REMOVED =
cc

Subject
teitac-websoftware Digest, Vol 7, Issue 30






Send teitac-websoftware mailing list submissions to
= EMAIL ADDRESS REMOVED =

To subscribe or unsubscribe via the World Wide Web, visit

http://list.teitac.org/mailman/listinfo/teitac-websoftware
or, via email, send a message with subject or body 'help' to
= EMAIL ADDRESS REMOVED =

You can reach the person managing the list at
= EMAIL ADDRESS REMOVED =

When replying, please edit your Subject line so it is more specific
than "Re: Contents of teitac-websoftware digest..."


Today's Topics:

1. Re: Flashing provisions (Gregg Vanderheiden)
2. Re: Authoring Tools (David Poehlman)
3. New Version of Flat Sortable (Gregg Vanderheiden)


----------------------------------------------------------------------

Message: 1
Date: Thu, 12 Apr 2007 18:43:12 -0500
From: "Gregg Vanderheiden" < = EMAIL ADDRESS REMOVED = >
Subject: Re: [teitac-websoftware] Flashing provisions
To: "'TEITAC Web/Software Subcommittee'"
< = EMAIL ADDRESS REMOVED = >
Message-ID: <010101c77d5c$556d2cf0$a117a8c0@NC84301>

Actually the provision was designed to be easier to meet.

If there are no more than 3 flashes in any second you are done.

If there are - you can change it so that there aren't OR you can do
additional things to check and see if it might still be safe.

It also allow the Access Board to list some common things (like most
blinking LEDs) that are known to fall into this category.

Finally, there is a free Tool that Trace released that will analyze any
screen capture to see if it would violate this. (It is based on Graham
Hardings work and was developed with Dr Harding and CRS)

Trace released the tool awhile ago in beta. It is available from our
website for free (and will stay free).


Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.



> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Fratkin, Mike
> Sent: Monday, April 09, 2007 9:11 AM
> To: TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] Flashing provisions
>
>
> With the current requirement, measuring the flash or blink
> frequency has always been an issue. Adding these additional
> requirements seems to add more complexity to this task for
> procurement officials or federal application testers.
>
> Additionally, there is an additional aspect of flashing that
> seems to bother our users as well. This is the occurrence of
> screen flashing upon a screen refresh. This can happen for
> any number of reasons and greatly affects users with screen
> magnifiers. This should be considered but the ability to
> measure any of this is paramount.
>
> Mike Fratkin
>
> [Andi wrote:]
> When we discussed the flashing provision, we talked about
> harmonization with WCAG 2.0 but determined that the WCAG 2.0
> wording was too confusing and not mature enough at the time.
> The WCAG working group has recently settled on the following
> wording which is much simpler than what they had
> before:
>
> No more than 3 flashes above thresholds
> No part of the product flashes more that three
> times in any one second period unless
> a) the flashing is greater than 50 hz or
> b) the combined area of flashing occurring
> concurrently and contiguously occupies less than one quarter
> of any 10 degrees of visual field
> c) the flashing is not fully saturated red
> and the change in brightness is less than 10 percent of full
> scale brightness.
>
> This is being proposed in the general subcommittee. Are there
> any issues with replacing 21 (k) and 22 (j) with similar wording?
>
> 21 (k):
>
> Current: Software shall not use flashing or blinking text,
> objects, or other elements having a flash or blink frequency
> greater than 2 Hz and lower than 55 Hz.
>
> Proposed: Software shall not use flashing or blinking text,
> objects, or other elements having a flash or blink frequency
> of more than three times in any one second period unless:
> a) the flashing is greater than 50 hz or
> b) the combined area of flashing occurring concurrently
> and contiguously occupies less than one quarter of any 10
> degrees of visual field
> c) the flashing is not fully saturated red and the
> change in brightness is less than 10 percent of full scale brightness.
>
> 22 (j):
>
> Current: Pages shall be designed to avoid causing the screen
> to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
>
> Proposed: Pages shall be designed to avoid causing the screen
> to flicker more than three times in any one second period unless:.
> a) the flashing is greater than 50 hz or
> b) the combined area of flashing occurring concurrently
> and contiguously occupies less than one quarter of any 10
> degrees of visual field
> c) the flashing is not fully saturated red and the
> change in brightness is less than 10 percent of full scale brightness.
>
> Note that 55 Hz was apparently a typo in 508 and should have
> been 50 Hz.
>
> Andi
>
>

• Next message in Thread: None
• Previous message in Thread: None