Logically distinct assembly of content (such as a file, set of files, or streamed media) that: functions as a single entity rather than a collection; is not part of software; and does not...
Search Results "Software Development"
Commonly Searched Documents
-
Document
-
§382.43(e)
carrier covered under paragraph (c) of this section, you must provide a disclaimer activated when a user clicks a link on your primary Web site to an external Web site or to third-party software...
-
When to add alternate text to Images
Screen reader software cannot analyze images, and therefore cannot convert images/graphics to text automatically....
-
§ 382.43(e)
carrier covered under paragraph (c) of this section, you must provide a disclaimer activated when a user clicks a link on your primary Web site to an external Web site or to third-party software...
- Beneficial Designs High Efficiency Trail Assessment Process (HETAP) Software 3.0 Wheeled Instrumentation Sensor Package for Data Collection
-
§ 36.303(b)(2)
(2) Qualified readers, taped texts, audio recordings, brailled materials and displays, screen reader software, magnification software, optical readers, secondary auditory programs (SAP),...
-
§ 36.303(b)(2)
(2) Qualified readers; taped texts; audio recordings; Brailled materials and displays; screen reader software; magnification software; optical readers; secondary auditory programs (SAP);...
-
Dragon
I have ordered the current Dragon premium software and am looking forward to using it. Jay Seidel ...
-
Braille (Advisory Guidance)
On the other hand, manufacturers may wish to consider producing Braille documents "in house" using a personal computer, Braille translation software, and a Braille printer....
-
USDA Forest Service Missoula Technology and Development Center Facilities Toolbox: Accessibility Tools
This section of the facilities toolbox provides information to help integrate accessibility into facilities while complying with legal requirements and codes. The topics below...
-
D.1. - How does Section 508 affect the requirements development phase of an acquisition?
Section 508 requires agencies to take additional considerations into account when defining their needs for EIT – namely the Access Board’s standards. As noted above, Section 508...
-
E102.2 ANSI/HFES (Section-by-Section Analysis)
E102.2 ANSI/HFES (Section-by-Section Analysis) ANSI/HFES 200.2, Human Factors Engineering of Software User Interfaces — Part 2: Accessibility (2008), would be incorporated by reference...
-
Issue 8: What are the top issues for developing design guidance (i.e., Lowhanging fruit design issues)?
You know, it’s funny; we develop the research – and, as I said, we don’t do research; I’m just saying it is an opportunity to bring this low-vision issue into the criteria, you know, relatively...
- Allegion Schlage NDE Series Wireless Lock with ENGAGE™ Technology
-
Application
Software designed to perform, or to help the user to perform, a specific task or tasks....
-
Application
Software designed to perform, or to help the user perform, a specific task or tasks....
-
Application
Software designed to perform, or to help the user perform, a specific task or tasks....
-
Application
Software designed to perform, or to help the user to perform, a specific task or tasks....
-
Q5.) What dimensions and conditions can practitioners reasonably consider to be compliant when the conditions, as constructed, do not meet the technical requirements exactly and there are no official, published, industry-developed tolerances?
To our knowledge, none of the industry associations have developed official tolerances for sloped concrete or asphalt surfaces except those laid down by large paving machines. ...
-
502.2.2 No Disruption of Accessibility Features
Software shall not disrupt platform features that are defined in the platform documentation as accessibility features....
-
502.2 Documented Accessibility Features
Software with platform features defined in platform documentation as accessibility features shall conform to 502.2....
-
E. Assistive Technology
In this NPRM, the Board proposes to revise its existing 508 Standards and 255 Guidelines by: (a) updating the existing requirements for mainstream ICT software products—namely, platforms...
-
2. Treatment of WCAG 2.0
The existing 508 Standards and WCAG 1.0 were under development around the same time period in the late 1990s; WCAG 1.0 was finalized in May 1999, and the existing 508 Standards shortly thereafter...
-
I. Need For and Final Objectives of the Guidelines.
The Access Board is responsible for developing accessibility guidelines in conjunction with the Federal Communications Commission (FCC) under section 255(e) of the Telecommunications Act...