Sbs Best Practices Intro 30.11.2009

Hoe ontwerp je een effectief leernetwerk? dr. Hendrik Drachsler & dr. Wendy Kicken On 14 October 2011 three workshops took place in the study centre of the Open Universiteit in Eindhoven on learning in and with help of social networks. Reason for organizing the workshops is the publication of the book Learning Networks. Participants received a complimentary copy of the book.

HTML5 provides new semantic elements, forms, and multimedia capabilities without plugins. While support is still evolving, HTML5 can be used today with feature detection and polyfills for older browsers. Key features include <video>, <audio>, <canvas>, geolocation, and application cache APIs. HTML5 aims to unify browser support for emerging web standards, but support varies - it is best to use progressive enhancement and have fallback options. Overall HTML5 enhances the web platform, but may not completely replace other technologies like Flash in the near future.

Keynote presentation at symposium on mobile technologies for museums at Rijksmuseum 31 May 2016 http://www.lkca.nl/agenda/bijeenkomsten-lkca/mobiele-apps-rijksmuseum co-organized with Landelijk Kennisinstituut Cultuureducatie en Amateurkunst.

This document provides an overview of techniques for improving website accessibility using WAI-ARIA and HTML5. It begins by noting the large numbers of people with disabilities who have visual or hearing impairments. It then discusses WAI-ARIA roles, states, and properties for semantics and interaction. Screen readers and examples of companies with dedicated accessibility teams are also mentioned. The document concludes with references to books and links for further accessibility resources and training.

This document provides an introduction to web accessibility. It begins by addressing some common misconceptions about accessibility, noting that it aims to accommodate people with a wide range of disabilities, not just visual impairments. The document emphasizes that accessibility is important for both ethical and legal reasons, and that inclusive design benefits all users. It then outlines key web accessibility guidelines from the W3C, providing examples of how to make content more accessible through proper semantic markup and alternative text. The conclusion stresses that accessibility is an essential consideration for web development.

Web Accessibility is an important issue, and must be practiced by everyone. I hope this presentation is useful!!

Being tasked with an accessibility evaluation is can be daunting. How can you measure accessibility? What disabilities are the most important? What tools do you need? How long will it take? Where do I start? What does "accessible" even mean? These are all questions I asked myself last year when I performed my first accessibility eval. This session will share everything I learned since then in performing three accessibility evaluations.

This workshop was presented on May 30, 2018 at the Web Accessibility Summit on the University of Missouri campus in Columbia, Missouri.

This document provides an overview of accessibility and user-centered design. It discusses putting the user at the center of the design process to create accessible technologies. User-centered design is highlighted as an iterative process that uncovers problems early. Guidelines for accessibility like WCAG are also summarized, which include principles like content being perceivable, operable, understandable and robust. Assistive technologies that can be used to test accessibility are briefly described.

An introduction to accessibility: definition, concepts, some requirements from WCAG, checking the accessibility conformance, recommendations and curiosities.

Transcript and extra notes available at http://www.mardahl.dk/2012/11/02/getting-down-and-dirty-with-accessibility-usability-tcuk12-workshop/ Workshop at Technical Communication UK 2012 conference, Newcastle, UK.

The document discusses the importance of mobile-first strategies and addresses common myths and barriers to their adoption. It advocates designing for mobile users first by working backwards from their needs, focusing content over extras, and ensuring solutions are fast across all devices to avoid excluding any users.

This document discusses key concepts around usability, accessibility, and professional practices for web development. It defines usability as how easy a website is to use and emphasizes the importance of considering the intended audience. Accessibility involves measures to make websites usable for people with disabilities. Professional practices include following web standards, validating code, testing websites thoroughly, and keeping up-to-date with developments in the field through publications and mailing lists.

Web accessibility is important because it allows people with disabilities to access websites. Over 285 million people are blind or visually impaired and 275 million are deaf or hearing impaired. Accessible websites follow guidelines like WCAG to address the needs of people with visual, auditory, motor, and cognitive disabilities. W3C leads initiatives to promote web accessibility through standards, guidelines, and resources to help make websites accessible to people with disabilities.

