Here’s your delayed weekly a11y roundup. It’s a short one this week, as I’ve been on holiday for the last 10 days. Normal service shall be resumed next week!
Equal Entry Website Called Out as Inaccessible
- A bit of a clickbaity headline, describing how Equal Entry responded to a complaint that one of their web pages had 2 accessibility errors, which was the result of an automated tool and turned out to be all false positives. For example, one of the errors was that an input was missing a label, but it was a
textarea
used for visual spacing only. It hadaria-hidden="true"
, so it didn’t need a label. The post has a useful overview of how the consultancy conducts an accessibility test, with a reminder that aiming for a 100% pass rate can be a false prophet.
Why Deaf People Oppose Using Gene Editing to “Cure” Deafness
- Article suggesting that people who are deaf view themselves through the social model, rather than medical model, where societal barriers are the source of disability. It argues that an inaccessible society causes more harm than being deaf itself, and that there can be biological advantages to being deaf. ‘Deaf gain’, as it is known, includes being better able to accurately recognise faces, having faster peripheral vision reaction times, and perhaps some protection against Alzheimer’s. A gene that causes hereditary deafness may actually offer improved wound healing.
- Another excellent Adrian Roselli round-up, detailing the latest WCAG v2 proposal (deadline for comments by 18th September). There are 4 new Level A success criteria: 2.4.13 Fixed Reference Points, 3.2.6 Findable Help, 3.3.7 Accessible Authentication, 3.3.8 Redundant Entry, and existing criterion 2.4.7 Focus Visible has been ‘promoted’ from level AA to A. There are also 4 new Level AA criteria and one new Level AAA.
Did you know that you can subscribe to dai11y, week11y, fortnight11y or month11y updates! Every newsletter gets the same content; it is your choice to have short, regular emails or longer, less frequent ones. Curated with ♥ by developer @ChrisBAshton.