fortnight11y issue 47

Your fortnightly frequent11y newsletter, brought to you by @ChrisBAshton:

Picture of bump labels for keyboard. There's a bumpy red X over the right arrow key.
Image: Microsoft

Surface Adaptive Kit makes Microsoft’s laptops more accessible

  • Microsoft is creating a “Surface Adaptive Kit” for its range of laptops/tablets, to better accommodate people with disabilities.
  • The kit includes “keycap labels, bump labels, port indicators and device openers”.
  • For example, a device opener includes a pull tab and ring, to make it easier to open the laptop lid.
  • There’s no pricing information yet, but it is expected to launch this year.

Tips for Making HTML Lists Accessible

  • This article is a quick reminder on HTML list markup.
  • First of all, decide whether you actually need a list; sometimes it is better to format your content as paragraphs with headings instead. This way, assistive technology users can easily skip to the heading that they want to read.
  • If you do use a list, decide whether it should be unordered (<ul>), ordered (<ol>) or a description list (<dl>). The latter is useful for glossaries or recipes, e.g. <dl><dt>Chicken</dt><dd>A small bird that lays eggs</dd>...</dl>.

10 Video Games That Have Great Accessibility Options

There are some really interesting accessibility options in the games in this article:

  • Uncharted and The Last Of Us Part II are famously accessible, and are called out here.
  • A Blind Legend is a game that “can be played entirely through sound and only asks for touch screen or mouse input”. It does not incorporate visuals.
  • Grounded has the player shrunk to the size of an insect and having to find their way home across their back yard. The developers have considered arachnophobia – the intense fear of spiders – and thus offer an Arachnophobia Safe Mode Slider, allowing players to edit in-game spiders to have no legs, no eyes, or even no textures or sounds at all, without sacrificing the enemies’ difficulty.
  • Hyperdot is a game “where the player avoids incoming attacks by darting around the screen”. The game can be played on any controller, including eye trackers.

Does WAI-ARIA even work with WebXR?

As someone who has recently bought an Oculus Quest 2, this is really exciting technology that has come a long way in a very short time. It’s crucial that we address accessibility needs as this technology matures.

  • Thomas Logan writes about his experiment with ARIA and Web XR (“Web Extended Reality”, or VR).
  • He uses aframe-gui, a GUI component framework for A-Frame, which is a web framework for making 3D experiences. Here is Thomas’s demo.
  • Using ARIA to add the necessary role and aria-label to elements, as well as tabindex and onfocus handlers, Thomas has made an XR experience that is navigable via keyboard and by some assistive technology (AT) such as voice assisted navigation and screen readers. The full list of tested AT is in the article, which describes the usability issues encountered. For example, “Voice Control” on iOS/Safari does not detect the link or button in the demo.

This Brazilian pianist uses ‘bionic gloves’ to play

  • Pianist João Carlos Martins lost the use of his right hand in a mugging in Bulgaria in 1995.
  • Industrial designer Ubiratan Bizarro invented the “Bionic Extender Gloves”, which have rods that make the fingers spring back up after they depress the piano keys, allowing the pianist to continue playing.
  • The first pair of these gloves for Martins cost less than $100 to make, and are made by a 3D printer.
  • It has meant that Martins has been able to play his favorite Bach sonatas once more.

Twitter thread about “presentational list heuristics” by James Craig. The whole thing is worth a read, but here are the highlights:

  • There used to be a problem with too many lists for assistive tech users: “all I hear when reading news sites is ‘list, two items … end of list, list 4 items…’ and I don’t care about all the lists.”
  • This was caused by developers marking too much content up as lists, even when not appropriate.
  • Therefore, WebKit now applies some heuristics to these lists, to decide whether or not to expose the list semantics to the accessibility tree.
  • It considers whether the list has any bullet points. After all, if a sighted user doesn’t need to know it’s a list, then why should a screen reader user?
  • Similar principles are applied to table markup, which was regularly used for layouts in the early web.
  • “Many people think it’s only display: none; and visibility: hidden; but dozens, if not hundreds, of style characteristics contribute [to computing the accessibility tree].”
  • False positives are extremely rare. That said, developers can force the list semantics to be obeyed by applying role="list" to the <ul>/<ol>.

5 False Claims 1-Line “AI” Accessibility Script Vendors Make (video, 13m, or read the transcript)

  • Eric Eggert disputes five claims that companies [such as accessiBe] make about their products:
    1. “Accessibility can be fully automated”. Human judgement is required to determine what kind of alt text is appropriate in a given context.
    2. “AI solutions are effortless”. For you maybe, but the effort is simply shifted to the user, i.e. they now have to use the screen reader widget on your site rather than the native screen reader they’re used to.
    3. “These tools protect you from lawsuits”. Eric says that this is a scare tactic, and a poor motivator for implementing accessibility. Only 11,000 ADA Title III lawsuits happened in 2019, despite 98% of all websites not meeting WCAG 2.1, so the chance of being sued is statistically low.
    4. “It’s cheap”. These services cost $1,500 to $5,000 over a three year period of coverage. If you don’t renew, you lose those ‘benefits’, whereas if you pay an accessibility consultant to fix the problem at the source, the fix is permanent.
    5. “WCAG conformance. AA! 100%!”. Eric cites numerous examples of websites using these widgets, and still having accessibility violations. He summarises “I cannot fathom how they claim WCAG 2.1 AA accessibility.”

Colorblind Accessibility Manifesto

  • colorblindaccessibilitymanifesto.com lists 10 rules developers/designers should follow to not exclude the 350 million colourblind people in the world; nearly 8% of men and 0.4% of women.
    • Start with “Why?” [you are making the change in the first place]
    • Don’t communicate only with colors
    • Design with shapes
    • Choose the right copy
    • Test your designs in black and white
    • Rethink button states
    • Use contrast
    • The smaller the item, the bigger the problems
    • Less fancy, more usable
    • More than you think [have colourblindness]

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.

Loading...