kansas webmasters meetingkansas webmasters meeting web accessibility june 1 & 2, 2010

93
Kansas Webmasters Meeting Web Accessibility June 1 & 2, 2010

Upload: dwayne-young

Post on 23-Dec-2015

219 views

Category:

Documents


0 download

TRANSCRIPT

Kansas Webmasters Meeting

Web AccessibilityJune 1 & 2, 2010

Welcome!

Presenter:Cole Robison

Director of IT AccessibilityDivision of Information Systems and Communications (DISC), Department of Administration(785) [email protected]

Outline

• Background• Web accessibility• Current status

BACKGROUND

History

• 1996: U.S. Department of Justice Policy Ruling establishes that ADA Accessibility Requirements apply to Internet Web pages.

• 1997: World Wide Web Consortium (W3C) launches Web Accessibility Initiative (WAI).

• 1998: Rehabilitation Act Amendments of 1998 enacted; Section 508 establishes requirements for E&IT developed, maintained, procured, or used by the Federal government.

History

• 1999: W3C issues Web Content Accessibility Guidelines (WCAG) 1.0 as a Recommendation.

• 2000: U.S. Access Board publishes Section 508 Standards.

• 2001: Enforcement provision of Section 508 takes effect.

History

• 2008: UN Convention on the Rights of Persons with Disabilities (CRPD) explicitly identifies accessibility to ICT as a basic human right.

• 2009: U.S. signs CRPD.• 2010: U.S. House Judiciary Subcommittee on the

Constitution, Civil Rights and Civil Liberties holds an oversight hearing on “Achieving the Promise of the Americans with Disabilities Act in the Digital Age – Current Issues, Challenges, and Opportunities.”

Kansas Efforts: 1999–2008

• 1999: Web Accessibility Subcommittee (WAS) formed to address urgent need for state response to web accessibility issues.

• 2000–2001: ITEC Policy 1210: State of Kansas Web Accessibility Requirements approved; guidelines rolled out over an 18-month period, supported by training.

• 2002–2005: Continue to provide training, surveys, presentation to publicize effort, update guidelines and address emerging issues.

Kansas Efforts: 1999–2008

• 2005–2007: Strategic planning effort to determine how to approach growing need for resources and sponsorship.

• 2008: Director hired, Kansas Partnership for Accessible Technology (KPAT) founded by Executive Order of the Governor.

Kansas Efforts: 1999–2008Lessons Learned

• Staff turnover and changing technologies drive a continuous need for awareness-building and training.

• Assessment is needed to understand levels of compliance, training needs, as well as emerging issues.

• Need to emphasize accessibility early in the procurement process to ensure produces and services meet requirements.

Kansas Efforts: 1999–2008Lessons Learned

• Central resources are needed to research/address issues, support agencies, implement training & assessment.

• Executive-level sponsorship is required to focus resources and priority on the issue.

Kansas Partnershipfor Accessible Technology

Established by Governor’s Executive Order 08-12 on December 22, 2008. Primary objectives are to:• Provide recommendations on IT accessibility

issues, standards and policy to ITEC and other committees, boards and commissions, as appropriate.

• Develop and support programs for assessing and monitoring IT accessibility compliance.

Kansas Partnershipfor Accessible Technology

• Develop and coordinate delivery of training.• Establish a leadership role in the national

effort to improve access to information and services by individuals with disabilities.

Kansas Partnershipfor Accessible Technology

• Membership is diverse, including:– Agency decision-makers– Representatives from disability community

advocacy, support, and service organizations– IT officers– Legislative representative– and other interested parties

• 25 members—Executive Order allows up to 30

Current KPAT Membership

Three CITOs, CITAState ArchivistState GIS CoordinatorRegents IT CouncilINK Executive DirectorState ADA CoordinatorSchool for the BlindSchool for the DeafKanEdKansas Commission on

Disability Concerns

Director of PurchasesSRS, KHPA, AgingDepartment of EducationState RepresentativeKansas Association of CountiesLeague of MunicipalitiesDISCKDEMTelecommunications Access

ProgramDirector of IT Accessibility

IT Governance ModelGovernor

Dept of Administration

LegislativeLegislative Coordinating Council

JCIT Oversight

Supreme CourtOffice of Judicial Administration

Executive BranchChief InformationTechnology Officer

