wireframe.cc - minimal wireframing tool - for free 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é ?
Font Awesome Icons Font Awesome is the iconic font designed for use with Twitter Bootstrap. Dependencies Usage This simply adds the CSS, it's up to you to make use of the classes:<i class="icon-twitter"></i> Twitter For latest versions (4.x) of "Font-Awesome" library you need to use "fa" instead of "icon" class e.g. Support for latest Icons in Awesome 4.2.0 Support for new icons has been added in 7.x-2.x version. Related Fontello Alows uploading your own font bundle from Fontello, which has support for Font Awesome. Icon API This module provides integration for icon bundles and icon providers throughout Drupal, Font Awesome provides Integration of Icons for Icon API. Semantic UI API This module integrates Drupal with "Semantic UI":- Semantic empowers designers and developers by creating a language for sharing UI.. This module provides integration for icon bundles and icon providers throughout Drupal.
Design Accessibly, See Differently: Color Contrast Tips And Tools Advertisement Today, too many websites are still inaccessible. In our new book Inclusive Design Patterns, we explore how to craft flexible front-end design patterns and make future-proof and accessible interfaces without extra effort. Hardcover, 312 pages. When you browse your favorite website or check the latest version of your product on your device of choice, take a moment to look at it differently. Can you still see and use the website? In this article, I’ll share one aspect of design accessibility: making sure that the look and feel (the visual design of the content) are sufficiently inclusive of differently sighted users. I am a design consultant on PayPal’s accessibility team. Further Reading on SmashingMag: Link I created our “Designers’ Accessibility Checklist,” and I will cover one of the most impactful guidelines on the checklist in this article: making sure that there is sufficient color contrast for all content. Who benefits from designs that have sufficient contrast?
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
Welcome to Posterous Spaces 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.
Accessibility Many Android users have different abilities that require them to interact with their Android devices in different ways. These include users who have visual, physical or age-related limitations that prevent them from fully seeing or using a touchscreen, and users with hearing loss who may not be able to perceive audible information and alerts. Android provides accessibility features and services for helping these users navigate their devices more easily, including text-to-speech, haptic feedback, gesture navigation, trackball and directional-pad navigation. Android application developers can take advantage of these services to make their applications more accessible. Android developers can also build their own accessibility services, which can provide enhanced usability features such as audio prompting, physical feedback, and alternative navigation modes. The following topics show you how to use the Android framework to make applications more accessible. Making Applications Accessible
Why Keyboard Usability Is More Important Than You Think The idea of pressing a key to enter text has been around for a long time. One of the early prototypes of what later became the typewriter was invented in 1808 by Pellegrino Turri for his blind lover so she would be able to write him letters—or so the story goes. Image courtesy of Brenda Gottsabend. Fast forward to modern times: the keyboard remains a key element in ensuring that people with disabilities are able to communicate and engage in everyday activities. As our communication technologies advance and we become increasingly reliant on websites and apps to facilitate our interpersonal interactions, we must not forget the critical role of the keyboard. This is the first of two articles in which we’ll look at why and how to provide an accessible, enjoyable experience for people who use the keyboard to work with websites and applications. The basic keyboard commands Moving focus to the next active element on a pageActivating the element that currently has focus
Rgaa.net - Ressources sur le Référentiel général d’accessibilité pour les administrations