ImageVerifierCode 换一换
格式:PPT , 页数:25 ,大小:1.98MB ,
资源ID:379142      下载积分:2000 积分
快捷下载
登录下载
邮箱/手机:
温馨提示:
如需开发票,请勿充值!快捷下载时,用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)。
如填写123,账号就是123,密码也是123。
特别说明:
请自助下载,系统不会自动发送文件的哦; 如果您已付费,想二次下载,请登录后访问:我的下载记录
支付方式: 支付宝扫码支付 微信扫码支付   
注意:如需开发票,请勿充值!
验证码:   换一换

加入VIP,免费下载
 

温馨提示:由于个人手机设置不同,如果发现不能下载,请复制以下地址【http://www.mydoc123.com/d-379142.html】到电脑端继续下载(重复下载不扣费)。

已注册用户请登录:
账号:
密码:
验证码:   换一换
  忘记密码?
三方登录: 微信登录  

下载须知

1: 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。
2: 试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。
3: 文件的所有权益归上传用户所有。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 本站仅提供交流平台,并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

版权提示 | 免责声明

本文(Building Accessibility Into The Workflow.ppt)为本站会员(jobexamine331)主动上传,麦多课文库仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文库(发送邮件至master@mydoc123.com或直接QQ联系客服),我们立即给予删除!

Building Accessibility Into The Workflow.ppt

1、Building Accessibility Into The Workflow,Rick Ells Computing & Communications University of Washington Seattle, Washington rellscac.washington.edu http:/staff.washington.edu/rells/,Challenge,Accessible design standards are well defined Many sites do not follow accessible design standards Accessible

2、design advocates are on the outside of the process How can accessibility become part of the process?,Looking at Section 508,1194.22 Standards define 16 discrete criteria in no particular order,Decision Tree?,Basic Publication Workflow,Where does accessibility fit?,Going Beyond Retrofitting,“A common

3、 response from programmers after receiving an accessibility evaluation is that it would have been much easier to incorporate the requested changes at the beginning of the site development lifecycle. building accessibility into a site early in the development lifecycle saves time and money compared t

4、o retrofitting.” Law, Jacko, and Edwards, “Programmer-Focused Website Accessibility Evaluations,” ASSETS05 Conference, October 2005,Sorting Out The Requirements,Graphics and ColorC. All information conveyed with color is also available without colorJ. Avoid screen flicker between 2 Hz and 55 Hz Usab

5、le Design D. Documents readable without requiring associated style sheet. N. Forms should allow people using assistive technology access to information, elements, and functionality necessary to use form. O. Provide method to skip repetitive navigation links P. When a timed response is required, aler

6、t user and give sufficient time to indicate more time is needed. Other K. Provide text page with equivalent information and functionality when compliance not possible otherwise.,Alternative and Associative TextA. Text equivalent for every non-text elementG. Identify row and column headers in data ta

7、bles H. Associate data cells with header cells with markup in tables with multi-level row and column headersI. Title frames with text that facilitates identification and navigationL. When using scripting for display and interface, provide functional text that can be read with assistive technology Te

8、chnologies E. Each active region of a server-side image map shall be provided with redundant text links F. Use client-side image maps instead of server-side image maps if possible M. When page requires applet, plug-in, or application, provide link to compliant version,1194.22 For Roles,Decision Tree

9、 by Roles,Swimlanes,Writer/Editor Role,Write and gather text Text content Alternative texts for non-text objects Prepare for the Web Rewrite into “plain language” Organize into semantic structure (headings, paragraphs, lists, etc.),Web Publisher Role,Receive prepared text, graphics, alternative text

10、, and long descriptions Place content in templates Place associative attributes in tables and forms Publish,Graphics Designer Role,Develop color scheme, considering accessibility issues relating to color Provide direction to Web Designer on color issues Prepare graphics and photos for use Provide gr

11、aphics and photos to Writer/Editor for development of alternative text,Web Designer Role,Develop templates and CSS, taking accessibility into consideration Skip to content Linearity of content (works without CSS) Provide compliant support for applets Oversee selection and use of technologies used in

12、 Web site to insure accessibility Javascript, AJAX, PDF, Flash,Systematic Reuse Workflow,1194.22 for CMS,Elements and Attributes A. Text equivalent for every non-text element I. Title frames with text that facilitates identification and navigationL. When using scripting for display and interface, pr

13、ovide functional text that can be read with assistive technology N. Forms should allow people using assistive technology access to information, elements, and functionality necessary to use formTechnologies E. Each active region of a server-side image map shall be provided with redundant text links F

14、. Use client-side image maps instead of server-side image maps if possible P. When a timed response is required, alert user and give sufficient time to indicate more time is needed.,Table Structure G. Identify row and column headers in data tables H. Associate data cells with header cells with marku

15、p in tables with multi-level row and column headersTemplates and stylesheets C. All information conveyed with color is also available without color D. Documents readable without requiring associated style sheet. J. Avoid screen flicker between 2 Hz and 55 Hz O. Provide method to skip repetitive navi

16、gation links M. When page requires applet, plug-in, or application, provide link to compliant versionOther K. Provide text page with equivalent information and functionality when compliance not possible otherwise.,Content Management System,Building In Accessibility,Input,Text preparation Plain langu

17、age Semantic structure (use h-tags for main topic, subtopics, subsubtopic, etc.) Non-text elements Provide alternative text Tables Row and column headings Forms Associate form fields with descriptions of fields,Templates,Templates DOCTYPE statement Well-formed structure Standards conforming code Sta

18、ndard access keys (if any) Language declaration Skip to content link, if necessary Linearly intelligible content organization,Output,Output Valid X/HTML Meaningful title Alternatives to Javascript Navigation (previous/next links, nav links) Abbreviations and acronyms,Key Points,Prepare content into

19、semantic units before entry Require alternative and associative texts at time elements and objects are added to system Design templates for full use of alternative and associative texts, intelligible linearity, and usability Manage technology used in pages Look ahead at approaching technologies to a

20、void inadvertent accessibility blocks,Discussion,Content entry interfaces and processes need rethinking The approach of AJAX makes the need for better integration of accessibility into the design and management process imperative Javascript not as inherently structured as HTML, more care will be nec

21、essary in using it Accessibility as an add-on will no longer work,More Discussion - About Tables,Typical table entry interface Presents matrix of whole table You enter text into matrix cells Then you go back and make the cells at the top of each column and the first cells each row into headers Why n

22、ot Define columns and rows first, including heading text and scope definition, which will also define the data matrix Then enter the matrix contents This approach would define the logical structure of the table first, then put content into it. Result would be properly annotated, fully accessible tab

23、les.,References,Boiko, Bob, Content Management Bible, Hungry Minds, 2002 Law, Chris, Julie Jacko, and Paula Edwards, “Programmer-Focused Website Accessibility Evaluations,” ASSETS05 Conference, October 2005 National Center on Accessible Information Technology in Education (AccessIT) http:/www.washin

24、gton.edu/accessit/ Plain Language, http:/www.plainlanguage.gov/ Rockley, Ann, Managing Enterprise Content: A Unified Content Strategy, New Riders, 2003 Thatcher, Jim, et al, Constructing Accessible Web Sites, Glasshaus, 2002 W3C Implementation Plan for Web Accessibility, http:/www.w3.org/WAI/impl/Overview.html Selecting and Using Authoring Tools for Web Accessibility, http:/www.w3.org/WAI/impl/software.html,

copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
备案/许可证编号:苏ICP备17064731号-1