Legislative BranchChief InformationTechnology Officer

Judicial BranchChief InformationTechnology Officer

Information Technology Executive Council (ITEC)Cabinet Agency Heads, Branch CITOs, City- County- Private Sector CIOs, Regents, CITA

CITAChief

InformationTechnology

Architect

GISGeographicInformation

Systems PolicyBoard

E-PMOEnterprise

ProjectManagement

Office

KPATKansas

Partnership forAccessibleTechnology

ITSCInformationTechnology

SecurityCouncil

INKInformation

Networkof Kansas

Board

Information Technology Advisory Board (ITAB)State Agency- Regents- County- Local Government IT Directors, Associate Members, Technologists, Auditors

ITAB Subcommittees (as Identified)IT Technical Architecture, Long Range Planning, Web Standards, Public Key Infrastructure, Electronic Records

KPAT Initiatives

• Establishing/updating policies for accessible technology

• Awareness/outreach• Improved integration of accessibility evaluation

into the procurement process• Assessing the accessibility of state websites• Training for content creators• Research and information-sharing re: emerging

use of technologies

WEB ACCESSIBILITY

Why Is Web Accessibility Important?

E-Government

• IT is a vital part of everyday life, including government.

• More and more government services are provided online.

• IT innovation and the Web have emerged as a platform for fostering efficiencies within government and citizen participation.

E-Government and Equal Opportunity

• To function as intended, online resources must be available to all who require or would seek to use them (just like the rest of government).

• Therefore it is essential that they be accessible in order to provide equal opportunity to all citizens, including people with disabilities.

• Accessible web resources can help people with disabilities more actively participate in society, providing unprecedented access to information and interaction.

• Accessible technologies can increase the productivity of citizens, including government workers and our business partners.

Different Disabilities that Can Affect Web Accessibility

• There are barriers on the Web for many types of disabilities:– visual– auditory–physical– speech

– cognitive–neurological–multiple– age-related

20% of Adult KansansLive with a Disability of Some Kind

422,108People

Source: 2006 BRFSS Disability and Health Report

8% of Males Are Color Blind

Source: Prevent Blindness America

Majority of Working-Age Adults Likely to Benefit from the Use of Accessible Technology

Very Likely22%

Likely38%

Not Likely40%

Base: US 18- to 64-year-olds

Source: Study commissioned by Microsoft, conducted by Forrester Research, Inc., 2003

Majority of Working-Age Adults Likely to Benefit from the Use of Accessible Technology

• This study uniquely identifies individuals who are not measured in other studies as “disabled” but who do experience difficulty in performing daily tasks and could benefit from the use of accessible technology.

• Note that many or most of the individuals who have mild difficulties and impairments do not self-identify as having an impairment or disability

Majority of Computer Users Likely to Benefit from the Use of Accessible Technology

Very Likely17%

Likely40%

Not Likely43%

Base: US 18- to 64-year-old computer users

Source: Study commissioned by Microsoft, conducted by Forrester Research, Inc., 2003

Aging

• Aging is also a factor• Aging sometimes results in combinations of

accessibility issues:– Vision– Hearing– Dexterity– Memory

Aging13% of Kansans 65+

Source: 2000 Census

The Population is Aging

• The number of older people is increasing rapidly, and those reaching age 65 are living longer than ever before.

• Shifting workplace demographics and delayed retirement.

• Baby boomers start to turn 65 in 2011.• By 2030, the population age 65 and over will

almost double nationally, as will the 85 plus population.

Source: U.S. Administration on Aging Strategic Action Plan 2007-2012 (April 2007)

Other Beneficiaries of Accessible Technology

• Accessible web sites can benefit people with low literacy levels and people who are not fluent in the language of the site.– 8.7% of Kansans speak a language other than English

at home. (Source: 2000 Census)• Some aspects of web accessibility benefit people

with low bandwidth connections.– Rural locations– Financial situation (Digital Divide)– Mobile technology

Technical Advantages

• Reduce site development and maintenance time

• Reduce errors• Reduce server load• Device independence

Increased Web Site Use

• Increases potential use by more people• Increases findability (search engine

optimization)• Increases potential use in more situations• Increases usability• Improves customer satisfaction

Business Case

• For more information, see: http://www.w3.org/WAI/bcase/Overview.html

So Just What Is Web Accessibility?

Essential Components of Web Accessibility

Source: http://www.w3.org/WAI/intro/components.php

Web Accessibility Standards

• WCAG–http://www.w3.org/TR/WCAG/

• Section 508 E&IT Accessibility Standards, Web-based intranet and internet information and applications (36 CFR § 1194.22)–http://www.section508.gov/index.cfm?ID=

12#Web

What Web Accessibility Is Not:Common Myths

• Accessibility Forces You to Create Two Versions of Your Site

• A Text-Only Version Satisfies the Requirement for Equal or Equivalent Access

• Accessibility Costs Too Much• Accessibility Forces You to Create Primitive,

Low-End Designs• According to Section 508, Sites Must Look the

Same in All Browsers and User AgentsSource: Zeldman, Jeffrey. Designing with Web Standards. 3rd ed. New Riders, 2010. ISBN 978-0-321-61695-1.

General Principles: POUR

• Perceivable• Operable• Understandable• Robust

Perceivable

• Provide text alternatives for non-text content.• Provide captions and alternatives for audio and

video content.• Make content adaptable, and make it available

to assistive technologies.• Provide headings for data tables.• Use sufficient contrast to make things easy to

see and hear.• Do not rely on color alone to convey meaning.

Operable

• Make all functionality keyboard accessible.• Give users enough time to read and use content.• Do not use content that causes seizures.• Help users navigate and find content.• Allow users to skip repetitive elements on the

page.• Ensure users can complete and submit all forms.• Ensure links make sense out of context.

Understandable

• Make text readable and understandable.• Make content appear and operate in

predictable ways.• Use logical page structures.• Help users avoid and correct mistakes.

Robust

• Maximize compatibility with current and future technologies.

Web Accessibility Resources

• W3C Accessibility page– http://www.w3.org/standards/webdesign/accessibility

• WAI Introduction to Web Accessibility– http://www.w3.org/WAI/intro/accessibility.php

• WebAIM articles– http://www.webaim.org/articles/#usersperspective

• U.S. Department of Justice technical assistance document: Accessibility of State and Local Government Websites to People with Disabilities– http://www.ada.gov/websites2.htm

Web Accessibility Resources

• Guidance for Web Developers– http://da.ks.gov/kpat/resources/1210guidance.ht

m• WCAG Overview– http://www.w3.org/WAI/intro/wcag

• Section 508 Standards guide– http://www.access-board.gov/sec508/guide/

1194.22.htm• KPAT Resources page– http://da.ks.gov/kpat/resources/

Example: Using alt Attributes on img Elements

Inaccessible<img src="newsletter.gif" />

Accessible<img src="newsletter.gif" alt="Free newsletter. Get free recipes, news, and more. Learn more." />

Example: Using Heading Markup to Convey Structure

Inaccessible<p><strong>Welcome to CityLights</strong></p><p>Citylights is the new portal for visitors and residents...</p><p><strong>Heat wave linked to temperature</strong></p> <p>After three years of effort city scientists now agree that the primary cause of the 2003 heat wave was hot air from...</p>

Accessible<h1>Welcome to CityLights</h1><p>Citylights is the new portal for visitors and residents...</p><h2>Heat wave linked to temperature</h2> <p>After three years of effort city scientists now agree that the primary cause of the 2003 heat wave was hot air from...</p>

Example: Associating Header Cells and Data Cells in Data Tables

Inaccessible<table> <tr> <td></td> <td>Name</td> <td>Phone#</td> <td>City</td> </tr><tr> <td>1.</td> <td>Joel Garner</td> <td>412-212-5421</td> <td>Pittsburgh</td> </tr> …</table>

Accessible<table> <tr> <td></td> <th scope="col">Name</th> <th scope="col">Phone#</th> <th scope="col">City</th> </tr><tr> <td>1.</td> <th scope="row">Joel Garner</th> <td>412-212-5421</td> <td>Pittsburgh</td> </tr> …</table>

Example: Associating Text Labels with Form Controls

InaccessibleFirst name:<input type="text" name="firstname" id="firstname" />

Accessible<label for="firstname">First name:</label><input type="text" name="firstname" id="firstname" />

Example: Providing Link Text that Describes the Purpose of a Link

Inaccessible<h2>Heat wave linked to temperatures</h2> <p>After three years of effort city scientists now agree that the primary cause of the 2003 heat wave was hot air from...<br><a href="../news/#story1">Full story</a></p>

