accessibility

 Accessibility  is the practice of designing so that people with disabilities can have equal access to information and functionality, applicable to both websites as well as physical environments.

In keeping with the IndieWeb principles that "UX and design is more important than protocols, formats, data models, schema etc.", it's important to make sure that one's site is inclusively "human readable" by as many people as possible.

While designers may create for themselves in pristine and ideal environments, readers using other devices/hardware in harsher environments or who may have various visual, auditory, or other deficits may not be able to access their content easily or at all.

Considerations
Accessibility is focused on removing barriers to enable broad access to tools, information, and community. With that in mind, it's worth remembering to consider the following, regardless of whether you are working in physical or digital spaces:


 * Visual: People with blindness or low vision may rely on alternative senses, most commonly auditory and/or touch, to access information and navigate the world; colour-blindness and various other vision impairments mean that colour and contrast must be considered carefully.
 * Auditory/Hearing: People who are deaf or hard of hearing may need alternative methods to access audio or verbal information, and may miss purely audio-related cues or alerts.
 * Motor Control: Many people are unable to use specific input methods. Some people lack the fine motor control needed to use computer mice, whilst others may be able to use them but only slowly. Others struggle with the precision of touch inputs, particularly on smaller mobile interfaces. Consider response times and support a variety of input methods.
 * Cognitive Disabilities: Mental illnesses and cognitive conditions can be triggered by certain stimuli, such as animations or loud noises. Appropriate warnings and overrides should be provided as necessary.
 * Neurodiversity: A large percentage of the population live with some form of learning disability or neurodivergence, which can cause distractibility, inability to remember, or make it harder to focus on large amounts of information.

IndieWeb Examples

 * IndieWebCamp Bellingham 2017 had an accessibility notice about wheelchair access on day 1 under the "Where" subheading.
 * IndieWebCamp London 2020 has an "Accessibility" subheading with information on wheelchair access, childcare, quiet/nursing rooms, gender-neutral toilets.

Links

 * Guidelines for Visualizing Links - TLDR; only underline links
 * On link underlines - TL;DR: In general, I recommend underlining links in body content. In the absence of a better style appropriate for a specific site, this is the way to go.

Color and Contrast
Designers should consider the following experiences when deciding on the contrast of text and other visual elements:
 * elderly users or those with bad vision
 * low quality monitors
 * bad lighting and glare
 * reading on tiny screens

Why:
 * has written an interesting article on How the Web Became Unreadable which discusses some interesting accessibility issues that lead to many users having difficulty seeing material on websites.
 * Contrast Rebellion gives some great motivation why contrast is important

Tools:
 * : Color and Contrast chart
 * Lea Verou: Contrast Ratio tool
 * WebAIM: Color Contrast Checker
 * Firefox Add-on: WCAG Contrast checker
 * Learn UI Design: Accessible Color Generator

Writing
Text can be a tricky balancing act. Whilst most assistive technologies deal with text well, the content is naturally quite personal. Everything from local linguistic quirks to how text is formatted can be important for authorial intent and honesty, but it can also make it harder to access for certain people.

It is best to be most considerate when writing for a broad audience – for example, with technical documentation or introductory guides.

Language
There are many ways to increase how easy a section of text is to read. Simplifying the language you use by replacing or explaining technical words or niche phrasing helps a lot for people with various cognitive disabilities. It also makes content more accessible to non-native speakers.

Shortening sentences often helps those with learning disabilities, like dyslexia. That can also benefit people with ADHD or other neurodivergences who can be easily distracted or lose focus.

Plain Text
Plain text (or plain language) is a style of writing designed to reduce barriers to information and content. It uses an everyday vocabulary, short sentences, and a simplified grammatical structure to ensure text is as easy to understand as possible, to the widest audience.

You can see a full example of an article translated into plain text here: What makes writing more readable?

Excerpt from the above before translation:

"The benefits of plain language aren’t limited to universally challenging texts like legal documents and tax forms. Even everyday writing, like news articles, can still pose a barrier for some readers."

And the same passage translated to plain text:

"Some kinds of writing are hard for everyone to read, like tax forms. But everyday writing, like the news, can be hard to read too."

See Also:


 * NiemanLab talks about ProPublica using "ultra-accessible plain language"

Font Choice
In general, sans-serif fonts tend to be easier to read:

"It has been found that sans-serif fonts improve readability for people with reading/learning difficulties like Dyslexia http://dyslexiahelp.umich.edu/sites/default/files/good_fonts_for_dyslexia_study.pdf @mmatuzo" @LeonieWatson October 9, 2019 source

There are also "hyper legible" fonts specifically designed to help low vision readers, such as Atkinson Hyperlegible, which is freely available for use from the Braille Institute. Some research has suggested that these may also have benefits for people with dyslexia, though more study is needed.

Line Length
People will often struggle to read particularly long or wide lines of text. In general, somewhere between 60 and 75 characters is considered the upper limit, but smaller can be better for those with certain learning disabilities.


 * See additional research with more nuanced outcomes:
 * And IndieWeb research on their personal site by : Fixing a line width issue on this blog

In CSS, line length can be limited using font-relative units such as,  , or. A common pattern is to set the main content of an article to around : Limit line length to increase readability

Text Descriptions
Images are inherently visual content, so providing text-based descriptions can be extremely useful.

On websites, this "alternative text" (frequently referred to as "alt text" and provided in HTML via the  property) can then be used by assistive technologies such as screenreaders, converting an image into an audio description or a braille readout.

Usefully, browsers will also expose the alt text if an image fails to load, providing a graceful fallback even for sighted users.

In printed media, descriptions are most often presented as captions, typically to one side or beneath an image.

For more specific best practices, further reading, and IndieWeb examples, see: alt text

Video & Audio Content
Much like with images, video and audio content can be made accessible to many more people by providing a text alternative.

"Podcasts, are, by nature, designed for the blind and the visually impaired because they are audio experiences."

Closed Captions
Video content should be captioned, particularly for speech. Text can be overlaid to appear as the video plays, preferably so that the words on-screen mirror what someone can hear.

Some tools will bake captions directly into the video file, either by saving them onto the frames themselves, or by providing the necessary metadata for video players to dynamically render the text as an overlay on top of the video. The latter is generally considered better, as it allows users to alter font and colour, as well as providing assistive technology and localisation tools with an effective transcript that can be translated into whatever the user needs.

Apart from speech, it is often useful to caption important sound effects, the emotionality of music (e.g. "sad music begins playing"), or even the absence of sound entirely ("[silence]"), so that context is not lost.

Captions allow the hard-of-hearing and deaf users to access otherwise meaningless content, but they also benefit people watching videos in noisy environments – such as during a commute – or if they lack sounds for other reasons, e.g. a broken speaker.

Transcripts
For purely audio-based content, such as podcasts, providing a text transcript is necessary to allow access to deaf and hard-of-hearing users.

Transcripts should contain all spoken language within an audio clip, as well as any additional context like sound effects and who is currently talking. Providing timestamps can be beneficial, depending on how the audio is being used.

As mentioned above, well-formatted closed captions can often double up as transcripts, particularly if timestamps are included. However, it is still beneficial to provide a transcript in text format (rather than purely as captions on a video), so that users can effectively read through a video. This has been shown to help people who retain visual sources better than auditory ones, and can significantly help people with various learning disabilities. On sites like YouTube, this can be achieved by adding a transcript to the description beneath a video.

It can also be beneficial for video content to provide descriptive transcripts, preferably within the speech transcript. These include key details about what's happening on-screen, in the same way that descriptive text works with images. For example:

[00:00] Description: The keynote speaker, Steve Jobs, walks onto a stage looking confident, wearing their trademark black turtleneck and jeans. A slide appears that reads "Introducing". Steve smiles. [00:10] "[Steve] Welcome to this year's event!" [00:25] "We've got some exciting news for you today."

See also: transcript

Animations & Sound Design
Animations can be triggering for certain cognitive disorders, leaving people feeling ill, dizzy, or even in pain. They are also distracting, meaning that people with ADHD or other disorders who may easily lose focus or attention can struggle to ignore them. Particularly quick or strobing motion may even trigger seizures.

Similarly, sound design (sound effects or background music) can cause people to lose their train of thought, struggle to focus on text or imagery in front of them, or – if particularly loud and sudden – be a trigger for PTSD and other mental illnesses. When poorly implemented, sound effects can also leave people confused or unsure of what has happened, resulting in anxiety and stress.

