WebAIM - Web Accessibility In Mind

September 2017 Newsletter


Screen Reader User Survey #7

The 7th in our series of Screen Reader User Surveys is now open for responses. Please encourage screen reader users to participate.


WebAIM Training

Registration is open for the WebAIM training to be held December 5-6 in Logan, Utah.


Writing CSS with Accessibility in Mind

Tips on how to improve the accessibility of your web sites and apps with CSS.

Accessibility is not an edge case

There's a common misconception that people using assistive technologies are an edge case. That they fall into that 1% where people disable Javascript. But, this couldn't be further from the truth.

Creating an Accessibility Engineering Practice

Practical experiences and resources for implementing organizational accessibility.

Do you really care about accessibility? Stop box ticking!

We need to think about accessibility as not only ensuring web content is accessible but making sure that a culture of accessibility permeates through an entire organisation.

Fonts don't matter

Hampus Sethfors explains why fonts are overrated and what actually matters for readability.

Quick Tip: Generic Regions

HTML5 defines structural elements, called regions, for header, nav, main, footer, and aside elements in a web page. ARIA provides landmark roles for these same things. Either provides navigation to significant page areas. Some applications may contain important areas that do not fit into one of these defined regions or landmarks. In this case, you can define a custom or generic region using ARIA's role="region". Each region must be given a descriptive label via aria-label or aria-labelledby. When defined, these generic regions can be navigated along with other regions/landmarks.

WebAIM E-mail Discussion List

Subscribe to the WebAIM E-mail Discussion List

View the Discussion List Archives

Selected recent threads: