Accessibility Catchup & Required re-do's of projects Sorting and column example W3I quick tips, sources HW: Screen reader exercise. Majors.

Sorting & columns 2 phase xml to xml (done using Saxon) (modified) xml to html 1 st phase uses substring and creating of [new] xml tags 2 nd phase uses feature that absence of tags can be ok 2 nd phase uses [for the columns] uses position() and mod

from Macromedia An accessible website: 1.can be perceived 2.can be navigated 3.can be utilized (with keyboard or devices other than mice) 4.can be easily understood (even in attention-poor situations) Accessibility and usability are closely related, as they both improve satisfaction, effectiveness, and efficiency of users. But while accessibility is aimed at making the website open to a wider user population, usability is aimed at making the target population of the website happier, more efficient, more effective.

Repent from Flash Sins Today's Flash is like the green shag rug from the 70s. Four Flash sins listed: The "Hidden" Button Annoying Audio and Graphics Failing to Test But It's Art Dammit!

Section 508 guidelines by Macromedia & UofWisconsin (Blair Bundy & Tim Dugdale) (a)(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). (b)(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. (c)(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. (d)(d) Documents shall be organized so they are readable without requiring an associated style sheet. (e)(e) Redundant text links shall be provided for each active region of a server-side image map. (f)(f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. Priority (a)

(g)(g) Row and column headers shall be identified for data tables. (h)(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. (i)(i) Frames shall be titled with text that facilitates frame identification and navigation. (j)(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. (k)(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes. (l)(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology.

(m)(m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with § (a) through (l). (n)(n) When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. (o)(o) A method shall be provided that permits users to skip repetitive navigation links. (p)(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

from IBM (general usability and highly relevant to accessibility) The Prime Evils of user-experience design: Confusing navigation and unexpected behaviors Slow response time Bleeding-edge technologies Poor (or omitted) user testing Off-the-cuff design services

QUICK TIPS TO MAKE ACCESSIBLE WEB SITES Images & animations. Use the alt attribute to describe the function of each visual. Image maps. Use the client-side map and text for hotspots. Multimedia. Provide captioning and transcripts of audio, and descriptions of video. Hypertext links. Use text that makes sense when read out of context. For example, avoid "click here." Page organization. Use headings, lists, and consistent structure. Use CSS for layout and style where possible. Graphs & charts. Summarize or use the longdesc attribute. Scripts, applets, & plug-ins. Provide alternative content in case active features are inaccessible or unsupported. Frames. Use the noframes element and meaningful titles. Tables. Make line-by-line reading sensible. Summarize. Check your work. Validate. Use tools, checklist, and guidelines at (c) W3C (MIT, INRIA, Keio) 2001/01

Side benefit Creating alt tags with meaningful descriptions (phrases with keywords) contributes to search engines (e.g., google) storing information on sites. Also, use meta tags, descriptions on pdf documents, and any other 'alternative' file types.

Table Statistics about fruit flies average red eyes height weight males % females %

Suggestions Inspired (but not limited to) readers with some vision and/or senior citizens, but requiring magnification –Group related material. Place action buttons close to related text & images. –Do not put links too close together (requiring great dexterity). –Do not assume (graphics only) icons are obvious (even if you include onMouseOver text).

Accessibility Internet Rally California based competition scheduled for September 21,

Usability/accessibility checkers Found following problems in my site: no link back to home page from 3 pages img tags without width AND height –this checker advises always using actual width & height. put meta tag keywords in all pages make all titles less than 64 characters missing alt tag (standard links) (problem with studentdatadisk)

Exercise Locate a site and do the usability check. (Can try Purchase sites) Another checker is: index.jsp

Homework Do screenreader simulation (try to do tasks) Continue checking usability for any site Find other on-line checkers and report.