Frontend Dogma

“accessibility” Archive (2)

  1. Lost in Translation: Tips for Multilingual Web Accessibility (by) · · , ,
  2. Creating Accessible UI Animations (via) · ·
  3. Understanding HTML Landmarks and How to Apply Them (by/via) · · , ,
  4. Front End Devs Really Don’t Understand Accessibility (by) · ·
  5. How Long Until Your Website Is Accessible? (by) · ·
  6. Creating Accessible Content in Drupal 10 (by/via) · · ,
  7. Accessibility Training Will Not Save You (by) · · , ,
  8. Addressing Accessibility Concerns With Using Fluid Type (by/via) · · ,
  9. Removing List Styles Without Affecting Semantics (by) · · , ,
  10. To Hell With the Business Case (by) · · ,
  11. WCAG 2.2 Will Be a Part of EN 301 549 and With That a Part of WAD and EAA (by) · · , ,
  12. Totally Remdom, or How Browsers Zoom Text (by) · · , ,
  13. An Accessibility Bookmarklet for Testing 200% Text Size (by) · · ,
  14. Don’t Turn a Table Into an ARIA Grid Just for a Clickable Row (by) · · , ,
  15. How to Write Good Alt Text for Screen Readers (by) · · , , , ,
  16. Can AI Help Boost Accessibility? These Researchers Tested It for Themselves (via) · · ,
  17. Answers to Common (Web) Accessibility Questions (by) ·
  18. Getting Started With NVDA (via) · · , , , ,
  19. The “prefers-reduced-transparency” Media Feature (by) · · ,
  20. Accessibility by Degrees (by) · ·
  21. Don’t Disable Buttons (by) · · ,
  22. Let’s Reinvent the Wheel (by) · · , , ,
  23. So You’ve Been Publicly Accessibility-Shamed (by) · · ,
  24. What Does the “A” Mean in “DEAI”? (via) · ·
  25. Understanding SC 2.4.11 “Focus Not Obscured (Minimum)” (by/via) · · ,
  26. Give Your Site Some Focus! Tips for Designing Useful and Usable Focus Indicators (via) · · , , ,
  27. Color Contrast Accessibility Tools With Examples (via) · · , , , ,
  28. Splitting Within Selects (by) · · , , ,
  29. Accessibility Improvements for User-Agents (by) · ·
  30. Strikethrough Accessibility (by/via) · · , , , ,
  31. Embedding Accessibility Into Code Reviews (via) · · , ,
  32. What Should Be the Contrast Level of Inactive Buttons? (via) · · , ,
  33. Is CAPTCHA Accessible? (via) · ·
  34. Why Unique ID Attributes Matter (via) · · ,
  35. Web Accessibility Strategies for Non-Accessible Projects (by/via) · · , ,
  36. Does the HTML “hr” (Horizontal Rule) Benefit Screen Reader Users? (by/via) · · , , ,
  37. Burn Your Toast (by) · · ,
  38. Ensuring Negative Numbers Are Available for Everyone (by+/via) · · ,
  39. 2.4.11: Adversarial Conformance (by) · · ,
  40. Digital Accessibility Blogs and Newsletters (by/via) · ·
  41. Scrollbars Are Becoming a Problem (by) · · ,
  42. Honor User’s Transparency Setting in CSS (by) · · ,
  43. Skip Links on ikea.com (by) · · ,
  44. Designing for All: The Basic Principles of Web Accessibility (via) · · , , ,
  45. Inclusivity in the Digital Age: The Importance of Accessibility Advocacy (via) · · , ,
  46. Obligatory WCAG 2.2 Launch Post (by) · · ,
  47. Don’t Use Fixed CSS “height” or “width” on Buttons, Links, or Any Other Text Containers (by) · · , , ,
  48. Welcome WCAG 2.2 and Goodbye Success Criterion 4.1.1 “Parsing” (by) · · ,
  49. The Nonvisual Website (by) · ·
  50. Writing Accessible Form Messages (by) · · ,
  51. WCAG 2.2 and Validation (by) · · , ,
  52. Demystifying WCAG 2.2 (by/via) · · ,
  53. WCAG 2.2 Is Now a Published Web Standard (by) · · , ,
  54. Web Content Accessibility Guidelines (WCAG) 2.2 (by+/via) · · , ,
  55. WCAG 2.2 Is Now a W3C Recommendation (by) · · ,
  56. Intopia Launches WCAG 2.2 Map (by/via) · · ,
  57. What’s New in WCAG 2.2 (by/via) · · , ,
  58. Accessibility vs. Inclusive Design (by/via) · · , ,
  59. It’s Time to Rethink the Americans With Disabilities Act (via) · ·
  60. How to Be an Accessibility Ally (by) · · ,
  61. Nine Things Automated Accessibility Tests Can’t Test (by) · · ,
  62. Four Reasons to Give WCAG AAA a Second Look (via) · · ,
  63. Easy Dark Mode With “color-scheme” (by) · · , , ,
  64. Overlays: Just Another Disability Dongle (by/via) · ·
  65. Top 5 ARIA Implementation Errors (by/via) · · ,
  66. Form Accessibility and Usability Beyond the Basics (via) · · ,
  67. Real AI Solutions for Accessibility Challenges (via) · ·
  68. What Are Accessibility Overlays? (by) · · ,
  69. Misconceptions Can Kill Accessibility Momentum (by) · · ,
  70. Accessibility Is Easy… Except for When It Isn’t (by/via) · ·
  71. Accessible Web Components? (by/via) · · ,
  72. Save Our World With Progressive Enhancement and Accessibility (by/via) · · ,
  73. Unlocking a World of Accessibility: How Internationalization Is the Key (by/via) · · , ,
  74. What Makes an Accessible Date Picker? Is It Even Possible? (by/via) · · ,
  75. Native Mobile Accessibility Testing (by/via) · · , ,
  76. Building a Core Accessibility Team: The Keys to the Kingdom (by/via) · · ,
  77. What an Economist Article Says About Website Accessibility and Lawsuits (by/via) · ·
  78. First Steps to an Accessible Website—Skip Links (via) · ·
  79. How to Make a Strong Case for Accessibility (by/via) · · ,
  80. Expanding Your Touch Targets (by) · · ,
  81. Accessibility and Inclusivity: Study Guide (by/via) · · , ,
  82. Whataboutism (by) ·
  83. State of Web Accessibility, ARIA in HTML, and Missing UI Patterns (by+/via) · · , ,
  84. Web Components Accessibility FAQ (by) · ·
  85. Is AI the Silver Bullet of Accessibility? (via) · ·
  86. First, Do No Harm: Mistakes to Avoid in Creating Accessible User Experiences (via) · · ,
  87. Browser Video Players Review (by) · · , , , , ,
  88. The Perpetual Circle of Accessibility (by) · ·
  89. Equivalent Experience Can Cut Both Ways (by) · ·
  90. Decoding WCAG: “Alternative for Time-Based Media” and “Media Alternative for Text” (by/via) · · ,
  91. How to Make Charts and Graphs More Accessible (via) · · , ,
  92. What Is Inclusion Anyways? Lessons From the Disabled Community · · , ,
  93. Accessibility Theater (via) ·
  94. Building Accessibility Into Your Company, Team, and Culture (by/via) · · ,
  95. Navigating Web Accessibility Litigation: Advice From a General Counsel (via) · ·
  96. How I Write Alt Text for Code Snippets on Social Media (by) · · , ,
  97. Accessible Navigation (by) · ·
  98. Dark Mode: How Users Think About It and Issues to Avoid (by/via) · · , ,
  99. Where to Put Focus When Deleting a Thing (by) · ·
  100. What Is Alt Text and How to Write It (via) · · ,
  101. Main-ly Speaking (by) · ·
  102. European Accessibility Act: Article 32, and Why It Sucks (by) · ·
  103. How to Get 12% More LinkedIn Followers, Impressions, and Clicks—Practical Accessibility Tips and Tricks (by/via) · · , , ,
  104. How Organisations Respond to Accessibility Monitoring (via) · ·
  105. “We’re All Just Temporarily Abled” (by) ·
  106. Being “Polite” Does Not Ensure Access (via) · ·
  107. Tabs Are Objectively Better Than Spaces (by) · · ,
  108. Accessibility Is Not Inclusive Design or Disability Rights—It’s a Part of It (by) · · ,
  109. Beginner’s Guide to Lists and How to Make Them Accessible (via) · · ,
  110. Useable (by) · ·
  111. An “alt” Decision Tree Using Only “:has()” (by) · · ,
  112. Designing Accessible Text Over Images: Best Practices, Techniques, and Resources II (by/via) · · , , ,
  113. WCAG 3.0: Further on Up the Road (by/via) · · ,
  114. OKLCH in CSS: Consistent, Accessible Color Palettes (by/via) · · , , ,
  115. Progressively Enhanced HTML Accordion (by) · · , ,
  116. 8 Common Heading Questions (via) · · ,
  117. Alt Text Hall of Fame (by/via) · · , ,
  118. Assistive Technology Shouldn’t Be a Mystery Box (by) · · , , , ,
  119. Designing Accessible Text Over Images: Best Practices, Techniques, and Resources (by/via) · · , , ,
  120. The Easy Intro to the APCA Contrast Method (by) · · , , ,
  121. How Does Reflowing Content Affect People With Screen Magnification? (via) · · , ,
  122. Contextual Form Errors and ARIA (by) · · , ,
  123. New DOJ Web Accessibility Regulation Is a Disaster (by/via) · ·
  124. Accessibility of the Button: Should We Fix It or the Root Cause Problem? (via) · · ,
  125. CSS and Accessibility: Inclusion Through User Choice (by/via) · · , ,
  126. The Curious Case of “iff” and Overriding Screenreader Pronunciations (by) · · , , ,
  127. What Happens When Developers Are Liable for Accessibility? (via) · ·
  128. Accessibility Represents Maturity (by) · ·
  129. Contrast Checker Bookmarklet (via) · · , ,
  130. Do We Need WCAG 3 (Now)? (by) · · ,
  131. How to Make Your Captions and Audio Descriptions WCAG-Compliant (via) · · , , , ,
  132. Testing a Component’s Accessibility (via) · · , ,
  133. Web Accessibility in High-Risk Segments (by) · · ,
  134. Solving the Accessibility Palette Riddle (by/via) · · ,
  135. Blockquotes in Screen Readers (by) · · , , , ,
  136. The Problem With Auto-Generated Alternative Texts for Images (by) · · ,
  137. Understanding the WCAG 3 Working Draft Update (by) · ·
  138. Accessible Animated GIF Alternatives (by/via) · · , , ,
  139. We Deleted More Than 5,000 Pages From Our College Website—Here’s Why (by/via) · · ,
  140. Web Content Accessibility Guidelines (WCAG) 2.2 (by+/via) · · , ,
  141. Visually Hidden Links With 0 Dimensions (by) · · , , ,
  142. Getting Instant Return From Your Accessibility Testing (by) · ·
  143. O “dialog” Focus, Where Art Thou? (by) · · , ,
  144. React-ing to Accessibility: Building Accessible Forms That Everyone Can Use (by/via) · · , ,
  145. Interoperability With Specific Assistive Technologies or: “Does the Website Work on JAWS?” (by) · · , , , ,
  146. A Roadmap to Leadership Inclusion: 15 Keys to Unlocking a Diverse and Empowered Workplace II (by) · · ,
  147. Top 20 Must-Know Tips for Web Accessibility · ·
  148. The alt-text.org Project Is Moving Forward (by) · ·
  149. ARIA Can Hurt or Help Web Accessibility: How to Review Your Website’s ARIA (via) · · , ,
  150. Making Numbers in Web Content Accessible (by/via) ·
  151. Getting Started—Understanding the History of Web Accessibility (by/via) · · , ,
  152. Developing Inclusivity Features (via) · · ,
  153. A Roadmap to Leadership Inclusion: 15 Keys to Unlocking a Diverse and Empowered Workplace (by) · · ,
  154. There’s No Such Thing as a “Normal” User (by) ·
  155. Resources for Procurement of Accessible Digital Products and VPAT (by/via) · · , , ,
  156. The “article” Element and Screen Readers (by) · · , , , ,
  157. Your Browser May Be Having a Secret Relationship With a Screen Reader (via) · · , ,
  158. Combat Accessibility Decay: How to Maintain Ongoing Accessibility (via) · · ,
  159. WCAG 2.2, Quick and Simplified (by) · · ,
  160. Accessible Overlays Aren’t Accessible (via) · ·
  161. Under-Engineered Comboboxen? (by) · · , ,
  162. Web and App ADA Lawsuits: 6 Trends So Far in 2023 (via) · · ,
  163. 4 Ways to Improve Mobile Accessibility (by) · ·
  164. Screen Magnification: Digital Accessibilitiy (via) · · , ,
  165. Top Tips From a Web Accessibility Evaluator at WebAIM (by/via) · · ,
  166. Live Regions in React (by) · · , ,
  167. Designing for Inclusion (by/via) · · ,
  168. WCAG 2.2 Removes 4.1.1 Parsing and How axe-core Is Impacted (by/via) · · , ,
  169. Thoughts From “Meet Safari for Spatial Computing” (by) · · , , ,
  170. Continuous Accessibility (by) · · ,
  171. Three Key Principles for an Accessible Website (by+/via) · ·
  172. Can Web Developers Be Held Liable? (by/via) · ·
  173. The Five Types of People Who Produce Inaccessible Code (by) · ·
  174. 6 Quick Tests You Can Do to Test Your Forms for Accessibility (by) · · ,
  175. Design vs. Accessibility and the CSS “visually-hidden” Class (by/via) · · , ,
  176. You Can Stop Using “user-scalable=no” and “maximum-scale=1” in Viewport Meta Tags Now (by) · · , ,
  177. The Universal Focus State (by) · · ,
  178. No, “AI” Will Not Fix Accessibility (by) · ·
  179. Sticky Content: Focus in View (by/via) · · , ,
  180. Testing Sites and Apps With Blind Users: A Cheat Sheet (by+/via) · · , , , , ,
  181. Before Your Next Frontend Pull Request, Use This Checklist (by+/via) · · , , , , ,
  182. Accessible Rich Internet Applications (WAI-ARIA) 1.2 (via) · · ,
  183. Accessibility and Artificial Intelligence (by) · ·
  184. Assume the Position—a Labelling Story (by/via) · · ,
  185. Accessibility Testing—Pay Attention to the Details (via) · ·
  186. The Problem With Automatically Focusing the First Input and What to Do Instead (by) · · , ,
  187. How We Created an Accessible, Scalable Color Palette · · , , ,
  188. WCAG 2.2 Misses Mark on Defining Visible Focus (by) · · , ,
  189. Accessible Components: The Hamburger Menu · · ,
  190. Accessibility Audits for All (by) · · ,
  191. Don’t Meddle With User Input (by) · ·
  192. The Problem With Nested Fieldsets and How to Avoid Them (by) · · , ,
  193. How Screen-Reader Users Type on and Control Mobile Devices (by/via) · · , , , ,
  194. When to Use Plain Text or Images Instead of MathML (via) · · ,
  195. Brief Note on Popovers With Dialogs (by) · · , , ,
  196. We Need to Talk About How We Talk About Accessibility (by+/via) · · ,
  197. Levelling Up Accessibility Skills in Your Organisation (by+/via) · ·
  198. “display: contents” Considered Harmful (by) · ·
  199. Reading a Voluntary Product Accessibility Template (VPAT) or Accessibility Conformance Report (ACR) (by/via) · · ,
  200. Addressing Timeout Modals: Navigating the Nuances for Inclusive Web Design (by/via) · · ,
  201. A Beginners Guide to Digital Accessibility (by) · ·
  202. What Devs Can Do on Global Accessibility Awareness Day (by) · ·
  203. Are We There Yet? WCAG 2.2 Is at the Candidate Recommendation [Stage] v3 (by/via) · · ,
  204. Accessible Numbers (by) · ·
  205. Semantics and the “popover” Attribute: What to Use When? (by) · · , ,
  206. Fieldsets, Legends, and Screen Readers Again (by/via) · · , , , ,
  207. Why Is Web Accessibility Important? (by/via) · ·
  208. HTML Landmark Roles Screen Reader Demo (by/via) · · , , , ,
  209. Using HTML Landmark Roles to Improve Accessibility (by/via) · ·
  210. The Problem With Disabled Buttons and What to Do Instead (by) · · ,
  211. Screen Readers Don’t Announce When the User Reaches the “maxlength” Character Limit (by/via) · · , , , ,
  212. Respect Your Children (by/via) · · ,
  213. ShatGPT (by) · ·
  214. React Testing Library and Accessibility (by) · · , , ,
  215. Digital Accessibility Is a Bigger Education Issue Than We Think—Here’s What We Can Do About It (by/via) · ·
  216. Why “font-size” Must Never Be in Pixels (by) · · , ,
  217. Short Note: Why Isn’t “role=presentation”/“none” Allowed on Focusable Elements? (by) · · , ,
  218. Progress Over Perfection: The Better Way for Communication and Accessibility Advocacy (by) · · , ,
  219. Accessible Target Sizes Cheatsheet (by/via) · ·
  220. The Potentially Dangerous Non-Accessibility of Cookie Notices (by/via) · · , , ,
  221. Meeting WCAG Level AAA (by/via) · · , ,
  222. Designing and Coding for Voice (by) ·
  223. Visually Accessible Data Visualization (by/via) · ·
  224. Audio Accessibility in Miro: A Hackathon Story in 3 Acts (by/via) · · ,
  225. Answering “What ARIA Can I Use?” (by/via) · · , , , ,
  226. Web Accessibility: A Reference to Creating Inclusive Websites (via) ·
  227. Breaking Down Accessibility Barriers: Top 4 Challenges With Screen Magnifiers (by/via) · · ,
  228. Shifting Left, or: Making Accessibility Easier by Doing It Earlier (by) · · , ,
  229. Don’t Override Screen Reader Pronunciation (by) · · , , ,
  230. Accessibility in Design Systems: Building More Inclusive Products for a Better User Experience (via) · · , , ,
  231. HTML Accessibility API Mappings 1.0 (by+/via) · · ,
  232. Chasing Rainbows (by/via) · ·
  233. Establishing Metrics for Accessibility ROI (by) · · ,
  234. The Alt Text War—SEO vs. Accessibility (by/via) · · , , ,
  235. What’s New in WCAG 2.2? (by/via) · · ,
  236. Designing for Reduced Motion (by/via) · ·
  237. Foundations: Accessible Names and Descriptions (by/via) · · , ,
  238. What Makes a Good Screenshot? (by/via) · ·
  239. Five Pieces of Advice for More Accessible Websites (by) · ·
  240. Exposing Field Errors (by) · · , , ,
  241. Accessibility for Designers: Where Do I Start? (by) · · ,
  242. 10 Ways to Hide Elements in CSS (by/via) · · ,
  243. When I Get That Low Contrast Feeling, I Need Non-Textual Healing (by/via) · · ,
  244. The Ultimate Guide to Automatic Accessibility Testing in CI/CD for React Apps · · , , , ,
  245. We Need Accessibility Action (by) · ·
  246. Alternative Text in the Wild: 5 Alternative Text Examples (via) · · ,
  247. The WebAIM Million (via) · · , ,
  248. Connecting Dots of an Accessibility Audit (by/via) · ·
  249. Accessibility vs. Emojis (via) · · , ,
  250. Guardrails for Better Accessibility Support in Frontend (by) · · ,