Automated accessibility tools don’t catch HTML parsing errors

It would save a lot of time in the day of an accessibility practitioner if automated tools could catch more accessibility errors. However, I think it’s a reasonable assumption that they should catch errors with incorrect nesting of HTML or ARIA. Unfortunately this is not the case, and Adrian Roselli has a nice breakdown with tests on his blog:

Developers who build a broken thing, but do not have the necessary testing or even standards experience might rely on automated tools and produce problematic content as a result.

Source: Beware False Negatives | Adrian Roselli

Categorised as General

John Gruber on Annoying Sharing Bars

Over on Daring Fireball, John Gruber has some true words to say about those pesky floating sharing bars (or “dickbars” like he calls them) used by Medium and others.

A website should not fight the browser. Let the browser provide the chrome, and simply provide the content. Web developers know this is right — these dickbars are being rammed down their throats by SEO experts. The SEO folks are the same dopes who came up with the genius strategy of requiring 5-10 megabytes of privacy-intrusive CPU-intensive JavaScript on every page load that slows down websites. Now they come to their teams and say, “Our pages are too slow — we gotta move to AMP so our pages load fast.”

Categorised as General, Web

CSS Grid Layout and Accessibility

CSS Grid is the future. However just like with many other layout techniques, it’s very easy to go crazy with it and cause an accessibility nightmare. There’s an excellent article on MDN on potential pitfalls:

If at any time in the design process you find yourself using grid to relocate the position of an element, consider whether you should return to your document and make a change to the logical order too. 

Full article: