Perhaps I'm missing something but where is this Strategic Plan that is open for review? I was under the impression this would be a discussion about the plan in its current state but there seem to be only small exerts presented in this forum. Was that the intent and if so could someone explain why?
Some of the biggest challenges are obviously time, money, resources, personnel. Set policies that account for these challenges. Grandfathering: allow old documents to be OCR scanned and "grandfathered" in without full compliance. There are reams of info that may never be available to the public if people are afraid to put them out there for lack of resources and fear of not being 508 compliant. Disclaimers: create sets ...more »
It should be inexcusable to procure noncompliant basic products such as phone systems; photocopiers; security systems, blackberries/PDAs, and basic software (word processing, email, spreadsheet, time and attendance, travel, performance management, etc.) Find out what is 508 compliant and, for such basic products, require one of those options to be used.
For best practice, even for equipment that is grandfathered in, a certain length of time it is reasonable to review the accessibility of that equipment and to look for alternatives that are more accessible.
Comment from Accessibility Committee virtual Listening Session, Sep 8, 2011
Conformance to Section 508 isn't a "one and done." Technology, and user needs change over time. Just like in the InfoSec community, systems (aka EIT) change and with each change induces or reduces risk (aka Section 508 conformance). Why not look at "conformance" to Section 508 as Risk Management. Over 350 million users in the USA have the capability of accessing our ICT/EIT, 35 million are known to have disabilities, ...more »
Section 508 is unique among federal accessibility requirements in that it gets into a lot of technical detail. The upcoming version will do even more of that, being based on WCAG 2.0 and its interpretations for non-web. Industry correctly argues that having different standards and requirements is confusing and ultimately self-defeating. Wherever possible, federal accessibility regulations (ADA, ACAA, CVAA, 501, 503, ...more »
No one likes to be chained to certain set of rules and guidelines. Even though most will agree that Rules and Guidelines are needed in order to have structure, most will also agree that having freedom and flexibility to find what works best for your agency. The problem is that there is no place for different agencies to place their success stories or their struggles. This will allow agencies to see what works and what ...more »
Infrastructure Infrastructure exemplary practice: 1. Establish infrastructure that supports accessible ICT policies and practices: Four key areas-outsourcing, procurement, training and deployment Outsourcing: Provide outsourcing guidelines to suppliers and business partners, including copies of ICT accessibility guidelines; Ensure that contracts stipulate suppliers will, where relevant, apply ICT accessibility standards ...more »
What are the essential leadership positions in the Federal government responsible for ensuring Accessible information and communication technology? What should be their roles and responsibilities? Who and or what else should be considered on the topic of roles, responsibilities, and leadership? Who is currently failing to carry out their duties and why?
IF it is true that the Blackberry phones are not 508 compliant, why are Federal agencies allowed to buy them? Why isn't GSA prohibiting the purchase of items that are not 508 compliant?
I love the idea of the posting the VPAT forms, but it would be great to see the audit reports of sites that have been through a 508 audit. Not only does it show the agency responsible, but also the contractor who did the work.
Not to mention those audit reports give a wealth of information from the people doing the actual site auditing for 508.
Building usability and accessibility into web design during the design phase was a recurrent theme during the dialogue on web reform. Read what others said during that dialogue. http://web-reform-dialogue.ideascale.com/a/dtd/Make-usability-testing-and-508-testing-required-PRIOR-to-launch/81928-4097