1. BY: C.MADHUMATHI, II MCA “B” SEC, 08MCA54

2. Contents Product Accessiblity 1. Introduction 2. Text Equivalents –Audio,Video,Images 3. Low Vision 4. Style sheets 5. Numerous Colors 6. Reduce flicker rate,speed of moving text avoid flashes and blinking 7. Mobility impaired users 8. Conclusion 9. Summarize 10. References

3. INTRODUCTION “ Product Accessibility”- Providing accessibility in the product through standards and guidelines. Product- should do everything -ensuring the basic accessibility features - utilized by it. Designing of product’s user interface: 1. Good understanding of basic accessibility features. 2. Requirements of different types of users with special needs. 3. Categories of users, their abilities and challenges. Help from various websites Accessibility standards - 508 and W3C refer to a complete set of requirements.

4. TEXT EQUIVALENTS HAVE TO BE PROVIDED FOR AUDIO, VIDEO AND PICTURE IMAGES  Accessibility Impaired users  Visually Impaired  Hearing Impaired  Mobility Impaired product - all kind of users - must have certain accessibility tools eg. narrator

5. EXAMPLES

6. PEOPLE WITH LOW VISION see the pages in extra-large fonts - use the product comfortably. product expecting a particular resolution, font size display all fields on the screen - usability issues. Hello Everybody Hello everybody

7. adequate spacing between the fields and text -messages appearing on the screen do not look cluttered - font size is increased. Contd……… Hello Everybody

8. STYLESHEETS STYLESHEETS - Documents and fields should be organized so that they can be read without requiring a particular resolution of the screen, and templates Normally, Information on web pages - displayed on the screen using templates (STYLE SHEETS)

9. TYPES OF STYLESHEETS Stylesheets Internal Stylesheets Eg. MS-word External Stylesheets Eg. pdf

10. Explanation of the types of Stylesheets Internal Stylesheets: Hard coded sheets that dictate the fields, size and their positions on the screen. This creates problems for users when they want to adjust the windows and size of fonts. External Stylesheets: It is the safest method. The programs written for the product should not tamper with user-defined external style sheets.

11. Problems in identifying numerous colors Color Blindness:  Product using color text, color pictures and color screens should not use color as the sole method of identification of user interface elements.  User interfaces should be designed so that all information conveyed with color is also available without color.

12. EXAMPLE Press the green button to start the program. you can use the red button to stop the running program CONTINUE STOP

13. Reduce flicker rate, speed of moving text, avoid flashes and blinking text Different people read at different speeds. People with below-average speed in reading -find it irritating to see text that is blinking, flashing as it further impacts reading speed. People with good vision -find the flashes, flickers beyond a particular frequency -uncomfortable. The flickers should be between the frequencies of 2 Hz and 55 Hz, as defined by some of the usability standards.

14. Examples Reduce flicker rate Hello everybody Reduce speed of moving text Avoid flashes and blinking text Hello everybody Va maa minnal… Va maa minnal... God is now here

15. Persons with mobility-impaired users and nerve-related problems Cannot move the eyeballs as fast as others. Health problems - prevent them from reading as fast as others. Rolling and moving Text:  Speed at which the text rolls or moves - compatible with the reading capability of the slowest product user.  The product - feature to alter the speed of moving text.

16. ….contd Physical movement - to use the product – minimized - assisting mobility impaired users. Spreading user interface elements to the corner of the screens - avoided - require the users to move the pointing devices to the corners, involving effort.

17. Examples Name Register no Dept Location C.Madhumathi MCA 08MCA54 Trichy

18. individual screens and entire set of screens in totality - designed keeping minimum movement requirements in mind. multiple screens are used in performing a set of operations - the corresponding sequence of positive responses - CONTINUE, ACCEPT BACK,EXIT buttons - aligned across screens - the pointing devices - not realigned when the screen changes.

19. User interfaces - expect users use fewer devices - regular operations. Using the keyboard is essential - information to be typed - using a pointing device may be avoided - key used to navigate among the fields. Mixing the use of several devices - keyboard and mouse increases the complexity of user interface. Reduce physical movement requirements for the users - designing the interface - allow adequate time for user responses.

20. Examples NameC.Madhumathi Reg. No.08Mca54 DepartmentMCA LocationTrichy

21. TIMED RESPONSE When a timed response is required, the user should be alerted and given sufficient time to indicate that more time is required. Some users require more time to think and act, as they may be challenged in more fashion. Click on this ok button within 5 seconds if information is correct

22. conclusion The sample requirements given are some examples to improve accessibility. There are many more requirements like these and they are normally classified on the basis of the technology used for providing the user interface. (for eg, web- based interface, client-based interface and so on) in the popular standards (such as 508 guidelines) defined for accessibility. Selecting the right standard for the technology used in the interface will go a long way in improving accessibility.

23. Summarize Providing accessibility in the product through standards and guidelines is called product accessibility. Text equivalents - audio, video and picture images. style sheets. User interfaces - designed -informations conveyed with color & without color. Reduce flicker rate, speed of moving text, avoid flashes and blinking text. Reduce physical movement requirements - designing the interface & allow adequate time for user responses. 508 and w3c –accessibility standards

24. References “software Testing”-principles and practises by srinivasan Desikan and Gopalaswamy Ramesh. www.w3c.org www.w3c.com

26. THANK YOU