#web content accessibility guidelines

[specialneedsalliance]

More than ever before, the internet has become the standard way of accessing information, performing required tasks, and participating in society in general. While many find this quick and convenient, it can be a struggle for those with disabilities. Thankfully, the Department of Justice (DOJ) has recently outlined regulations to ensure that everyone can use and navigate government websites effectively.

[akwyz]

Digital inaccessibility: Blind and low-vision people have powerful technology but still face barriers to the digital world.

Despite advances in assistive tech, the visually impaired face digital hurdles. Inaccessible websites & software limit job opportunities. Let's advocate for a fully accessible digital world. 🌍💼👁️ #DigitalInclusion #Accessibility #TechForAll #axschat

Screen reader software converts text to audio for people who are blind. Access Matters/Flickr, CC BY-NC-SA Michele McDonnall, Mississippi State University Imagine that you have low vision and you’re completing an online job application using screen reader software. You get through half the form and then come to a question with drop-down options the screen reader cannot access because the…

[adasitecompliance]

WCAG 2.2

Explore the latest in web accessibility with a guide to WCAG 2.2. Enhance your website's inclusivity and compliance!

[wip]

An Update on the Tumblr Android App

For those of you who access Tumblr through our Android app, we wanted to share that starting today you may see some differences for search queries and posts that may contain specific types of sensitive content. In order to comply with Google’s Play Store Guidelines, we have adjusted what you’re able to access as it relates to potentially sensitive content while using the Android app. 

To remain available within Google's Play Store, we have added more measures and limit exposure to potentially sensitive content in order to comply with their guidelines and to provide a safer experience to you. To learn more about Google’s Play Store Guidelines, click here. 

How you may experience these changes

When browsing Tumblr through Dashboard, Search, Communities and other surfaces you might experience less content and some searches might not produce any results unless you enable “show mature content” in Tumblr settings. Please refer to our Help Center article to learn more.

Why these changes are being made

We want to make sure Tumblr is available everywhere you would like to access it. In order for us to remain in Google’s Play Store and for our Tumblr Android app to be available, we needed to make changes that would help us be more compliant with Google’s policies around sensitive content. 

We understand that, for some of you, these changes may be very frustrating – we understand that frustration and we apologize for any disruption that these changes may cause. 

Who this impacts

These changes will only impact those who are accessing Tumblr through the Android app. If you are using our iOS app, accessing Tumblr through mobile web or online through tumblr.com, your experience will remain unchanged.

For more information on our guidelines or to understand these changes more fully, please visit:

Tumblr’s Community Guidelines

Tumblr’s Help Center

[uiexpertayyaj]

Web Accessibility in UI Design: Explore the principles and best practices of creating accessible user interfaces, ensuring inclusivity for users with disabilities.

In the expansive realm of user interface (UI) design, the commitment to inclusivity has become a central tenet. Web accessibility, the practice of designing and developing digital interfaces that can be used by people of all abilities, is crucial in ensuring that the digital landscape is accessible to everyone, regardless of their physical or cognitive capabilities. In this article, we delve into the principles and best practices of creating accessible user interfaces that prioritize inclusivity for users with disabilities.

Understanding Web Accessibility: Web accessibility encompasses the design and development of websites, applications, and digital tools that can be navigated and used by individuals with various disabilities. This includes but is not limited to visual, auditory, motor, and cognitive impairments. The goal is to remove barriers and provide an equitable digital experience for all users.

Principles of Web Accessibility: Perceivable, Operable, Understandable, Robust Best Practices for Web Accessibility in UI Design: Semantic HTML. Alternative Text for Images, Keyboard Navigation, Contrast and Readability, Captions and Transcripts, Focus Indicators, Form Accessibility, Avoiding Flashing Content, Testing with Assistive Technologies, Education and Awareness Conclusion: Web accessibility is not just a legal requirement; it is a moral imperative and a design philosophy that enriches the digital experience for everyone. By adhering to the principles of perceivability, operability, understandability, and robustness, and implementing best practices in UI design, designers can contribute to a digital landscape that is truly accessible to users of all abilities. In embracing the ethos of inclusivity, we move closer to a future where technology is a bridge rather than a barrier, ensuring that the benefits of the digital age are shared equitably among all individuals.

[calware]

i'm not sure if this is the most useful tool for doing this but it's the one that i currently like the most: contrast grid by eightshapes. this tool is useful for testing text colors on different backgrounds to see if they are accessible. this is so important because while you may be able to read the text on your blog/carrd/website/etc, not everyone can, and this site will tell you if your color combination meets the web content accessibility guidelines for color contrast

for example, here is the grid for my website (minus the graphics like the fake text files or the pesterlogs, which have preset colors). AAA means high contrast, AA means good contrast, AA18 means "only use for large or bold text, not body text" and DNP stands for Does Not Pass

there are a lot of other sites out there that can help you test your web colors, but i like this one because it allows you to enter your entire palette at once and see how each color interacts with the rest. it's also fun to name your colors and they all look nice laid out like this

this firefox extension is also very helpful; it allows you to click around a website and it'll tell you what passes and what doesn't

also, i should note that not *everything* has to pass 100%. for example, this blue-on-white doesn't pass:

it's just good to know what does and doesn't pass, and the more that passes, the better. just know that if something doesn't pass, some people might not be able to read it well

[anistarrose]

This post — written by Ashlee M. Boyer, an accessibility consultant who is disabled — is a short, enlightening read about how colleges are reacting to the new digital accessibility guidelines (WCAG 2.1) under the ADA.

From conversations I've had both online and with IRL acquaintances who work for my alma mater, I've gotten the impression of a lot of attention towards this issue right now, at the start of 2025. So, this felt like a good time to share this post. In particular, I'd like to highlight these paragraphs:

We can see it with physical accessibility at colleges too. Accessibility has been treated as a burden far more than it’s been treated as a priority. This has been thoroughly researched and discussed by (critical) disability studies scholars for several decades. Remediating a lot of inaccessible content may be a “painful” experience for colleges. But colleges won’t feel more pain than financial or reputational. People will bear the real pain. Either disabled people because colleges won’t comply with the rule, or the staff working to reach compliance because they will more than likely continue to be under-supported and under-funded.

[proton-selfships]

So I just read this great post by @kittyandco and it struck a really, really deep chord with me as someone who was also in the selfship community in ye olden days (as in, pre-pandemic olden days).

Now, don't get me wrong, those days weren't perfect either. I still experienced hostility for little reason, and it still hurts me to think about and affects my ability to trust people to this day. And I sure as hell wasn't the only one, or the one who had it the worst. But that lack of good faith that used to be the exception really does feel like the norm now, and it makes interacting way more stressful than it ever was back then. You're expected to read novella-length DNIs and can't interact with or follow anyone without fearing that you missed one of your fandoms on their DNI list and will get shit for it.

(And those pages are often confusing to navigate and use hard-to-read colors, to boot. Seriously, the Web Content Accessibility Guidelines should be mandatory reading for anyone making a Carrd or Rentry account)

And that's not even to mention the fear of what you say to someone in a private conversation getting twisted and shared and vagueposted about without your permission. That's something I've witnessed happen to multiple friends of mine. Again, isolated incidents back then, way more common than it should be now.

Meanwhile, *old woman voice* back in my day... What I always think back to was the really popular ask game that would go around, where you could ask whoever reblogged it to come up with headcanons for your F/Os. And people were sending each other asks left and right! People were excited to look up F/Os they'd never heard of to come up with a little pick-me-up for the person in their ask box! And I remember them being a blast to read and write!

Nowadays? If your F/Os are from sources that's not in the media zeitgeist or another limited set of perennial sources people will generally know enough to engage with... Good luck getting anyone to talk to you. (And that definitely goes double for anyone who ships with characters who aren't white men or isn't white themselves, that's a whole other issue that I've definitely experienced as a lesbian.)

I think it's both the growing atmosphere of hostility and social media in general's growing focus on "making content" and "branding" that keeps people from reaching out to each other unless they ship the same kinds of things they do. It's not really a community anymore. And that sucks, because that's a problem that's infected selfship spaces from the social media landscape as a whole

But I think we could still make the choice to see each other as people. Because, at the end of the day, selfshippers don't really have anywhere else to go. We're all just a bunch of people who carry love for characters in our hearts. Shouldn't we be willing to extend that love to each other, too?

