Thread Subject: Re: Proposal for a new 'UI Settings (Non-Visual)'provision
Note
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
From: David Poehlman
Date: Wed, Oct 10 2007 5:00 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: None
- Previous message in thread: Katie Haritos-Shea: "Proposal for a new 'UI Settings (Non-Visual)' provision"
- Messages sorted by: Author | Thread | Date
Nonvisual is confusing.
----- Original Message -----
From: "Katie Haritos-Shea" < = EMAIL ADDRESS REMOVED = >
To: < = EMAIL ADDRESS REMOVED = >
Sent: Wednesday, October 10, 2007 4:30 PM
Subject: [teitac-websoftware] Proposal for a new 'UI Settings
(Non-Visual)'provision
Action Item for KHS.
All,
I am re-submitting this new provision proposal taking into account:
(a) changes to Draft since July 25
(b) because most of the responses/conversation on the list were off topic
(c) react to relevant responses
My action item was to produce a proposal for a new User Preference Settings
(Non-Visual) provision that is seperate from the Visual Display setting of
3-D User Preferences which is currently placed in the Teitac DRAFT under:
Technical Provisions, User Interface and Electronic Content Provisions,
3-D User Preferences.
This new proposed provision, discussed first at the July 25 TEITAC
Web/Software
telecon, is meant/designed to cover tactile, olfactory, gustatory, vocal and
aural settings, and possibly other sensory modality user-set needs and
preferences.
I think there are at least two issue that must be covered;
(1) stopping, and
(2) controlling non-visual interactions.
With that said, I realize that this proposal is very broad, and meant to be
that way.
New Provision Proposal:
Name: 'UI Settings (Non-Visual)' or 'Non-Visual UI Settings'.
Provision Text: If an application [user interface] provides a mode of
interaction other than visual (such as vocal, aural, gustatory, olfactory,
tactile) that can affect human sensory functions, settings shall be provided
that allow the user to stop and control those functions, or, provides a mode
that utilizes the platform user settings for control of those functions.
Back in July Peter Korn was concerned with the testability of this
provision. "Unlike with the visual, where we can speak to color, contrast,
font, font size, and focus indication, we have no idea what the specific
control points are for olfactory and tactile and taste user interfaces are,
let alone how to measure those control points."
I do not think control points are necessary to define. For testability
purposes
one needs to ask two questions;
(1) Does the user interface provides a mode of interaction other than
visual?
and then, IF yes....
(2) Does the application then allow the user to stop and control those
functions, or, provide a mode that utilizes the platform user settings for
control of those functions?
Others were concerned that this provision guilty of was seperating-out
abilities, and/or was too futuristic.
Each and every day we use 'all' of our senses to interact with our
world........technology is quickly catching up. We need some way assert
accessibility into this paradigm. The possibility that other sensory
modalities
will be utilized to "grab" the attention of consumers is very real. This is
a testable broad provision meant to cover just that.
Reference Original Email Thead:
http://teitac.org/mailarchives/mail_thread.php?thread=1366&id=6029#6029
Reference:
Taste and Smell Disorders: http://www.anosmiafoundation.org/smell.shtml
Also, provided for reference......
(3-D User Preferences:
Applications must provide a mode that utilizes platform settings for color,
contrast, font type, font size, and focus cursor. In the absence of platform
settings for color and contrast, all text (and images of text) must have a
contrast ratio of at least 5:1 except for unavailable items or pure
decoration.
Large scale text (or images of large scale text) must allow a contrast ratio
of
at least 3:1.)
* katie *
Katie Haritos-Shea
Section 508 Technical Policy Analyst
703-371-5545
People may forget exactly what it was that you said or did,
but they will never forget how you made them feel.......
- Next message in Thread: None
- Previous message in Thread: Katie Haritos-Shea: "Proposal for a new 'UI Settings (Non-Visual)' provision"