Accessible<h2><a href="../news/#story1">Heat wave linked to temperatures</a></h2> <p>After three years of effort city scientists now agree that the primary cause of the 2003 heat wave was hot air from...<br><a href="../news/#story1">Heat wave - full story</a></p>

HTML Accessibility Resources

• Articles– http://www.webaim.org/articles/#html

• WCAG Techniques– http://www.w3.org/TR/WCAG20-TECHS/html.html

• Importance of HTML Headings for Accessibility– http://www.youtube.com/watch?v=AmUPhEVWu_E

• Semantic (X)HTML Markup: Using Tables Appropriately– http://www.communitymx.com/content/article.cfm?

cid=0BEA6

CSS Misapplication Example

Inaccessible<p class="heading1">Welcome to CityLights</p><p>Citylights is the new portal for visitors and residents...</p><p class="heading2">Heat wave linked to temperature</p> <p>After three years of effort city scientists now agree that the primary cause of the 2003 heat wave was hot air from...</p>

Accessible<h1>Welcome to CityLights</h1><p>Citylights is the new portal for visitors and residents...</p><h2>Heat wave linked to temperature</h2> <p>After three years of effort city scientists now agree that the primary cause of the 2003 heat wave was hot air from...</p>

CSS Example: Ensuring Sufficient Contrast Between Text & Background

Inaccessiblebody { color: white; background-color: white;}

Accessiblebody { color: black; background-color: white;}

CSS Accessibility Resources

• Creating Accessible CSS– http://www.webaim.org/techniques/css/

• WCAG Technigues– http://www.w3.org/TR/WCAG20-TECHS/css.html

Scripting Example: Using Redundant Keyboard and Mouse Event Handlers

Inaccesible<a href="…" onmouseover= "updateImage(true);" onmouseout= "updateImage(false);">…</a>

Accessible<a href="…" onmouseover= "updateImage(true);" onfocus= "updateImage(true);" onmouseout= "updateImage(false);" onblur= "updateImage(false);">…</a>

Scripting Resources

• Creating Accessible JavaScript– http://www.webaim.org/techniques/javascript/

• WCAG Techniques– http://www.w3.org/TR/WCAG20-TECHS/client-sid

e-script.html

Rich Internet Applications Accessibility Resources

• Accessibility of Rich Internet Applications– http://www.webaim.org/techniques/aria/

• WAI-ARIA Overview– http://www.w3.org/WAI/intro/aria.php

• WAI-ARIA 1.0– http://www.w3.org/TR/wai-aria/

• WAI-ARIA Primer– http://www.w3.org/TR/wai-aria-primer/

Rich Internet Applications Accessibility Resources

• WAI-ARIA Authoring Practices– http://www.w3.org/TR/wai-aria-practices/

• WCAG Techniques– http://www.w3.org/TR/WCAG20-TECHS/aria.html

Rich Internet Applications Accessibility Resources

• Accessible Web 2.0 Applications with WAI-ARIA– http://www.alistapart.com/articles/waiaria/

• ARIA Resources– http://wiki.codetalks.org/wiki/index.php/

ARIA_Resources• Accessible Drag and Drop Using ARIA– http://dev.opera.com/articles/view/accessible-dra

g-and-drop/

Ajax Accessibility Resources

• Accessibility of AJAX Applications– http://www.webaim.org/techniques/ajax/

• Hijax– http://domscripting.com/blog/display/41

Flash Accessibility Resources

• Creating Accessible Flash Content– http://www.webaim.org/techniques/flash/

• Adobe Flash Accessibility– http://www.adobe.com/accessibility/products/

flash/• Creating Accessible Sites in Flash– http://www.adobe.com/accessibility/products/

flash/tutorial/

Flash Accessibility Resources

• Creating an accessible animated presentation in Flash– http://www.adobe.com/devnet/flash/articles/

accessible_animated_preso.html• Adobe Flash Accessibility Design Guidelines– http://www.adobe.com/accessibility/products/flash/

best_practices.html• Flash Accessibility Requirements and Methods– http://www.doodledoo.com/accessibility/

FARM_v2_0.pdf

Flash Accessibility Resources

• Flash Accessibility Tips– http://doodledoo.com/blog/?cat=5

• DoodleDoo– http://www.doodledoo.com/accessibility.htm

Silverlight Accessibility Resource

• Silverlight Accessibility Overview– http://msdn.microsoft.com/

en-us/library/cc707824(VS.95).aspx

PDF Accessibility Resources

• PDF Accessibility– http://www.webaim.org/techniques/acrobat/

• Adobe Acrobat Pro Accessibility Guide: Best Practices for Accessibility– http://www.adobe.com/accessibility/products/

acrobat/pdf/A9-access-best-practices.pdf• Facts and Opinions About PDF Accessibility– http://www.alistapart.com/articles/

pdf_accessibility

PDF Accessibility Resources

• Creating accessible PDFs from Word 2007– http://www.abilitynet.org.uk/webarticle87

• Adobe Acrobat Pro– http://www.adobe.com/products/acrobatpro/

• NetCentric CommonLook for Adobe Acrobat– http://www.net-centric.com/products/

cl_s508_adobe.aspx• NetCentric PDF Accessibility Wizard (PAW) for

Microsoft Office– http://www.net-centric.com/products/PAW.aspx

Captioning Resources• Best Practices in Online Captioning

– http://joeclark.org/access/captioning/bpoc/• Web Captioning Overview

– http://www.webaim.org/techniques/captions/• W3C Multimedia Accessibility FAQ

– http://www.w3.org/2008/06/video-notes• Caption It Yourself

– http://www.dcmp.org/ciy/• Accessible Digital Media Guidelines

– http://ncam.wgbh.org/invent_build/web_multimedia/accessible-digital-media-guide

• Captioning Key– http://www.captioningkey.org/index.html

Captioning Resources• Accessible HTML5 Video with JavaScripted captions

– http://dev.opera.com/articles/view/accessible-html5-video-with-javascripted-captions/

• Media Access Generator (MAGpie)– http://ncam.wgbh.org/invent_build/web_multimedia/tools-guidelines/magpie

• CCforFlash– http://ncam.wgbh.org/invent_build/web_multimedia/tools-guidelines/

ccforflash• YouTube Adding / Editing captions

– http://www.google.com/support/youtube/bin/answer.py?answer=100077• YouTube Help with captions

– http://help.youtube.com/support/youtube/bin/answer.py?answer=100076• OverStream

– http://www.overstream.net/

Captioning Resources

• Caption Solutions– http://captionsolutions.com/

• 20/20 Captioning– http://www.2020captioning.com/

• DCMP Approved Captioning Service Vendors– http://www.dcmp.org/caai/nadh11.pdf

• Multimedia– http://joeclark.org/book/sashay/serialization/Chapter13.html

• This is How the Web Gets Regulated– http://www.alistapart.com/articles/

thisishowthewebgetsregulated/

CURRENT STATUS

ITEC Policy 1210, Revision 2

• http://da.ks.gov/itec/documents/itecitpolicy1210.htm

• ITEC Policy 1210 requires:– Level AA conformance with WCAG– Conformance with the Section 508 Web Standards

• ITEC Policy 1210 was last updated April 23, 2009.• The main change of this revision was to update the

WCAG conformance requirement from WCAG 1.0 to WCAG 2.0.– WCAG 2.0 was released December 11, 2008.

What’s New in WCAG 2.0

• Reorganized• Modernized material• Items generalized to apply more broadly to different

types of web technologies– current, future, non-W3C

• Clearer criteria, more precisely testable• Adaptable, flexible for different situations• Extensive supporting materials,

practical implementation guidance

Changes in Requirements

• Most websites that conform to WCAG 1.0 will not require significant changes in order to conform to WCAG 2.0, and some may not need any changes.

• Most new guidelines map to previously existing guidelines

• Comparison table from W3C:http://www.w3.org/WAI/WCAG20/from10/comparison/

Captions

One requirement for multimedia that is not new, but has been strengthened:

Now requires captions (not just transcripts)

WCAG 1.0 WCAG 2.0

1.4: For any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation. [Priority 1]

1.2.2 Captions (Prerecorded): Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such. (Level A)1.2.3 Audio Description or Media Alternative (Prerecorded): … (Level A)1.2.4 Captions (Live): … (Level AA)1.2.5 Audio Description (Prerecorded): … (Level AA)

ITEC Policy 1210, Revision 2

