davidbgk
/
larlet-fr-david-cache
Beobachten 1
Favorisieren 0
Fork 0
Code Releases 0 Aktivität
A place to cache linked articles (think custom and personal wayback machine)
Du kannst nicht mehr als 25 Themen auswählen Themen müssen mit entweder einem Buchstaben oder einer Ziffer beginnen. Sie können Bindestriche („-“) enthalten und bis zu 35 Zeichen lang sein.
58 Commits
1 Branch
Struktur: 1599e90c79
Branches Tags
${ item.name }
Erstelle Branch ${ searchTerm }
von „1599e90c79“
${ noResults }
larlet-fr-david-cache/cache/2020/a70068c881eba36604b2f4f8aec.../index.html

index.html 8.9KB
Originalformat Blame Verlauf

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102 
  1. <!doctype html><!-- This is a valid HTML5 document. -->

  2. <!-- Screen readers, SEO, extensions and so on. -->

  3. <html lang="fr">

  4. <!-- Has to be within the first 1024 bytes, hence before the <title>

  5.   See: https://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset -->

  6. <meta charset="utf-8">

  7. <!-- Why no `X-UA-Compatible` meta: https://stackoverflow.com/a/6771584 -->

  8. <!-- The viewport meta is quite crowded and we are responsible for that.

  9.   See: https://codepen.io/tigt/post/meta-viewport-for-2015 -->

  10. <meta name="viewport" content="width=device-width,initial-scale=1">

  11. <!-- Required to make a valid HTML5 document. -->

  12. <title>HTML: The Inaccessible Parts (archive) — David Larlet</title>

  13. <!-- Generated from https://realfavicongenerator.net/ such a mess. -->

  14. <link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons2/apple-touch-icon.png">

  15. <link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons2/favicon-32x32.png">

  16. <link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons2/favicon-16x16.png">

  17. <link rel="manifest" href="/static/david/icons2/site.webmanifest">

  18. <link rel="mask-icon" href="/static/david/icons2/safari-pinned-tab.svg" color="#07486c">

  19. <link rel="shortcut icon" href="/static/david/icons2/favicon.ico">

  20. <meta name="msapplication-TileColor" content="#f0f0ea">

  21. <meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">

  22. <meta name="theme-color" content="#f0f0ea">

  23. <!-- Documented, feel free to shoot an email. -->

  24. <link rel="stylesheet" href="/static/david/css/style_2020-04-25.css">

  25. <!-- See https://www.zachleat.com/web/comprehensive-webfonts/ for the trade-off. -->

  26. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light)" crossorigin>

  27. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light)" crossorigin>

  28. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light)" crossorigin>

  29. <link rel="preload" href="/static/david/css/fonts/triplicate_t3_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>

  30. <link rel="preload" href="/static/david/css/fonts/triplicate_t3_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>

  31. <link rel="preload" href="/static/david/css/fonts/triplicate_t3_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>

  32. 

  33.   <meta name="robots" content="noindex, nofollow">

  34.   <meta content="origin-when-cross-origin" name="referrer">

  35.   <!-- Canonical URL for SEO purposes -->

  36.   <link rel="canonical" href="https://daverupert.com/2020/02/html-the-inaccessible-parts/">

  37. 

  38. <body class="remarkdown h1-underline h2-underline h3-underline hr-center ul-star pre-tick">

  39. 

  40. <article>

  41. <h1>HTML: The Inaccessible Parts</h1>

  42. <h2><a href="https://daverupert.com/2020/02/html-the-inaccessible-parts/">Source originale du contenu</a></h2>

  43. <p>I’ve always abided in the idea that “HTML is accessible by default and then we come along and mess it up.” In a lot places this is very true and by just using a suitable HTML element instead of a generic <code>div</code> or <code>span</code> we can have a big Accessibility impact.</p>

  44. 

  45. <p>But that’s not always the case. There are some cases where even using plain ol’ HTML causes accessibility problems. I get frustrated and want to quit web development whenever I read about these types of issues. Because if browsers can’t get this right, what hope is there for the rest of us. I’m trying to do the best I can, use the platform, but seems like there’s a dozen “gotchas” lurking in the shadows.</p>

  46. 

  47. <p>I’m going to start rounding up those HTML shortfalls in this here post as a little living document that I can personally reference every time I write some HTML.</p>

  48. 

  49. <p><hr/>

  50. <p><code>&lt;input type="number"&gt;</code><br/>

  51. Gov.UK finds <a href="https://technology.blog.gov.uk/2020/02/24/why-the-gov-uk-design-system-team-changed-the-input-type-for-numbers/">Number Inputs aren’t inclusive</a>. (2020)</p>

  52. <p><code>&lt;input type="date"&gt;</code><br/>

  53. Graham Armfield finds <a href="https://www.hassellinclusion.com/blog/input-type-date-ready-for-use/">Date Inputs not ready for use</a>. (2019)</p>

  54. <p><code>&lt;input type="search"&gt;</code><br/>

  55. Adrian Roselli points out <a href="https://adrianroselli.com/2019/07/ignore-typesearch.html">Search Inputs aren’t as useful as originally thought</a>. (2019)</p>

  56. <p><code>&lt;select multiple&gt;</code><br/>

  57. Sarah Higley tests with actual users and finds <a href="https://www.24a11y.com/2019/select-your-poison-part-2/">Select Multiple has a 25.3% success rate</a>. (2019)</p>

  58. <p><code>&lt;progress&gt;</code><br/>

  59. Scott O’Hara finds <a href="https://scottaohara.github.io/a11y_styled_form_controls/src/progress-bar/">numerous errors with the Progress element</a>. (2018)</p>

  60. <p><code>&lt;meter&gt;</code><br/>

  61. Scott O’Hara finds <a href="https://scottaohara.github.io/a11y_styled_form_controls/src/meter/">more numerous errors with the rare Meter element</a>. (2018)</p>

  62. <p><code>&lt;dialog&gt;</code><br/>

  63. Scott O’Hara declares <a href="https://www.scottohara.me/blog/2019/03/05/open-dialog.html">Dialog not ready for production</a>. (2019)</p>

  64. <p><code>&lt;details&gt;&lt;summary&gt;</code><br/>

  65. Adrian Roselli feels <a href="https://adrianroselli.com/2019/04/details-summary-are-not-insert-control-here.html">Details/Summary are only good in limited contexts</a> (e.g. <a href="https://daverupert.com/2019/12/why-details-is-not-an-accordion/">Details doesn’t work as an Accordion</a>, which is what I would expect). (2019)</p>

  66. <p><code>&lt;video&gt;</code><br/>

  67. Scott Vinkle goes with a third-party player after seeing that <a href="https://scottvinkle.me/blogs/blog/how-accessible-is-the-html-video-player">the native HTML Video Player is a very inconsistent experience for screen readers</a>. (2019)</p>

  68. <p><code>&lt;div onclick&gt;</code><br/>

  69. Technically this is JavaScript, but the screen reader <a href="https://github.com/carbon-design-system/carbon/issues/986#issuecomment-412968245">JAWS announces “Clickable” when the element or one its ancestors have a click event handler</a>. This is a bummer for trying to make tap areas bigger. (2018)</p>

  70. <p><code>&lt;div aria-label&gt;</code><br/>

  71. Paciello Group educates how <a href="https://developer.paciellogroup.com/blog/2017/07/short-note-on-aria-label-aria-labelledby-and-aria-describedby/"><code>aria-label</code>, <code>aria-labelledby</code> , and <code>aria-describedby</code> only work on certain elements… and not <code>&lt;div&gt;</code> elements</a>. It’s not very intuitive to me that <code>aria-label</code> would only work <em>sometimes</em> and it seems like something linters like <a href="https://www.deque.com/axe/">axe</a> should catch. (2017)</p>

  72. <p><code>&lt;a href&gt;&lt;div&gt;Block Links&lt;/div&gt;&lt;/a&gt;</code><br/>

  73. Adrian Roselli finds <a href="https://adrianroselli.com/2020/02/block-links-cards-clickable-regions-etc.html">Block Links in a Card UI have usability issues</a>. (2020)</p>

  74. <p><code>aria-controls</code><br/>

  75. The <code>aria-controls</code> attribute is a great way to establish a relationship between two elements and is in tons of tutorials… only one problem… Heydon Pickering points out <a href="https://heydonworks.com/article/aria-controls-is-poop/"><code>aria-controls</code> doesn’t do anything</a>. (2016)</p>

  76. <p><code>role="tablist"</code><br/>

  77. After some user testing, Jeff Smith discovered <a href="http://simplyaccessible.com/article/danger-aria-tabs/">the best way to make accessible tabs is to remove <code>role="tablist"</code>, <code>role="tab"</code>, <code>role="tabpanel"</code> from their tabs</a>. FWIW, these <a href="https://medium.theuxblog.com/danger-testing-accessibility-with-real-people-4515f72db648">findings were contested in a 3,900 word blog post by Léonie Watson</a>. (2016)</p>

  78. <hr/>

  79. <p>Your mileage may vary, test with actual users. I’ll do my best to update this as the situation evolves glacially over the next 20 years.</p>

  80. <p><em>Edit 2/28/2020:</em></p>

  81. <ul>

  82. <li>Added the year to each link to help reflect the potential “staleness” of the information.</li>

  83. <li>Added a note to test with actual users.</li>

  84. <li>Added a link to Léonie Watson’s rebuttal under the <code>tablist</code> discussion.</li>

  85. </ul></p>

  86. </article>

  87. 

  88. 

  89. <hr>

  90. 

  91. <footer>

  92.   <p>

  93.     <a href="/david/" title="Aller à l’accueil">🏠</a> •

  94.     <a href="/david/log/" title="Accès au flux RSS">🤖</a> •

  95.     <a href="http://larlet.com" title="Go to my English profile" data-instant>🇨🇦</a> •

  96.     <a href="mailto:david%40larlet.fr" title="Envoyer un courriel">📮</a> •

  97.     <abbr title="Hébergeur : Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33184162340">🧚</abbr>

  98.   </p>

  99. </footer>

  100. <script src="/static/david/js/instantpage-3.0.0.min.js" type="module" defer></script>

  101. </body>

  102. </html>