| 6 Questions for Eric Eggert (yat+/fro) | | 1698 |
| interviews, eaa, legal |
| Which VoiceOver? (aar) | | 1697 |
| voiceover, screen-readers, unix-like, apple |
| Alt Text Accessibility: Balancing AI and Human Oversight (cda+/equ) | | 1696 |
| podcasts, images, multimedia, alt-text, ai, quality |
| 10 Digital Accessibility Mistakes to Avoid (gov) | | 1695 |
| mistakes, alt-text, images, contrast, colors, keyboard-navigation, aria, semantics, headings, labels, forms, pop-ups, testing |
| Before You Buy an Accessibility Audit (cer) | | 1694 |
| auditing, training, testing, culture |
| The Politics of Accessibility (bri) | | 1693 |
| history, advocacy |
| The DOJ Provides Practical Guidance on How to Implement a Digital Accessibility Program (sey) | | 1692 |
| how-tos, processes, prioritization |
| Considerations for Making a Tree View Component Accessible (eri/git) | | 1691 |
| components, keyboard-navigation, aria, case-studies |
| Best Practices for EU Web Accessibility Compliance Monitoring (tae/a11) | | 1690 |
| compliance, eaa, legal, monitoring |
| How to Build a “Copy Code” Snippet Button and Why It Matters (whi) | | 1689 |
| how-tos, buttons, functionality, developer-experience |
| Creating Accessibility Systems to Fix Accessibility Issues (vis/ass) | | 1688 |
| processes, automation |
| 9 Design System Metrics That Matter (sup) | | 1687 |
| design-systems, metrics, user-experience, consistency, maintenance, documentation, economics |
| Exploring AI, Web Development, and Accessibility in Tech With Stefan Judis (ste+/wea) | | 1686 |
| videos, interviewing, ai, javascript, runtimes, screen-readers, craft |
| The Four Most Dangerous Words to People With Disabilities (ins) | | 1685 |
| communication |
| Audio Description in Advertising (eri+/a11) | | 1684 |
| videos, monetization, multimedia |
| Don’t Wrap Figure in a Link (aar) | | 1683 |
| html, links, screen-readers |
| On Certification (mar) | | 1682 |
| career, training |
| Advancing Accessibility: Strategies for Continuous Improvement (seg/equ) | | 1681 |
| strategies, processes, culture |
| ADA Title II: Top 20 Questions Answered (gwi/deq) | | 1680 |
| ada, legal, wcag |
| A11y 101: 1.3.1 Info and Relationships (nat) | | 1679 |
| introductions, wcag |
| Accessibility of Emojis for List Bullets—Potential Issues (cer) | | 1678 |
| emoji, lists, screen-readers, pronunciation |
| HTML Developers: Please Consider—in the Year of 2025 (ste) | | 1677 |
| html, aria |
| How to Conduct Accessibility Testing With Screen Readers (sit) | | 1676 |
| how-tos, testing, screen-readers, assistive-tech |
| Can AI Be Used as an Accessibility Testing Partner? (tho) | | 1675 |
| ai, testing, tooling, comparisons |
| Automated and Manual Accessibility Testing Work Best Together (pop) | | 1674 |
| testing, comparisons |
| Accessibility Always a Focus in Drupal (the+/the) | | 1673 |
| interviews, drupal |
| “aria-description” Does Not Translate (aar) | | 1672 |
| aria, browsers, localization |
| Accessibility Essentials Every Front-End Developer Should Know (mar) | | 1671 |
| fundamentals, html, semantics, forms, keyboard-navigation, modals, alt-text, focus, responsive-design, aria |
| Brief Note on Figure and Figcaption Support (aar) | | 1670 |
| html, screen-readers, support |
| Quick Note: Limit Use of “Logo” in Alt Text (nat) | | 1669 |
| images, logos, alt-text, microcontent |
| Updated Brief Note on Description List Support (aar) | | 1668 |
| html, lists, semantics, screen-readers, support |
| FTC Orders AI Accessibility Startup accessiBe to Pay $1M for Misleading Advertising (kyl/tec) | | 1667 |
| legal, ai |
| Using Iframes to Embed Arbitrary Content Is Probably a Bad Idea (tem) | | 1666 |
| frames, embed-code, keyboard-navigation, scrolling, screen-readers |
| Improve Accessibility of User Authentication (cer) | | 1665 |
| authentication, forms, labels, validation |
| Misleading Icons: Icon-Only-Buttons and Their Impact on Screen Readers (ale/mat) | | 1664 |
| html, buttons, icons, images, screen-readers |
| Why Heading Order Matters in HTML (gra) | | 1663 |
| html, headings |
| Principles of Web Accessibility (hey) | | 1662 |
| principles |
| The Search Input: They Almost Got It Right (stv/mat) | | 1661 |
| html, forms, labels, screen-readers, assistive-tech |
| Why Are We So Rubbish at Accessibility? (car) | | 1660 |
| craft, culture |
| Don’t Hide Skip Links (oze) | | 1659 |
| skip-links |
| PSA: Stop Using the “title” Attribute as Tooltip (dni/mat) | | 1658 |
| html, attributes, tooltips, toggles |
| Please Keep Your HTML Tables Clean and Lean, if You Really Need to Use Them (cer) | | 1657 |
| html, tables |
| Accessibility First: How to Design Inclusive Frontend Experiences (the/fro) | | 1656 |
| how-tos, design, html, semantics, alt-text, keyboard-navigation, aria, contrast, forms, focus |
| AI and the Future of Accessibility with Dr. Gregg Vanderheiden (ind) | | 1655 |
| podcasts, interviews, assistive-tech, ai, outlooks |
| No ARIA Is Better Than Bad ARIA (kar) | | 1654 |
| videos, aria, html |
| The European Accessibility Act: Understanding Digital Accessibility (coo/dac) | | 1653 |
| legal, eaa |
| Have an Accessible New Year With These 12 Resolutions (ins) | | 1652 |
| captions, wcag, testing, headings, modals |
| How to Make Your Angular Projects More Accessible (dan) | | 1651 |
| how-tos, angular, examples |
| How I Gained a New Perspective on ARIA (mei/mat) | | 1650 |
| aria |
| You Don’t Need the “isOpen” Class (mau/mat) | | 1649 |
| html, aria |
| The Gift You Do Not Want: A Div in a Button’s Clothing (cor/mat) | | 1648 |
| html, buttons |
| Potential Dangers of Status Messages (cer) | | 1647 |
| wcag, microcontent |
| Page by Page: How Pagination Makes the Web Accessible (mat) | | 1646 |
| pagination, html, css, svg |
| How to Dehumanize Accessibility With AI (ash) | | 1645 |
| how-tos, ai |
| Easily Check for Web Accessibility Problems in Ten Minutes or Less (axe) | | 1644 |
| testing, keyboard-navigation, zooming |
| ARIA in HTML (sco+/w3c) | | 1643 |
| standards, aria, html |
| How Strict Should We Be When Testing for WCAG Conformance? (sib/tpg) | | 1642 |
| videos, wcag, compliance |
| Updated Drafts for Review: W3C Accessibility Guidelines (WCAG) 3.0 (w3c) | | 1641 |
| wcag, w3c, standards |
| Preventing Ageism in Design: Digital Accessibility for Older Adults (tpg) | | 1640 |
| design, dei |
| The “Perilous Pitfalls” of Accessibility Maturity (ins) | | 1639 |
| leadership, product-management |
| Accessibility Fail Friday: “1” for “Yes” and “0” for “No” (byr) | | 1638 |
| forms |
| Accessibility Best Practices for Single Page Applications (SPAs) (sit) | | 1637 |
| best-practices, single-page-apps |
| AI and Accessibility: Ethical Considerations and Solutions (tae/a11) | | 1636 |
| ai, ethics |
| Almost, but Not Quite, Entirely Unlike… (tin/mat) | | 1635 |
| buttons, html, ai |
| The Importance of Graceful Degradation in Accessible Interface Design (ele/sma) | | 1634 |
| design, user-experience, graceful-degradation, progressive-enhancement |
| “aria-labelledby = self” (wes/mat) | | 1633 |
| aria |
| Forced Colors Mode Futility (css/mat) | | 1632 |
| colors, contrast, css |
| The Complete Guide to ARIA Live Regions for Developers (flo/a11) | | 1631 |
| guides, aria, live-regions |
| When Is a Skip Link Needed? (tpg) | | 1630 |
| skip-links, keyboard-navigation, focus |
| How to Include Web Accessibility in Your Web Development Process (pop) | | 1629 |
| how-tos, processes, tooling, webaim |
| How to Include Web Accessibility in Your Content Writing Process (pop) | | 1628 |
| how-tos, content, writing, processes |
| A Link on a Logo in the Header, What Should the Alt-Text Be? (ria/mat) | | 1627 |
| branding, links, logos, images, alt-text |
| Designed With Care (rac) | | 1626 |
| websites, books, design, content, compliance |
| The Future of Front-End Development: Trends to Watch in 2025 (max) | | 1625 |
| ai, qwik, solidjs, webassembly, esm, design-systems, headless, sustainability, dev-tools, low-and-no-code |
| Designing Your Own Accessibility Vendor Monitoring Program (a11) | | 1624 |
| videos, business-relations, monitoring |
| A False Sense of Accessibility: What Automated Testing Tools Are Missing (in/a11) | | 1623 |
| videos, testing, automation, tooling |
| Don’t Fuck With Scroll (as) | | 1622 |
| websites, scrolling, user-experience, usability, maintainability |
| Stop Aiming for Compliance: Craft a Better Product Strategy Instead (car/tho) | | 1621 |
| compliance, product-management, strategies, processes |
| The Many Faces of Digital Accessibility (aar/a11) | | 1620 |
| videos, career |
| Create Accessible Websites: Top Free Tools You Need to Know (ask) | | 1619 |
| testing, jaws, nvda, screen-readers, linting, tooling |
| Language of Parts Bookmarklet (bea) | | 1618 |
| bookmarklets, html, metadata |
| How to Comply With DOJ’s Seemingly Impossible Web Accessibility Regulation (con) | | 1617 |
| how-tos, legal, compliance |
| Old Alt Text Advice (ste) | | 1616 |
| images, alt-text, html, microcontent, best-practices |
| Using Severity Ratings to Prioritize Web Accessibility Remediation (ala/web) | | 1615 |
| prioritization |
| Introducing the Leader’s Guide to Accessibility (gov) | | 1614 |
| guides, introductions, leadership, processes, terminology |
| Doing the Numbers: Digital Accessibility and Shifting Left (deq) | | 1613 |
| processes, metrics, economics |
| Avoid Read-Only Controls (aar) | | 1612 |
| html, forms |
| Why Accessibility Matters for Your SEO Strategy (tae/a11) | | 1611 |
| seo, strategies |
| How to Use Lighthouse Wisely in Your Front-End Projects (ele/des) | | 1610 |
| guest-posts, how-tos, lighthouse, google, performance, seo, best-practices |
| Mastering Accessible Modals With ARIA and Keyboard Navigation (a11) | | 1609 |
| keyboard-navigation, aria, modals, javascript |
| Web Accessibility and the Second Trump Administration (con) | | 1608 |
| legal |
| Foundations: Types of Disability (tet) | | 1607 |
| fundamentals |
| Why Responsive Design Is Failing Modern Users (web) | | 1606 |
| responsive-design, performance, usability |
| Some Tips for Keyboard Support on Native Mobile Applications (cer) | | 1605 |
| mobile, native, keyboard-navigation, tips-and-tricks |
| Alt Text: Not Always Needed (tbk/nng) | | 1604 |
| images, alt-text, writing |
| How Is Digital Accessibility Awareness Being Promoted Across the Globe? (oze) | | 1603 |
| advocacy |
| The Myth of “Accessible Components and Done” (mic/a11) | | 1602 |
| components, myths |
| Global Digital Accessibility Salary Survey (web) | | 1601 |
| career, surveys |
| Accessibility Misinformation (col) | | 1600 |
| wcag, apca |
| The European Accessibility Act—Get Ready (int) | | 1599 |
| legal, eaa |
| Most Disabled People “Excluded” by Unfit Designs (des) | | 1598 |
| design, dei |
| What Accessibility Statements Are Really For (jon) | | 1597 |
| legal |
| Accessibility (mgi/htt) | | 1596 |
| web-almanac, studies, research, metrics |
| Two Different Kinds of “Focusable” UI Elements (yat) | | 1595 |
| focus, keyboard-navigation |
| How to Identify Decorative Images and Boost Accessibility (a11) | | 1594 |
| how-tos, images, decoration, html, aria |
| My Anti-Overlay Client Letter (acc) | | 1593 |
| overlays, business-relations, communication, advocacy |
| Beautiful Focus Outlines (med) | | 1592 |
| css, focus, examples |
| How to Test JavaScript for Accessibility Compliance (flo/a11) | | 1591 |
| how-tos, javascript, compliance, wcag, testing |
| Unlocking Accessibility: Content Designers Share Their Experience and Advice (gov) | | 1590 |
| interviews, design |
| Disabled and Obscured (ste) | | 1589 |
| html, forms, wcag, standards |
| The Only Accessibility Video You Will Ever Need (dev) | | 1588 |
| videos |
| JavaScript Do’s and Don’ts (mua) | | 1587 |
| javascript |
| 25 Accessibility Tips to Celebrate 25 Years (jar/web) | | 1586 |
| tips-and-tricks, aria, html |
| “Functionality” Is Not Constrained by Content (duf/pdf) | | 1585 |
| pdf, wcag, content |
| Testing With a Screen Reader Is an Important Step (mic) | | 1584 |
| testing, screen-readers |
| Reducing Digital Accessibility Litigation Risk (byr) | | 1583 |
| legal, standards, processes |
| Tooltip Best Practices (zel/css) | | 1582 |
| tooltips, best-practices |
| PDF Accessibility on the Web: Tricks and Traps (ons/tpg) | | 1581 |
| pdf, tips-and-tricks |
| Clarifying the Relationship Between Popovers and Dialogs (zel/css) | | 1580 |
| pop-overs, modals, html, comparisons |
| Naming Things Is Still a Common and Enduring Challenge in Accessibility (cer) | | 1579 |
| naming |
| The Internet Is Unusable—the Disabled View (a11/web) | | 1578 |
| videos, web |
| Talkin’ Tables (aar/web) | | 1577 |
| videos, tables, html |
| Improving Accessibility Through Design Systems (xir/web) | | 1576 |
| videos, design-systems |
| Accessibility for the Deaf / Hard of Hearing and Progress Over Perfection (mer/web) | | 1575 |
| videos |
| Designing for Anyone: The Power of Accessible Products (ant) | | 1574 |
| design, dei |
| Six Things Not Related to Accessibility That Will Improve Your Disability Inclusion Efforts (ins) | | 1573 |
| dei, culture, leadership |
| What’s New in WAI–ARIA 1.3 (all/iaa) | | 1572 |
| videos, aria |
| Making Accessibility Accessible (bas) | | 1571 |
|
| Be a Dolphin Not a Shark: Using Cooperation Over Conflict to Advance Digital Accessibility (lfl/par) | | 1570 |
| videos, advocacy, collaboration, strategies |
| 10 Simple Ways to Make Your Social Media Posts Accessible (vis) | | 1569 |
| social-media, content, images, alt-text, captions, contrast |
| Accessible Design: WCAG or Trendy? No, WCAG and Trendy! (bat/wpa) | | 1568 |
| videos, design, wcag |
| Foundations: Form Validation and Error Messages (tet) | | 1567 |
| fundamentals, forms, validation, errors, usability |
| Accessibility Challenges With Single Page Applications (wpa) | | 1566 |
| videos, single-page-apps |
| If You Care (a11) | | 1565 |
|
| Developing a Web Site Nonvisually in a Linux Environment (jas) | | 1564 |
| unix-like, hugo, pico, processes |
| Tips for Inclusive and Accessible Hiring and Recruiting (gwi/deq) | | 1563 |
| dei, hiring, tips-and-tricks, myths, strategies |
| “aria-activedescendant” Is Not Focus (cod) | | 1562 |
| aria, focus |
| Understanding VPATs and ACRs: Key Insights (nat) | | 1561 |
| vpat-acr |
| What Makes a Font Accessible? A Designer’s Guide (a11) | | 1560 |
| guides, design, fonts, typography |
| Design Systems and How to Use Them in an Accessible Way (bol/tes) | | 1559 |
| videos, how-tos, design-systems |
| The Elephant in the New Accessibility Law: PDFs (bex) | | 1558 |
| legal, pdf |
| AI for Accessibility Conformance Testing? Why? (ste) | | 1557 |
| compliance, testing, ai |
| The Value of Accessibility Annotations in Inclusive Design (ant/wet) | | 1556 |
| design, dei, annotations |
| Shopify, Accessibility Lawsuits, and “Compliance” | | 1555 |
| shopify, legal, compliance |
| Why GOV.UK’s “Exit This Page” Component Doesn’t Use the Escape Key (bat) | | 1554 |
| user-experience, keyboard-navigation |
| No Industry for Old Men (ste/web) | | 1553 |
| videos, retrospectives, html, aria, browsers, screen-readers, w3c |
| Designing for Accessibility: Enhancing Math Learning for the Blind Using the NVDA Screen Reader | | 1552 |
| design, nvda, screen-readers |
| Reminder—Automatic Accessibility Testing Can Detect Inaccessibility but Can’t Detect Accessibility (cer) | | 1551 |
| testing |
| How a Bottom-Up Design Approach Enhances Site Accessibility (ele/sma) | | 1550 |
| design, processes |
| Practical Accessibility Tips You Can Apply Today (pic) | | 1549 |
| tips-and-tricks, html |
| JAWS (Only) No More (ste) | | 1548 |
| jaws, nvda, voiceover, apple, google, screen-readers, support |
| “Straight to the Pool Room”: The Pitfalls of Placing Accessibility Issues in the Backlog (int) | | 1547 |
| processes, prioritization, project-management |
| How to Identify a Toxic Accessibility Culture, and What You Can Do About It (ins) | | 1546 |
| how-tos, culture |
| Celebrating WebAIM’s 25th Anniversary (jar/web) | | 1545 |
| webaim, anniversaries |
| Making Maps Accessible to Screen Readers (mni) | | 1544 |
| screen-readers, link-lists |
| The State of Accessibility (slo/tpg) | | 1543 |
| videos, podcasts, standards |
| Challenging the Case for Delayed ADA Compliance (tec/equ) | | 1542 |
| podcasts, interviews, ada, compliance, legal |
| Accessibility Is Everyone’s Responsibility (mer) | | 1541 |
| culture, dei |
| Your Accessibility Questions Answered by a Blind Person (usa) | | 1540 |
|
| A Step-by-Step Guide to Conducting a Web Accessibility Audit (tpg) | | 1539 |
| guides, auditing, testing, processes |
| Accessibility Preference Settings, Information Architecture, and Internalized Ableism (eri) | | 1538 |
| information-architecture, wcag, apple |
| Brief Note on Disclosures in Fieldsets (aar) | | 1537 |
| forms, pop-overs |
| But Why?? (a11) | | 1536 |
| slides, design-patterns, testing, keyboard-navigation, contrast, colors, zooming |
| Good Forms (dav) | | 1535 |
| forms, best-practices, usability, validation |
| Using Controllers for Keyboard Accessibility (nik/a11) | | 1534 |
| videos, keyboard-navigation |
| Prioritize Accessibility in Procurement for Better CX and EX (gin/for) | | 1533 |
| prioritization, processes |
| The Folly of Chasing Demographics (hey/inc) | | 1532 |
| videos, dei |
| Understanding the “Why” Around Neurodivergent Inclusive Web Design (owe/inc) | | 1531 |
| videos, dei |
| How to Find the Accessible Name of a Button With Google Chrome (eri) | | 1530 |
| how-tos, buttons, chrome, google, browsers, dev-tools |
| Stop Recreating the Wheel: Local Government Organizations Sharing Accessibility Information (tec+/equ) | | 1529 |
| podcasts, interviews, processes, vpat-acr |
| WCAG and Accessibility Beyond Naive Misconceptions (ope) | | 1528 |
| wcag, testing, auditing |
| Mobile Accessibility Testing: Enhancing User Experience for All (a11) | | 1527 |
| user-experience, testing, mobile |
| I Need an Accessible Hero (acc) | | 1526 |
| design-patterns |
| “display: contents” Is Not a CSS Reset (aar) | | 1525 |
| css, resetting |
| Avoiding Accessibility Barriers With a Checklist for Custom Controls—Opinion (jer) | | 1524 |
| mobile |
| Should Form Labels Be Wrapped or Separate? (sib/tpg) | | 1523 |
| html, forms, labels, browsers, assistive-tech |
| Another Stab at Truncated Text (geo/css) | | 1522 |
| design, usability, css |
| Tackling a System’s Accessibility Without Testing (jbu+/gov) | | 1521 |
| wcag, case-studies, heuristics |
| Be Careful When Using Generative Artificial Intelligence to Produce Code (cer) | | 1520 |
| ai, code-generation |
| Headings (web) | | 1519 |
| html, headings |
| An Enhancement to Accessible Responsive Tables (tem) | | 1518 |
| tables, responsive-design, javascript |
| Harnessing Copilot and Other Gen-AI Tools to Increase Digital Accessibility Efficiency (vle) | | 1517 |
| videos, ai, microsoft, tooling, images, alt-text |
| Paragraphs (sco) | | 1516 |
| html |
| What the Heck Is ARIA? A Beginner’s Guide to ARIA for Accessibility (kat/a11) | | 1515 |
| videos, guides, aria, html |
| The “aside” Element (hey) | | 1514 |
| html, semantics |
| Building Better Logins: A UX and Accessibility Guide for Developers (uxd) | | 1513 |
| guides, user-experience |
| Make Me One (Input) With Everything (mor/mat) | | 1512 |
| html, forms, simplicity |
| WCAG’s A and AA Distinction Is Mostly Academic (yat) | | 1511 |
| wcag, standards |
| Why Is Reaching WCAG Level AAA Not Recommended? (cer) | | 1510 |
| wcag, standards |
| Is Using “aria-label” to Add Alternative Text But No “alt” Attribute Still a WCAG Fail? | | 1509 |
| discussions, html, attributes, forms, labels, aria, alt-text, images |
| Spoiler Alert: It Needs to Be Accessible (sco) | | 1508 |
| html, web-components, aria |
| Improving the Screen Reader Experience for “Learn WCs” (and) | | 1507 |
| user-experience, screen-readers, assistive-tech, apple, voiceover, case-studies |
| Basic Keyboard Shortcut Support for Focused Links (eri) | | 1506 |
| links, focus, support, browser-engines, keyboard-shortcuts |
| Foundations: Labelling Text Fields With Input and Label (tet) | | 1505 |
| fundamentals, forms, labels, html |
| Understanding WCAG 2.1’s Success Criteria 1.4.10 Reflow (mni) | | 1504 |
| wcag, reflow, zooming |
| Batteries Included Accessibility: A Pragmatic Guide to Get Started Today (mme+/iaa) | | 1503 |
| videos, guides, introductions |
| Accessibility Specialists Warn Against Using AI for Alt Text (mar/uka) | | 1502 |
| alt-text, images, ai |
| The “Other” C in CSS (sar/css) | | 1501 |
| videos, css |
| How Can Accessibility Improve Your Conversion Rate Optimization Efforts? (cer) | | 1500 |
| user-conversion, optimization, usability, economics |
| WCAG 2.2 Summary and Breakdown (mar) | | 1499 |
| wcag, guidelines, overviews |
| 80/20 Accessibility (mar) | | 1498 |
| principles |
| Writing Alt Text for a Scientific Figure (kri) | | 1497 |
| images, alt-text, writing, information-design |
| Captions vs. Subtitles: Leave No Viewer Behind (mer) | | 1496 |
| captions, readability, multimedia, comparisons |
| Alternatives to Using Pure Black (“#000000”) for Text and Backgrounds (ser/uxp) | | 1495 |
| design, colors, backgrounds |
| Designing for Accessibility: A Checklist for Designers (cod/acc) | | 1494 |
| design, checklists |
| Context Is King: Long Live the King! (llo/tpg) | | 1493 |
| usability, techniques, aria |
| The Importance of Communication in Accessibility Testing (con) | | 1492 |
| testing, communication |
| Things to Do Before Asking “Is This Accessible?” (aar) | | 1491 |
| terminology, communication |
| The Most Important Thing to Look at When Choosing an Accessibility Auditor (kar/a11) | | 1490 |
| auditing, vpat-acr |
| Design Patterns and WCAG (gra/tet) | | 1489 |
| design-patterns, wcag |
| Good Intentions, Poor Context (tpg) | | 1488 |
| microcontent, images, buttons, links |
| When It Comes to Digital Accessibility Lawsuits, the Best Defense Is a Good Offense (deq) | | 1487 |
| legal |
| WCAG 2.2 Map by Theme (hic) | | 1486 |
| wcag, standards |
| The “abbr” Element (hey) | | 1485 |
| html, semantics |
| Disability Data Alarmingly Absent From AI Algorithmic Tools, Report Suggests (for) | | 1484 |
| ai, tooling |
| Let’s Make a Simpler, More Accessible Web (cod) | | 1483 |
| web, web-platform, tooling, simplicity, usability, optimization |
| AT Is More Than Screen Readers (aar) | | 1482 |
| assistive-tech, screen-readers, terminology, concepts |
| European Accessibility Act Requires Culture to Shift! (cer) | | 1481 |
| legal, eaa, culture, leadership |
| How to Make the Internet More Accessible (gra+/bos) | | 1480 |
| how-tos, web |
| Types of Accessibility Approaches (a11) | | 1479 |
| processes, career, collaboration |
| Attitudes to Digital Accessibility 2024 (abi) | | 1478 |
| surveys |
| The Anatomy of Accessible Forms: Best Practices (deq) | | 1477 |
| forms, html, best-practices |
| Decoding WCAG: “Change of Context” and “Change of Content” (web) | | 1476 |
| wcag, standards |
| Interop 2024: Chrome at 100% for the Accessibility Focus Area (dev) | | 1475 |
| interoperability, browsers, google, chrome |
| Developing a RACI Matrix for Accessibility (kar/a11) | | 1474 |
| processes, project-management |
| Accessible Heading Structures for Home Pages (pop) | | 1473 |
| headings, homepages |
| WCAG, VPAT, S508, Level A—What on Earth? (int) | | 1472 |
| standards, legal, terminology, wcag, vpat-acr, section-508 |
| User “Wants” vs. Accessibility (tem) | | 1471 |
| usability |
| The Infuriating Inefficiency of Accessibility Audits (yat) | | 1470 |
| auditing, efficiency |
| What a New Accessibility Class Action Lawsuit Means for Agencies (acc) | | 1469 |
| legal, business-relations |
| Green Accessibility for Web Developers (umn) | | 1468 |
| videos, sustainability |
| Assessing Components and Patterns for WCAG 2.2 (mbg) | | 1467 |
| wcag, components, design-patterns |
| Getting to the Bottom of Minimum WCAG-Conformant Interactive Element Size (eri/sma) | | 1466 |
| design, wcag, css |
| How to Incorporate Accessibility Into Your Agile Sprints (mic) | | 1465 |
| how-tos, agile, processes, technical-debt |
| Alternative Text in Action (gov) | | 1464 |
| images, alt-text, writing, examples |
| To Hell With the Business Case, Again (mat) | | 1463 |
| economics |
| What ARIA Still Does Not Do (ste) | | 1462 |
| html, aria, standards |
| It’s Really This Thing That Gets Me (chr) | | 1461 |
| overlays |
| Going With the PDF Reflow (ons/tpg) | | 1460 |
| wcag, pdf |
| Rian Rietveld on Understanding the European Accessibility Act and Its Impact on Websites (ria+/wpt) | | 1459 |
| podcasts, interviews, legal, eaa, wordpress |
| How to Check and Document Design Accessibility in Your Mockups (ste) | | 1458 |
| how-tos, auditing, documentation, prototyping, design |
| A Quick-Ish Accessibility Review: shadcn/ui Charts (ash) | | 1457 |
| information-design, tooling, auditing, link-lists |
| Exploring the Challenges in Creating an Accessible Sortable List (Drag-and-Drop) (gas/git) | | 1456 |
| keyboard-navigation |
| Don’t Use web.dev for Accessibility Info (aar) | | 1455 |
| learning |
| How to Transform Your Approach to Digital Accessibility From a Reactive Break-Fix Cycle to a Proactive Shift Left Approach (a11/deq) | | 1454 |
| how-tos, processes, best-practices |
| A Practical Guide to Designing for Colorblind People (nam) | | 1453 |
| guides, design, colors, color-blindness |
| European Accessibility Act (EAA): Top 20 Key Questions Answered (deq) | | 1452 |
| legal, eaa |
| Dialog Dilemmas and Modal Mischief (hdv/hey) | | 1451 |
| videos, modals, pop-overs |
| Overlays Misunderstand Accessibility (joe) | | 1450 |
| overlays |
| Accessible Form Validation From Scratch—Preparing for Validation (dbe/uxd) | | 1449 |
| forms, validation |