Many of the things accessibility advocates believe are out of date. Yes, the web industry has loads of myths about accessibility which we constantly need to battle. But some of the understanding of accessibility advocates is equally flawed. In this talk to a11yLDN 2012 I challenge some of the accepted assumptions many of us hold that I believe are really not serving us, or the disabled and elderly people we are trying to help, well at all. In their place I detail some more researched, more effective findings from which to continue to grow our influence in the web community. Find the original blog, and join in the discussion at: http://www.hassellinclusion.com/2011/12/accessibility-myths-2011/

Some of our key accessibility ideas are back to front. The most important aspect of the accessibility of images isn't 'alt-text'. The number of disabled people who use assistive technologies is tiny compared with those who don't. And for many people video is more accessible than text, not less accessible. In this CSUN 2014 talk, Professor Jonathan Hassell exposes 16 foundational things that all advocates “know” about accessibility as myths, using real user-research to show how they need to be replaced to properly serve today’s tablet and mobile-obsessed disabled and older users.

Web accessibility aims to make websites usable by the widest range of people, including those with disabilities. It is important for ethical and legal reasons, as disabilities affect a significant portion of the population. Ensuring websites are accessible involves accounting for various disabilities like blindness, deafness, physical impairments, and cognitive disabilities. Key aspects of accessibility include semantic HTML, accessibility standards like WCAG, and tools for different impairments.

Media queries, server-side or client-side sniffers, how do we determine if the user is a mobile or desktop device? This tech talk will discuss which is the right solution(s) and how to implement it taking into consideration the various mobile user's browser capacity, bandwidth restrictions, as well as user choice. Jenifer Hanen @msjen http://blackphoebe.com/msjen

This document summarizes a presentation given by Michael Fienen and Dylan Wilbanks on the topic of accessibility and usability. The presentation argues that accessibility and usability have many similarities and should be considered together from the beginning of a project. It provides recommendations for making templates, forms, and videos accessible. It also discusses testing for accessibility and strategies for getting buy-in for accessibility within an organization, emphasizing an early and iterative approach. The overall message is that accessibility should be a priority from the start of any project to create a better experience for all users.

Slides from a presentation I gave to an ISTC group meeting on November 12th 2013. The audience consisted mainly of technical authors - most of whom were not technically orientated. The presentation is an introduction to web accessibility, and as well as a definition for web accessibility I presented some reasons why it's important to take it seriously. I looked at various types of disability and impairment, some examples of assistive technology, and some simple things that content authors can do to help keep their articles and posts accessible.

This document provides an introduction to accessibility. It discusses different types of disabilities, understanding accessibility barriers, and the Accessibility for Ontarians with Disabilities Act (AODA). It covers the Web Content Accessibility Guidelines (WCAG) 2.0 and places to start improving accessibility, such as adding text alternatives, using semantic HTML, providing captions, and ensuring sufficient color contrast. Resources for further information on accessibility are also listed.

This document provides an overview of microformats, which are simple, open data formats built upon existing web standards like HTML and CSS. Microformats aim to solve specific problems by marking up common types of information like contacts, events, reviews, and tags in a standardized way. This makes the data more accessible for machines and easier to aggregate. The document discusses the benefits of microformats, provides examples of how to mark up contacts and events, and lists tools and sites that implement microformats.

This document discusses inclusive design and accessibility. It defines inclusive design and disabilities. It outlines tools for making content accessible, including screen readers like NVDA and JAWS. It describes the four main WCAG guidelines of perceivable, operable, understandable and robust. It demonstrates how to use VoiceOver on iOS. It provides four "golden rules" of inclusive design around images, links, markup and color contrast. It recommends a tool for checking color contrast ratios. The overall message is that inclusive design benefits all users and we should aim to understand different user experiences.

