WebAIM June 2023 Newsletter

Read this newsletter online at https://webaim.org/newsletter/2023/june

Feature

Top Tips from a Web Accessibility Evaluator at WebAIM

WebAIM's Alaina Foust shares some ideas about more effectively conducting web accessibility testing.

Upcoming WebAIM Events

• Document Accessibility Course - July cohort is now open for registrations
• Virtual Web Accessibility Training - July 5–6

2nd Annual Web Accessibility in Mind Conference

Join WebAIM and Pope Tech online on August 29th and 30th, 2023, for two days of carefully curated digital accessibility talks. All free and recorded for future viewing. Registration is open, and we will begin to announce speakers soon.

Resources

Three key principles for an accessible website

Accessibility experts on the ScienceDirect team share their approach to making Elsevier’s research platform accessible to people with disabilities.

WCAG 2.2 misses mark on defining visible focus

Recent changes to the WCAG 2.2 draft have resulted in an important success criterion being shifted to Level AAA.

The problem with sticky menus that appear on scroll and what to do instead

Four problems and four possible alternatives to an increasingly common menu system.

aria-hasPopUp less is more

An updated report on support (and the lack thereof) for this promising ARIA attribute.

June accessibility focus: Videos and audio

Pope Tech provides tips on how to make accessible videos and audio including suggestions for the easiest way to make accessible videos.

Making a positive change: PDF to HTML

PDFs can be unwieldy, slow to download and costly to update. Consider the needs of the people you are publishing the information for. Engage with them early to explore alternative options that may better meet their needs.

6 Quick tests you can do to test your forms for accessibility

Whenever I do a full audit for a website, I have almost 40 individual, highly granular, form-related checks. Those checks can be boiled down to the following 6 high level goals.

Quick Tip: aria-required vs. required

The semantics for aria-required="true" and the HTML required attribute are the same—screen readers present them identically. However, aria-required only indicates that a field is required, whereas the required attribute provides a functionality change—it will visually inform the user that a field is required if it is bypassed without entered content and will mark the field as invalid.

WebAIM E-mail Discussion List

Subscribe to the WebAIM E-mail Discussion List

View the Discussion List Archives

Select recent threads:

• Visual transcript for training videos
• Clarification on the banner role not being at the top of a page
• Accordion design patterns
• HTML disabled or aria-disabled on checkbox

Read more about WebAIM Training, Web Site Evaluation, and Consultation Services.

WebAIM is a non-profit organization based at the Institute for Disability Research, Policy & Practice at Utah State University.