Accessible content writing starter kit | Access iQ Content author requirements On websites, content provides a big chunk of what makes your site successful. Whether you are in charge of writing, producing videos or commissioning others to produce content on your site, the accessibility of your content should always be a priority. Content management process Web content is dynamic and increasingly convergent. Creating web content that is accessible and complies with WCAG 2.0 is a process that involves the collaborative efforts of a web developer, designer and content author. A complete guide to web accessibility for content authors A practical premium resource for content authors that shows you how to comply with WCAG 2.0 Level AA. Five ways to improve the accessibility of your content How content is presented has a direct impact on the accessibility of a website. Accessible Word documents Creating Word documents that can be read by people of all abilities is just as important as creating accessible web content. Useful accessibility tools
Aide & accessibilité - Pas-de-Calais le Département Pasdecalais.fr est le site du Département du Pas-de-Calais. Afin de vous aider à naviguer sur le site, cette page vous propose Aides disponibles sur pasdecalais.fr Aide à l'orientation pasdecalais.fr est structuré de la manière suivante : le bandeau d'en-tête est constituédu logo du Département, qui redirige vers la page d'accueil du sitedu menu principal, comprenant les sept grandes thématiques de pasdecalais.fr (Solidarité & Santé, Éducation, Sports & Loisirs, Développement, Culture, Europe, L'institution)de l'accès à la navigation par profille menu secondaire inclutdes liens de suivi (réseaux sociaux, flux RSS, lettre d'information)des raccourcis vers les pages les plus visitées du sitede l'accès à la navigation par profilla zone centrale est constituée des actualités et agendas en page d'accueil, ou du contenu des pages internesla colonne suivant la zone centrale est constituée :en page d'accueil du sitede Pas-de-Calais TVdu bloc "Le saviez-vous ?" Aide à la navigation Logo Fil d’Ariane
ACE: the Accessible Colour Evaluator When you click each squares on the top row, you will be able to choose different colours for the text which you plan to use on your website. The labels above each square indicate where the font will be seen on the example page, this can be turned off. The three vertical squares on the left side of the grid are for choosing background colours and when clicked will let you choose background colours. Again, the labels indicate where the colours are going to be used on the example page, but can be turned off if desired. When you select a colour and you have confirmed it the results table will update accordingly. The HEX value (e.g., #FF0000) for each of the palette block displays underneath so that you can copy the colour code easily to put into your files. The image on the left shows how the results square will look if no minimum contrast level is met. Once colours have been chosen, click the link to see the example page.
Quelques tests d’accessibilité sur Fnac.com Samedi dernier, j'ai eu la chance de participer à l'atelier « Tester l'accessibilité de son site Web avec NVDA » présenté par Denis Boudreau à Paris Web. Après une présentation très intéressante (où j'ai appris notamment qu'il y avait 39 000 000 de non-voyants dans le monde, mais seulement 22 000 utilisateurs de NVDA), les participants ont été invités à faire des tests à l'aide d'un lecteur d'écran sur le site de la Fnac par petits groupes. Je me suis donc retrouvé à faire la connaissance de @ouik_web et @joellechong avec qui nous avons testés les formulaires de la création de compte du site. N'ayant pas de PC sous la main, nous avons fait des tests avec VoiceOver sous OS X. Afin de créer un compte, nous avons sélectionné le lien « Me connecter » du header du site. Le premier point surprenant, c'est que cette page contient également un formulaire d'identification (alors que je viens pourtant explicitement de cliquer sur un lien « Créer mon compte »).
H71: Providing a description for groups of form controls using fieldset and legend elements | Techniques for WCAG 2.0 The objective of this technique is to provide a semantic grouping for related form controls. This allows users to understand the relationship of the controls and interact with the form more quickly and effectively. Form controls can be grouped by enclosing them within the fieldset element. All controls within a given fieldset are then related. The first element inside the fieldset must be a legend element, which provides a label or description for the group. Authors should avoid nesting fieldsets unnecessarily, as this can lead to confusion. Grouping controls is most important for related radio buttons and checkboxes. It can also be useful to group other sets of controls less tightly related than radio buttons and checkboxes. Authors sometimes avoid using the fieldset element because of the default display in the browser, which draws a border around the grouped controls. Resources are for information purposes only, no endorsement implied. Procedure Expected Results
Investigating the Accessibility and Usability of Job Application Web Sites for Blind Users - International Journal of Usability Studies Jonathan Lazar, Abiodun Olalere, and Brian Wentz Journal of Usability Studies, Volume 7, Issue 2, February 2012, pp. 68 - 87 Interventions It is important to note that there were a total of 34 interventions required, where participants asked for assistance in moving forward. Figure 1. Figure 2. The other 18 interventions occurred in situations where the participants asked for a suggestion to help them move forward. Previous | Next Visible Keyboard Focus Within the accessibility community, it is well-understood that visually indicating focus is a crucial step in ensuring access for sighted users who rely on their keyboard when interacting with the web. After all, it is explicitly listed in WCAG 2.0 as Success Criterion 2.4.7, [a]ny keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. But it has also been addressed repeatedly over the years by different people. Yet, providing visible keyboard focus is still not as widespread a practice as it should be. I am not at all a designer, but I do appreciate that in some cases the default focus rectangle might be seen to detract from a web page's visual design. Whether or not the default focus rectangle on links is removed using outline:none; or outline:0;, I think it's almost always a good idea to give keyboard users the same visual effect when they set focus to a link that mouse users get when they hover over a link with their cursor.
Shared Web Experiences: Barriers Common to Mobile Device Users and People with Disabilities This page describes many of the barriers that people with disabilities and people using mobile devices experience when interacting with web content, including web applications. It shows how these barriers are similarly addressed in W3C's Web Content Accessibility Guidelines (WCAG), Mobile Web Best Practices, and Mobile Web Application Best Practices. Background People with disabilities using computers have similar interaction limitations as people without disabilities who are using mobile devices. A comprehensive comparison between MWBP and WCAG is provided in Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG). Introduction The barriers on this page are grouped under four principles: perceivable, operable, understandable and robust. This page includes links to some relevant solutions in: The information below is also available in tabular format. Contents Perceivable Experiences discussed below are also available in tabular format. Text entry
Web Accessibility Testing: What Can be Tested and How | Karl Groves The Short Version Read this if you’re disinclined to read the entire list of specific WCAG Success Criterion and look at how each can be tested. If someone was to ask me what I consider to be my biggest strengths when it comes to accessibility, I’d say it is in testing. The thing about automatic testing is that there are some things which can be tested by machine testing quite reliably. With the above in mind, I’ve undertaken an exercise to determine exactly what can be tested. What does this mean? In short, it means that relying solely on automatic testing is probably a bad idea. The data These three tables detail how many items can be tested for using automated testing. How I arrived at this data The data presented above does not use or describe any information from any previous or current employer. Create a list of all WCAG Success Criterion, organized by Level. Some Caveats This list does not take into account the capabilities (or lack thereof) of any particular tool.