When I was working on a team with an accessibility requirement. The bulk of the work wasn't coloring work, nor writing alternative texts, but ensuring that the website could be navigated well using a screen reader.<p>We used JAWS[0] and tested every change and new feature with it to ensure users of it could make sense of the website. This was a lengthy process that took a lot of effort and learning on the part of devs to pick up JAWS.<p>The tough part of it was it being a subjective process. No one can tell you if the final experience was "correct" or not.<p>This part of web accessibility isn't mentioned as often, but its just as important. Likely because not many people really know about it.<p>Edit: I think part of it is the high cost of products like JAWS. The current price of a home license is $1,000. A business license is $1,285.<p>[0] <a href="https://www.freedomscientific.com/products/software/jaws/" rel="nofollow">https://www.freedomscientific.com/products/software/jaws/</a>
This article isn’t all bad, but it’s not particularly high quality either.<p><pre><code> <img src=”baby_elephants.png” alt=”A group of two baby elephants walking behind their mom in a open field.”>
</code></pre>
… followed immediately by a demonstration baby elephant image with <i>empty</i> alt text (which in a case like this is worse than no alt attribute, because it tells accessibility tech that the image is purely decorative and should not be announced).<p>(Note also the use of ” instead of ".)<p>This is not encouraging.<p>> <i>You can add a landmark by using the role attribute. Some examples of landmarks are banner, form, and search. Something to note is that you should only place the role attribute on elements like <div> and <span>, do not place on elements that have semantic meaning like a <ul> or <p>.</i><p>There is nothing wrong with overriding the role of an element with semantics; it purely comes down to whether you do it correctly. And the thing that they don’t mention here is that the converse applies at least as much: if there’s a built-in element with your desired semantics, you should use that instead of a role, so the example is a bad example: its <div role="navigation"> should be <nav>.
If you prefer reader mode, like I do, any Medium-based platform is a PITA cause all images are blurred. Anyone who is on a crappy connection will have them same. What a fuxxing shame! Can we stop using this crappy platform please?
One problem here: line height should be unit-less. Use just a number and that number will become a multiple of the font value so font-size 2rem line-height:1.3 don’t use units
Something not mentioned that a ton of modern websites fail at is having readable text due to either too-low contrast, too-thin or too-small fonts, or all of those things combined. These days it seems like I have to use reader mode for half the articles or blog posts I read daily.