Frontend Dogma

“accessibility” Archive

Supertopics: · subtopics: , , , , , ,  (non-exhaustive) · glossary look-up: “accessibility”

Featured on Frontend Dogma? Confirm and whitelist your domain.

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