Posted 11:48:26 AM. About GitHubAs the global home for all developers, GitHub is the complete AI-powered developer…See this and similar jobs on LinkedIn.
Over the last week, I’ve been seeing a wave of articles and Mastodon posts from people who I would consider advocates of React about how React is actually bad now.
The first one I saw was from Tom MacWright.
In this post Matt discusses 16 accessibility issues and solutions we've encountered while building a bi-lingual website application for a public sector…
React community appears to be finally starting to see how maybe, just maybe, things are a little overwrought and oversold for an abstraction that ultimately derives HTML.
I recently needed to test the support of a dynamic accessible description – a element’s description that is initially one (or no) value, then changes to…
This week, we’ve been looking at harmful complexity in web projects, and why choosing React for mostly static web projects is bad.
These days, it’s common for mostly static websites to have a little bit of dynamic content.
Recently, a post from the web performance monitoring tool DebugBear about why they won't report website carbon emissions in their platform caught my attention.
Yesterday, I discovered that quite a few of my articles have made their way onto Hacker News.
And the conversations around them are actually, generally speaking, pretty good for what I generally expect from the site.
I have some other questions in this area. Safari removes list semantics if you remove the bullets (with exceptions, such as if the list is a child of "nav"), due to alleged "list-itis". At what point do lists become inappropriate? If I have a list of blog posts, and I format them as cards, with a heading, publish date, summary, and an image, is that too much content for each <li>?
Also, MDN and WHATWG point out not all links should be contained in navs (such as footer links), and "nav" should instead signal major blocks of navigation links. Would my prior example of a list of blog posts count as a major block? Should I enclose my list of blog posts in a nav? Does that extend to all section, category, and tag pages listing pages in that section/category/tag?
Feel free to respond if you have opinions, but keep it civil, and boosts are appreciated.
While it is often sufficient to test the mobile view of websites and applications on the desktop, with desktop browsers, it’s sometimes not enough: Some websites use device sniffing to hash out which device is used and deliver different code to users…
“Search Engine Optimization” Blech. I hate it. This is what SEO should be: Write content on the internet. Make sure it is output in semantic, accessible HTML. Make sure the performance …
A follow-up to my talk at A11yTO I cannot pinpoint the source of this misconception, it could have been a vendor, or long-lost blog post, or one of the many webinars I attended in my early days as a program lead.
Accessible Chips demo — "modified to use the HTML datalist element instead of a custom autosuggest". Nice! kindhearted-meal.glitch.me/ By @mfairchild365 (and inspired by me 😁 ). This demo is actually 4 years old! Browser support (for datalist) is better. #webdev #html #a11y
This document is a practical guide for developers on how to add
accessibility information to HTML elements using the
Accessible Rich Internet Applications specification [WAI-ARIA-1.
Ensuring negative numbers are available for everyone. "The minus character (−) yields great support in most screen readers, and suffers less situational gotchas than the hyphen-minus character"
