September 2021 Newsletter
A new WebAIM resource is available to guide testers through a wide variety of accessibility checks.
Registration is open for WebAIM's next virtual web accessibility training to be held October 12-13.
The WAVE web accessibility testing tool is now available as a Microsoft Edge extension.
Jeremy Keith describes the root cause of three categories of accessibility issues, and how to start addressing them.
GOV.UK explains the causes of and solutions for accessibility problems with conditionally revealed form fields.
While screen readers mostly ignore styles, CSS can impact the screen reader experience in significant ways.
Sara Soueidan on why she thinks adding a new HTML sectioning element for search is a good idea.
An exploration of common mistakes made with ARIA attributes.
Before designing a website, or even making a small change to an existing one, ask if your design choices consider the needs of people with color blindness.
Quick Tip: Regions at a glance
Most pages need four regions for an accessible structure. Most of the content should go in the main region. The content at the top of the page - logins, settings, navigation, everything that is shown to the user before the main content - should be wrapped in a header region. If the header has a set of links or a menu for navigating to other places on the site, that should be further contained in a nav region. The content that comes after the main region at the bottom of the page - links to resources, logos, contact information - belongs in the footer.