はてなブックマーク

The WebAIM Million The 2024 report on the accessibility of the top 1,000,000 home pages You are here: Home > WebAIM Projects > The WebAIM Million Introduction For the sixth consecutive year, WebAIM conducted an accessibility evaluation of the home pages for the top 1,000,000 web sites. The evaluation was conducted using the WAVE stand-alone API (with additional tools to collect site technology and

You are here: Home > WebAIM Projects > Screen Reader User Survey #7 Results Introduction In October 2017, WebAIM surveyed preferences of screen reader users. We received 1792 valid responses. This was a follow-up to 6 previous surveys that were conducted between January 2009 and July 2015 (see Related Resources). A few disclaimers and notices: Totals may not equal 100% due to rounding. Total respo

You are here: Home > WebAIM Projects > Screen Reader User Survey #6 Results Introduction In July 2015, WebAIM conducted a survey of preferences of screen reader users. We received 2515 valid responses to this survey, our highest thus far. This was a follow-up survey to the original WebAIM Screen Reader User Survey of January 2009 and the follow-up surveys from October 2009, December 2010, May 2012

CSS in Action Invisible Content Just for Screen Reader Users You are here: Home > Articles > CSS in Action: Invisible Content Just for Screen Reader Users Introduction There are occasional instances where content should be made available to screen reader users but hidden from sighted users. In the vast majority cases, content that is available visually should be available to screen reader users, a

You are here: Home > WebAIM Projects > Screen Reader User Survey #5 Results Introduction In January 2014, WebAIM conducted a survey of preferences of screen reader users. We received 1465 valid responses to this survey. This was a follow-up survey to the original WebAIM Screen Reader User Survey of January 2009 and the follow-up surveys from October 2009, December 2010, and May 2012. Additional su

Today is Global Accessibility Awareness Day (GAAD). To celebrate and to help promote accessibility, here are 10 simple accessibility tips that most anyone can implement today into their web site’s HTML and CSS to make it more accessible. 1. Add Alternative Text to Your Logo Alternative text is presented to blind screen reader users in place of images they cannot see. Every image that conveys conte

The Web Content Accessibility Guidelines 2.0 became a W3C Recommendation (code for “finalized specification”) in December 2008. I am proud to have my name listed as a contributor to WCAG 2.0. All of WebAIM’s current clients are working toward WCAG conformance. None of them are seriously considering only the antiquated Section 508, the update of which is perpetually stuck in bureaucratic delay tact

You are here: Home > Resources > Web Accessibility for Designers The focus of web accessibility is often on web development – the things that happen in HTML, CSS, or JavaScript. Optimal accessibility should start much earlier, as part of the visual design process. This infographic highlights many important principles of accessible design. Plan Heading Structure Early Ensure all content and design

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. We received 1245 valid responses to this survey (1049 English, 101 Spanish, 91 French, and 4 Portuguese responses). This was a follow-up survey to the original WebAIM Screen Reader User Survey of January 2009 and follow-up surve

This is the fifth in a multipost series about the immediate and likely future of web accessibility. Each week or so I’ll discuss a different upcoming technology, tag, platform, or system from an accessibility perspective. Additions, corrections, or further thoughts are welcome in the comments. Previous posts: HTML5 <video>, HTML5 Semantic Elements, New <input> Types in HTML5, HTML5 <input> Extensi

For years, we have recommended to developers that they download the trial version of JAWS to perform basic evaluation of the accessibility of their web sites. Our recent, and quite popular, article on using JAWS to evaluate web content again makes this recommendation. The demo version (which runs for 40 minutes per session) can be a valuable tool for web developers to not only ensure their content

Overview On most pages, keyboard and screen reader users must navigate a long list of navigation links and other elements before ever arriving at the main content. This can be particularly difficult for users with some forms of motor disabilities. Consider users with no or limited arm movement who navigate a web page by tapping their heads on a switch or that use a stick in their mouth to press ke

We have web accessibility in mind Expanding the potential of the web for people with disabilities by empowering individuals and organizations to create accessible content. Accessibility Training WebAIM can provide web, document, Zoom, and strategic accessibility training to fit your needs. Technical Assistance Need assistance implementing accessibility? WebAIM's expert staff can provide the assist

The experts at WebAIM can audit your web site and provide a detailed report to help you remediate accessibility and WCAG compliance issues. Learn more about WebAIM Evaluation Services The following is NOT the Web Content Accessibility Guidelines (WCAG) 2. It is a checklist that presents our recommendations for implementing the most common accessibility principles and techniques for those seeking W

Explanation Enter a foreground and background color in RGB hexadecimal format or choose a color using the Color Picker. Enter an Alpha value to adjust the transparency of the foreground color. Use the Lightness slider to adjust the perceived lightness of the color. WCAG 2.0 level AA requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. WCAG 2.1 requires a contrast rat

In the beginning there was NCSA Mosaic, and Mosaic called itself NCSA_Mosaic/2.0 (Windows 3.1), and Mosaic displayed pictures along with text, and there was much rejoicing. And behold, then came a new web browser known as “Mozilla”, being short for “Mosaic Killer,” but Mosaic was not amused, so the public name was changed to Netscape, and Netscape called itself Mozilla/1.0 (Win3.1), and there was

Follow-up surveys were administered in October 2009, December 2010, May 2012, January 2014, July 2015, and October 2017. Be sure to check out the results of these surveys for updated data and trends. Introduction In December 2008 through January 2009, WebAIM conducted a survey of preferences of screen reader users. We received 1121 valid responses to the screen reader survey. A few disclaimers and

Web Accessibility Gone Wild Now even wilder! You are here: Home > Articles > Web Accessibility Gone Wild This article presents a wide variety of mistakes, misconceptions, over-indulgences, intricacies, and generally silly aspects of modern accessibility. While most accessibility issues are due to lack of knowledge, sometimes the most egregious errors are made by well-meaning developers who simply

Accessible JavaScript Overview of Accessible JavaScript You are here: Home > Articles > JavaScript JavaScript Accessibility Issues JavaScript allows developers to add increased interaction, information processing, and control in web-based content. However, JavaScript can also introduce accessibility issues. These issues may include: Navigation. Inability or difficulty navigating using a keyboard o

PDF Accessibility Defining PDF Accessibility You are here: Home > Articles > PDF Accessibility > Defining PDF Accessibility PDF Tags When people talk about "accessible" PDF files, they are usually referring to "tagged" PDF files. Tags are “...a set of standard structure types and attributes that allow page content (text, graphics, and images) to be extracted and reused for other purposes.” (PDF Te