1 / 28

Elegance in Structure

Learn why websites must be accessible under the law and how to create beautiful, interactive sites that are inclusive. Educate clients, designers, and users, choose the right technology, prototype effectively, and implement an interactive solution that exceeds accessibility standards.

nuala
Télécharger la présentation

Elegance in Structure

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. Elegance in Structure spotlight.abs.gov.au

  2. Why must your site be accessible?

  3. It’s the Law “Under the Disability Discrimination Act 1992, Australian Government agencies are required to ensure information and services are provided in a non-discriminatory accessible manner.”

  4. You’re going to be disabled one day.

  5. How do we make a beautiful interactive website and keep it accessible?

  6. Educate

  7. Who to educate • Clients • Why extra cost and time? • Easier with government agencies • Designers and creatives • Considerations when designing layout and colours • Users • When they come to the website (more on this later)

  8. Choose the right technology for the task Not buzzwords

  9. Prototype

  10. Prototyping • Get a dedicated JAWS testing machine or VM • Run accessibility tests early on • Test how it copes with the user interface concepts • Test it works with different technologies • Share the creative vision • Collaborate and look for creative solutions

  11. Spotlight prototyping considerations • Lots of animation • Data-driven • Validation • Interruptible process • Voice over • Tied in with the animation • Generic on statistics

  12. Flash can be appropriate • Mature platform • Best for multimedia • Productive tools • Faster development • Designers understand it • Lots of users have it • At the moment • HTML 5 media is inaccessible • At the moment

  13. … but you still need HTML pages • For information-driven pages • E.g. About, Contact, Accessibility • For mobile users • Adobe has stopped developing Flash for mobile • For screen readers • HTML accessibility is best • Familiar behaviour • Existing mastery of tools

  14. Spotlight solution Interactive (Flash) Accessible version (HTML) Tailored script based on the interactive version Designed to adhere to and exceed WCAG 2 SEO Friendly Works with mobile • Beautiful smooth animation • Visually appealing • Voice over • Captioned • Works on 98% of machines

  15. Working together Data HTML Flash Graphics

  16. Walkthrough

  17. To take away • Educate involved parties in accessibility • Prototype early on to choose the best technology and approach • Focus on user experience not just technical requirements of WCAG 2 • Test early and test often • Complain

  18. What I would like • Better ability to interact with social media plugins • More education on how to use the accessibility features of websites • An agnostic and measured approach to technology decisions

  19. Questions?

  20. Thanks! Twitter: @williamparry Email: williamparry@gmail.com

More Related