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)
• 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.
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.
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...