(Obviously, this comes with caveats. I don't know if this is just me and my friends, but it also feels like we're all just too tired nowadays to reach out or meaningfully engage with other shippers' work. I'm definitely guilty of going MIA for long periods for that reason, so I'm not going to act like the lack of interaction with my blog specifically isn't my fault there. But in my experience I've seen a lot of that exhaustion come from this, from the walking on eggshells and the lack of reciprocity of the energy you put in, so it all still applies)

[bag-bang]

[ID: Event infographic for Be A Goldfish: A Ted Lasso Multimedia Microbang, dated 1 May to 30 June 2025. Across the middle, a variety of mediums are listed in three columns: "6-by-9s, meta, poetry, podfic, ficlets, drabbles, paintings, graphics, sketches, gifsets, icons, zines, playlists, fanvids, (web) weaves, recipes, crafts and more!"

The bottom left reads "Award banners and tokens, comment oriented, small fanworks, 750 words max, and no check-ins. A star in the bottom right reads "Sign up now!" /End ID]

Welcome to Be A Goldfish: A Ted Lasso Multimedia Microbang! This event is dedicated to small fanworks and taking the time to appreciate the little things.

This is a two-month event during which you may post as few or as many (micro) fanworks as you like, in any medium you desire. As well as leave some nice comments on any works created throughout.

You can read our full set of guidelines here, which includes multimedia guidelines, content restrictions, and image accessibility and comment resources.

As you create works and leave comments, fill out the Entry Submission and Comment Milestone forms as needed.

If posting works to tumblr, feel free to tag us directly and/or use the #beagoldfish 2025 tag. We also have a Dreamwidth Community and an AO3 Collection where you can share works and leave comments as desired.

And join our Discord, if you fancy it. There are general and opt-in NSFW content channels for sharing WIPs and finished works and calling for betas and pickers.

Sign up now!

Have any questions? Send us an Ask or an email. All answered asks can be found under our #bag.ask tag.

[songbird-at-the-fireside-chat]

Browsing the World Wide Web

Browsing the World Wide Web

One of my favorite passions is creating/finding ways to navigate the web that are healthy, authentic, and fun! Here are some resources I use to guide my internet usage. Some language has been slightly adapted for tone and accessibility. For more in-depth reading, follow the links! (taken with permission from https://yair.garden/browsing). Shared Ideals

MelonKing has an excellent list of shared ideals which I try to keep in mind as I browse the web. It's a great starting point!

Creativity is First: We see the ability to design, decorate, and graffiti digital spaces as essential and powerful.

The Internet is Fun: We want the Web to be a playground that's free to explore and enjoy.

Corporations are Boring: We are tired of the monetization, data abuse, and endless breaches of trust in corporate culture.

The Web is Friendly: We believe the Web should be friendly and supportive; caring is a radical act.

Right to Repair: We value the freedom to make, break, and repair our stuff - tinkering is a form of debate and protest.

One World Wide Web: We want free open knowledge and global connectivity, without paywalls, bubbles, or borders.

Chaotic Effort: We believe that value comes from the time and effort put into projects they love for no reason other than love.

No to Web3: In many (but not all) situations, cryptocurrencies, NFTs, unfairly trained AIs, and buzzword tech are unwelcome and uncool.

Manifesto for a New Web

The YesterWeb is an organization seeking to progressively transform internet culture and beyond. After two years, they created three core commitments and three social behavior guidelines to benefit everyone.

A commitment to social responsibility and partisanship.

A commitment to collective well-being and personal growth.

A commitment to rehumanizing social relations and reversing social alienation.

50 additional manifestos can be found here Social Etiquette

Engage in good faith.

Engage in constructive conflict.

Be mindful of participating in a shared, public space.

Why say no to Web 3.0?

One of the shared ideas of our community of web surfers is to push back against "Web 3.0". Here's why:

It's driven by predatory marketing tactics.

It requires complex technological and financial knowledge to fully understand.

It is actively harming the environment.

It caters to early adopters and whales.

It profits off artificial scarcity.

Investors are banking on Web3, and they really don't want to be wrong.

Personalized Web Surfing Guide

Make your web surfing personal and adventurous, away from corporate influences. Here's a simple guide for a unique browsing experience.

Configure your browser

Remove Ads and Clean up Privacy:

Ublock Origin for removing ads

ClearURLs for removing tracking elements from URLs

SponsorBlock for skipping sponsorships on YouTube

Make it a Safer Space:

ShinigamiEyes for highlighting transphobic/anti-LGBTQ sites

TriggerRemover for removing trigger-inducing content from pages

Clean up UI for Beauty and Minimalism:

CleanerReads for a muted Goodreads experience

Minimal; for a minimal and less attention-grabbing internet

Bonuses for a Cool Experience:

Library Extension: Check book availability at local libraries

Translate Web Pages: Translate pages in real-time

Return YouTube Dislike: Bring back the YouTube dislike feature

How to Browse and Surf the Web

Explore Beyond Corporate Sites: While the internet is vast, the majority of users only see a small fraction dominated by large corporate sites. These sites often prioritize shock value and extreme content, overshadowing the richness of the wider web. Explore alternative avenues to discover the internet's diversity.

Search Engines: Avoid corporate search engines like Google. Instead, consider using alternatives like Kagi, which focuses on privacy and doesn't sell your data. While it costs around $10/month, Kagi offers a diverse mix of web content, making it a worthwhile investment for varied search results. Other niche or non-commercial search engines can also provide unique content. While they may not be sustainable for daily use, they're great for discovering new sites. Find them here.

Webrings: Webrings are collections of websites united by a common theme or topic. They offer a unique way to explore sites created by real people, spanning a wide range of interests. Here are some of my favorite webrings:

Hotline Webring

Retro Webring

Low Tech Webring

Geek Webring

Soft Heart Clinic Mental Health Circle ...and here are some list of webring databases to explore!

Curated List of 64 Webrings

Neocities Webrings

Curated List of Active Webrings

Comprehensive List of 210 Webrings

Cliques/Fanlistings Web Cliques/Cliques are groups which you can join usually if you fulfill a certain task such as choosing an animal or listing your astrological sign. Fanlistings do the same for fans of various topics! You can then be linked on the clique's/fan group's site for further website discovery! Here are some web clique directories:

Project Clique

Cliqued

Fanlistings Network

5. Link Directories

Many sites have smaller link directories of buttons where you can find sites that they are "mutuals" (both creators follow each other) and "friends/neighbors" — sites they follow. It's a great way to build community. There are also larger link directories of sites which someone finds cool, and it's a great way to intentionally explore the web. Here are some of my favorites:

SadGrl Links

Melonland Surf Club

Neocities Sites

Onio.Cafe

Though there are many more! 6. Random Site Generators

Finally, there are random site generators which allow you to randomly stumble upon websites. While not very practical, they are a lot of fun and offer a unique way to discover new corners of the web.

A list can be found here

What now?

The next question you have is probably how can you become an active member/contribute in this world of the underground web? I unfortunately don't have the energy to write a guide right now but it will come soon! In broad strokes, consider making a site on Neocities. If you do make a site, remember to include a robots.txt file to get AI and bots out of there and don't forget to rate your site so we can know who it's for. If you'd like to transition off social media I recommend an RSS Reader such as the one at 32bit.cafe or on Fraidycat (guide on this to come soon as well!). For your twitter-fix you can always post a status at Status Cafe and your mood at imood. There is a whole world out there full of passionate and friendly people who are ready to reclaim the web. Excited to see you there!

[gamerwoman3d]

Listen, if Ed Boon asked me to write official tie-in novel filth for Mortal Kombat, I would. I don't care if he sends a studio note that says "If you make Sub-Zero any gayer I'll rip your fucking head off," I'd still work for him. Who needs a head anyways. Love that guy.

Anyways here's a wonderwall of filth.

[🔞🔞🔞Check below the cut🔞🔞🔞]

Explicit, Spicy, Juicy, and definitely🔞🔞🔞past this point

I should mention- You can actually read all of my writings directly on my masterlist without logging in to tumblr.

◜Sub-Zero, Smoke, Liu Kang options - Please Be Bi-Han 🙏◞

Just use any browser app and type in mk1erotica.netlify.app in the browser's address bar to access my masterlist from anywhere on any device.

Yes. Any device. This may even work on an Apple watch, on the Parrity browser. You can probably ask Siri to open a browser and navigate to the masterlist. You can use any browser. You can use Safari, Chrome, Brave, Firefox, Microsoft Edge. It can work on a Roku if you have a web browser like Web Browser X or Xfinity. It will run on ųBrowser or Opera. But I recommend DuckDuckGo!

Multi-Character Choose your own MK1 Adventure

Reptile [Syzoth, MK1 Version]

◜ mk1 men using their powers in the bedroom part 1 of ?◞

Sub-Zero [Bi-han, MK1 version]

Neck tattoo imagines parts 1 2 AND 3

◜ mk1 men using their powers in the bedroom part 2 of ?◞

◜ mk1 men using their powers in the bedroom part 2 of ?◞

◜I Need Attention◞

◜mk1 Sub-Zero: sexiest angst trope?◞

Johnny Cage [MK1 Version]

◜ mk1 men kinks & darker motivations part 2 of ?◞

Scorpion [Kuai Liang, MK1 version]

Beta Tester [Can be read as Hanzo if you're imaginative]

Bloody Horny Kuai Liang Scorpion - https://www.tumblr.com/gamerwoman3d/737285442221801472/%F0%9D%9F%B9

BONUS MATERIAL

Skins That Would Be in MK1 If I Had A Voodoo Doll of Ed Boon [Fun, Sexy skins for Kenshi, Scorpion, Kitana, & Sub-Zero]

The Gollum Test [Essay about writing better x readers]

Sub-Zero Long Hair Posts[linked without box because of tumblr post limitations]

Part 2 : Sub-Zero Long Hair Posts[linked without box because of tumblr post limitations]

Other horny drabbles [separate list]

About This Blog [links to post about guidelines reqs etc]

[Need more MK1 smut? Check the pin 📌]

Permissions summary: YOU HAVE MY EXPRESSED PERMISSION TO USE ANY SCREENSHOTS, GIFS, ASSETS OR CONTENT THAT I HAVE MADE OF THE GAME MK1 [MORTAL KOMBAT 1 (2023)]. EVERYONE has my enthusiastic consent. You don't have to make something I *enjoy* with those assets. You're under no obligation to please me with your content, even if it's made with bits of my content. Enjoy yourselves, go wild! Any MK1 screenshots or gifs that I make can be used for your fanworks as long as you have the legal rights to do so. [I'm pretty sure you all have the legal right to make any fanart/icons/reposts/headers/photo edits/collages/parody that you like, but I do not know every single law for every country. You're on your own to research whether you'd get in trouble for SubScorp art in Indonesia or the PRC or Alabama or wherever you are where all the rules get weird. But as long as you're not getting punished for using my MK1 gameplay in your work, go nuts! You have my permission to use the assets I've made from the game.]

[fastenoffyal]

"Amplifying the leadership of persons with disabilities for an inclusive and sustainable future"

December 3 is the International Day for Persons with Disabilities. This day promotes an understanding of disability issues, and mobilizes support for the dignity, rights, and well-being of people with disabilities. We're big into this kind of support - it's one of the principles (perhaps the most crucial principle!) upon which our event was founded. Accessibility - true accessibility - is so much more than wheelchair ramps and alt text on webpage images. We encourage everybody to learn more. To that end, we're highlighting some terrific relevant resources, including resources related to the fibre arts, and some links to help you search for makers with disabilities.

The UN's webpage on the IDPD

Accessibility resources from Accessibility Services Canada (tons of great resources linked to from here)

W3C's Web Content Accessibility Guidelines (WCAG) 2.0

Accessibility & inclusivity articles from Digits & Threads

Why accessibility is important in the crafting world

Accessibility resources from experts and PWD

Return on Disability's 2024 annual report

FOYAL 2024 participating designers with disabilities

Yarn Database's designer search (you can filter for designers with disabilities)

[adasitecompliance]

Web Content Accessibility Guidelines

WCAG 2.2: Decoding The Latest Web Accessibility Guidelines

In the ever-evolving digital landscape, accessibility has become a non-negotiable imperative for all users. The updated and latest Web Content Accessibility Guidelines (WCAG) 2.2, released in October 2023, stands as a beacon of inclusivity, providing comprehensive guidelines for making web content accessible to people with disabilities. Moreover, lawsuits against businesses with non-compliant websites have proliferated. According to ADA attorney Nolan Klein, thousands of ADA lawsuits have been filed in federal court alleging non-compliance with WCAG standards. Implementation of WCAG 2.2 standards is therefore critical not only for inclusivity but also for proper litigation risk management. As we explore WCAG 2.2 and its anticipated updates in 2023, this article aims to simplify its complexities, shedding light on the importance of web accessibility for the general public.

What is Web Accessibility?

In today’s interconnected world, the Internet has become indispensable for communication, education, employment, and social engagement. Practically everyone turns to the internet for a solution to all their queries, be they booking tickets, job opportunities, or making purchases. However, for individuals with disabilities, the web can present a daunting landscape of barriers, hindering their ability to participate in the digital sphere fully. This is where web accessibility comes into play. It is the practice of designing and developing websites and web applications so that even people with disabilities can easily and comfortably access and use them. By removing accessibility barriers and ensuring that web content is perceivable, operable, understandable, and robust, web accessibility promotes inclusivity and empowers individuals with disabilities to navigate the digital world quickly.

The Significance of Web Accessibility

The importance of a strong web accessibility initiative cannot be overstated. It is a fundamental human right enshrined in the United Nations Convention on the Rights of Persons with Disabilities (CRPD). Moreover, web accessibility makes good business sense. By catering to a broader audience, businesses can expand their customer base, enhance their brand reputation, and gain a competitive edge.

Impact on Diverse User Experiences

Web accessibility considerations extend far beyond the realm of disabilities. They encompass a broad spectrum of user experiences, including those related to age, language barriers, and situational impairments. Examples of situational impairments include watching videos with only audio in libraries or those with stubby fingers preferring larger call-to-action buttons. By designing websites that are inclusive and accessible to all, we can create a more equitable and user-friendly digital landscape.

W3C Releases: Shaping the Evolution of Accessibility

The World Wide Web Consortium (W3C) plays a pivotal role in developing and maintaining WCAG, ensuring that the guidelines remain relevant and effective in the face of evolving technologies and user needs. The WCAG 2.2 was developed through the W3C process with other individuals and worldwide organizations to provide web content accessibility guidelines that meet international governments’, organizations’, and individuals’ accessibility needs. The W3C recommends using the WCAG 2.2 as a standard for the web.And thus provides the necessary resources and training as guidance and clarity on implementing WCAG.

WCAG 2.2: A New Standard for Web Accessibility

In October 2023, the World Wide Web Consortium (W3C) released WCAG 2.2, the latest iteration of the Web Content Accessibility Guidelines. The WCAG 2.2 is built on WCAG 2.0 and 2.1, the previous versions were built on WCAG 1.0, designed to apply different present and future technologies and tested through manual and automated testing. The update incorporates new WCAG success criteria and techniques, addressing the evolving needs of users with cognitive, language, and learning disabilities and reflecting advancements in web technologies.

WCAG 2.2 and Its Relevance

The release of WCAG 2.2 marks a significant step forward in pursuing web accessibility. By adopting these guidelines, web developers, content creators, and organizations ensure their digital products and services are accessible to a wider audience, fostering a more inclusive and equitable online experience.

Multiple Layers of Guidance

The various individuals and organizations using WCAG include policymakers, web designers, teachers, and students. Thus, multiple layers of guidance meet this varied audience’s comprehensive needs. These layers include:

Overall Principles

The foundation of WCAG 2.2 rests upon four fundamental principles: perceivable, operable, understandable, and robust. These principles, each encompassing specific guidelines and measurable success criteria, form the cornerstone of accessible web content.

Perceivable: Content must be presented so that users with visual, auditory, or other sensory impairments can perceive it.

Operable: Users with diverse abilities, including motor and speech impairments, must be able to operate a user interface component and navigate content effectively.

Understandable: Content must be presented clearly and unambiguously so that users with cognitive, learning, or language disabilities can comprehend it easily.

Robust: Content must remain accessible across all various assistive technology and user environments.

General Guidelines

These come next and are the 13 guidelines providing the goals authors adhere to for making content more accessible to users with different disabilities. While they aren’t testable, they provide the basic framework for authors to understand success criteria and, thus, better implement techniques.

Testable Success Criteria

Each guideline has testable success criteria to ensure WCAG 2.2 is used wherever requirements and performance testing are required. This includes design specifications, contractual agreements, and purchasing. WCAG 2.2 defines three levels of conformance level: A, AA, and AAA, each representing a progressive level of accessibility in different groups and situations.

Level A: The minimum level of accessibility, ensuring basic functionality for all users.

Level AA: A higher level of conformance, addressing the needs of many disabled users. It is considered the recommended level for most websites.

Level AAA: The most stringent level, catering to a wider range of disabilities and user preferences. It is often considered an aspirational goal for websites.

Sufficient and Advisory Techniques

Various techniques are used for each guideline and success criterion in WCAG 2.2, divided into two categories. Sufficient techniques for meeting success criteria and advisory techniques that let authors go beyond the individual success criteria to address guidelines better. They may address accessibility problems or barriers the testable success criteria do not cover. These layers of guidance together guide web developers to make content more accessible by applying as many layers as possible. This includes including advisory techniques so that the content addresses the needs of most users.

WCAG 2.2: A Watershed Moment in Digital Accessibility

WCAG 2.2 addresses the ever-changing technological landscape and evolving user needs, thus emerging as a pivotal step forward from its predecessor, WCAG 2.1. This enhanced iteration introduces nine tool accessibility guidelines and new success criteria meticulously crafted to enhance accessibility for users with visual, physical, and cognitive disabilities. These additional success criteria encourage:

1. Improved Focus Management

WCAG 2.2 introduces three enhanced focus management success criteria catering to users with motor impairments. These success criteria enable users to navigate web content smoothly and efficiently. These success criteria are:

2.4.11 Focus Not Obscured (Minimum) (AA): According to this success criterion, there might be some degree of hiding or obscuring keyboard-focused user interface components like buttons or links in a website or app design.

2.4.12 Focus Not Obscured (Enhanced) (AAA): According to this success criterion, content web developers create, like website and app design, cannot hide any part of keyword-focused user interface components.

2.4.13 Focus Appearance (AAA): According to this success criterion, visible keyboard focus indicator parts must be a minimum of a 2 CSS pixel thick perimeter of unfocused components or sub-components. They should also have a minimal 3:1 ratio between pixels in focused and unfocused states.

2. Enhanced Touch Input Support

Recognizing the growing prevalence of touch-enabled devices, WCAG 2.2 introduces refined guidelines for touch input and page break navigation. This ensures seamless interaction for users with limited or no mouse interaction. These success criteria are:

2.5.7 Dragging Movements (AA)

According to this success criterion, a single pointer can perform dragging movements without dragging. Exceptions are when dragging is crucial to the functionality or the user agent dictates the functionality and remains unaltered by the author.

2.5.8 Target Size (Minimum) (AA)

According to this success criterion, the minimum size for pointer input targets is 24 by 24 CSS pixels, with exceptions in:

Spacing: Targets smaller than 24 by 24 CSS pixels can be positioned so that, if a 24 CSS pixel diameter circle is centered on each target’s bounding box, the circles do not intersect with other targets.

Equivalent: The same function can be accomplished through a different control on the same page, meeting the 24 by 24 CSS pixel criterion.

Inline: The target is within a sentence, or its size is constrained by the line height of non-target text.

User-agent control: The user agent determines the target size and remains unaltered by the author.

Essential: A specific presentation of the target is deemed essential or is legally required for conveying the information.

3. Clearer Color Contrast Guidance

WCAG 2.2 provides clearer and more stringent guidelines for color contrast to address the needs of low-vision users. It thus ensures text is easily distinguishable from its background. These success criteria are:

3.2.6 Consistent Help (A)

According to this success criterion, if web pages include certain help mechanisms like human contact details, human contact mechanisms, self-help options, and fully automated contact mechanisms, they should maintain a consistent order across multiple pages unless a user-initiated change occurs.

3.3.7 Redundant Entry (A)

According to this success criterion, user-provided information that must be repeatedly entered in the same process is auto-populated or made available for the user to select. Exceptions are when:

Re-entering the information is deemed essential

The information is necessary for ensuring content security

The previously entered information is no longer valid

3.3.8 Accessible Authentication (Minimum) (AA)

According to this success criterion, an authentication process does not mandate cognitive function tests like remembering a password or solving a puzzle. Exceptions are when the step offers at least one of the following:

Alternative: Another authentication method that doesn’t involve a cognitive function test.

Mechanism: A mechanism aids the user in completing the cognitive function test.

Object Recognition: The cognitive function test involves recognizing objects.

Personal Content: The cognitive function test identifies non-text content the user provides to the website.

3.3.9 Accessible Authentication (Enhanced) (AAA)

According to this success criterion, cognitive function tests, like recalling a password or solving a puzzle, are not obligatory at any stage in an authentication process unless the step offers either:

Alternative: An alternative authentication method not dependent on a cognitive function test.

Mechanism: A mechanism is accessible to aid the user in completing the cognitive function test.

The new success criteria may reference new terms that have also been added to the glossary and form part of the normative requirements of the success criteria. WCAG 2.2 also introduces new sections detailing aspects of specifications impacting privacy and security.

Was Any Success Criterion Removed from WCAG 2.2?

Yes, the success criterion 4.1.1 Parsing was removed from WCAG 2.2. It was removed as it was considered obsolete due to the advancements in web technology. Besides, new success criteria in WCAG 2.2 provide a more robust and up-to-date approach to ensuring accessible web content to disabled users. Here is why 4.1.1 Parsing was removed from WCAG 2.2:

It was primarily focused on older technologies, such as HTML 4.0 and earlier versions of XHTML, which are no longer widely used.

It was not well-defined and could be interpreted differently, leading to inconsistencies in implementation.

It was not as effective as other success criteria in ensuring that web content is parsable by user agents.

Removing 4.1.1 Parsing from WCAG 2.2 does not mean the parsing issue is no longer important. However, the new success criteria in WCAG 2.2 provide a more comprehensive and effective way to address this issue.

WCAG 2.1 vs. WCAG 2.2- The Differences

The latest Web Content Accessibility Guidelines, WCAG 2,2, builds upon its predecessor, WCAG 2.1, to further enhance web accessibility for people with disabilities. While WCAG 2.1 laid a solid foundation for accessible web development, WCAG 2.2 introduces new success criteria, refines existing guidelines, and provides clearer instructions to make accessibility more achievable and maintainable. There are thus these five major differences between the two:

1. New Success Criteria in WCAG 2.2

WCAG 2.2 introduces nine additional success criteria, addressing areas such as:

Focus appearance: Ensuring that focus indicators are sufficiently visible and distinguishable to aid navigation for users with low vision or cognitive disabilities.

Page break navigation: Providing clear and consistent mechanisms for navigating between page breaks, particularly for users who rely on screen readers or keyboard navigation.

Dragging movements: Making drag-and-drop interactions accessible to users with motor disabilities by providing adequate target sizes and clear visual feedback.

Consistent help: Providing consistent and easily accessible help or support mechanisms throughout the website or application.

Visible controls: Ensuring that all controls, including form fields and buttons, are clearly visible and distinguishable even to low-vision users.

These new success criteria reflect the evolving technological landscape and a deeper understanding of user needs, particularly those with cognitive disabilities.

2. Enhanced Mobile Accessibility

WCAG 2.2 continues to refine mobile accessibility guidelines, recognizing the growing prevalence of mobile devices and the need for websites and applications to be accessible across all platforms. This includes improvements in:

Touch target sizes: Ensuring touch targets are large enough and spaced appropriately to accommodate ease of use to users with motor disabilities or limited dexterity.

Input modalities: Providing alternative input modalities, such as voice control or keyboard navigation, to cater to users with different physical abilities.

Context-aware activation: Preventing unintentional activation of elements, such as pop-ups or overlays, that could hinder navigation for users with cognitive disabilities.

3. Improved Usability and Clarity

WCAG 2.2 aims to make the guidelines more user-friendly and actionable for developers and content creators through:

More explicit guidelines: Provide clearer and more explicit instructions for each success criterion to reduce the need for interpretation and ensure consistent implementation.

Additional examples: Offer more comprehensive and illustrative examples to demonstrate how to meet each success criterion in real-world scenarios.

Improved organization: Structuring the guidelines more logically and intuitively makes it easier for developers to find the information they need.

4. Backward Compatibility and Continuous Evolution

WCAG 2.2 maintains backward compatibility with WCAG 2.1, meaning that websites and applications conforming to WCAG 2.2 also adhere to WCAG 2.1 accessibility standards. This ensures that accessibility efforts are not lost with each new guidelines version. As technology and user needs evolve, WCAG will adapt and refine its guidelines to ensure that the web remains an inclusive and accessible space for all.

5. Removal of One Success Criterion

The success criterion 4.1.1 Parsing was removed from WCAG 2.2 as it was considered obsolete compared to web technology advancements. Besides, new additional success criteria in WCAG 2.2 ensure web content is accessible to users with disabilities.

Impact on User Experience

As always, the WCAG 2.2 offers an improved user experience, rendering digital content more user-friendly and inclusive for everyone, including users with disabilities. By adhering to the latest WCAG 2.2 guidelines, websites, and digital platforms become more accessible to all their users and visitors, regardless of their abilities. It doesn’t matter what disability the user may have or where they are, they can easily navigate, comprehend, and interact with the digital content. This is thus a win-win situation for both users and web developers. For example, visually impaired users easily navigate websites with images with alt text. In addition to improved accessibility, the alt text helps with SEO, thus improving the digital platform’s SEO rankings. Similarly, users with physical impairments and, in general, all users can easily navigate websites that are keyboard-navigable.

WCAG and Its Benefits for Businesses:

Embracing web accessibility guidelines should never be considered a waste of time or investment. It’s because web accessibility perfectly aligns with any and every business’s interests. It offers benefits like:

Broader Customer Base

Not only does WCAG 2.2 ensure everyone has equal access to the web, but the additional success criteria in WCAG 2.2 address additional disabilities to foster a broader customer base. People with disabilities form a major part of any website visitors. They will not be able to use or visit inaccessible websites. This, in turn, prevents them from accessing important information or performing important tasks like applying for jobs, booking tickets, or making purchases.

Increased Compliance

Adhering to WCAG 2.2 guidelines helps businesses and organizations comply with legal standards like accessibility laws and regulations protecting the rights of users with disabilities. Examples include the Americans with Disabilities Act (ADA), Section 508 of the Rehabilitation Act, and the European Web Directive. With businesses adhering to the latest WCAG 2.2, there are reduced chances of users filing cases for inaccessibility. Businesses thus save money by avoiding lawsuits. Besides, by ensuring equal access to users with disabilities, organizations and businesses contribute to creating a more inclusive and equitable digital environment for all.

Common Challenges in WCAG 2.2 Implementation and Useful Solutions:

Implementing WCAG 2.2 can be complex and challenging for businesses and organizations, as incorporating them into web development and maintenance processes can pose significant hurdles.

5 Common Challenges Businesses Face

The five common challenges faced by most businesses and web developers while implementing WCAG 2.2 include:

Lack of Awareness and Understanding: Many businesses and organizations lack a comprehensive understanding of WCAG 2.2 and its implications for their websites and applications. This lack of knowledge can lead to unintentional non-compliance and potential legal issues.

Resource Constraints: Implementing WCAG 2.2 often requires significant financial and human resources. Businesses may need to allocate additional funds for accessibility testing, training, and software tools while dedicating staff time to address accessibility issues.

Legacy Technology and Codebases: Websites and applications built on older technologies or with complex codebases may be more challenging to adapt to WCAG 2.2 standards. This can require extensive, time-consuming, and costly refactoring and code remediation.

Content Management Systems (CMS) and Third-party Tools: Integrating WCAG 2.2 compliance into CMS and third-party tools can be tricky, especially in tools lacking built-in accessibility features.

Ongoing Maintenance and Testing: WCAG 2.2 compliance is not a one-time project. It requires ongoing maintenance and testing to ensure new content and updates adhere to the guidelines. This can add to the ongoing costs and resource demands for maintaining an accessible website.

Practical Solutions to Overcome Challenges

The good news is that there are practical solutions that web developers can easily use to overcome these challenges. They include:

Educating and Training Staff: Regular training sessions for web developers, designers, and content creators raise awareness of WCAG 2.2 guidelines and best practices.

This helps ensure that accessibility considerations are integrated into all web development and maintenance aspects.

Prioritize Accessibility from the Start: Incorporating accessibility considerations into web development projects’ planning and design phases helps.

This proactive approach can help identify and address potential accessibility issues early on, thus preventing costly retrofits later.

Utilize Accessibility Testing Tools: Employing automated accessibility testing tools to identify and troubleshoot accessibility issues throughout the development process also helps.

These tools can provide valuable insights and help streamline the remediation process.

Choose Accessible CMS and Third-party Tools: When selecting CMS and third-party tools, prioritize those that offer built-in accessibility features and support WCAG 2.2 compliance.

This can save time and effort in the long run. Businesses may need to customize these tools or find alternative solutions that meet accessibility requirements.

Establish an Accessibility Workflow: Implementing a clear accessibility workflow that outlines roles, responsibilities, and procedures for ensuring and maintaining WCAG 2.2 compliance helps.

This will help keep accessibility at the forefront of web development and maintenance.

Clearing Common WCAG 2.2 Implementation Misconceptions

A few common misconceptions about implementing WCAG 2.2 discourage web developers from implementing them. Here are 5 common misconceptions dispelled:

Accessibility is Expensive: True

Yes, implementing WCAG 2.2 can involve upfront costs. However, the long-term benefits of an accessible website outweigh these expenses. An accessible website can increase user engagement, improve brand reputation, and reduce the risk of legal issues.

Accessibility is Only for People with Disabilities: False

Accessibility benefits everyone, not just those with disabilities. An accessible website is more user-friendly and usable for all, regardless of their abilities or limitations.

Accessibility is Too Technical: True

While some technical expertise is required to implement WCAG 2.2, accessibility is not solely a technical issue. It requires collaboration between designers, developers, content creators, and stakeholders to ensure a truly accessible user experience.

Accessibility Can Wait: False

Accessibility should not be an afterthought for website owners. It is essential to integrate accessibility considerations into all web development and maintenance phases. Addressing accessibility early on can save time and resources in the long run.

Accessibility is Binary: False

Accessibility is not a pass-fail situation but a spectrum of conformance levels. Businesses should strive to achieve the highest level of accessibility possible, as even incremental improvements can make a significant difference for users with disabilities.

Conclusion

WCAG 2.2 marks a significant milestone in pursuing digital accessibility by addressing more accessibility needs. It builds on WCAG 2.1 by adding new guidelines and success criteria and clarifying and updating existing ones. It makes the web more accessible and offers a roadmap for creating inclusive and user-friendly websites for individuals with diverse abilities. By adhering to these guidelines, web developers, content creators, and organizations play a pivotal role in bridging the digital divide, thus ensuring everyone has equal access to digital content across the internet.

Web Content Accessibility Guidelines Experts – ADA Site Compliance

Contact ADA Site Compliance today for all your ADA website compliance and website accessibility needs! Get your FREE SITE SCAN now. We are leaders in assistive technologies and making all your websites accessible.

[geekysciencemom]

I wanted to get the word out about what is currently happening in regards to Section 504.

Section 504 is an important law that protects people with disabilities. Section 504 says you can’t discriminate against disabled people if you get money from the United States government.

Schools have their own rules regarding Section 504. Students who don't qualify for an IEP will often be placed on a 504 Plan. This plan helps make the learning environment accessible to the student who has the plan. Within this plan, you will find the accommodations that the student needs to be successful at school. A student can have academic accommodations in both the K-12 and college settings. College students can also get living accommodations if they live on campus. People can also request accommodations in the work place.

Health and Human Services have their own rules for people with disabilities when it comes to providing access to medical health care, this includes dentists and behavioral health. There is a wide range of accommodations that health providers are required to provide under Section 504.

This is all thanks to the Rehabilitation Act of 1973, which Section 504 is included, and the Americans with Disabilities Act (ADA), which is attached to Section 504.

Section 504 regulations were signed in 1977. Last year, the rule was updated. This was done due to what happened during the height of the COVID-19 pandemic.

Among other important protections, the rule now covers:

Discrimination in medical treatment: The rule addresses discrimination in medical care and ensures that medical treatment decisions are not based on biases or stereotypes about people with disabilities, judgments that an individual will be a burden on others, or beliefs that the life of an individual with a disability has less value than the life of a person without a disability. These include, for example, decisions about life-sustaining treatment, organ transplantation, and rationing care in emergencies.

Community integration: The rule clarifies obligations to provide services in the most integrated setting appropriate to the needs of individuals with disabilities, consistent with the Supreme Court’s decision in Olmstead v. L.C.

Accessibility of medical equipment: The rule adopts the U.S. Access Board’s accessibility standards for medical equipment to address barriers to care, like exam tables that are inaccessible because they are not height-adjustable, weight scales that cannot accommodate people in wheelchairs, and mammogram machines that require an individual to stand to use them. The rule requires most doctors’ offices to have an accessible exam table and weight scale within two years.

Web, mobile app, and kiosk accessibility: The rule adopts the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA accessibility standards for websites and mobile applications. It also requires web-enabled systems in self-service kiosks in medical providers’ offices to be accessible. These provisions are particularly important given the increased use of websites, apps, telehealth, video platforms, and self-service kiosks to access health care.

Value assessment methods: Value assessment methods are often used to decide whether a medical treatment will be provided and under what circumstances. The rule prohibits the use of any measure, assessment, or tool that discounts the value of a life extension on the basis of disability to deny, limit, or otherwise condition access to an aid, benefit, or service.

Section 504 is now under attack. There is a court case happening right now where 17 states are trying to end Section 504. If they succeed in ending this foundational law, the laws attached to it (the ADA and civil rights laws pertaining to race and sex) will be in jeopardy.

The Disability Rights Education and Defense Fund (DREDF) provides additional information about the court case as well as steps to take to protect Section 504.

"This page explains what the lawsuit Texas v. Becerra is, how Texas v. Becerra threatens Section 504, and why Section 504 is important. Further down on this page, learn what you can do to help."

[mariacallous]

Researchers found a vulnerability in a Kia web portal that allowed them to track millions of cars, unlock doors, honk horns, and even start engines in seconds, just by reading the car's license plate. The findings are the latest in a string of web bugs that have impacted dozen of carmakers. Meanwhile, a handful of Tesla Cybertrucks have been outfitted for war and are literally being-battle tested by Chechen forces fighting in Ukraine as part of Russia’s ongoing invasion.

As Israel escalates its attacks on Lebanon, civilians on both sides of the conflict have been receiving ominous text messages—and authorities in each country are accusing the other of psychological warfare. The US government has increasingly condemned Russia-backed media outlets like RT for working closely with Russian intelligence—and many digital platforms have removed or banned their content. But they’re still influential and trusted alternative sources of information in many parts of the world.

And there's more. Each week, we round up the privacy and security news we didn’t cover in depth ourselves. Click the headlines to read the full stories. And stay safe out there.

New Digital Identity Guidelines Strike Back at Dreadful Password Policies

A new draft of the US National Institute of Standards and Technology's “Digital Identity Guidelines” finally takes steps to eliminate reviled password management practices that have been shown to do more harm than good. The recommendations, which will be mandatory for US federal government entities and serve as guidelines for everyone else, ban the practice of requiring users to periodically change their account passwords, often every 90 days.

The policy of regularly changing passwords evolved out of a desire to ensure that people weren't choosing easily guessable or reused passwords; but in practice, it causes people to choose simple or formulaic passwords so they will be easier to keep track of. The new recommendations also ban “composition rules,” like requiring a certain number or mix of capital letters, numbers, and punctuation marks in each password. NIST writes in the draft that the goal of the Digital Identity Guidelines is to provide “foundational risk management processes and requirements that enable the implementation of secure, private, equitable, and accessible identity systems.”

DOJ Indicts Alleged Iranian Hackers Over Trump Campaign Breach

The US Department of Justice unsealed charges on Friday against three Iranian men who allegedly compromised Donald Trump’s presidential campaign and leaked stolen data to media outlets. Microsoft and Google warned last month that an Iranian state-sponsored hacking group known as APT42 had targeted both the Joe Biden and Donald Trump presidential campaigns, and successfully breached the Trump campaign. The DOJ claims the hackers compromised a dozen people as part of its operation, including a journalist, a human rights advocate, and several former US officials. More broadly, the US government has said in recent weeks that Iran is attempting to interfere in the 2024 election.

“The defendants’ own words made clear that they were attempting to undermine former President Trump’s campaign in advance of the 2024 U.S. presidential election,” Attorney General Merrick Garland said at a press conference on Friday. "We know that Iran is continuing with its brazen efforts to stoke discord, erode confidence in the US electoral process, and advance its malign activities.”

Irish Regulator Fines Meta More Than $100 Million Over 2019 Password Lapse

The Irish Data Protection Commission fined Meta €91 million, or roughly $101 million, on Friday for a password storage lapse in 2019 that violated the European Union's General Data Protection Regulation. Following a report by Krebs on Security, the company acknowledged in March 2019 that a bug in its password management systems had caused hundreds of millions of Facebook, Facebook Lite, and Instagram passwords to be stored without protection in plaintext in an internal platform. Ireland's privacy watchdog launched its investigation into the incident in April 2019.

“It is widely accepted that user passwords should not be stored in plaintext, considering the risks of abuse that arise from persons accessing such data," Irish DPC deputy commissioner Graham Doyle said in a statement. “It must be borne in mind that the passwords, the subject of consideration in this case, are particularly sensitive, as they would enable access to users’ social media accounts.”

The Tor Project and the Tails Privacy Operating System Are Merging

The digital anonymity nonprofit the Tor Project is merging with privacy- and anonymity-focused Linux-based operating system Tails. Pavel Zoneff, the Tor Project’s communications director, wrote in a blog post on Thursday that the move will facilitate collaboration and reduce costs, while expanding both groups' reach. “Tor and Tails provide essential tools to help people around the world stay safe online,” he wrote. “By joining forces, these two privacy advocates will pool their resources to focus on what matters most: ensuring that activists, journalists, other at-risk and everyday users will have access to improved digital security tools.”