Frontend Dogma

“accessibility” Archive (3)

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

  1. What Makes an Accessible Date Picker? Is It Even Possible? (by/via) · · ,
  2. Building a Core Accessibility Team: The Keys to the Kingdom (by/via) · · ,
  3. What an Economist Article Says About Website Accessibility and Lawsuits (by/via) · ·
  4. First Steps to an Accessible Website—Skip Links (via) · ·
  5. How to Make a Strong Case for Accessibility (by/via) · · ,
  6. Expanding Your Touch Targets (by) · · ,
  7. Accessibility and Inclusivity: Study Guide (by/via) · · , , ,
  8. Whataboutism (by) ·
  9. State of Web Accessibility, ARIA in HTML, and Missing UI Patterns (by+/via) · · , ,
  10. Web Components Accessibility FAQ (by) · ·
  11. Is AI the Silver Bullet of Accessibility? (via) · ·
  12. The Perpetual Circle of Accessibility (by) · ·
  13. First, Do No Harm: Mistakes to Avoid in Creating Accessible User Experiences (via) · · ,
  14. Equivalent Experience Can Cut Both Ways (by) · ·
  15. Browser Video Players Review (by) · · , , , , ,
  16. How to Make Charts and Graphs More Accessible (via) · · , ,
  17. Decoding WCAG: “Alternative for Time-Based Media” and “Media Alternative for Text” (by/via) · · ,
  18. Accessibility Theater (via) ·
  19. What Is Inclusion Anyways? Lessons From the Disabled Community · · , ,
  20. Building Accessibility Into Your Company, Team, and Culture (by/via) · · ,
  21. Navigating Web Accessibility Litigation: Advice From a General Counsel (via) · ·
  22. How I Write Alt Text for Code Snippets on Social Media (by) · · , ,
  23. Dark Mode: How Users Think About It and Issues to Avoid (by/via) · · , ,
  24. Accessible Navigation (by) · ·
  25. Where to Put Focus When Deleting a Thing (by) · ·
  26. What Are Exceptions to Section 508 Accessibility Requirements? (via) · · ,
  27. What Is Alt Text and How to Write It (via) · · ,
  28. Main-ly Speaking (by) · ·
  29. European Accessibility Act: Article 32, and Why It Sucks (by) · ·
  30. How to Get 12% More LinkedIn Followers, Impressions, and Clicks—Practical Accessibility Tips and Tricks (by/via) · · , , ,
  31. How Organisations Respond to Accessibility Monitoring (via) · ·
  32. “We’re All Just Temporarily Abled” (by) ·
  33. Being “Polite” Does Not Ensure Access (via) · ·
  34. Tabs Are Objectively Better Than Spaces (by) · · ,
  35. Accessibility Is Not Inclusive Design or Disability Rights—It’s a Part of It (by) · · ,
  36. Beginner’s Guide to Lists and How to Make Them Accessible (via) · · ,
  37. Useable (by) · ·
  38. An “alt” Decision Tree Using Only “:has()” (by) · · ,
  39. Designing Accessible Text Over Images: Best Practices, Techniques, and Resources II (by/via) · · , , ,
  40. OKLCH in CSS: Consistent, Accessible Color Palettes (by/via) · · , , ,
  41. WCAG 3.0: Further on Up the Road (by/via) · · ,
  42. Progressively Enhanced HTML Accordion (by) · · , ,
  43. 8 Common Heading Questions (via) · · ,
  44. Alt Text Hall of Fame (by/via) · · , ,
  45. Assistive Technology Shouldn’t Be a Mystery Box (by) · · , , , ,
  46. The Easy Intro to the APCA Contrast Method (by) · · , , ,
  47. Designing Accessible Text Over Images: Best Practices, Techniques, and Resources (by/via) · · , , ,
  48. How Does Reflowing Content Affect People With Screen Magnification? (via) · · , ,
  49. New DOJ Web Accessibility Regulation Is a Disaster (via) · ·
  50. Contextual Form Errors and ARIA (by) · · , ,
  51. CSS and Accessibility: Inclusion Through User Choice (by/via) · · , ,
  52. Accessibility of the Button: Should We Fix It or the Root Cause Problem? (via) · · ,
  53. What Happens When Developers Are Liable for Accessibility? (via) · ·
  54. The Curious Case of “iff” and Overriding Screenreader Pronunciations (by) · · , , ,
  55. Contrast Checker Bookmarklet (via) · · , ,
  56. Accessibility Represents Maturity (by) · ·
  57. Do We Need WCAG 3 (Now)? (by) · · ,
  58. How to Make Your Captions and Audio Descriptions WCAG-Compliant (via) · · , , , ,
  59. Testing a Component’s Accessibility (via) · · , ,
  60. Be an Active Ally for Those Living With Disabilities (via) · ·
  61. Solving the Accessibility Palette Riddle (by/via) · · ,
  62. Web Accessibility in High-Risk Segments (by) · · ,
  63. Blockquotes in Screen Readers (by) · · , , , ,
  64. Understanding the WCAG 3 Working Draft Update (by) · ·
  65. The Problem With Auto-Generated Alternative Texts for Images (by) · · ,
  66. Accessible Animated GIF Alternatives (by/via) · · , , ,
  67. Web Content Accessibility Guidelines (WCAG) 2.2 (by+/via) · · , ,
  68. We Deleted More Than 5,000 Pages From Our College Website—Here’s Why (by/via) · · ,
  69. Visually Hidden Links With 0 Dimensions (by) · · , , ,
  70. Getting Instant Return From Your Accessibility Testing (by) · ·
  71. O “dialog” Focus, Where Art Thou? (by) · · , ,
  72. React-ing to Accessibility: Building Accessible Forms That Everyone Can Use (by/via) · · , ,
  73. Interoperability With Specific Assistive Technologies or: “Does the Website Work on JAWS?” (by) · · , , , ,
  74. A Roadmap to Leadership Inclusion: 15 Keys to Unlocking a Diverse and Empowered Workplace II (by) · · ,
  75. Top 20 Must-Know Tips for Web Accessibility · ·
  76. The alt-text.org Project Is Moving Forward (by) · ·
  77. Making Numbers in Web Content Accessible (by/via) ·
  78. Getting Started—Understanding the History of Web Accessibility (by/via) · · , ,
  79. Developing Inclusivity Features (via) · · ,
  80. ARIA Can Hurt or Help Web Accessibility: How to Review Your Website’s ARIA (via) · · , ,
  81. There’s No Such Thing as a “Normal” User (by) ·
  82. A Roadmap to Leadership Inclusion: 15 Keys to Unlocking a Diverse and Empowered Workplace (by) · · ,
  83. Resources for Procurement of Accessible Digital Products and VPAT (by/via) · · , , ,
  84. The “article” Element and Screen Readers (by) · · , , , ,
  85. Your Browser May Be Having a Secret Relationship With a Screen Reader (via) · · , ,
  86. Accessible Overlays Aren’t Accessible (via) · ·
  87. WCAG 2.2, Quick and Simplified (by) · · ,
  88. Under-Engineered Comboboxen? (by) · · , ,
  89. Combat Accessibility Decay: How to Maintain Ongoing Accessibility (via) · · ,
  90. Web and App ADA Lawsuits: 6 Trends So Far in 2023 (via) · · ,
  91. 4 Ways to Improve Mobile Accessibility (by) · ·
  92. Screen Magnification: Digital Accessibilitiy (via) · · , ,
  93. Top Tips From a Web Accessibility Evaluator at WebAIM (by/via) · · ,
  94. Magnification and Zoom Accessibility Guide—Everything You Need to Know (via) · · , ,
  95. Live Regions in React (by) · · , ,
  96. Designing for Inclusion (by/via) · · ,
  97. WCAG 2.2 Removes 4.1.1 Parsing and How axe-core Is Impacted (by/via) · · , ,
  98. Three Key Principles for an Accessible Website (by+/via) · ·
  99. Thoughts From “Meet Safari for Spatial Computing” (by) · · , , ,
  100. Continuous Accessibility (by) · · ,
  101. Can Web Developers Be Held Liable? (via) · ·
  102. The Five Types of People Who Produce Inaccessible Code (by) · ·
  103. 6 Quick Tests You Can Do to Test Your Forms for Accessibility (by) · · ,
  104. Design vs. Accessibility and the CSS “visually-hidden” Class (by/via) · · , ,
  105. You Can Stop Using “user-scalable=no” and “maximum-scale=1” in Viewport Meta Tags Now (by) · · , ,
  106. Sticky Content: Focus in View (by/via) · · , ,
  107. The Universal Focus State (by) · · ,
  108. No, “AI” Will Not Fix Accessibility (by) · ·
  109. Testing Sites and Apps With Blind Users: A Cheat Sheet (by+/via) · · , , , , ,
  110. Before Your Next Frontend Pull Request, Use This Checklist (by+/via) · · , , , , ,
  111. Assume the Position—a Labelling Story (by/via) · · ,
  112. Accessible Rich Internet Applications (WAI–ARIA) 1.2 (via) · · ,
  113. Accessibility and Artificial Intelligence (by) · ·
  114. Accessibility Testing—Pay Attention to the Details (via) · ·
  115. The Problem With Automatically Focusing the First Input and What to Do Instead (by) · · , ,
  116. How We Created an Accessible, Scalable Color Palette · · , , ,
  117. WCAG 2.2 Misses Mark on Defining Visible Focus (by) · · , ,
  118. Accessible Components: The Hamburger Menu · · ,
  119. Accessibility Audits for All (by) · · ,
  120. Don’t Meddle With User Input (by) · ·
  121. The Problem With Nested Fieldsets and How to Avoid Them (by) · · , ,
  122. How Screen-Reader Users Type on and Control Mobile Devices (by/via) · · , , , ,
  123. When to Use Plain Text or Images Instead of MathML (via) · · ,
  124. We Need to Talk About How We Talk About Accessibility (by+/via) · · ,
  125. Brief Note on Popovers With Dialogs (by) · · , , ,
  126. Levelling Up Accessibility Skills in Your Organisation (by+/via) · ·
  127. “display: contents” Considered Harmful (by) · ·
  128. Reading a Voluntary Product Accessibility Template (VPAT) or Accessibility Conformance Report (ACR) (by/via) · · ,
  129. Addressing Timeout Modals: Navigating the Nuances for Inclusive Web Design (by/via) · · ,
  130. A Beginners Guide to Digital Accessibility (by) · ·
  131. What Devs Can Do on Global Accessibility Awareness Day (by) · ·
  132. Are We There Yet? WCAG 2.2 Is at the Candidate Recommendation [Stage] v3 (by/via) · · ,
  133. Accessible Numbers (by) · ·
  134. Fieldsets, Legends, and Screen Readers Again (by/via) · · , , , ,
  135. Why Is Web Accessibility Important? (by/via) · ·
  136. Semantics and the “popover” Attribute: What to Use When? (by) · · , ,
  137. Using HTML Landmark Roles to Improve Accessibility (by/via) · ·
  138. HTML Landmark Roles Screen Reader Demo (by/via) · · , , , ,
  139. The Problem With Disabled Buttons and What to Do Instead (by) · · ,
  140. Screen Readers Don’t Announce When the User Reaches the “maxlength” Character Limit (by/via) · · , , , ,
  141. Respect Your Children (by/via) · · ,
  142. ShatGPT (by) · ·
  143. React Testing Library and Accessibility (by) · · , , ,
  144. Digital Accessibility Is a Bigger Education Issue Than We Think—Here’s What We Can Do About It (by/via) · ·
  145. Why “font-size” Must Never Be in Pixels (by) · · , ,
  146. Short Note: Why Isn’t “role=presentation”/“none” Allowed on Focusable Elements? (by) · · , ,
  147. Progress Over Perfection: The Better Way for Communication and Accessibility Advocacy (by) · · , ,
  148. Accessible Target Sizes Cheatsheet (by/via) · ·
  149. The Potentially Dangerous Non-Accessibility of Cookie Notices (by/via) · · , , ,
  150. Meeting WCAG Level AAA (by/via) · · , ,
  151. Designing and Coding for Voice (by) · ·
  152. Visually Accessible Data Visualization (by/via) · ·
  153. Audio Accessibility in Miro: A Hackathon Story in 3 Acts (by/via) · · ,
  154. Answering “What ARIA Can I Use?” (by/via) · · , , , ,
  155. Web Accessibility: A Reference to Creating Inclusive Websites (via) ·
  156. Breaking Down Accessibility Barriers: Top 4 Challenges With Screen Magnifiers (by/via) · · ,
  157. Shifting Left, or: Making Accessibility Easier by Doing It Earlier (by) · · , ,
  158. HTML Accessibility API Mappings 1.0 (by+/via) · · ,
  159. Don’t Override Screen Reader Pronunciation (by) · · , , ,
  160. Accessibility in Design Systems: Building More Inclusive Products for a Better User Experience (via) · · , , ,
  161. Chasing Rainbows (by/via) · · , ,
  162. Establishing Metrics for Accessibility ROI (by) · · ,
  163. Foundations: Accessible Names and Descriptions (by/via) · · , ,
  164. What’s New in WCAG 2.2? (by/via) · · ,
  165. The Alt Text War—SEO vs. Accessibility (by/via) · · , , ,
  166. Designing for Reduced Motion (by/via) · ·
  167. What Makes a Good Screenshot? (by/via) · ·
  168. Five Pieces of Advice for More Accessible Websites (by) · ·
  169. Exposing Field Errors (by) · · , , ,
  170. Accessibility for Designers: Where Do I Start? (by) · · ,
  171. When I Get That Low Contrast Feeling, I Need Non-Textual Healing (by/via) · · ,
  172. 10 Ways to Hide Elements in CSS (by/via) · · ,
  173. We Need Accessibility Action (by) · ·
  174. The Ultimate Guide to Automatic Accessibility Testing in CI/CD for React Apps · · , , , ,
  175. Alternative Text in the Wild: 5 Alternative Text Examples (via) · · ,
  176. The WebAIM Million (via) · · , ,
  177. Accessibility vs. Emojis (via) · · , ,
  178. Guardrails for Better Accessibility Support in Frontend (by) · · ,
  179. Connecting Dots of an Accessibility Audit (by/via) · ·
  180. A Quick Guide to Reviewing a VPAT ACR (by) · · , ,
  181. CSS-Only Widgets Are Inaccessible (by) · ·
  182. The “search” Element (by) · · ,
  183. What We’ve Learned About Designing for Accessibility From Our Users (by/via) · ·
  184. Accessible but Never Boring: Rebranding the Wise Design System for Everyone II (by/via) · · ,
  185. Certifications Should Be Hard (by) · · ,
  186. When Is “:focus-visible” Visible? (by) · · ,
  187. Visually Hidden Content Is a Hack That Needs to Be Resolved, Not Enshrined (by) · · , , ,
  188. Annotating Designs for Accessibility (by/via) · · ,
  189. Foundations: Pointer Gestures (by/via) · ·
  190. How Screen Readers Read Special Characters: An Update (by/via) · · , , , ,
  191. Hijacking Screenreaders With CSS (by/via) · · , , , ,
  192. It’s About Time CAPTCHAs Become Accessible (via) · ·
  193. Accessibility and Design Systems: The Deep-Dive Q&A (by+/via) · · , ,
  194. Accessibility Beyond Code Compliance (by) · ·
  195. The H1 Conundrum: Understanding the Challenges of Heading Level One (by/via) · · , ,
  196. Fix Color Contrast—Web Accessibility for Text and UI Design (by) · · ,
  197. Best Practices for Structuring Accessibility Testing (by/via) · · ,
  198. Making Calendars With Accessibility and Internationalization in Mind (by/via) · · ,
  199. We Don’t Need “.visually-hidden” (by/via) · · , ,
  200. “content” Is Your Content? (by/via) · · , , ,
  201. My Ideal Accessible Components Resource Is Holistic, Well Tested and Easy to Use (by) · ·
  202. ARIA Live Regions for JavaScript Frameworks (by/via) · · , , ,
  203. 50.1% Empty Links (by) · · , , ,
  204. Client-Side JavaScript and React Criticism: What Comes Next? (by) · · , , , ,
  205. Toolkit Tuesday: Using YouTube for Captions and Transcripts (via) · · , ,
  206. Are You Making These Five Mistakes When Writing Alt Text? (by/via) · · , ,
  207. The WebAIM Strategic Accessibility Framework (via) · ·
  208. The Web Needs a Native “.visually-hidden” (by) · ·
  209. Accessible but Never Boring: Rebranding the Wise Design System for Everyone (by/via) · · ,
  210. A Native “Visually Hidden” in CSS? Yes Please! (by/via) · · , , ,
  211. A Beginner’s Guide to Manual Accessibility Testing (via) · · ,
  212. How People Read Online (by/via) · · , ,
  213. Without Accessibility, There Is No Privacy or Security (via) · · ,
  214. Conformance and Accessibility (by) · · ,
  215. A Guide to Accessible Form Validation (by/via) · · , , ,
  216. How to Style Your Alt Text (by) · · , ,
  217. Successful Teams Ensure 100% of Their Members Understand Keyboard Accessibility (via) ·
  218. The Importance of Adding Accessibility Design Reviews to the Design Process (by/via) · · ,
  219. Open Captions vs. Closed Captions: What’s the Difference? (via) · · ,
  220. How Shadow DOM and Accessibility Are in Conflict (by/via) · · ,
  221. Automatic Captions: Our Experiments and Best Practices (via) · · , ,
  222. Understanding the Cost of Not Being Accessible (by) · ·
  223. Not Everyone Uses a Computer in the Same Way That You Do (by/via) · ·
  224. ARIA vs. HTML (by) · · , , ,
  225. Keys to an Accessibility Mindset (by/via) · ·
  226. Ideas for Making Accessibility and Equity a Core Part of the Software Development Lifecycle (by) · · ,
  227. Avoid Spanning Table Headers (by) · · , ,
  228. Software Accessibility for Users With Attention Deficit Disorder (ADHD) (via) ·
  229. If You’re Going to Do a Job, Do It Properly (by) · ·
  230. A Step-by-Step Guide to Building Accessible Carousels (by/via) · · , , ,
  231. Screen Readers Don’t Convey the Semantics of “strong” and “em” (by) · · , , , ,
  232. Scaling Accessibility Through Design Systems (by+/via) · · , ,
  233. Buttons, Links, and Focus (by) · · , , ,
  234. A Practical Approach to Automated Accessibility (by) · · ,
  235. Automation Is Not the Enemy (by) · · ,
  236. Automated Testing Won’t Solve Web Accessibility (by) · · ,
  237. Foundations: Introduction to WAI–ARIA (by/via) · · ,
  238. The Troublesome Life and Lamentable Death of Success Criterion 4.1.1 · · , ,
  239. Testing Colour Accessibility With Dev Tools (by/via) · · , , ,
  240. How to Build Accessible Main Navigation? (by/via) · · ,
  241. Focus Appearance Thoughts (by) · · ,
  242. Non-Text Content Contrast Also Matters (by) · · ,
  243. WCAG 2.2 Update: It’s Time to Say Goodbye to the Parsing Criterion (by) · · ,
  244. Understanding Color and Accessibility (by) · ·
  245. Setting Expectations for Asking ChatGPT Web Accessibility Questions (by) · ·
  246. External Links: In or Out (by/via) · · , ,
  247. Léonie Watson on Accessibility (by+/via) · · ,
  248. New WCAG 2.2 Features Rated (by) · · ,
  249. Accessible Hamburger Buttons Without JavaScript · · ,
  250. Use the Dialog Element (Reasonably) (by) · · ,