Why “font-size” Must Never Be in Pixels (gra) | | 948 |
css, units, responsive-design |
Short Note: Why Isn’t “role=presentation”/“none” Allowed on Focusable Elements? (ste) | | 947 |
focus, aria, html |
Accessible Target Sizes Cheatsheet (vit/sma) | | 946 |
user-experience |
Progress Over Perfection: The Better Way for Communication and Accessibility Advocacy (mer) | | 945 |
communication, advocacy, processes |
The Potentially Dangerous Non-Accessibility of Cookie Notices (mar/sma) | | 944 |
cookies, legal, privacy, user-experience |
Meeting WCAG Level AAA (pat/tet) | | 943 |
wcag, conformance, standards |
Designing and Coding for Voice (bri) | | 942 |
voice |
Visually Accessible Data Visualization (dmt/pla) | | 941 |
information-design |
Audio Accessibility in Miro: A Hackathon Story in 3 Acts (sin/mir) | | 940 |
multimedia, experiments |
Answering “What ARIA Can I Use?” (kin/w3c) | | 939 |
aria, browsers, screen-readers, assistive-tech, support |
Web Accessibility: A Reference to Creating Inclusive Websites (sta) | | 938 |
|
Breaking Down Accessibility Barriers: Top 4 Challenges With Screen Magnifiers (abi/ael) | | 937 |
assistive-tech, screen-magnification |
Shifting Left, or: Making Accessibility Easier by Doing It Earlier (hdv) | | 936 |
videos, slides, processes |
Don’t Override Screen Reader Pronunciation (aar) | | 935 |
screen-readers, pronunciation |
HTML Accessibility API Mappings 1.0 (ste+/w3c) | | 934 |
html, apis |
Accessibility in Design Systems: Building More Inclusive Products for a Better User Experience (kna) | | 933 |
videos, design-systems, dei, user-experience |
Chasing Rainbows (wax/ver) | | 932 |
colors, color-blindness, user-experience |
Establishing Metrics for Accessibility ROI (kar) | | 931 |
metrics, economics |
The Alt Text War—SEO vs. Accessibility (art/dig) | | 930 |
seo, images, writing, alt-text, comparisons |
Foundations: Accessible Names and Descriptions (ihe/tet) | | 929 |
fundamentals, naming, writing, aria |
What’s New in WCAG 2.2? (mon/acc) | | 928 |
wcag, standards |
Designing for Reduced Motion (lup/cra) | | 927 |
animations |
What Makes a Good Screenshot? (llo/tpg) | | 926 |
images |
Five Pieces of Advice for More Accessible Websites (cit) | | 925 |
html |
Accessibility for Designers: Where Do I Start? (ste) | | 924 |
design, link-lists |
Exposing Field Errors (aar) | | 923 |
forms, aria, assistive-tech, support |
10 Ways to Hide Elements in CSS (cra/sit) | | 922 |
css, performance |
When I Get That Low Contrast Feeling, I Need Non-Textual Healing (llo/tpg) | | 921 |
contrast, colors |
The Ultimate Guide to Automatic Accessibility Testing in CI/CD for React Apps | | 920 |
guides, testing, automation, ci-cd, react |
We Need Accessibility Action (yat) | | 919 |
web |
Alternative Text in the Wild: 5 Alternative Text Examples (pop) | | 918 |
writing, examples |
The WebAIM Million (web) | | 917 |
studies, research, metrics |
Guardrails for Better Accessibility Support in Frontend (net) | | 916 |
quality, tooling |
Connecting Dots of an Accessibility Audit (art/dig) | | 915 |
auditing |
Accessibility vs. Emojis (uxd) | | 914 |
emoji, unicode, comparisons |
A Quick Guide to Reviewing a VPAT ACR (kar) | | 913 |
vpat-acr, conformance, auditing |
CSS-Only Widgets Are Inaccessible (aar) | | 912 |
css |
Senior Engineering Strategies for Advanced React and TypeScript (tec) | | 911 |
strategies, react, typescript, architecture, testing, performance, security, maintenance |
The “search” Element (sco) | | 910 |
html, semantics |
What We’ve Learned About Designing for Accessibility From Our Users (and/sla) | | 909 |
design |
Accessible but Never Boring: Rebranding the Wise Design System for Everyone II (ste/wis) | | 908 |
design, design-systems |
Certifications Should Be Hard (kar) | | 907 |
training, learning |
Visually Hidden Content Is a Hack That Needs to Be Resolved, Not Enshrined (sco) | | 906 |
browsers, screen-readers, assistive-tech, css |
Annotating Designs for Accessibility (cla/int) | | 905 |
videos, design |
When Is “:focus-visible” Visible? (ire) | | 904 |
css, selectors |
How Screen Readers Read Special Characters: An Update (sop/ele) | | 903 |
screen-readers, support, unicode |
Hijacking Screenreaders With CSS (ben/deq) | | 902 |
videos, screen-readers, css |
Foundations: Pointer Gestures (gra/tpg) | | 901 |
fundamentals, usability |
Accessibility and Design Systems: The Deep-Dive Q&A (ger+/sup) | | 900 |
interviews, design-systems, deep-dives |
Accessibility Beyond Code Compliance (aar) | | 899 |
compliance |
It’s About Time CAPTCHAs Become Accessible (uxd) | | 898 |
captcha |
The H1 Conundrum: Understanding the Challenges of Heading Level One (art/dig) | | 897 |
semantics, headings, html |
Fix Color Contrast—Web Accessibility for Text and UI Design (gly) | | 896 |
colors, contrast |
Best Practices for Structuring Accessibility Testing (aa/tpg) | | 895 |
testing, best-practices |
Making Calendars With Accessibility and Internationalization in Mind (mad/css) | | 894 |
functionality, internationalization |
We Don’t Need “.visually-hidden” (den/web) | | 893 |
css, semantics, quality |
“content” Is Your Content? (cat/css) | | 892 |
css, content, seo, maintainability |
My Ideal Accessible Components Resource Is Holistic, Well Tested and Easy to Use (hdv) | | 891 |
components |
ARIA Live Regions for JavaScript Frameworks (its/log) | | 890 |
aria, live-regions, javascript, frameworks |
50.1% Empty Links (mat) | | 889 |
html, links, semantics, seo |
Client-Side JavaScript and React Criticism: What Comes Next? (mol) | | 888 |
javascript, react, performance, resilience, progressive-enhancement |
Are You Making These Five Mistakes When Writing Alt Text? (dan/a11) | | 887 |
writing, alt-text, images, mistakes |
Toolkit Tuesday: Using YouTube for Captions and Transcripts (kno) | | 886 |
videos, captions, youtube |
The WebAIM Strategic Accessibility Framework (web) | | 885 |
webaim, strategies |
A Native “Visually Hidden” in CSS? Yes Please! (mic/css) | | 884 |
browsers, screen-readers, assistive-tech, css |
Accessible but Never Boring: Rebranding the Wise Design System for Everyone (ste/wis) | | 883 |
design, design-systems |
A Beginner’s Guide to Manual Accessibility Testing (pop) | | 882 |
guides, testing |
The Web Needs a Native “.visually-hidden” (ben) | | 881 |
css |
Without Accessibility, There Is No Privacy or Security (lev) | | 880 |
privacy, security |
Conformance and Accessibility (j9t) | | 879 |
conformance, quality |
How People Read Online (evi/uxd) | | 878 |
content, readability, user-experience |
A Guide to Accessible Form Validation (as/sma) | | 877 |
guides, forms, validation, user-experience |
How to Style Your Alt Text (ede) | | 876 |
how-tos, css, alt-text, images |
Successful Teams Ensure 100% of Their Members Understand Keyboard Accessibility (mni) | | 875 |
|
Automatic Captions: Our Experiments and Best Practices (equ) | | 874 |
captions, best-practices, automation |
Open Captions vs. Closed Captions: What’s the Difference? (3pl) | | 873 |
captions, comparisons |
How Shadow DOM and Accessibility Are in Conflict (sun/iga) | | 872 |
dom, shadow-dom |
The Importance of Adding Accessibility Design Reviews to the Design Process (dav/adh) | | 871 |
design, processes |
Not Everyone Uses a Computer in the Same Way That You Do (hdv/hux) | | 870 |
videos |
ARIA vs. HTML (aar) | | 869 |
html, aria, semantics, comparisons |
Understanding the Cost of Not Being Accessible (kar) | | 868 |
economics |
Keys to an Accessibility Mindset (dan/sma) | | 867 |
design |
Ideas for Making Accessibility and Equity a Core Part of the Software Development Lifecycle (eli) | | 866 |
dei, processes |
Avoid Spanning Table Headers (aar) | | 865 |
assistive-tech, html, tables |
If You’re Going to Do a Job, Do It Properly (tem) | | 864 |
css |
Software Accessibility for Users With Attention Deficit Disorder (ADHD) (uxd) | | 863 |
|
A Step-by-Step Guide to Building Accessible Carousels (swe/sma) | | 862 |
guides, carousels, html, user-experience |
Screen Readers Don’t Convey the Semantics of “strong” and “em” (mat) | | 861 |
screen-readers, semantics, html |
Scaling Accessibility Through Design Systems (ger+/sup) | | 860 |
videos, design-systems, scaling |
Buttons, Links, and Focus (tem) | | 859 |
semantics, buttons, links, focus |
A Practical Approach to Automated Accessibility (ste) | | 858 |
testing, automation |
Automation Is Not the Enemy (kar) | | 857 |
testing, automation |
Automated Testing Won’t Solve Web Accessibility (yat) | | 856 |
testing, automation |
Foundations: Introduction to WAI–ARIA (ihe/tet) | | 855 |
fundamentals, introductions, aria |
The Troublesome Life and Lamentable Death of Success Criterion 4.1.1 | | 854 |
wcag, conformance, standards |
How to Build Accessible Main Navigation? (tim/iod) | | 853 |
how-tos, navigation |
Focus Appearance Thoughts (ala) | | 852 |
focus, css |
Testing Colour Accessibility With Dev Tools (mic/css) | | 851 |
colors, testing, browsers, dev-tools |
Non-Text Content Contrast Also Matters (ia) | | 850 |
colors, contrast |
WCAG 2.2 Update: It’s Time to Say Goodbye to the Parsing Criterion (jon) | | 849 |
wcag, standards |
Setting Expectations for Asking ChatGPT Web Accessibility Questions (sco) | | 848 |
ai, chatgpt |
External Links: In or Out (art/dig) | | 847 |
seo, links, user-experience |
Understanding Color and Accessibility (kat) | | 846 |
colors |
Léonie Watson on Accessibility (tin+/inf) | | 845 |
podcasts, interviews |
New WCAG 2.2 Features Rated (yat) | | 844 |
wcag, standards |
Accessible Hamburger Buttons Without JavaScript | | 843 |
javascript, navigation |
Pointing and Calling and Accessibility Testing (bri) | | 842 |
testing |
Use the Dialog Element (Reasonably) (sco) | | 841 |
html, modals |
Musing Upon an “[alt]” Text Badge on Images (chr) | | 840 |
html, css |
Are We There Yet? WCAG 2.2 Is at the Candidate Recommendation Stage Again (gwi/deq) | | 839 |
wcag, standards |
A Simple Custom (ste) | | 838 |
forms, usability, css |
Creating a Community That Values Accessibility (web) | | 837 |
community |
If You Need a Link, Don’t Use a Button (tem) | | 836 |
html, semantics, links, buttons |
Be a Digital Ally: Further Exploration of WCAG 2.2 (kno) | | 835 |
wcag, standards |
Comparing Level Access Automated Tools to Manual Accessibility Testing (rac) | | 834 |
tooling, testing, automation |
Web Accessibility Global Usage Survey | | 833 |
surveys |
Comparing Manual and Free Automated WCAG Reviews (aar) | | 832 |
wcag, auditing, comparisons |
Accessible Writing Is Just Good Writing (get) | | 831 |
writing |
Blind News Audiences Are Being Left Behind in the data Visualisation Revolution: Here’s How We Fix That (joh/ris) | | 830 |
information-design |
Foundations: Visible Focus Styles (joe/tet) | | 829 |
fundamentals, focus, css |
Manual Accessibility Testing (dev) | | 828 |
testing |
The Main Areas of WAI–ARIA (ia) | | 827 |
aria |
Closed Captions and Subtitles UX (vit/sma) | | 826 |
captions, user-experience |
2023 Design Trends From an Accessibility Perspective (acc) | | 825 |
design, trends |
Stock Photos of People With Disabilities (den/web) | | 824 |
content, images |
A New Accessibility Strategy for the GOV.UK Design System (dav+/gov) | | 823 |
strategies, design-systems |
JAWS, NVDA, and VoiceOver Braille Viewers (aar) | | 822 |
screen-readers, jaws, nvda, voiceover, apple |
WAI–Adapt Explainer (see+/w3c) | | 821 |
|
Quick Thoughts on Typeface and Font Accessibility (jon) | | 820 |
fonts, typography |
Carry On Testing 2023 (ste/tpg) | | 819 |
testing |
A Beginner’s Guide to Link and Text Accessibility (pop) | | 818 |
guides, links, content |
Overlapping Interactive Areas (tem) | | 817 |
design |
Fluid Typography: Predicting a Problem With Your User’s Zoom-In (rus/sma) | | 816 |
typography, css, zooming |
Website Accessibility (15 Best Practices) (bru) | | 815 |
best-practices, content, readability, captcha, images, alt-text, forms, focus, html, tooling |
User Stylesheets Are Still Pretty Great and Should Be More Widely Supported (nic/pxl) | | 814 |
css, user-styles |
Top 10 Accessibility News of 2022 (equ) | | 813 |
retrospectives |
Obscure CSS: Restoring Visibility (kiz) | | 812 |
css |
Aligning Jakob Nielsen’s 10 Usability Heuristics With the WCAG 2.1 (hom) | | 811 |
wcag, usability, heuristics |
Cache the World: Turbo Charging Firefox Accessibility Performance and Maintainability (jcs) | | 810 |
firefox, mozilla, browsers, caching |
What Is the Difference Between Alternative Text, Long Description, and Caption? (red/mat) | | 809 |
|
An Inclusive and Planet-Friendly Digital Style Guide (th/uxd) | | 808 |
design, style-guides, dei, sustainability, ethics |
Quick Start for Evaluating and Testing Web Accessibility (jar+/web) | | 807 |
videos, testing |
The Intended Consequence of Inaccessible Digital Ads (joe+/web) | | 806 |
videos, monetization |
Accessibility Convincing (lfl/web) | | 805 |
videos, ethics, legal |
Building an Accessible Theme Picker With HTML, CSS, and JavaScript (fos) | | 804 |
html, css, javascript, theming, functionality |
Foundations: Target Sizes (joe/tet) | | 803 |
fundamentals, usability |
Useful Accessibility and Usability Examples to Help Improve Your Designs (sma) | | 802 |
usability, examples |
Bad Performance Is Bad Accessibility (bru) | | 801 |
performance |
Prevent Focused Elements From Being Obscured by Sticky Headers (sib/tpg) | | 800 |
usability, css, focus |
5 HTML Elements, and a Partridge in a Despair Tree (mat) | | 799 |
html, semantics |
How to Find and Fix the Top 3 Accessibility Issues (deq) | | 798 |
videos, how-tos, auditing |
Accessibility Starts With an Organisation’s Culture (cra/gov) | | 797 |
culture |
A Guide for Making Apps Accessible | | 796 |
guides |
Federal Web Accessibility Focus Has Private Sector on Notice (edw/bla) | | 795 |
legal |
Top 5 Accessibility Issues in 2022 (lar/int) | | 794 |
retrospectives |
Accessible Front-End Patterns for Responsive Tables II (cod/sma) | | 793 |
tables, responsive-design |
State of A11Y (thi) | | 792 |
videos |
WCAG 3.0: Are We There Yet? (ons/tpg) | | 791 |
wcag, standards |
Five Myths About Digital Accessibility (sco) | | 790 |
videos, myths |
WCAG—Priority of Constituencies (ala) | | 789 |
wcag, prioritization |
Meaningful Labels Using ARIA—or Not (cfd/mat) | | 788 |
html, forms, labels, aria |
W3C Publishes WCAG Testers Consistency List (wil/deq) | | 787 |
wcag, testing |
Accessible Front-End Patterns for Responsive Tables (cod/sma) | | 786 |
tables, responsive-design |
Accessibility: The Land That “Time to Interactive” Forgot (tin/per) | | 785 |
videos, performance |
Brief Note on Description List Support (aar) | | 784 |
html, lists, semantics, screen-readers, support |
Swearing and Automatic Captions (eri) | | 783 |
multimedia, captions |
The 411 on 4.1.1 (aar) | | 782 |
wcag, standards |
Reading the Meter (sup/mat) | | 781 |
html, semantics |
Website Accessibility Is Not an Afterthought | | 780 |
|
Landmarks and Where to Put Them (kil/mat) | | 779 |
html, semantics, aria |
Accessibility and MVPs (dav) | | 778 |
principles |
How to Use the WAVE Extension and Start Manual Accessibility Testing (pop) | | 777 |
how-tos, testing, tooling, webaim |
You Don’t Need ARIA for That (den/mat) | | 776 |
html, aria |
HTML Semantics and Accessibility Cheat Sheet (web) | | 775 |
cheat-sheets, html, semantics |
Which Images Need Descriptive Text? (tem) | | 774 |
writing |
Making Microservices Accessible (abb) | | 773 |
microservices |
Making Accessibility Simpler in Higher Education and Beyond (vle) | | 772 |
videos |
Shadow DOM and Accessibility: The Trouble With ARIA (nol) | | 771 |
dom, shadow-dom, aria, html |
Addressing Concerns About CSS Speech (tin) | | 770 |
css, voice |
Positioning Notification Messages With Accessibility in Mind (cod) | | 769 |
notifications, positioning |
Setting Up a Screen Reader Testing Environment on Your Computer (sar) | | 768 |
screen-readers, testing, tooling |
Accessibility and Inclusive Design Systems (bra/hux) | | 767 |
videos, design-systems, dei |
Preparing for WCAG 2.2 (sar+/int) | | 766 |
videos, wcag |
The Value of Accessibility (ann+/des) | | 765 |
podcasts |
Page Title Conventions (ada) | | 764 |
html, seo |
A Guide to Keyboard Accessibility: JavaScript (its/sma) | | 763 |
guides, keyboard-navigation, javascript |
Incorporating Accessible Design Elements Into Your Web Site (con/uxm) | | 762 |
design |
DOJ and Congressional Updates on Digital Accessibility (con) | | 761 |
legal |
Analyzing the Top 100 Retailers for Digital Accessibility (deq) | | 760 |
studies, research |
Brief Note on “aria-readonly” Support (aar) | | 759 |
html, aria, assistive-tech, support |
5 Insider Tips to Make Accessibility Part of Workflow (at/mni) | | 758 |
tips-and-tricks, processes |
Accessibility Is in Style—Styles and Style Guides (mbf/kno) | | 757 |
writing, design, documentation, style-guides, consistency, quality |
Using Automated Test Results to Improve Accessibility (a11+/sma) | | 756 |
automation, testing |
Significant Improvements for Screen Readers Now in Nightly Firefox (asa/moz) | | 755 |
browsers, screen-readers, mozilla, firefox |
Your Accessibility Claims Are Wrong, Unless… (aar) | | 754 |
communication |
A Guide to Keyboard Accessibility: HTML and CSS (its/sma) | | 753 |
guides, keyboard-navigation, html, css |
Don’t Disable the Zoom Functionality (ia) | | 752 |
zooming |
The Anatomy of “visually-hidden” (sib/tpg) | | 751 |
css |
Are You Using an Accessibility Overlay to Help Disabled Users? Don’t! (med/sen) | | 750 |
overlays, legal |
What’s New in WCAG 2.2 (rav/a11) | | 749 |
videos, wcag, standards |
Accessfuturism: Digital Accessibility in 2032 (sco/web) | | 748 |
videos, outlooks |
Designing for People Who Use a Mouse (ihe/web) | | 747 |
videos |
Dialogs, Modality, and Popovers Seem Similar—How Are They Different? (hdv) | | 746 |
html, semantics, modals, pop-overs |
Accessibility Contrast Requirements Explained and How to Fix 5 Common Low-Contrast Issues (pop) | | 745 |
colors, contrast |
Foundations: Native Versus Custom Components (tet) | | 744 |
fundamentals, components, html, comparisons |
What Designers Can Learn From Apple’s New Accessibility Features (uxd) | | 743 |
design, apple |
Responsive Accessibility Using “visibility: hidden” (sco) | | 742 |
responsive-design, css |
A Simpler Approach to Document and Web Accessibility (con) | | 741 |
|
Why You Need to Monitor and Report on Accessibility—All the Time (deq) | | 740 |
monitoring, compliance, legal |
5 Takeaways From Screen Reader Usability Interviews (jes) | | 739 |
screen-readers, usability |
Accessibility “Gaps” in MVPs (aar) | | 738 |
|
Caring About the World Wide Web (ada/hux) | | 737 |
videos, dei, web |
Why You Need to Involve Deaf and Hard of Hearing People in Research and Testing (mer/a11) | | 736 |
videos |
A Deep Dive Into Accessible Notifications (rus/a11) | | 735 |
videos, notifications, deep-dives |
Progress Over Perfection: A Better Way to Accessibility (mer) | | 734 |
processes |
A Testing Strategy for Accessibility in New Apps (mar) | | 733 |
testing |
7 Tactics That Benefit Both Accessibility and SEO (deq) | | 732 |
seo |
Next Steps for the W3C Web Accessibility Initiative (sab/g3i) | | 731 |
videos, w3c |
“aria-label” Is a Code Smell (eri) | | 730 |
aria, labels, quality, technical-debt |
Complexity and Caution (tem) | | 729 |
usability, complexity |
Do We Need an Interop for Assistive Technologies? (hdv) | | 728 |
browsers, screen-readers, assistive-tech, interoperability |
5 Visual Treatments that Improve Accessibility (nng) | | 727 |
design |
Why You Should Never Use “px” to Set “font-size” in CSS (jjc) | | 726 |
css |
Getting WCAG Color Contrast Right (luk/uxd) | | 725 |
wcag, colors, contrast |
Accessibility Beyond the “Obvious” (tem) | | 724 |
|
Web Accessibility: ARIA 101 (vav/thi) | | 723 |
videos, aria |
Twitter Reminds Us About Alt Text, but How Good Are We at It? (she/uxd) | | 722 |
writing, alt-text, images, twitter+x |
The Truth Behind Implicit/Explicit Form Labels (the) | | 721 |
html, forms, labels |
SEO and Accessibility Are Symbiotic (deq) | | 720 |
seo |
Why We Need CSS Speech (tin) | | 719 |
css, voice |
Digital Accessibility—Ask Me Anything (max+/tpg) | | 718 |
videos |
How to Build the Foundation for Digital Accessibility (a11/deq) | | 717 |
how-tos, policies, processes |
Google on Alt Text SEO and Accessibility (joh+/sea) | | 716 |
google, seo, writing, alt-text, images |
Common ARIA Mistakes and How to Avoid Them (ale) | | 715 |
html, aria, mistakes |
Designing for Users With Disabilities: 10 Factors to Consider (uxm) | | 714 |
design, usability |
Accessibility Checkers—a Good Start, Not a Solution (mbf/kno) | | 713 |
testing, tooling |
New Brutalism and Web Accessibility: What You Need to Know (rya/uxd) | | 712 |
design |
What I Learned About SVG Accessibility (Among Other Things) From NBC News’ Senate “What If” Project (joe) | | 711 |
svg, images, lessons |
Intro to Why Accessibility Is Important for Good SEO (deq) | | 710 |
introductions, seo |
Some Things I Took Away From an Event Apart 2022 in Denver (geo/css) | | 709 |
web, css |
Representation in “alt” Text (aar) | | 708 |
dei, writing |
How to Write Good Alt Text (cfe) | | 707 |
how-tos, writing, alt-text, images |
WCAG 2.2 Success Criteria (bho) | | 706 |
wcag |
4 Required Tests Before Shipping New Features (5t3) | | 705 |
testing |
Five Months Worth of Takes on the Digital Accessibility Space (gin/for) | | 704 |
testing, tooling |
Foundations: HTML Semantics (ihe/tet) | | 703 |
fundamentals, html, semantics |
3 Things to Consider Before You Implement CAPTCHA for Accessibility (uxd) | | 702 |
captcha |
When Going Somewhere Does a Thing: On Links and Buttons (kil) | | 701 |
html, links, buttons, semantics |
Where Are the Accessibility Statements? Digital Accessibility Shouldn’t Be a Surprise (deq) | | 700 |
|
A Beginner’s Complete Guide to Form Accessibility: The 5 Things Accessible Forms Need and How to Fix Common Errors (pop) | | 699 |
guides, forms |