Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Web Accessibility in 10mins or less...

PK
April 09, 2014

Web Accessibility in 10mins or less...

Quick introduction to the what/where/why of web accessibility. The reference to slide 8 points back to the adoption of standards and best practices (the How)

PK

April 09, 2014
Tweet

More Decks by PK

Other Decks in Design

Transcript

  1. Equality act 2010 May be unlawful for a website to:

    • have links not accessible to a screen reader • have application forms in PDF that cannot be read by a screen reader • have core service information that is not accessible to screen readers. • use text, colour contrasting and formatting that make the website inaccessible to partially users • change security procedures (e.g e-commerce site) without considering blind/partially sighted customers.
  2. The One Web • It’s the right thing to do.

    • Content accessible for all, inclusive experiences. • Equal access and equal opportunity • Wider, more engaged audience.
  3. Users and Assistive Technologies • Accessibility effects all users •

    Browser • Keyboard / Monitor • Braille displays • Screen magnifiers • Screen Readers: • e.g JAWS / NVDA / Window Eyes + browser extensions and OS features. • AT use aural, visual, tactile and verbal methods to expose web content for human consumption and interaction.
  4. Standards and Best Practices Web Content Accessibility Group (WCAG) /

    Accessible Rich Internet Applications (ARIA) Aligned with content focussed, progressively enhanced, contextual (RWD/AWD) sites. Make it part of our mindset not an afterthought. Accessibility should be considered from the outset: content creators, designers, developers and testers...
  5. Web Content Accessibility Guidelines • Principles - Technology independent •

    Perceivable • Operable • Understandable • Robust • Techniques • Success Criteria for implementing the Principles • Technology specific
  6. Accessible Rich Internet Applications • Specific techniques to augment semantics

    in HTML and enhance accessibility • Uses Roles and labels • Techniques for ARIA can be used to deliver the guidelines and principles of WCAG2.0