As a result, the general rule of thumb is to use animations and sound design sparingly and only where its purpose is clear. For example, having a button make a reassuring "click" when pressed provides meaningful auditory feedback and may even improve the accessibility of a user interface.

That said, it is always best to provide people with clear options to disable animations and mute sound effects. Where possible, using predefined settings, such as OS-level preferences, is also considered a good practice.

Physical Environments
Remember those with disabilities when setting up event spaces.
 * This is something that came to mind while planning IWC Bellingham and some of the event space is not wheelchair accessible. I'm researching and considering how to best advertise that clearly to potential attendees.

Event accessibility statement examples:
 * Beyond Tellerrand Terms of Service: Accessibility heading "Please contact us, if you want to attend at workshops or the conference and have any special requirements such as access for wheelchairs. We will do our very best to accommodate you."
 * Beyond Tellerrand Accessibility: "On this page you can find the accessibility information for the venues and this website."

More reading:
 * http://geekfeminism.wikia.com/wiki/Accessibility
 * http://geekfeminism.wikia.com/wiki/Cons_with_Accessibility_Policies
 * https://adata.org/publication/temporary-events-guide
 * http://opensourcebridge.org/wiki/Accessibility
 * Appears to be primarily software-related, but haven't gone through all the links yet
 * https://twitter.com/ellenfromnowon/status/846010218404306946 Ellen Murray's Twitter thread about accessibility information disabled people are looking for on event websites

Accessibility Overlays
In recent years a number of companies have released (normally paid-for) accessibility "plugins" that claim to be able to make websites accessible and/or meet specific WCAG or ADA compliance levels.

These services can be added to a website in a similar way to consent forms or chatbots. Most commonly, this means loading a third-party JavaScript file that then attempts to "fix" accessibility concerns by altering the web page before it is fully rendered in the browser. Some also provide a floating GUI "toolbox" that allows users to take accessibility-related actions, such as modifying the font size or UI colours. Examples include AccessiBe, UserWay, and EqualWeb.

Criticisms
Accessibility overlays are typically marketed as "one-click installs" or "quick fixes" that can solve all accessibility concerns. However, in practice, they have routinely been found to _decrease_ the accessibility of a given site or page, and the companies behind them are frequently caught up in controversies.

Common concerns include:
 * An over-reliance on JavaScript, particularly in ways that often conflict with assistive technologies like screen readers. Even where conflicts are well managed, client-side JavaScript can fail for other reasons, resulting in extremely broken user experiences (see js;dr).
 * Being too focused on legal compliance, rather than actual user needs.
 * Marketing one-size-fits-all solutions that result in frequent edge cases that break or degrade user experiences, particularly for people using assistive technology.

As a result, in May 2021 a large number of key accessibility specialists, experts, and disability rights activists signed an open letter discouraging the use of accessibility overlays: The Overlay Factsheet.

Additional Information

 * Accessibility advocates sign open letter urging people not to use AccessiBe and other overlay products - excellent write up of the release of the Overlay Factsheet and the history of overlays from WP Tavern.
 * Adrian Roselli's series "X Overlay Will Get You Sued", which shows how popular overlays fail at even their claims of legal compliance: Userway, AccessiBe, FACIliti.
 * Accessibility at the Edge W3C CG is an Overlay Smokescreen - looks into the formation of a W3C community group ("Accessibility at the Edge") founded by a collective of overlay vendors, seemingly as a way to garner positive publicity.
 * Should I Use An Accessibility Overlay?

Resources
Below is a list of useful resources to turn to when considering web accessibility:
 * W3C's Web Accessibility Initiative
 * How to meet WCAG Quick Reference
 * ARIA Authoring Practices Guide including examples for common UI patterns
 * Web Accessibility in Mind
 * software/tools
 * disability simulators
 * Survey of users with low vision
 * Survey of users with motor disabilities
 * An accessibility analysis of the top one million home pages (February 2019)
 * Accessibility Club
 * Wikipedia on Accessibility
 * Totally: An accessibility visualization toolkit

To Do
Several IndieWebCamps and even HWC meetings have included material and discussions on accessibility that could be transplanted onto this page.