
Find me on: Mastodon at @WebAxe@a11y.info a11y.info/@WebAxe My blog: WebAxe.org Facebook: facebook.com/WebAxe/

Blog about web accessibility. Find me on Mastodon at @WebAxe@a11y.info a11y.info/@WebAxe

Find me on: Mastodon at @WebAxe@a11y.info a11y.info/@WebAxe My blog: WebAxe.org Facebook: facebook.com/WebAxe/

Essential information for Keyboard Accessibility: webaim.org/techniques/keyboa… by @WebAIM #a11y #keyboard #testing

Designing With Reduced Motion For Motion Sensitivities (2020) smashingmagazine.com/2020/09… #webdesign #a11y #motion #css

Dive into: The <label> element maxdesign.com.au/articles/la… #label #a11y #html #forms

Heading off confusion: When do headings fail WCAG? tpgi.com/heading-off-confusi… #wcag #headings #a11y

The HTML dialog element is closer to being accessible. scottohara.me/blog/2023/01/2… #dialog #html #webdev #a11y

Include—Accessibility Annotations, a Figma plugin figma.com/community/plugin/1…—Accessibility-Annotations #figma #a11y #webdesign #UIDesign


React Testing Library & Accessibility dev.to/steady5063/react-test… #reactJS #a11y #webdev

ARIA 1.2 is now a W3C Recommendation w3.org/blog/news/archives/99… #aria #webdev #a11y

Support navigation and wayfinding: accessibility.huit.harvard.e… Good tips from Harvard Univ. #webdesign #usability #a11y

Should I Use An Accessibility Overlay? [No!] shouldiuseanaccessibilityove… #overlaysSuck #a11y

Screen Reader support for text-level HTML semantics (there isn’t much) tpgi.com/screen-readers-supp… #a11y #html

Great video about Source Order vs Display Order vs Keyboard Focus Order (what they are and why they must match) accessibilityoz.com/resource… via AccessibilityOz #a11y #webdev

if you're using javascript:void(0) as the value of the href attribute, the element you're actually looking for is <button> matuzo.at/blog/its-very-like… Great series from @matuzo@front-end.social #webdev #html #a11y

Web Accessibility and SEO webaim.org/blog/web-accessib… Always excellent and concise info from WebAIM #webdev #seo #a11y