Documentation:November 2
Documentation > November 2
Minutes
MEETING NOTES
- Next week , the Co-Chairs will report on Co-Chair selection, how many times we’ve met and things we will be addressing as a subcommittee.
- Next week, plan to go through laundry list of issues, evaluate and analyze them and then prioritize them.
Consider a broad response: Maybe some things that are not in our jurisdiction that can be put in the issue bin, for other subcommittees or for the committee as a whole.
Either not addressed by current guidelines, or need updating or refreshing or have arisen due to changes in technology.
- Subpart D 1194.41 and definition of Alternative Formats
Definitions in Subpart A (but no reason we cannot alter it). We’ll be adding to the list of terms defined there.
Who’s choice is it? Which format? Braille? That’s enough? 1194.41 it gets more complicated because of the (at no additional charge) from vendor to agency or agency to user? Not clear.
Recreation of documentation as needed; already usually requested electronically. How do we address this? Not necessarily a 508 question.
New Question - If I’m providing a copy of the materials to the government in an electronic format, then the idea is that the agency will produce it in alternate format. What about copyright? Esp. if manuals are sold.
Answer - Copyright law offers an exception for access purposes for people with disabilities.
- 1194.41(b) – Accessibility and Compatibility features of products shall be available.
(VPAT – either is or is more detailed then) but is not reference anywhere else. Tremendous value – how it can be made more salient and thorough and an in integral part of the 508 process. Something that is not being implemented right now. Further clarifying it and explaining what is affected.
- 1194.41(a) – who should be providing the document in alternate format?
The vendor or the government agency? Clarification?
Further Questions and Discussion Points
It’s been done both ways. Usually received in electronic format, and what constitutes an accessible electronic format. Much of this subpart had language added that once an agency purchased an item or service, then the agency’s IT help and service would make it accessible. Vendor’s do manuals, then agency picks up the rest. Once “internal” then the processes the agency put in place will handle the troubleshooting. – documentation (what comes in the box) and also help-desk. Who’s responsibility?
What responsibilities lie with the vendor and what with the agency’s internal IT support services? Who’s responsibility for documents in alternate format?
Response from Terry Weaver - It is based on contract. The agency is the one who falls under 508 and should require that the information be provided in an accessible format. Under the FAQs @ www.section508.gov. There is nothing preventing an agency form requiring a vendor to provide as much technical support as needed. Especially if it is a product the agency does not have technical support for that product, it can be written into the contract.
Initial information the agency can provide. The question then comes to be – where is the hand off? The principle is that there is a shared responsibility as there is a value chain from vendor to agency to end user and there needs to be good guidance on how to divide up that responsibility so it is clear.
Specific in the RFP. – competitive factor and decision factor in evaluating bids. Making it more of a business proposition. You want to get vendors to be as comprehensive as possible in what they provide and allows for specificity and open expectations.
Eg. Purchasing wireless service vs. purchasing a software program that will be heavily modified inside the agency.
What constitutes an accessible electronic format? Tend to cite to the web standards.
Participants
- Easter Seals - Jennifer Dexter
- American Council of the Blind – Day Al-Mohamed
- Information Technology Industry Council - Ken Salaets
- Sun Microsystems, Inc - Michele Budris
- GSA - Terry Weaver
- AT&T - Toni Acton
- Council of Citizens with Low Vision - Dawn Wilcox
- Amy Chen
- ITAA - Rex Lint
- Social Security Administration - Mike Fratkin
- Jim Tobias
- US Access Board - David Baquis
- GSA - Helen Chamberlin
- Microsoft - Laura Ruby
- HP - Michael Takemura