WCAG is supposed to give us a reasonably objective way of saying whether or not the sites we are building/auditing are "accessible" (to a particular baseline). However, they are only as useful as our understanding and interpretation of the guidelines' normative text. And, of course, it is not perfect - with some omissions, handwaving, and straight-up loopholes. So where does this leave developers and auditors? In this talk - a reprise of a previous talk, now updated to cover new SCs from WCAG 2.2 - Patrick may not have all the answers, but he'll have a good rant around the subject anyway...

Update about Pointer Events Level 3 work for the upcoming W3C Technical Plenary and Advisory Committee (TPAC) 2023 in Seville https://www.youtube.com/watch?v=r0spZl1qaa0 https://w3c.github.io/pointerevents/ https://www.w3.org/TR/pointerevents/ https://www.w3.org/2023/09/TPAC/ https://patrickhlauke.github.io/touch/w3c_tpac2023_pewg/ Cross-posted from https://www.w3.org/2023/09/TPAC/group-updates.html#pointer-events

WCAG is supposed to give us a reasonably objective way of saying whether or not the sites we are building/auditing are "accessible" (to a particular baseline). However, they are only as useful as our understanding and interpretation of the actual guidelines' normative text. And of course they're not perfect - with some omissions, handwaving, and straight up loopholes. So where does this leave developers and auditors? In this talk, Patrick may not have all the answers, but he'll have a good rant around the subject anyway...

WCAG is supposed to give us a reasonably objective way of saying whether or not the sites we are building/auditing are "accessible" (to a particular baseline). However, they are only as useful as our understanding and interpretation of the actual guidelines' normative text. And of course they're not perfect - with some omissions, handwaving, and straight up loopholes. So where does this leave developers and auditors? In this talk, Patrick may not have all the answers, but he'll have a good rant around the subject anyway...

HTML offers many features and attributes that can make your sites more accessible...but only if they're used wisely. Can there really be "too much accessibility"? Audio recording: https://archive.org/details/Psf8August2007.PatrickH.Lauke-TooMuchAccessibilityGoodIntentions

Patrick H. Lauke: Styling Your Web Pages with Cascading Style Sheets / EDU course / University of Salford / 13 February 2006

Patrick H. Lauke: Evaluating web sites for accessibility with Firefox / Manchester Digital Accessibility Working Group (MDAWG) / 1 March 2006

Patrick H. Lauke: Managing and educating content editors - experiences and ideas from the trenches / Public Sector Forums / 10 May 2007

Patrick H. Lauke - Implementing Web Standards across the institution: trials and tribulations of a redesign / Institutional Web Management Workshop IWMW / Birmingham / 28 July 2004

Patrick H. Lauke: Geolinking content - experiments in connecting virtual and physical places / Institutional Web Management Workshop IWMW / York / 16 July 2007

WCAG 2.0 is the new set of web accessibility guidelines that was released in 2008 as a recommendation by the W3C. It addresses some issues with the previous WCAG 1.0 guidelines by being technology-agnostic, having clearly testable success criteria focused on user outcomes rather than techniques, and removing outdated requirements. WCAG 2.0 provides more freedom for authors while still ensuring accessibility. It includes 4 principles, 12 guidelines and 61 success criteria to evaluate websites. The transition from WCAG 1.0 involves evaluating sites based on the new success criteria and testing areas that may be different.

Patrick H. Lauke: Doing it in style - creating beautiful sites, the web standards way / WebDD / Reading / 3 February 2007

The document discusses common misconceptions and pitfalls around using web standards. It argues that web standards are about more than just validation - they are about semantics, separation of concerns, and pragmatism. Some key points include: using the most appropriate HTML elements to convey meaning rather than appearance; applying styles through CSS instead of presentational markup; avoiding non-semantic class names; and recognizing that not all uses of tables or images are invalid. The document advocates for balancing standards with practical concerns like multiple authors and one-off content needs.

Ian Lloyd/Patrick H. Lauke: Accessified - practical accessibility fixes any web developer can use / South By Southwest SXSW / Austin, Texas, 11 March 2007

One from the archives...presentation about the development of the University of Salford website in 2007

Patrick H. Lauke: Keyboard accessibility - just because I don't use a mouse doesn't mean I'm second class / Skillswap Bristol / 11 Nobember 2008