18-month rollout period from April 23, 2009current deadline: October 23, 2010.

Recommended Approach

Make New Content Accessible

• Be sure that all new content from this point forward complies with the requirements.

Inventory Existing Content

• Determine what you have.• Basic link checking programs can be used to assist

with this, e.g.,– Xenu’s Link Sleuth

• http://home.snafu.de/tilman/xenulink.html

– SiteOrbiter• http://siteorbiter.com/

• Additional information in article:http://www.usability.gov/methods/design_site/inventory.html

Categorize

• Divide inventory into categories.• Size up the various content types, roles, etc.• Understand content prioritization.– Highest traffic, business critical content most

important– Server logs, with the aid of analysis software, can

be used to determine page traffic statistics; see:http://en.wikipedia.org/wiki/List_of_web_analytics_software

Assess

• Determine level of compliance.• There are many tools that can be of assistance,

including:– Checkers built into development software, e.g.,

Dreamweaver, Acrobat, etc.– Total Validator

• http://www.totalvalidator.com/

– WAVE• http://wave.webaim.org/

– Firefox Web Developer Toolbar• http://chrispederick.com/work/web-developer/

Assess

– Web Accessibility Toolbar for Internet Explorer• http://www.visionaustralia.org.au/info.aspx?page=614

– Cynthia Says• http://www.contentquality.com/

– Others listed at:• http://www.w3.org/WAI/ER/tools/• http://www.webaim.org/articles/freetools/• http://www.webaim.org/articles/tools/

• Additional information:– http://www.w3.org/WAI/eval/Overview.html– http://www.webaim.org/articles/process/

Prioritize and Plan Remediation Work

• Based on your content prioritization and the conformance levels of the guidelines that need addressed, as well as level of effort, etc., develop a plan for working through content that requires correction.

Fix Inaccessible Content

• Carry out your plan to remediate any content found to be inaccessible.

84

Undue Burden

• ITEC Policy 1210 outlines an undue burden procedure:– 7.4 In cases where a webpage, web service, or web

application cannot be made compliant as required in Section 7.1 without an undue burden, an exception may be requested for review by the State ADA Coordinator and the Director of Statewide Web/IT Accessibility. The procedure for obtaining an undue burden exception is as follows: • 7.4.1 The request for an exception shall be in writing, shall state

the reason(s) that compliance will create a financial or administrative undue burden, and shall be submitted to the State ADA Coordinator. Such requests must receive approval by the State ADA Coordinator prior to deployment.

Undue Burden

• 7.4.2 Entities shall describe in detail the challenges faced in making the webpage, web service, or web application accessible, including an estimate of hard and soft costs that would be incurred in doing so.• 7.4.3 Entities shall describe their short-term and long-

term solutions for making the webpage, web service, or web application accessible.• 7.4.4 Entities shall submit a timeline in which the

webpage, web service, or web application will be made accessible, and provide progress updates as requested by the KPAT.

85

86

Undue Burden

• Your remediation plan is key.– To the extent that it brings your site into compliance

by 10/23, you will have successfully met the requirements.

– Where work will need to extend beyond 10/23, the plan becomes the basis for an undue burden request.

• Either way, your agency is following a plan and making progress toward full accessibility, which is what’s important.

What We’re Doing To Help

Assessment Tool

• The KPAT received a grant from the Information Network of Kansas in February 2010 to:– Procure access to web-based assessment tool to

support agencies in assessing compliance levels and performing remediation.

– Will also set baseline for identifying common issues, measuring progress, developing training

Assessment Tool

• It is anticipated that this tool will help with content inventory and reporting, in addition to handling the assessment.

Rollout Guidance and Assessment/Reporting Instrument

• We’re working on a document detailing the recommended steps outlined here.

• We also intend to provide an assessment template, which the assessment tool would feed into, to be used for reporting.

Captioning Pilots

• The INK grant also enables the KPAT to conduct small-scale captioning pilots with the Kansas Legislature and selected state agencies.

• Intent is to assess resources requirements and demonstrate feasibility, while developing roadmap.

How Can We Best Help You?

Thank You!

Contact information:Cole Robison

Director of IT AccessibilityDivision of Information Systems and Communications (DISC), Department of Administration(785) [email protected]

This presentation is available at:http://da.ks.gov/kpat/groups/webmasters/