background preloader

Color Contrast Checker

Color Contrast Checker
You are here: Home > Resources > Color Contrast Checker <p><strong>This tool requires Javascript.</strong></p> Normal Text WCAG AA: Pass WCAG AAA: Pass The five boxing wizards jump quickly. Large Text Explanation Enter a foreground and background color in RGB hexadecimal format (e.g., #FD3 or #F7DA39) or choose a color using the color picker. WCAG 2.0 level AA requires a contrast ratio of 4.5:1 for normal text and 3:1 for large text.

Accessibility - W3C The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect. Tim Berners-Lee, W3C Director and inventor of the World Wide Web The Web is fundamentally designed to work for all people, whatever their hardware, software, language, location, or ability. Thus the impact of disability is radically changed on the Web because the Web removes barriers to communication and interaction that many people face in the physical world. Accessibility is essential for developers and organizations that want to create high quality websites and web tools, and not exclude people from using their products and services. The mission of the Web Accessibility Initiative (WAI) is to lead the Web to its full potential to be accessible, enabling people with disabilities to participate equally on the Web. See below for: Why: The Case for Web Accessibility The Web must be accessible to provide equal access and equal opportunity to people with diverse abilities.

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

Web Content Accessibility Guidelines (WCAG) 2.1 abbreviation shortened form of a word, phrase, or name where the abbreviation has not become part of the language Note This includes initialisms and acronyms where: initialisms are shortened forms of a name or phrase made from the initial letters of words or syllables contained in that name or phrase NoteNot defined in all languages. Some companies have adopted what used to be an initialism as their company name. accessibility supported supported by users' assistive technologies as well as the accessibility features in browsers and other user agents To qualify as an accessibility-supported use of a Web content technology (or feature of a technology), both 1 and 2 must be satisfied for a Web content technology (or feature): The way that the Web content technology is used must be supported by users' assistive technology (AT). When a Web Technology is used in a way that is "accessibility supported," it does not imply that the entire technology or all uses of the technology are supported. audio

Top 25 Awesome Accessibility Testing Tools for Websites Cookies are short reports that are sent and stored on the hard drive of the user's computer through your browser when it connects to a web. Cookies can be used to collect and store user data while connected to provide you the requested services and sometimes tend not to keep. Cookies can be themselves or others. There are several types of cookies: Technical cookies that facilitate user navigation and use of the various options or services offered by the web as identify the session, allow access to certain areas, facilitate orders, purchases, filling out forms, registration, security, facilitating functionalities (videos, social networks, etc..). So when you access our website, in compliance with Article 22 of Law 34/2002 of the Information Society Services, in the analytical cookies treatment, we have requested your consent to their use. However, please note that you can enable or disable cookies by following the instructions of your browser.

Accessible Form Validation with HTML5, WAI-ARIA, & jQuery Plugin By Paul J. Adam on May 25, 2012 Old browsers? Old AT? JavaScript to the rescue! Demo Form with HTML5, WAI-ARIA, & jQuery Validation (Default Settings) Demo Form with HTML5, WAI-ARIA, & jQuery Validation (Tweaked Settings) HTML5 and ARIA Have Limitations – JavaScript Does Not! Sure JavaScript has some limitations but really there are none when you code it with accessibility in mind. Adding the jQuery Validation Plugin jQuery is the dominant JavaScript framework on the web and can be declared the winner of the JS framework wars of the past years. jQuery’s motto is “Write Less, Do More”. It’s very simple to add jQuery Validation to any HTML form. The plugin picks up on our inputs with the HTML5 required attribute and by default will instead do its own JavaScript validation and not use HTML5. jQuery Validation Default Settings There are some issues with the default settings. So we have two problems so far with default settings. Tweaking jQuery Validation Options for the validate() method

Bruk av farger | Universell utforming Publisert: 30. jun 2015, Sist endret: 04. mar 2019 Introduksjon Alle brukere vil ha stor glede av visuell markering i menyen av aktiv side, og dette blir gjerne løst med fargeendring. Videre surfer brukerne stadig mer med mobil og nettbrett, i alle mulige situasjoner og omgivelser. Det resulterer ofte i krevende lysforhold som stiller store krav til fargebruk for at det skal ha effekt for alle brukere. Løsninger som møter kravene i forskriften Fargebruk i tekst Hvis du bruker farge til å formidle funksjonalitet eller viktighet, må du supplere med andre metoder for å sikre at alle brukere skjønner hva du formidler. Eksempel på supplerende markering er fet stil for visuell utheving eller understreking av lenker. Kodeeksempel for korrekt markering av uthevet tekst: Hvordan ikke markere <a href=”eks.html” style=”color: #6e1873;”>lenke i brødtekst</a>. Husk at layout skal defineres i CSS, eksempelet skal bare vise merverdien av supplerende markering. Diagram

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

The Myths of Color Contrast Accessibility - UX Movement - Medium There’s a growing demand for designers to make their interfaces accessible to all users. It’s important to accommodate users with disabilities, but there are many myths to color contrast accessibility being perpetuated by misinformed people. They often parrot these myths to discredit a design, without understanding in which situations a color contrast standard applies. Not only that, but they assume an interface is inaccessible whenever color contrast is used to convey information. Because of this, designers often feel the need to obsess over accessibility, and are misled into believing their interface isn’t accessible when it actually is. Myth 1: The WCAG requirements are always optimal The Web Content Accessibility Guidelines (WCAG) is a set of principles used as the standard for determining accessible color contrast. One case where the WCAG standards aren’t applicable is with the brightness contrast of white text. Myth 2: Text must meet the AAA requirement, or it’s inaccessible

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.

Building keyboard accessible dropdown menus – Interface - Blog of Web Communications at the University of Missouri When developing a dropdown menu for your site, it’s important not to assume that all your visitors will be navigating with a mouse. Some might be using the keyboard exclusively to navigate your website. Fortunately, enabling keyboard access is a relatively simple task. Here’s a typical dropdown menu example, one that follows the popular Suckerfish model: View Dropdown Menu Example It uses an unordered list, with second level lists for the dropdowns. Note that the additional ul li.hover ul rule is specifically for Internet Explorer 6, which unfortunately doesn’t support the :hover pseudo class on anything besides the <a> tag. So take a second look at the demo again, and instead of using a mouse, try using the tab key to go through the links. At most you’ll get an outline around any top level links that are selected, and no visual indication at all if one of the second level links are selected. Javascript to the Rescue Compliment :hover with :focus and :active and

Screen Reader User Survey #3 Results You are here: Home > WebAIM Projects > Screen Reader User Survey #3 Results Introduction In December 2010, WebAIM conducted a survey of preferences of screen reader users. A few disclaimers and notices: Totals may not equal 100% due to rounding. Demographics Disability Reported Screen Reader Proficiency Those who use screen readers due to a disability report themselves as being much more proficient with screen readers. 3% of those with disabilities considered their proficiency to be "Beginner" compared to 36% of those without disabilities. Internet Proficiency 61% of those who use screen readers due to a disability reported "Advanced" Internet proficiency compared to 86% of those without disabilities. Primary Screen Reader Most notable is a significant decline in primary usage of JAWS - down to 59.2% from 66.4% as reported in October 2009. Screen Readers Commonly Used The following chart shows changes in screen reader usage over time. Screen Reader Updates Browsers JavaScript Enabled Mobile Platforms

Accessible Dropdown Menus | Terrill Thompson A couple weeks ago at the 27th Annual CSUN International Technology and Persons with Disabilities Conference I gave a presentation on accessible dropdown menus. In that presentation, I walked through several examples of accessible menu techniques (and a few not-so-accessible ones). All the examples are available on my Dropdown Menus Test Page. Dropdown and flyout menus on websites are great for reducing clutter, simplifying page content, and providing a consistent navigation structure that (if done well) makes it easy to find content from anywhere on the site. Most dynamic menus depend on users being able to use a mouse. The quest for an accessible dynamic menu started as early as 2003, when Patrick Griffiths and Dan Webb published an article on A List Apart titled Suckerfish Dropdowns, proposing a menu system that was structured in HTML using a very simple nested unordered list, with a small amount of CSS and JavaScript that made it look and behave like a menu. Which model is best?

Related: