fmaury/seirdy.one
1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-12-24 17:52:11 +00:00
Code Issues Projects Releases Wiki Activity

New note: 2022 almnac

Browse source
This commit is contained in:
Rohan Kumar 2022-10-10 21:37:53 -07:00
parent 1c031ce891
commit 14f0f75927
No known key found for this signature in database
GPG key ID: 1E892DB2A5F84479
1 changed files with 26 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
content/notes/2022-web-almanac-accessibility.md Normal file
View file

@ -0,0 +1,26 @@
---
title: "Reflections on the 2022 Web Almanac’s accessibility findings"
date: 2022-10-10T21:37:52-07:00
replyURI: "https://almanac.httparchive.org/en/2022/accessibility"
replyTitle: "Accessibility: The 2022 Web Almnac"
replyType: "TechArticle"
replyAuthor: "HTTP Archive"
replyAuthorURI: "https://httparchive.org/"
replyAuthorType: "Organization"
---
I have a few thoughts on these findings:
1. The Almanac says skip links commonly skip to the `<main>` element; I consider [large focusable containers an anti-pattern]({{<relref "/posts/website-best-practices.md#against-focusable-containers">}}) since they ruin keyboard navigability, and recommend skipping to a heading instead.
2. The Almanac identifies accessible live regions by `role="live"`. I'd suggest also looking into `role="feed"`, which represents a common type of live region.
Some common accessibility issues I'd be interested in for future editions:
- Contrast that's too high
- Setting custom foregrounds but not custom backgrounds, and vice versa
- Removing link underlines
- Focusable containers
- Using icon fonts without accessible names
Overall, it's a good look at the small subset of accessibility issues that are automatically detectable (most of which are far less critical than manually-detectable issues).