Thread Subject: teitac-documentation: potential revisions
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: Hoffman, Allen
Date: Tue, Jun 12 2007 6:40 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
All:
Again, sorry for my delay.
I believe to sum up my changes here I have rolled 7.1a,b, and c together
greatly--as i feel much of this content in b and c is a subpart of what
was being addressed in a. I have suggested a new provision to require
electronic content as a whole to be provided in at least one accessible
format, and to be authored to meet accessibility standards related to
the accessibility functionalities of the format. I only strengthened
7.1d slightly to ensure that the shoulds are musts as all of those
practices are needed, and not "nice to haves".
Information documentation and support updates to currently drafted
provisions.
Current provision: none specifically
Revised (new):
Electronic content shall be provided in at least one format that meets
minimum format accessibility standards, and shall be authored to be
accessible using the accessibility functionalities of that format.
Rationale:
This proposed provision will require that ALL electronic content is
delivered in at least one format that is accessible, and has been
authored to meet the accessibility standards using the functionalities
available in the format. This is needed to overcome the scope of the
current intra and internet applications label for CFR1194.22, whether
intentional or not. It is not sufficiently broad to address specific
product or service information needs, but is the foundation for the
delivery of the content itself. This could be added at top of
electronic content format standards rather than here possibly.
Disabilities: Primary blind/low-vision, motor, and cognitive
Current provision 7.1a:
7.1a: To provide documentation to users on the installation,
configuration and use of the product, Federal agencies shall require
that all documentation supporting
The product, including but not limited to reports, system documentation
and user training or technical support materials conform the relevant
accessibility
Provisions in 1194 Subparts B and C.
Revised:
7.1a: Documentation regarding product or service installation,
configuration, integration, operation or usage, including keyboard
operation, accessibility features, maintenance, and troubleshooting
shall be provided in at least one electronic format which meets
applicable content format accessibility standards, and is authored to
meet applicable standards from CFR1194 parts B and C which relate to the
specific accessibility functionality of the format.
Discussion:
Note, documentation may include, but is not limited to reports, system
documentation and user training or technical support materials.
Rationale:
First, I have included "and service" here to address documentation for
services. Second I have included "integration" in the list as that
information is often critical to ensuring that items can be deployed
successfully including the accessibility features. I have also included
reference to keyboard operation to eliminate need for entirely separate
provision. I have included reference to content format accessibility
standards, and the fact that the content must also be authored to use
the capacities of the format for accessibility. I think a more general
provision should say that all electronic content shall be provided in at
least one format that meets minimum format accessibility standards, and
the content shall be authored to be accessible using the accessibility
functionalities of the selected format, see first suggested provision.
I have not included the "alternate formats upon request" or "alternate
methods" because I believe provision of an accessible electronic format
should allow for the information to be used effectively. I have
integrated information from 7.1B I think in this new 7.1a.
Current provision 7.1b:
Wrap in to 7.1a.
Current provision 7.1c:
7.1c: Information about keyboard shortcuts shall be made available in
documentation.
Recommendation:
Integrate into 7.1a. This is an important detail, but doesn't seem to
rise to provision level to me.
Current provision 7.1d:
7.1d: Best practices for providing documentation to people with
disabilities include:
1. Context-sensitive help, which offers documentation or support for the
features and functions of the current page, screen or window should be
offered,
using a consistent set of accessible commands to access it.
2. Documentation and training materials should include text descriptions
of the interface. These descriptions should stand on their own and be
understandable
Without relying on graphic images in the materials.
3. Descriptions of a user interface should refer to elements by name or
function, in addition to their location in the visual interface.
Revision:
Only minor to make these stronger.
Best practices for providing documentation to people with disabilities
include, but not limited to:
1. Context-sensitive help, which offers documentation or support for the
features and functions of the current page, screen or window must be
offered,
using a consistent set of accessible commands.
2. Documentation and training materials must include text descriptions
of the user interface. These descriptions must stand on their own and be
understandable
without relying on graphic images in the materials.
3. Descriptions of a user interface must refer to elements by name or
function, in addition to their location in the visual interface.
Discussion:
Each of the best practices above are critical to successfully providing
product or service information to people with disabilities, but are some
of the options available to ensuring such information is accessible, and
useable.
Allen Hoffman
DHS : CRCL & OCIO;
DHS Office On Accessible Systems and Technology
v: 202-447-0303; c: 202-213-1835; tty: 202-401-0725
email: = EMAIL ADDRESS REMOVED = or = EMAIL ADDRESS REMOVED =
This communication, along with any attachments, is covered by federal
and state law governing electronic communications and may contain
sensitive and legally privileged information. If the reader of this
message is not the intended recipient, you are hereby notified that any
dissemination, distribution, use or copying of this message is strictly
prohibited. If you have received this in error, please reply
immediately to the sender and delete this message.
Thank you.
- Next message in Thread: None
- Previous message in Thread: None