Introducing
Your new presentation assistant.
Refine, enhance, and tailor your content, source relevant images, and edit visuals quicker than ever before.
Trending searches
End
Suggestions for changes:
Positive feedback:
1. Have accessibility experience on the team
2. Introduce accessibility form the beginning of a project
3. Communicate accessibility within the team
4. Follow existing design principles
5. Test accessibility at key stages
6. Use WAI-ARIA mark-up
7. Follow and validate the HTML standard
8. Combine WAI-ARIA and HTML5 mark-up
9. Use Progressive enhancement
10. Use Unobtrusive JavaScript
11. Use device independent methods
12. Use accessible modal windows
13. Use technology that facilitates accessibility
Does the findings reflect views of Universal Design in the IT business?
http://accessibilityagent.no/guidelines
Uncovering accessibility issues
Finding suggested solutions for discovered issues
Surveying existing research - RIA accessibility issues
Surveying existing suggestions for solutions
Creation of guidelines
Evaluation of guidelines
Modifying the guidelines
Sort and present material
Semi-structured interviews inspired by previous research evaluating WCAG
Participants reflected while evaluating guidelines:
Result: Thorough reflections and natural conversations
What to do?
How to do it?
Everybody needs to use the Web
RIA dependence on client-side code execution
JavaScript = popular!
JavaScript = non-accessible?
RQ 1: What specific problems exist with RIA accessibility?
RQ 2: What can be done to avoid RIA accessibility problems?
Project goal:
Making it easier to create accessible RIAs using existing standardized technologies
Linn Steen-Hansen and Siri Fagernes