1 / 15

ICAWEB402A

ICAWEB402A. Confirm Accessibility of Website for People with Special Needs. L Osborne. Scenario:.

konane
Download Presentation

ICAWEB402A

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ICAWEB402A Confirm Accessibility of Website for People with Special Needs L Osborne

  2. Scenario: • With the development of a new website for people with special needs. The project manager needs you to present to the other members of the team as small presentation informing them on issues that will need to be considered to ensure that the website will meet the accessibility needs of a number of specific groups. You are required to discuss the following topics: Part A: - Identify Accessibility Standards • 1. Identify an legislative or industry standards that may influence accessibility in a web context • 2. List 3 or more specific user groups and describe some of their accessibility requirements. • 3. Creating 2 example checklists, which could be used with web-related work • 4. Select one of the accessibility standards and further discuss

  3. Part B: - Test Accessibility & Pages • Export your presentation in, Part A above, to a format suitable for display on the Internet. Ensure that each of the following guidelines are implemented: • 1. Ensure that a text equivalent for every non-text element is present in the web site, and that pages are logical and accessible in a text-only environment • 2. Verify that all information conveyed with colour is also available without colour and pages are not dependent on colour and can operate in a monochrome environment o Visit Colour Doctor: http://www.fujitsu.com/global/accessibility/assistance/cd/ • o Provide a screen capture of the comparison made • 3. Ensure that pages can be read without style sheets • 4. Test site with different user agents (browsers) to ensure that the site transforms successfully and maintains accessibility • 5. Test that content conforms to the client (project team) expectations and technology. • Run your presentation through appropriate W3C accessibility evaluation tools and present the results.

  4. Identify an legislative or industry standards that may influence accessibility in a web context • Australia.gov.au tells thecurrently compliant to Level A of the Web content accessibility guidelines version 2.0(WCAG 2.0) standard is in place to show the current guidelines • This is also strengthened under the Disability Discrimination Act ,under Commonwealth law , this also the effort that is required to comply to.

  5. Web content accessibility guidelines version 2.0 (WCAG 2.0) standard • Guideline 1.1 Text Alternatives: Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language. • Guideline 1.2 Time-based Media: Provide alternatives for time-based media • Guideline 1.3 Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure. • Guideline 1.4 Distinguishable: Make it easier for users to see and hear content including separating foreground from background.

  6. Guideline 2.1 Keyboard Accessible: Make all functionality available from a keyboard • Guideline 2.2 Enough Time: Provide users enough time to read and use content. • Guideline 2.3 Seizures: Do not design content in a way that is known to cause seizures. • Guideline 2.4 Navigable: Provide ways to help users navigate, find content, and determine where they are.

  7. Guideline 3.1 Readable: Make text content readable and understandable. • Guideline 3.2 Predictable: Make Web pages appear and operate in predictable ways. • Guideline 3.3 Input Assistance: Help users avoid and correct mistakes. • Principle 4: Robust - Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies. • Guideline 4.1 Compatible: Maximize compatibility with current and future user agents, including assistive technologies.

  8. List 3 or more specific user groups and describe some of their accessibility requirements.

  9. Colour Blindness People with colour blindness have trouble interpreting certain colours that could assisting them by : • Using black text and a white or sometimes grey background • Not use coloured text and backgrounds • Separate cascading style sheets for people with disability’s • Grey scale picture with colour descriptions of the object

  10. Hearing Loss People with Hearing loss have problems interpreting sound and noise around them small things such as help them: • Text labels such as the alt=“ e.g. “ in images and text, use a code for tabbing (<A TABINDEX="1" ACCESSKEY="P" HREF=" ....">) and the summary tag <summary> </summary> • Large text to make large amounts of writing easy to read • Caption in videos and pictures to describe the subject • Using sign language instead of written language such as engish,french

  11. Physical Disabilities • This can include motor disabilities like weakness, limitation of movement, joint problems, missing limbs and pain that impedes movement. • Barriers that may occur could include: • Time-limited response options on Web pages • Browsers that do not support keyboard alternatives • No tabbing in forms

  12. To over come some hearing disability barriers you can: • Captions • Volume controls • Transcripts on sites • Images with descriptions • Language options

  13. Ten Common Problems related to webpage Design • 1. Failure to include appropriate text descriptions (such as “alt-text” labels) for images; • 2. Failure to provide accessible alternatives when using a visual CAPTCHA; • 3. Failure to use technologies (such as Flash and JavaScript) in ways that are accessible; • 4. Failure to use HTML features appropriately to indicate content structure such as the hierarchy of headings; • 5. Failure to explicitly associate form input controls with their labels; • 6. Failure to ensure sufficient difference between foreground (text) colour and background colour;

  14. 7. Failure to identify data tables with Summary or Caption, and failure to mark-up data tables correctly; • 8. Failure to provide a way for users to disable content such as advertisements from flashing rapidly (rapidly-flashing content may cause seizures in susceptible individuals), and failure to provide a way for users to stop a page from auto-refreshing; • 9. Failure to ensure that web pages can be used from the keyboard (that is, without the mouse); • 10. Failure to alert the user to changes on a web page that are triggered automatically when selecting items from a dropdown menu.

  15. Biography • http://australia.gov.au/about/accessibility • http://www.humanrights.gov.au/disability_rights/standards/www_3/www_3.html • http://www.w3.org/TR/WCAG20/ • http://www.abice.cessnock-ict.net/ICAWEB402A/presentation_files/frame.htm

More Related