|
|
|
|
|
by Theodores
2617 days ago
|
|
This article makes a lot of noise about Uber's commitment to accessibility. So I am led to believe that this new React gizmo is fully accessible. Yet Uber can't be bothered to make efforts to get basic accessibility right on the page that tells us this. The main content is not in a <main> element, this <main> element being the landmark that tells people using assistive technologies where the main content is. Then the navigation links, e.g. in the footer are not in <nav> elements. The code sample in the middle is an image. It should be in a <figure>, <pre>formatted and in a <code> block for accessibility. It is a bit hypocritical to write an article about how wonderful your product is for accessibility and not make it accessible. |
|
What you're suggesting is that when someone releases a library with a commitment to accessibility, they are also responsible to reach out to some completely unrelated comms-focused team, take over their CMS workflow, rewrite it entirely with the new framework, and only then make a blog post about the thing you were trying to talk about.