Frontend Dogma

“accessibility” Archive

(Need an explanation or context? Look for “accessibility” on WebGlossary.info.)

  1. Avoid Read-Only Controls (by) · · ,
  2. How to Use Lighthouse Wisely in Your Front-End Projects (by/via) · · , , , , , ,
  3. Alt Text: Not Always Needed (by/via) · · ,
  4. Accessibility Misinformation (by) · · ,
  5. Accessibility (by/via) · · , , ,
  6. My Anti-Overlay Client Letter (by) · · , , ,
  7. Unlocking Accessibility: Content Designers Share Their Experience and Advice (via) · · ,
  8. How to Test JavaScript for Accessibility Compliance (by/via) · · , , , ,
  9. Beautiful Focus Outlines (by) · · , ,
  10. The Only Accessibility Video You Will Ever Need (by) · ·
  11. JavaScript Do’s and Don’ts (by) · ·
  12. 25 Accessibility Tips to Celebrate 25 Years (by/via) · · , ,
  13. “Functionality” Is Not Constrained by Content (by/via) · · , ,
  14. Testing With a Screen Reader Is an Important Step (by) · · , , ,
  15. Reducing Digital Accessibility Litigation Risk (by) · · , ,
  16. PDF Accessibility on the Web: Tricks and Traps (by/via) · · ,
  17. Tooltip Best Practices (by/via) · ·
  18. Clarifying the Relationship Between Popovers and Dialogs (by/via) · · , , ,
  19. Naming Things Is Still a Common and Enduring Challenge in Accessibility (by) · ·
  20. Designing for Anyone: The Power of Accessible Products (by) · · ,
  21. Talkin’ Tables (by/via) · · , ,
  22. Accessibility for the Deaf / Hard of Hearing and Progress Over Perfection (by/via) · ·
  23. Improving Accessibility Through Design Systems (by/via) · · ,
  24. The Internet Is Unusable—the Disabled View (by/via) · · ,
  25. Six Things Not Related to Accessibility That Will Improve Your Disability Inclusion Efforts (by) · · , ,
  26. Making Accessibility Accessible (by) ·
  27. What’s New in WAI–ARIA 1.3 (by/via) · · ,
  28. Accessibility Challenges With Single Page Applications (via) · · ,
  29. Accessible Design: WCAG or Trendy? No, WCAG and Trendy! (by/via) · · , ,
  30. 10 Simple Ways to Make Your Social Media Posts Accessible (via) · · , , , ,
  31. Foundations: Form Validation and Error Messages (via) · · , , ,
  32. If You Care (by) ·
  33. Developing a Web Site Nonvisually in a Linux Environment (by) · · , , ,
  34. Tips for Inclusive and Accessible Hiring and Recruiting (by/via) · · , , , ,
  35. “aria-activedescendant” Is Not Focus (by) · · ,
  36. What Makes a Font Accessible? A Designer’s Guide (via) · · , , ,
  37. Understanding VPATs and ACRs: Key Insights (by) · ·
  38. Design Systems and How to Use Them in an Accessible Way (by/via) · · , ,
  39. The Elephant in the New Accessibility Law: PDFs (by) · · ,
  40. AI for Accessibility Conformance Testing? Why? (by) · · , ,
  41. The Value of Accessibility Annotations in Inclusive Design (by/via) · · ,
  42. Why GOV.UK’s “Exit This Page” Component Doesn’t Use the Escape Key (by) · · ,
  43. Shopify, Accessibility Lawsuits, and “Compliance” · · , ,
  44. No Industry for Old Men (by/via) · · , , , , , , ,
  45. Designing for Accessibility: Enhancing Math Learning for the Blind Using the NVDA Screen Reader · · , , , ,
  46. Reminder—Automatic Accessibility Testing Can Detect Inaccessibility but Can’t Detect Accessibility (by) · ·
  47. How a Bottom-Up Design Approach Enhances Site Accessibility (by/via) · · ,
  48. Practical Accessibility Tips You Can Apply Today (via) · · ,
  49. How to Identify a Toxic Accessibility Culture, and What You Can Do About It (by) · · ,
  50. “Straight to the Pool Room”: The Pitfalls of Placing Accessibility Issues in the Backlog (via) · · , ,
  51. JAWS (Only) No More (by) · · , , , , , , ,
  52. Celebrating WebAIM’s 25th Anniversary (by/via) · ·
  53. The State of Accessibility (by/via) · · , ,
  54. Making Maps Accessible to Screen Readers (via) · · , , ,
  55. Challenging the Case for Delayed ADA Compliance (by/via) · · , , ,
  56. Accessibility Is Everyone’s Responsibility (by) · · ,
  57. Your Accessibility Questions Answered by a Blind Person (via) ·
  58. A Step-by-Step Guide to Conducting a Web Accessibility Audit (via) · · , , ,
  59. Accessibility Preference Settings, Information Architecture, and Internalized Ableism (by) · · , ,
  60. Brief Note on Disclosures in Fieldsets (by) · · ,
  61. But Why?? (by) · · , , , , , ,
  62. Good Forms (by) · · , , ,
  63. Prioritize Accessibility in Procurement for Better CX and EX (by/via) · · ,
  64. The Folly of Chasing Demographics (by/via) · · ,
  65. Understanding the “Why” Around Neurodivergent Inclusive Web Design (by/via) · · ,
  66. Using Controllers for Keyboard Accessibility (by/via) · · ,
  67. How to Find the Accessible Name of a Button With Google Chrome (by) · · , , , , ,
  68. WCAG and Accessibility Beyond Naive Misconceptions (by) · · , ,
  69. Stop Recreating the Wheel: Local Government Organizations Sharing Accessibility Information (by/via) · · , , ,
  70. Mobile Accessibility Testing: Enhancing User Experience for All (by/via) · · , ,
  71. “display: contents” Is Not a CSS Reset (by) · · ,
  72. I Need an Accessible Hero (via) · ·
  73. Avoiding Accessibility Barriers With a Checklist for Custom Controls—Opinion (via) · ·
  74. Should Form Labels Be Wrapped or Separate? (by/via) · · , , ,
  75. Another Stab at Truncated Text (by/via) · · , ,
  76. Tackling a System’s Accessibility Without Testing (by+/via) · · , ,
  77. Be Careful When Using Generative Artificial Intelligence to Produce Code (by) · · ,
  78. Headings (via) · · ,
  79. An Enhancement to Accessible Responsive Tables (by) · · , ,
  80. Harnessing Copilot and Other Gen-AI Tools to Increase Digital Accessibility Efficiency (by) · · , , , ,
  81. What the Heck Is ARIA? A Beginner’s Guide to ARIA for Accessibility (by/via) · · , , ,
  82. Paragraphs (by) · ·
  83. Building Better Logins: A UX and Accessibility Guide for Developers (via) · · ,
  84. The “aside” Element (by) · · ,
  85. Make Me One (Input) With Everything (by/via) · · , ,
  86. Why Is Reaching WCAG Level AAA Not Recommended? (by) · · ,
  87. WCAG’s A and AA Distinction Is Mostly Academic (by) · · ,
  88. Is Using “aria-label” to Add Alternative Text But No “alt” Attribute Still a WCAG Fail? · · , , , ,
  89. Improving the Screen Reader Experience for “Learn WCs” (by) · · , , , , , ,
  90. Spoiler Alert: It Needs to Be Accessible (by) · · , ,
  91. Foundations: Labelling Text Fields With Input and Label (via) · · ,
  92. Understanding WCAG 2.1’s Success Criteria 1.4.10 Reflow (via) · · , ,
  93. Basic Keyboard Shortcut Support for Focused Links (by) · · , , , ,
  94. Batteries Included Accessibility: A Pragmatic Guide to Get Started Today (by+/via) · · , ,
  95. Accessibility Specialists Warn Against Using AI for Alt Text (by/via) · · , ,
  96. The “Other” C in CSS (by/via) · · ,
  97. How Can Accessibility Improve Your Conversion Rate Optimization Efforts? (by) · · , , ,
  98. WCAG 2.2 Summary and Breakdown (by) · · , ,
  99. 80/20 Accessibility (by) · ·
  100. Designing for Accessibility: A Checklist for Designers (by/via) · · ,
  101. Alternatives to Using Pure Black (“#000000”) for Text and Backgrounds (by/via) · · , ,
  102. Captions vs. Subtitles: Leave No Viewer Behind (by) · · , , ,
  103. Writing Alt Text for a Scientific Figure (by) · · , ,
  104. Context Is King: Long Live the King! (by/via) · · , ,
  105. The Importance of Communication in Accessibility Testing (via) · · ,
  106. Things to Do Before Asking “Is This Accessible?” (by) · · ,
  107. The Most Important Thing to Look at When Choosing an Accessibility Auditor (by/via) · · ,
  108. Design Patterns and WCAG (by/via) · · ,
  109. Good Intentions, Poor Context (via) · · , , ,
  110. When It Comes to Digital Accessibility Lawsuits, the Best Defense Is a Good Offense (via) · ·
  111. WCAG 2.2 Map by Theme (by) · · ,
  112. The “abbr” Element (by) · · ,
  113. Disability Data Alarmingly Absent From AI Algorithmic Tools, Report Suggests (via) · · ,
  114. Let’s Make a Simpler, More Accessible Web (by) · · , , , , ,
  115. European Accessibility Act Requires Culture to Shift! (by) · · , ,
  116. AT Is More Than Screen Readers (by) · · , , , ,
  117. Attitudes to Digital Accessibility 2024 (via) · ·
  118. Types of Accessibility Approaches (by) · · , ,
  119. How to Make the Internet More Accessible (by+/via) · · ,
  120. The Anatomy of Accessible Forms: Best Practices (via) · · , ,
  121. Interop 2024: Chrome at 100% for the Accessibility Focus Area (via) · · , , ,
  122. Decoding WCAG: “Change of Context” and “Change of Content” (via) · · ,
  123. Developing a RACI Matrix for Accessibility (by/via) · · ,
  124. WCAG, VPAT, S508, Level A—What on Earth? (via) · · , , , , ,
  125. Accessible Heading Structures for Home Pages (via) · · ,
  126. User “Wants” vs. Accessibility (by) · ·
  127. The Infuriating Inefficiency of Accessibility Audits (by) · · ,
  128. What a New Accessibility Class Action Lawsuit Means for Agencies (via) · · ,
  129. Green Accessibility for Web Developers (via) · · ,
  130. Assessing Components and Patterns for WCAG 2.2 (by) · · , ,
  131. Getting to the Bottom of Minimum WCAG-Conformant Interactive Element Size (by/via) · · , ,
  132. How to Incorporate Accessibility Into Your Agile Sprints (by) · · , , ,
  133. Alternative Text in Action (via) · · , , ,
  134. What ARIA Still Does Not Do (by) · · , ,
  135. To Hell With the Business Case, Again (by) · ·
  136. It’s Really This Thing That Gets Me (by) · ·
  137. Going With the PDF Reflow (by/via) · · ,
  138. Rian Rietveld on Understanding the European Accessibility Act and Its Impact on Websites (by+/via) · · , , ,
  139. How to Check and Document Design Accessibility in Your Mockups (by) · · , , , ,
  140. Exploring the Challenges in Creating an Accessible Sortable List (Drag-and-Drop) (by/via) · ·
  141. Don’t Use web.dev for Accessibility Info (by) · ·
  142. A Quick-Ish Accessibility Review: shadcn/ui Charts (by) · · , , ,
  143. How to Transform Your Approach to Digital Accessibility From a Reactive Break-Fix Cycle to a Proactive Shift Left Approach (by/via) · · , ,
  144. A Practical Guide to Designing for Colorblind People (by) · · , , ,
  145. European Accessibility Act (EAA): Top 20 Key Questions Answered (via) · ·
  146. Dialog Dilemmas and Modal Mischief (by/via) · · , ,
  147. Accessible Form Validation From Scratch—Preparing for Validation (by/via) · · ,
  148. Overlays Misunderstand Accessibility (by) · ·
  149. Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT) (by/via) · · ,
  150. Feedback on a Pagination Pattern (by) · ·
  151. European Accessibility Act (EAA)—What You Need to Know (by/via) · ·
  152. Accessible PDF Forms Online—There’s a Catch (by/via) · · ,
  153. 7 Ways to Champion Accessibility in Your Company (by) · ·
  154. A Proposal for MDN to Use the APG (by) · ·
  155. Accessibility Object Model (by+/via) ·
  156. The State of Digital Accessibility in Europe (via) · · ,
  157. How to Make a Strong Case for Accessibility (by/via) · · , ,
  158. Two New Artificial Intelligence Laws and Their Effects on Accessibility (via) · · ,
  159. Why Is It So Difficult to Give Best in Class Accessibility Examples of Websites? (by) ·
  160. In Detail: 1.4.11 Non-Text Contrast (User Interface Components) (by) · · , , ,
  161. Design Extremes of Custom Accessibility Actions (via) · · ,
  162. A Brief Introduction to Keyboard Accessibility (by/via) · · , ,
  163. What Does “aria-hidden=true” Actually Do to Interactive Elements? (by) · · , , ,
  164. How to Create Truly Accessible Forms (by/via) · · , ,
  165. The European Accessibility Act and Irish Law (via) · ·
  166. How to Browse the Web With the Keyboard Alone (by) · · ,
  167. Can ADA Title II Local Government Accessibility Be Efficient? A Response to Richard Hunt (via) · ·
  168. Support for “aria-errormessage” Is Getting Better, but Still Not There Yet (by) · · , , , ,
  169. How to Use “rem” Units in CSS for Accessible Design (by/via) · · , ,
  170. The Ultimate Guide to Accessible Website Design · · ,
  171. Improving Web Accessibility With Web Platform Tests (via) · · ,
  172. Maybe Don’t Name That Landmark (by) · · ,
  173. Doing My Heading In (by+) · · , ,
  174. The Unclear Case of Usability Widgets on Your Website (by) · · , ,
  175. What’s Wrong With VPATs? (by) · ·
  176. Semantic Code in HTML: What Is It and Does It Still Matter? (by) · · , , , ,
  177. World Wide Accessibility—Benefits of Standardization (by) · · , ,
  178. Applying the Four Principles of Accessibility (by) · · ,
  179. Creating an Accessible Toggle Switch in Tailwind CSS (by/via) · · ,
  180. Typographer vs. Accessibility (by/via) · · ,
  181. My Approach to Alt Text (by) · · , ,
  182. Alt Left (by) · · , ,
  183. A Complete Guide for Adding Captions to YouTube Videos (via) · · , , ,
  184. Predictors of Postsecondary Web Accessibility, 2012 to 2022 (by+/via) · · ,
  185. Two Important AI Developments Affecting Accessibility (via) · · ,
  186. What AI Can Do for (and to) Web Accessibility (by+/via) · · ,
  187. Why Are There No Mobile Accessibility Guidelines in WCAG? (via) · · ,
  188. Not So Short Note on “aria-label” Usage—Big Table Edition (by) · · ,
  189. DOJ ADA Title II: Small Government WCAG Accessibility Guide (via) · · , ,
  190. Danger! Preventing Zoom From Changing Text Size (by/via) · · ,
  191. “contrast-color()” Is a Good Thing, but Also Solving the Problem at the Wrong Layer (by) · · , , ,
  192. WAI–ARIA: “role=deletion” (by) · ·
  193. WAI–ARIA: “role=strong” (by) · ·
  194. W3C Unveils 174 New Outcomes for WCAG 3.0 (by/via) · · , ,
  195. The WCAG 3 Working Draft Update Is Ready for Your Review (by/via) · · ,
  196. Rethinking Text Resizing on Web (by/via) · ·
  197. ADA Title II and You (via) · · ,
  198. Dark Mode and Accessibility Myth (by) · · ,
  199. I’m Worried About the Tabbing Behaviour, Rather Than the Syntax and Name of CSS Masonry (by/via) · · , , ,
  200. Understanding the Role of ARIA “role=alert”: Best Practices and Common Issues (by) · · ,
  201. Regarding Keyboard Testing (via) · · ,
  202. Intopia’s WCAG 2.2 Maps (by/via) · · ,
  203. Accessible SVG Forms (by) · · , ,
  204. Quick Incremental Accessibility Audits for Small Business Websites (by) · ·
  205. All I Want for GAAD (via) · · ,
  206. Digital Inaccessibility: Blind and Low-Vision People Have Powerful Technology but Still Face Barriers to the Digital World (via) ·
  207. Best Intention Barriers (ARIA Edition) (by) · · ,
  208. Accessibility Overlays Are Not for Disabled People (by) · ·
  209. Manifesto for a Humane Web (by) · · , , , , ,
  210. Level-Setting Heading Levels (by) · · , , ,
  211. Transparent Borders (by) · · , , ,
  212. How We’re Building More Inclusive and Accessible Components at GitHub (by/via) · · , , ,
  213. Focus vs. Accessibility Focus (via) · · ,
  214. Mastering User-Centered Design, With 5 Advanced Tips (via) · · , , ,
  215. Inclusive Digital Experiences: Redesign Strategies for Addressing Diverse Abilities and Accessibility Challenges II (via) · · , ,
  216. An Introduction to the European Accessibility Act (EAA) (via) · · ,
  217. A Brief Note on Highlighted Text (by) · · , , ,
  218. WCAG After Quarter of a Century—We Still Need More Awareness (by) · · ,
  219. The Value of Open Source in Furthering Accessibility Goals (by/via) · · ,
  220. A to Z of Assistive Technology for Reading Digital Text (by) · · , , ,
  221. Quick-and-Dirty Accessibility (via) · ·
  222. Why Are My Live Regions Not Working? (by/via) · · ,
  223. Web Forms: Costly Mistakes You Want to Avoid (by) · · , , , ,
  224. Web Accessibility in the 2024 [U.S.] Presidential Campaigns (via) · ·
  225. How to Design Accessible Forms in 10 Steps (by/via) · · , ,
  226. Accessibility Evolution of Organizations (by) · · ,
  227. Introduction to Manual Website Accessibility Testing (via) · · , ,
  228. Conducting Accessibility Research in an Inaccessible Ecosystem (by/via) · · , ,
  229. Images as the First Thing in a Button or Link (by) · · , , ,
  230. Write Alt Text Like You’re Talking to a Friend (by/via) · ·
  231. Make Sure That Your Design System Is Accessible (by) · ·
  232. Long Alt (by) · · , , , ,
  233. Building a Culture of Accessibility (by/via) · ·
  234. Accessibility Overlays—Friend or Foe? (by/via) · · ,
  235. When Security and Accessibility Clash: Why Are Banking Applications So Inaccessible? (by) · ·
  236. The Impact of Color Contrast on Accessibility (via) · · ,
  237. ARIA in HTML (by+/via) · · , ,
  238. 10 Top Accessibility Errors and How to Avoid and Fix Them (by) ·
  239. Beware—Automatic Tools Over-Report Accessibility Issues and Steal Your Time (by) · · ,
  240. My “Skip to Content” Markup Was Breaking the Back Button on iOS (by) · · , ,
  241. 9 Signs Your Frontend Code Has Quality Issues That Affect Your Users (by) · · , , , , ,
  242. The Dos and Don’ts of Using “tabindex” in Web Design (by/via) · · ,
  243. Accessible Interactions in JavaScript Apps (by/via) · · , ,
  244. Web Accessibility Statement: How to Write One (via) · · ,
  245. Socks, Lies, and Accessibility (by) · · ,
  246. Purging Design System “Rot” From Our Checkboxes (by/via) · · , , ,
  247. Complete a VPAT: Show How Accessible Your Product Is (via) · · , ,
  248. A Comparison of Automated Testing Tools for Digital Accessibility (via) · · , , ,
  249. I Never Knew a Website Could Hurt Someone (by/via) · ·
  250. The ADA Now Has Regulations for Accessibility of Web Content and Mobile Apps (by/via) · · , ,