Documentation:Topic List
Contents |
Topic List
This page is for tracking issues/topics this subcommittee needs to look into.
All drafts have been moved to: the main Documentation page, including the most current draft of all provisions, and drafting history.
Documentation Issues
- Keyboard short cuts: Should keyboard shortcuts be required on every step of a process listed in the documentation? (New provision included in March 12 draft submission)
- Context-sensitive help: Should we require context-sensitive help in software applications?
- Alternate formats
- Verify current 508 text is clear on who supplies alternate format (who pays for it).
- What are acceptable electronic formats? pdf, ascii, a word processor file such as Word
- How can we ensure that links to documentation in accessible formats are presented in an equivalent way to non-accessible formats?
- Documentation of workarounds or other AT/application notes.
- Within documentation, what accessibility and compatibility features are included in the product and how they can be modified.
- When products have visibly discernible landmarks, how should these be included in the documentation?
- Cognitive issues in documentation (discussion)
Support Issues
- Remote assistance feature for cognitive disabilities (discussion transcript)
- Ensure text is clear on what falls under vendor or agency responsibilities. When the transition happens.
- Examine where delivery mechanisms for technical support have changed and need to be addressed (email, instant messages etc.)
Other Topics Raised
- Specific inclusion of a point of contact for technical support (to not be bounced back and forth)
- Accessibility of any training provided/contracted in relation to the product
- VPAT how can we make this more thorough to permeate the entire 508 process?
- Include guidelines for Plain Language?