Frontend Dogma

“accessibility” Archive (3)

  1. React Testing Library and Accessibility (by) · · , , ,
  2. Digital Accessibility Is a Bigger Education Issue Than We Think—Here’s What We Can Do About It (by/via) · ·
  3. Why “font-size” Must Never Be in Pixels (by) · · , ,
  4. Short Note: Why Isn’t “role=presentation”/“none” Allowed on Focusable Elements? (by) · · , ,
  5. Progress Over Perfection: The Better Way for Communication and Accessibility Advocacy (by) · · , ,
  6. Accessible Target Sizes Cheatsheet (by/via) · ·
  7. The Potentially Dangerous Non-Accessibility of Cookie Notices (by/via) · · , , ,
  8. Meeting WCAG Level AAA (by/via) · · , ,
  9. Designing and Coding for Voice (by) ·
  10. Visually Accessible Data Visualization (by/via) · ·
  11. Audio Accessibility in Miro: A Hackathon Story in 3 Acts (by/via) · · ,
  12. Answering “What ARIA Can I Use?” (by/via) · · , , , ,
  13. Web Accessibility: A Reference to Creating Inclusive Websites (via) ·
  14. Breaking Down Accessibility Barriers: Top 4 Challenges With Screen Magnifiers (by/via) · · ,
  15. Shifting Left, or: Making Accessibility Easier by Doing It Earlier (by) · · , ,
  16. Accessibility in Design Systems: Building More Inclusive Products for a Better User Experience (via) · · , , ,
  17. Don’t Override Screen Reader Pronunciation (by) · · , , ,
  18. HTML Accessibility API Mappings 1.0 (by+/via) · · ,
  19. Chasing Rainbows (by/via) · · , ,
  20. Establishing Metrics for Accessibility ROI (by) · · ,
  21. The Alt Text War—SEO vs. Accessibility (by/via) · · , , ,
  22. What’s New in WCAG 2.2? (by/via) · · ,
  23. Designing for Reduced Motion (by/via) · ·
  24. Foundations: Accessible Names and Descriptions (by/via) · · , ,
  25. What Makes a Good Screenshot? (by/via) · ·
  26. Five Pieces of Advice for More Accessible Websites (by) · ·
  27. Exposing Field Errors (by) · · , , ,
  28. Accessibility for Designers: Where Do I Start? (by) · · ,
  29. 10 Ways to Hide Elements in CSS (by/via) · · ,
  30. When I Get That Low Contrast Feeling, I Need Non-Textual Healing (by/via) · · ,
  31. The Ultimate Guide to Automatic Accessibility Testing in CI/CD for React Apps · · , , , ,
  32. We Need Accessibility Action (by) · ·
  33. Alternative Text in the Wild: 5 Alternative Text Examples (via) · · ,
  34. The WebAIM Million (via) · · , ,
  35. Connecting Dots of an Accessibility Audit (by/via) · ·
  36. Accessibility vs. Emojis (via) · · , ,
  37. Guardrails for Better Accessibility Support in Frontend (by) · · ,
  38. A Quick Guide to Reviewing a VPAT ACR (by) · · , ,
  39. CSS-Only Widgets Are Inaccessible (by) · ·
  40. The “search” Element (by) · · ,
  41. What We’ve Learned About Designing for Accessibility From Our Users (by/via) · ·
  42. Accessible but Never Boring: Rebranding the Wise Design System for Everyone II (by/via) · · ,
  43. Certifications Should Be Hard (by) · · ,
  44. When Is “:focus-visible” Visible? (by) · · ,
  45. Visually Hidden Content Is a Hack That Needs to Be Resolved, Not Enshrined (by) · · , , ,
  46. Annotating Designs for Accessibility (by/via) · · ,
  47. How Screen Readers Read Special Characters: An Update (by/via) · · , , , ,
  48. Hijacking Screenreaders With CSS (by/via) · · , , , ,
  49. Foundations: Pointer Gestures (by/via) · ·
  50. Accessibility and Design Systems: The Deep-Dive Q&A (by+/via) · · ,
  51. Accessibility Beyond Code Compliance (by) · ·
  52. It’s About Time CAPTCHAs Become Accessible (via) · ·
  53. The H1 Conundrum: Understanding the Challenges of Heading Level One (by/via) · · , ,
  54. Fix Color Contrast—Web Accessibility for Text and UI Design (by) · · ,
  55. Making Calendars With Accessibility and Internationalization in Mind (by/via) · · ,
  56. Best Practices for Structuring Accessibility Testing (by/via) · · ,
  57. We Don’t Need “.visually-hidden” (by/via) · · , ,
  58. “content” Is Your Content? (by/via) · · , , ,
  59. My Ideal Accessible Components Resource Is Holistic, Well Tested and Easy to Use (by) · ·
  60. ARIA Live Regions for JavaScript Frameworks (by/via) · · , , ,
  61. 50.1% Empty Links (by) · · , , ,
  62. Are You Making These Five Mistakes When Writing Alt Text? (by/via) · · , ,
  63. Toolkit Tuesday: Using YouTube for Captions and Transcripts (via) · · , ,
  64. Accessible but Never Boring: Rebranding the Wise Design System for Everyone (by/via) · · ,
  65. A Native “Visually Hidden” in CSS? Yes Please! (by/via) · · , , ,
  66. The WebAIM Strategic Accessibility Framework (via) · ·
  67. The Web Needs a Native “.visually-hidden” (by) · ·
  68. A Beginner’s Guide to Manual Accessibility Testing (via) · · ,
  69. How People Read Online (by/via) · · , ,
  70. Without Accessibility, There Is No Privacy or Security (via) · · ,
  71. Conformance and Accessibility (by) · · ,
  72. A Guide to Accessible Form Validation (by/via) · · , , ,
  73. How to Style Your Alt Text (by) · · , ,
  74. Successful Teams Ensure 100% of Their Members Understand Keyboard Accessibility (via) ·
  75. How Shadow DOM and Accessibility Are in Conflict (by/via) · · ,
  76. The Importance of Adding Accessibility Design Reviews to the Design Process (by/via) · · ,
  77. Open Captions vs. Closed Captions: What’s the Difference? (via) · · ,
  78. Automatic Captions: Our Experiments and Best Practices (via) · · , ,
  79. Understanding the Cost of Not Being Accessible (by) · ·
  80. Not Everyone Uses a Computer in the Same Way That You Do (by/via) · ·
  81. ARIA vs. HTML (by) · · , , ,
  82. Ideas for Making Accessibility and Equity a Core Part of the Software Development Lifecycle (by) · · ,
  83. Keys to an Accessibility Mindset (by/via) · ·
  84. Avoid Spanning Table Headers (by) · · , ,
  85. A Step-by-Step Guide to Building Accessible Carousels (by/via) · · , , ,
  86. If You’re Going to Do a Job, Do It Properly (by) · ·
  87. Software Accessibility for Users With Attention Deficit Disorder (ADHD) (via) ·
  88. Buttons, Links, and Focus (by) · · , , ,
  89. Screen Readers Don’t Convey the Semantics of “strong” and “em” (by) · · , , , ,
  90. Scaling Accessibility Through Design Systems (by+/via) · · , ,
  91. A Practical Approach to Automated Accessibility (by) · · ,
  92. Automation Is Not the Enemy (by) · · ,
  93. Automated Testing Won’t Solve Web Accessibility (by) · · ,
  94. Foundations: Introduction to WAI-ARIA (by/via) · · ,
  95. The Troublesome Life and Lamentable Death of Success Criterion 4.1.1 · · , ,
  96. How to Build Accessible Main Navigation? (by/via) · · ,
  97. Focus Appearance Thoughts (by) · · ,
  98. Testing Colour Accessibility With Dev Tools (by/via) · · , , ,
  99. Non-Text Content Contrast Also Matters (by) · · ,
  100. WCAG 2.2 Update: It’s Time to Say Goodbye to the Parsing Criterion (by) · · ,
  101. External Links: In or Out (by/via) · · , ,
  102. Understanding Color and Accessibility (by) · ·
  103. Setting Expectations for Asking ChatGPT Web Accessibility Questions (by) · ·
  104. Léonie Watson on Accessibility (by+/via) · · ,
  105. New WCAG 2.2 Features Rated (by) · · ,
  106. Accessible Hamburger Buttons Without JavaScript · · ,
  107. Use the Dialog Element (Reasonably) (by) · · ,
  108. Musing Upon an “[alt]” Text Badge on Images (by) · · ,
  109. Are We There Yet? WCAG 2.2 Is at the Candidate Recommendation Stage Again (by/via) · · ,
  110. A Simple Custom (by) · · , ,
  111. If You Need a Link, Don’t Use a Button (by) · · , , ,
  112. Creating a Community That Values Accessibility (via) · ·
  113. Be a Digital Ally: Further Exploration of WCAG 2.2 (via) · · ,
  114. Web Accessibility Global Usage Survey · ·
  115. Comparing Level Access Automated Tools to Manual Accessibility Testing (by) · · , ,
  116. Comparing Manual and Free Automated WCAG Reviews (by) · · , ,
  117. Accessible Writing Is Just Good Writing (via) · ·
  118. Blind News Audiences Are Being Left Behind in the data Visualisation Revolution: Here’s How We Fix That (by/via) · ·
  119. Foundations: Visible Focus Styles (by/via) · · ,
  120. Manual Accessibility Testing (via) · ·
  121. The Main Areas of WAI-ARIA (by) · ·
  122. Closed Captions and Subtitles UX (by/via) · · ,
  123. 2023 Design Trends From an Accessibility Perspective (via) · · ,
  124. Stock Photos of People With Disabilities (by/via) · · ,
  125. A New Accessibility Strategy for the GOV.UK Design System (by+/via) · · ,
  126. JAWS, NVDA, and VoiceOver Braille Viewers (by) · · , , , , , ,
  127. WAI–Adapt Explainer (by+/via) ·
  128. Quick Thoughts on Typeface and Font Accessibility (by) · · ,
  129. Carry On Testing 2023 (by/via) · ·
  130. A Beginner’s Guide to Link and Text Accessibility (via) · · , ,
  131. Fluid Typography: Predicting a Problem With Your User’s Zoom-In (by/via) · · , ,
  132. Overlapping Interactive Areas (by) · ·
  133. User Stylesheets Are Still Pretty Great and Should Be More Widely Supported (by/via) · · ,
  134. An Inclusive and Planet-Friendly Digital Style Guide (by/via) · · , , , ,
  135. What Is the Difference Between Alternative Text, Long Description, and Caption? (by) ·
  136. Aligning Jakob Nielsen’s 10 Usability Heuristics With the WCAG 2.1 (by) · · , ,
  137. Top 10 Accessibility News of 2022 (via) · ·
  138. Obscure CSS: Restoring Visibility (by) · ·
  139. The Intended Consequence of Inaccessible Digital Ads (by+/via) · · ,
  140. Quick Start for Evaluating and Testing Web Accessibility (by+/via) · · ,
  141. Building an Accessible Theme Picker With HTML, CSS, and JavaScript (by) · · , , ,
  142. Accessibility Convincing (by/via) · · , ,
  143. Useful Accessibility and Usability Examples to Help Improve Your Designs (via) · · ,
  144. Foundations: Target Sizes (by/via) · ·
  145. Bad Performance Is Bad Accessibility (by) · ·
  146. Prevent Focused Elements From Being Obscured by Sticky Headers (by/via) · · , ,
  147. 5 HTML Elements, and a Partridge in a Despair Tree · · ,
  148. How to Find and Fix the Top 3 Accessibility Issues (via) · · , ,
  149. Accessibility Starts With an Organisation’s Culture (by/via) · ·
  150. A Guide for Making Apps Accessible · ·
  151. Top 5 Accessibility Issues in 2022 (by/via) · ·
  152. State of A11Y (via) · ·
  153. Federal Web Accessibility Focus Has Private Sector on Notice (by/via) · ·
  154. Five Myths About Digital Accessibility (by) · · ,
  155. WCAG 3.0: Are We There Yet? (by/via) · · ,
  156. WCAG—Priority of Constituencies (by) · · ,
  157. Meaningful Labels Using ARIA—or Not (by) · · , ,
  158. W3C Publishes WCAG Testers Consistency List (by/via) · · ,
  159. Accessible Front-End Patterns for Responsive Tables (by/via) · · ,
  160. Accessibility: The Land That “Time to Interactive” Forgot (by/via) · · ,
  161. Reading the Meter (by) · · ,
  162. Swearing and Automatic Captions (by) · · ,
  163. Website Accessibility Is Not an Afterthought ·
  164. The 411 on 4.1.1 (by) · · ,
  165. Brief Note on Description List Support (by) · · , , ,
  166. Landmarks and Where to Put Them (by) · · , ,
  167. You Don’t Need ARIA for That (by) · · ,
  168. Accessibility and MVPs (by) · ·
  169. Which Images Need Descriptive Text? (by) · ·
  170. Making Microservices Accessible (by) · ·
  171. HTML Semantics and Accessibility Cheat Sheet (via) · · , ,
  172. Shadow DOM and Accessibility: The Trouble With ARIA (by) · · , , ,
  173. Making Accessibility Simpler in Higher Education and Beyond (by) · ·
  174. Addressing Concerns About CSS Speech (by) · ·
  175. Positioning Notification Messages With Accessibility in Mind (by) · ·
  176. Setting Up a Screen Reader Testing Environment on Your Computer (by) · · , , ,
  177. Accessibility and Inclusive Design Systems (by/via) · · , ,
  178. Preparing for WCAG 2.2 (by+/via) · · ,
  179. Page Title Conventions (by) · · ,
  180. The Value of Accessibility (by+/via) · · ,
  181. Incorporating Accessible Design Elements Into Your Web Site (by/via) · ·
  182. Analyzing the Top 100 Retailers for Digital Accessibility (via) · · ,
  183. A Guide to Keyboard Accessibility: JavaScript (by/via) · · , ,
  184. DOJ and Congressional Updates on Digital Accessibility (via) · ·
  185. Brief Note on “aria-readonly” Support (by) · · , , ,
  186. Accessibility Is in Style—Styles and Style Guides (by/via) · · , , , ,
  187. 5 Insider Tips to Make Accessibility Part of Workflow (by/via) · · ,
  188. Using Automated Test Results to Improve Accessibility (by+/via) · · ,
  189. Significant Improvements for Screen Readers Now in Nightly Firefox (by/via) · · , , , ,
  190. A Guide to Keyboard Accessibility: HTML and CSS (by/via) · · , , ,
  191. Your Accessibility Claims Are Wrong, Unless… (by) · ·
  192. Don’t Disable the Zoom Functionality (by) · ·
  193. The Anatomy of “visually-hidden” (by/via) · ·
  194. What’s New in WCAG 2.2 (by/via) · · , ,
  195. Are You Using an Accessibility Overlay to Help Disabled Users? Don’t! (by/via) · · ,
  196. Designing for People Who Use a Mouse (by/via) · ·
  197. Accessfuturism: Digital Accessibility in 2032 (by/via) · · ,
  198. Accessibility Contrast Requirements Explained and How to Fix 5 Common Low-Contrast Issues (via) · · ,
  199. Dialogs, Modality, and Popovers Seem Similar—How Are They Different? (by) · · , , ,
  200. What Designers Can Learn From Apple’s New Accessibility Features (via) · · ,
  201. Responsive Accessibility Using “visibility: hidden” (by) · ·
  202. Why You Need to Monitor and Report on Accessibility—All the Time (via) · · , ,
  203. A Simpler Approach to Document and Web Accessibility (via) ·
  204. 5 Takeaways From Screen Reader Usability Interviews (by) · · , ,
  205. Accessibility “Gaps” in MVPs (by) ·
  206. Caring About the World Wide Web (by/via) · · , ,
  207. Progress Over Perfection: A Better Way to Accessibility (by) · ·
  208. A Deep Dive Into Accessible Notifications (by/via) · · ,
  209. Why You Need to Involve Deaf and Hard of Hearing People in Research and Testing (by/via) · ·
  210. A Testing Strategy for Accessibility in New Apps (by) · ·
  211. 7 Tactics That Benefit Both Accessibility and SEO (via) · ·
  212. Next Steps for the W3C Web Accessibility Initiative (by/via) · · ,
  213. Complexity and Caution (by) · · ,
  214. “aria-label” Is a Code Smell (by) · · ,
  215. Do We Need an Interop for Assistive Technologies? (by) · · , , ,
  216. 5 Visual Treatments that Improve Accessibility (via) · ·
  217. Why You Should Never Use “px” to Set “font-size” in CSS (by) · ·
  218. Getting WCAG Color Contrast Right (by/via) · · , ,
  219. Accessibility Beyond the “Obvious” (by) ·
  220. Web Accessibility: ARIA 101 (by/via) · · ,
  221. Twitter Reminds Us About Alt Text, but How Good Are We at It? (by/via) · · , ,
  222. SEO and Accessibility Are Symbiotic (via) · ·
  223. How to Build the Foundation for Digital Accessibility (by/via) · · , ,
  224. Why We Need CSS Speech (by) · ·
  225. Digital Accessibility—Ask Me Anything (by+/via) · ·
  226. Google on Alt Text SEO and Accessibility (by+/via) · · , , ,
  227. Common ARIA Mistakes and How to Avoid Them (by) · · , ,
  228. Designing for Users With Disabilities: 10 Factors to Consider (via) · · ,
  229. New Brutalism and Web Accessibility: What You Need to Know (by/via) · ·
  230. Accessibility Checkers—a Good Start, Not a Solution (by/via) · · ,
  231. What I Learned About SVG Accessibility (Among Other Things) From NBC News’ Senate “What If” Project (by) · · ,
  232. Some Things I Took Away From an Event Apart 2022 in Denver (by/via) · · ,
  233. Intro to Why Accessibility Is Important for Good SEO (via) · · ,
  234. Representation in “alt” Text (by) · · ,
  235. How to Write Good Alt Text (by) · · , ,
  236. WCAG 2.2 Success Criteria (by) · ·
  237. 4 Required Tests Before Shipping New Features (by) · ·
  238. Five Months Worth of Takes on the Digital Accessibility Space (by/via) · · ,
  239. When Going Somewhere Does a Thing: On Links and Buttons (by) · · , , ,
  240. Where Are the Accessibility Statements? Digital Accessibility Shouldn’t Be a Surprise (via) ·
  241. 3 Things to Consider Before You Implement CAPTCHA for Accessibility (via) · ·
  242. A Beginner’s Complete Guide to Form Accessibility: The 5 Things Accessible Forms Need and How to Fix Common Errors (via) · · ,
  243. Learn Accessibility (by/via) · ·
  244. Intersectionality, Accessibility, and Inclusion (via) · · ,
  245. Yes, Accessibility Is Also a Backend Concern (by) ·
  246. Websites Need to Be Accessible to Be Inclusive (by+/via) · ·
  247. A Deep Dive Into WCAG 2.2—and Beyond (by+/via) · · ,
  248. Accessibility (by+/via) · · ,
  249. The Indisputable Truth About Accessibility (by/via) · ·
  250. Blind People Need to Be Considered More When Making Data Visualizations (by/via) · ·