» Making Your Website Accessible Part 2: Implementing WCAG ACRL TechConnect Blog In Part 1, I covered what web accessibility is, its importance, and the Web Content Accessibility Guidelines (WCAG). This post focuses on how to implement WCAG into the structure and layout of the website (including templates/themes, plugins, etc.). While I will be referring to WCAG, I have based this post on what I have found in terms of general best practices, so hopefully this post is applicable to any site. Using a Template for Layout First off, I’m going to assume that at the very least your website uses a template even if it doesn’t use a content management system (CMS). A template will help you with: consistent navigation (3.2.3)consistent identification of the different parts of each page (3.2.4) – i.e. you assign ids consistentlyavoiding tables for layout purposesproviding multiple ways to discover content (2.4.5)meaningful order to content (1.3.2) – more details belowkeyboard accessibility (2.1) by insert bypass blocks (2.4.1) – more details below Ordering Content Mobile view
Pourquoi le protocole HTTPS va devenir la norme ? | AntheDesign Google via son navigateur Chrome va commencer à signaler les sites non sécurisés à partir de janvier 2017. Cette évolution confirme la volonté de Google de voir tous les sites internet migrer vers le protocole HTTPS. Pourquoi cette évolution et quelles sont les conséquences pour les éditeurs de site web ? Certains sites n’utilisant pas le protocole HTTPS seront signalés dans quelques mois sur Chrome 56. Google a annoncé l’évolution de son navigateur Google Chrome son blog réservé aux développeurs. Signalement des sites non sécurisés sur Google Chrome à partir de janvier 2017 Les premières pages web concernées par ce signalement de Google Chrome seront toutes celles où nous laissons des informations potentiellement confidentielles. Qu’est ce que le protocole HTTPS ? Qu’est-ce que le protocole HTTPS ? Le protocole HTTPS (HyperText Transfer Protocol Secure) est un protocole HTTP auquel il a été ajouté une couche de chiffrement SSL (Secure Socket Layer). Comment identifier un site sécurisé ?
Quality Assurance Hosted Services Readability Test The readability test analyses a Web page to determine how readable it is. Luminosity Colour Contrast Ratio Analyser The luminosity colour contrast ratio analyser tests whether the contrast between the background and the foreground is sufficient. Image Analyser The image analyser tests Web pages to ensure that images have been specified properly. Greasemonkey User Scripts Form Help A configurable Greasemonkey user script that allows textarea controls to be resized to suit the user's preference, and allows dropdown lists to optionally be permanently expanded to the user's preference. Heading Navigation A configurable Greasemonkey user script that allows keyboard navigation to headings. Manage Access Keys A Greasemonkey user script that displays the access keys on a web page, along with a facility to edit them to suit the preferences of the user. Firefox Extensions Juicy Studio Accessibility Toolbar
Making elements keyboard focusable and clickable When you want to make an element on a web page clickable in order to trigger a JavaScript function, the best option is to use an element that has native support for keyboard interaction. In most cases a button (either <input type="button" /> or <button type="button"></button>) is the most appropriate element. It lets everybody trigger your function, whether they use a mouse or not. Unfortunately, many (maybe even most) developers do not use the correct HTML elements for this. Instead they often use elements that have no native support for keyboard interaction, like span, div or li. So why do so many developers choose the wrong element to trigger functionality? Another reason is lack of knowledge. What do I suggest then? Use real buttons and style them so they look the way you need them to look. In both cases, to avoid confusing non-JS users, you should also use JavaScript to add interactive elements to the DOM unless they do something useful even if JavaScript is disabled.
» Making Your Website Accessible Part 1: understanding WCAG ACRL TechConnect Blog With more and more services and resources becoming digital, web accessibility has become an ever increasingly important topic. As a result, I thought a summary of my findings would be useful to others that are involved with web services. What is Web Accessibility? Some define web accessibility to mean making the web accessible to those with disabilities (including visual, auditory, motor, and cognitive) . A quick (but common) example of a problem is how a user is expected to control a video if they cannot use a mouse to click on buttons (they may depend on a keyboard or be visually impaired), especially when most videos still use some form of Flash. What is WCAG? The Web Content Accessibility Guidelines are just that, a set of guidelines, written by the Web Accessibility Initiative (WAI) group of the W3C. The Breakdown of WCAG Many (myself included) find WCAG to be difficult to navigate and comprehend. WCAG 2.0 as a Mind Map by Avoka A Note on Techniques Criticisms & Lessons Learned
Web Animations Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this document are to be interpreted as described in RFC 2119. However, for readability, these words do not appear in all uppercase letters in this specification. All of the text of this specification is normative except sections explicitly marked as non-normative, examples, and notes. [RFC2119] Examples in this specification are introduced with the words “for example” or are set apart from the normative text with class="example", like this: Informative notes begin with the word “Note” and are set apart from the normative text with class="note", like this: Note, this is an informative note. This specification defines a number of procedures. Some procedures assert an invariant condition.
Rgaa.net - Ressources sur le Référentiel général d’accessibilité pour les administrations Making an accessible dialog box In today’s web applications, dialog boxes are about as common place as they are in desktop applications. It’s pretty easy to show or hide an element that is overlayed on the page using a little JavaScript and CSS but few take into account how this affects accessibility. In most cases, it’s an accessibility disaster. The input focus isn’t handled correctly and screen readers aren’t able to tell that something is changed. ARIA roles If you want screen reader users to be aware that a dialog has popped up, then you’ll need to learn a little bit about Accessible Rich Internet Applications (ARIA) roles. In most cases, dialog is the role to use. When an element with a role of dialog is made visible, the browser tells the screen reader that a new dialog has been opened. Dialogs are also expected to have labels. In the first example, the aria-label attribute is used to specify a label that is only used by screen readers. This example uses an element to contain the description. For JavaScript:
News Subscribe to NewsletterTell a FriendPrint this Page Most social media platforms such as blogs, social networks, podcasts, and file sharing services are not accessible to persons living with some form of disability. It's time we included the more than a billion people worldwide into the most popular way of communicating online, says Debra Ruh. I am a big fan of social media. Image: Social Media has to be accessible for persons with disabilities in order to ensure their full participation in online communications Blogs, podcasts, social networks and other social media platforms have increasingly become the communication tool and medium of choice for most of us, allowing users to communicate, receive information, distribute content and follow updates within and outside our networks easily. Consider that one out of every three households in the U.S. is impacted by disabilities, and according to the World Health Organization one in seven people are impacted by a disability worldwide. back
Posts