#web accessibility guidelines

[adasitecompliance]

WCAG 2.2

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

[reversedout-blog]

Does My Website Need To Be ADA-Compliant?

Does my website need to be ADA-compliant? Suppose you own a business or organization with a website and people visit your site in order to obtain information about or purchase your products or services. In that case, your site needs to comply with ADA regulations. Websites should be accessible to all individuals regardless of their ability or disability. The ADA is the principal civil rights statute for people with disabilities. Under Title III of the ADA, businesses and nonprofit service providers must make reasonable modifications in policies and procedures to permit access for all people, including those with disabilities.

In this guide, learn if your website needs to be ADA-compliant and what the ADA requires of your business.

Yes, it does.

The Americans with Disabilities Act (ADA) is a civil rights law that prohibits discrimination based on disability. It applies to all places of public accommodation, including websites that are part of those businesses.

Websites should be accessible to all individuals regardless of their ability or disability.

In the United States, the Americans with Disabilities Act (ADA) was signed into law in 1990, which requires all businesses and organizations to provide equal access to their goods and services. Websites should be no exception!

The ADA covers a wide range of conditions that may affect one’s ability to interact with others in various ways. These include: blindness/visual impairment; deafness/hard-of-hearing; autism spectrum disorder; cerebral palsy; diabetes; epilepsy or other seizure disorders; intellectual disability; learning disabilities and/or ADHD (attention deficit hyperactivity disorder); muscular dystrophy; multiple sclerosis or other degenerative brain diseases similar in nature; stroke, traumatic brain injury (TBI)/post-concussive syndrome.

The ADA is the principal civil rights statute for people with disabilities.

The ADA also prohibits discrimination based on disability in all programs, activities, and services offered by public entities. It applies to each of us – doctors, nurses, hospitals; restaurants and hotels; landlords who rent apartments or houses; theaters – any place we go to purchase something or do business.

However, what amounts to “reasonable” will vary from case to case. The law provides several factors for determining whether an accommodation is reasonable: best practices in the industry at issue; other relevant federal laws and regulations that require compliance with standards similar to or more stringent than those required by Title III (for example: Section 508); the resources available at that particular site; whether there are alternative ways of meeting both legitimate concerns raised by the organization as well as its legal obligations under Title III; what types of accommodations other customers without disabilities typically receive at that location or venue; how often customers without disabilities experience difficulties accessing such facilities due to structural barriers; whether making a change would be impracticable because it would produce significant economic hardship on small business owners who operate limited-service restaurants or retail stores catering primarily toward one sex or gender-based upon stereotypes about manners associated with certain genders (which might warrant a finding that allowing individuals into these locations would fundamentally alter their operations).

Legal action has already been taken against businesses where it was determined that their website was not compliant with ADA rules.

ADA compliance is not a suggestion, it’s a requirement. If you run any sort of business that has a physical presence, and if more than one person is present at that business, then ADA compliance applies to you.

This includes everything from the most basic retail store to your own website and digital presence. If you offer goods or services online (even if they’re free), then ADA compliance applies to your website as well.

The government has also made clear that they’re not just interested in large businesses when it comes to ADA rules—they want every business owner and operator on board. The law states: “The Americans with Disabilities Act requires all public entities…to ensure effective communication with individuals with disabilities.”

Web Content Accessibility Guidelines.

The Web Content Accessibility Guidelines (WCAG) 2.1 became effective on June 5, 2018. WCAG 2.1 builds upon WCAG 2.0 to ensure compliance with ADA regulations and laws by providing website owners with guidelines for ensuring that the content on their websites is accessible to all users, including those who have physical or mental disabilities. These include visual impairments (low vision, color blindness), hearing loss, physical limitations (mobility impairments), and cognitive limitations (dyslexia and language disorders).

The updated guidelines can be applied immediately when making changes to existing websites or content or planning new ones, even if a site hasn’t been built yet.

Conclusion

Keeping up with the latest web accessibility guidelines is important, but it’s not always easy. If you’re looking for ways to improve your website’s compliance with ADA standards or just want to ensure that it complies with other legal obligations, contact the experts at Reversed Out Creative today!

Contact Us

At Reversed Out Creative, we understand the challenges and opportunities presented by AI disruption. Our team of experts specializes in web design, SEO, graphic design, and digital marketing services. Reach out to us through our contact form to learn more about navigating the evolving job market and embracing the potential of AI. Together, let’s shape a future that combines human ingenuity with the power of AI.

Original content source: https://reversedout.com/does-my-website-need-to-be-ada-compliant/

[rocketbirdie]

I LOVE IT WHEN THE HELP SECTION ON A WEBSITE ONLY HAS VIDEOS AND NO TEXT I LOVE NOT BEING ABLE TO FIND USEFUL INFORMATION AT A GLANCE!!!!!!!!!!!! YAY :)

[spice-ghouls]

Cannot help but roll my eyes when I read posts bemoaning how boring the colors on the web have gotten v.s. the early web when things were regularly all bright and neon.

[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

[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.

[aeldata-usa]

Accessibility Guidelines for UX Designers: How to Design for Everyone?

Learn how to design for everyone with our accessibility guidelines for UX designers. Make your website usable and inclusive for all users.

[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…

[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.

[tech-ahead-corp]

UI/UX Principles

UI/UX Principles are fundamental guidelines governing both User Interface (UI) and User Experience (UX) design. They dictate how visual elements and interactive features should be designed to optimize user satisfaction!

[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.

[morimagdalene]

some graphic design resources cause im bored and itching to write something but i cant write anything i'm happy with--- anywayssss

unsplash for lots of royalty free pics

heres a cool site to learn how to pair fonts together

heres another site to learn kerning [spacing]

in fact heres a bunch of games to help u get better at graphic design stuff

some free online video editors x x x

color accessibility resources :]

savee.it - like pinterest but for designers!! unfortunately it has a save limit for free users but u should still be able to browse it for inspo i think?

some free fonts

aside from coolors i really love adobe color!! it has color palette generator [triads, monochrome, complementary, etc.], accessibility tools, palettes+gradients extractors, and color palettes inspired by trends within diff industries.

make moodboards online for freeee i miss u polyvore

spline and womp for web based 3d design! + blender of course [go make that donut!]

we all know and love them: photopea [photoshop but free and on a browser?!] and canva [no introduction needed im sure]

upscale the resolution / quality of pics it says anime but it works really well with most stuff like video game screenshots [gets rid of hard edges/pixels]

typography inspo

more color palette generators [already meets accessibility guidelines]

filmgrab - a curation of movie scenes 💕

here's another one but for color palettes from films

more inspo and tutorials

cargo - for web design stuffs

an archive of BRANDING GUIDES

free online zine hosting

milanote - very very useful for organizing creative projects :D kinda like a mix of notion and pinterest ? [its basically notion but more visual]

a collection of free luts

lots of pngs for editing

freepik - lots and lots of free design assets.

flaticon - lots of flat icons / vectors. i haven't used this in a while, but it was free last i checked

in case u need more help pairing fonts go here and here

idk ilu all have fun!!!!

[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

[mcytblrholidayexchange]

Holiday Exchange 2024: General Rules and FAQ

WHAT IS THIS?

MCYTBLR Holiday Exchange is a multi-mcyt gift exchange now in its third year! Because of the size of the exchange, we are going to be matching through Ao3 this year, including tag nominations. The discord will be open with more information in late October.

TIMELINE: 

Tag Nominations Open, Discord Opens: Monday 28 October (0:01 EDT)

Sign Ups Open Monday 4 November (0:01 EST)

Sign Ups Close: Sunday 17 November (23:59 EST) Monday 18 November, (11:59 EST)

Assignments out by: Friday 22 November (23:59 EST)

Check-in: Saturday 7 December (0:01 EST) through Sunday 8 December (23:59 EST)

Posting Week: Monday 23rd December (0:01) through Sunday 29 December (23:59 EST).

Final Pinch Hit Deadline: Sunday 5 January (23:59 EST)

LINKS

Discord: [here]

Ao3 tagset [here]

All Ages Collection [here]

18+ Collection [here]

RESOURCES:

How to nominate tags to a tag set. [link]

How to sign up for an Ao3 gift exchange. [link]

A guide to your Sign-up, stage by stage. [link]

Apply for an Ao3 account (currently a 10-day waiting list): [here]

How to add a treat to an Ao3 Collection. [here]

How to image-describe your art. [link1] [link2]

MINIMUM REQUIREMENTS FOR GIFTS: 

Art (1 drawing, created to a standard you would normally post as “finished”) 

Writing (1k+ words, a complete work that stands alone) 

Playlist (2 hour-long playlists, accessible without an account) 

Moodboard (2 boards, at least 9 elements each, for a total of at minimum 18 elements between both boards. Speak to mods if that really doesn't work for your designs)

Web Weaving (1 board of at least 10 elements, credited)

Podfic (1 podfic of at least 1k words, edited to your normal level of editing)

Rules and Guidelines and FAQ under the cut.

Rules and Guidelines

RULES AND GUIDELINES FOR NOMINATING TAGS:

Instructions for how to nominate tags [here]

For a tag to be used in signup, it must be part of the tag set, and thus, must be nominated and approved before it can be used.

Tag nomination is done through Ao3’s tag set nomination process. You can nominate up to 20 tags per fandom, and up to 10 fandoms. Fandoms do not need to have a canon tag to be nominated, but please use the canon tag if possible.

Please only nominate tags you intend to either offer or request, to help with matching.

Please nominate tags without using the creator’s tags names, just gamer tags. Do not use the canon tag, as that will be sorted into Video Blogging RPF automatically, (unless you are nominating RPF). Alphabetize the characters by gamer tag within the tags, i.e. GoodTimesWithScar & Grian (3rd Life)

& denotes a platonic relationship, / denotes a romantic and/or sexual relationship. Tommyinnit & Tubbo (DSMP) would be platonic, and Ranboo/Tubbo (DSMP) would be romantic.

You can nominate up to 6 characters within a tag, as long as it fits within Ao3’s character limit (100 characters). 

Please disambiguate (include the server name in parentheses after the characters), as that helps us distinguish between creators who’ve been on multiple servers, i.e. Grian could be in YHS, EVO, Hermitcraft, 3rd Life, 100 Hours Hardcore, or Guess the Build, and we need to know which one.

Please distinguish between Empires S1 and Empires S2 if you are nominating Empires.

If you want a work that focuses on one character instead of a relationship, whether or not other characters are present, you can nominate a solo character as Solo: [Character Name], i.e. Solo: TommyInnit (SMPEarth). 

Video Blogging RPF is allowed as a nominated fandom, as long as the creators are all over 18 and famous in their own right. Mods reserve the right to reject tags they feel to be in bad taste, such as a person accused of misconduct and the person who accused them.

Crossovers are allowed. Please nominate them in the format Grian (Hermitcraft) & Tommyinnit (Dream SMP) (Crossover Fandom), or if you wish a character to be moved to a different canon, please nominate them in the format Technoblade (Origins SMP) in QSMP (Crossover Fandom). Crossover tags do not need to be entirely MCYT, non-MCYT franchises are allowed. All crossovers go under the fandom Crossover Fandom.

This event does not allow Adult/Minor romantic relationships. A list of characters considered to be minors in canon will be available in the discord– we will be going with age during the bulk of content for past servers, or present age for currently-running servers. Minor/Minor romantic shipping is allowed as long as the character is not extremely underage (15 or younger). Because of the difficulty of moderating content on a tight schedule, this event will not allow aged up characters for the purposes of relationships not being adult/minor.

RULES AND GUIDELINES FOR SIGNING UP:

Instructions for signing up [here]

Must join our Discord for communication. If we cannot find you in the discord at the end of sign-ups, your signup will be deleted.

Must have an Ao3 account for sign-ups, as they happen on Ao3. If you do not have a Ao3 account and need help getting on, please contact the mods as soon as possible.

Because of Tumblr, Ao3 and Discord TOS, you must be 13 to participate.

Signups are divided into Requests (what you want to get as a gift) and Offers (what you’re offering to make). You must request and offer a minimum of three different relationships or solo character tags. They can be from any number of servers and your requests do not need to be the same as your offers. You can offer or request a maximum of 10 servers with 20 tags each.

There are two collections, all-ages and 18+. Signing up in the 18+ collection is opting into NSFW as a possibility. You must be 18 or older to sign up in the 18+ collection, and any under-18 persons found signing up for the 18+ side of the exchange will be banned from this and all future iterations of the exchange.

If you do not want shipping, simply only request & tags. If you do want shipping, request / tags. If you are open to either, request both tags. 

Must mention your tumblr blog username in your signup, so your recipient knows how to give you your gift.

You must either write down a DNW (things you Do Not Want) in your gift, or put down DNW: No Restrictions, for each fandom you sign up to. 

You must write down at least one like, prompt, or have a letter with more information linked, to give your creator something to work with.

if you are requesting a Solo character tag, you must indicate if you are okay with shipping or not, and any romantic or platonic relationships you don’t want to see in the work, because your creator will be picking from all canon characters as the supporting cast.

Signing up gives mods access to your Ao3 email (it's how we send you your assignment), so make sure the email attached to your AO3 account is one that a) you check regularly, and b) are comfortable with exchange mods seeing. You can verify your email here: archiveofourown.org/users/[your ao3 name here]/change_email

This event does not allow Underage or Adult/Minor relationships. A list of characters considered to be minors in canon will be available in the discord– we will be going with age during the bulk of content for past servers, or present age for currently-running servers. Minor/Minor shipping is allowed as long as the character is not extremely underage (15 or younger), but no NSFW, even if signing up to the 18+ collection. Because of the difficulty of moderating content on a tight schedule, this event will not allow aged up characters for the purposes of content not being underage or relationships not being adult/minor.

RULES AND GUIDELINES FOR CREATING: 

Your gift doesn’t have to contain only requested relationships, but it does have to center on at least one requested relationship or character. 

Respect your recipient’s use of / or & in their requested relationship. Ship work must be delivered for a / relationship, and platonic work must be delivered for a & relationship. 

If you are a participant in the 18+ collection, you do not have to deliver NSFW, but you can if you want.

If you are a participant in the All-ages collection, you may not deliver an NSFW gift, or a non-NSFW gift that is E-rated. The maximum rating of a gift in the all-ages collection is M-rated. 

Respect your giftee's DNW. Any gift found to be in violation of a reasonable DNW is grounds for a ban from future iterations of the exchange. 

Must check in at the half-way mark of creation to make sure everything is on-track.

Contact a mod ASAP if you don’t think you’ll get your gift out on time or at all, or you want to withdraw

No AI-created content.

RULES AND GUIDELINES FOR GIFTING

You do not need to post on Ao3. You can if you want, and clicking your assignment button will automatically gift it to your recipient, but this is optional.

You must make a tumblr post and tag your recipient to give them the gift.

Must tag this blog in your gift post so we can keep track of gifts

If you are posting from a blog other than the one you signed up with (an art blog, or a 18+ blog for example), you must inform the mods so we can keep track of gifts.

Dark or Violent themes must be tagged appropriately

MISC:

Your requests will be publicly available, to conform with normal exchange standards, and because of the mechanics of pinch hits and treating. If you have something you do not want to be public, do not request it. Your offers will remain private, and mods will work with you to give a gift on anon if necessary.

You will not necessarily be matched with someone who matches your “offer to create” exactly. If the algorithm can make a better match it will do that, but in cases where there are more obscure requests, you might be matched with someone who only has one ship in common between your Offer and their Request. In that case at least you know what to make pretty quickly!

You do not have to make a gift for every ship or character your recipient requested, even if you offered multiple ships they requested. You only have to pick one and make one gift. 

Please ask in the discord if you need information. You could also send an ask here, or if it is something you do not feel comfortable sending in an ask, you can message the head mod at @antimony-medusa​ 

Mods reserve the right to ban people for being assholes.

FAQ:

-I changed my mind about my sign-up, I want to add something, what do I do? You can edit your sign-up right until the sign-ups close! As soon as the sign-ups close, everything locks and you’ll be unable to edit it any more.

-I added my fic to the Ao3 collection, but I can’t see it? The collection is currently set to ‘unrevealed’, so works can be added but won’t be visible before reveal day, so it’s all a surprise.

- I don’t have an Ao3 account, what do I do? Speak to the mods— we can help you sign up (there is a waiting list), or we might be able to give you an instant sign-up link (we have a limited number of these).

-I need to contact my recipient, but they have anon off! What do I do? Talk to us, we’ll contact them for you.

-I can’t finish my gift by the deadline, what do I do? You have two options. Option one is to consider if you can still finish it within a couple days, and ask the mods if you can get an extension (you can get an extension of up to two days if necessary). Option two is to drop entirely, in which case you tell a mod, and we will assign your gift to a pinch-hitter so your recipient still gets something. In both cases, the important thing is that you get in contact with a mod as soon as possible— discord is best, but @antimony-medusa can be contacted here if discord is not an option— to figure out a plan.

- My recipient requested 10 different fandoms, do I have to make a gift for each of them? You only have to make one gift! Just pick one fandom and one ship that you like and focus on that one.

-If I want to make more than one gift, can I? You can make as many gifts as you'd like! If you really enjoy making gifts, we suggest signing up as a Pinch Hitter in the discord, and there is also Treating, if you want to look for signups that really catch your eye!

-I don't celebrate Christmas, can I sign up? This exchange welcomes all holidays (even a complete lack of holidays), and people will have an opportunity to opt in to what events they want represented in their gift, whether that's real-world holidays, imaginary minecraft events, or no holidays at all.

-I'm only a fan of a small server, can I sign up? You are very welcome to sign up even if your fandom doesn't have the most active tag, this is a broad MCYT exchange. We will do our best to match you with someone else who also likes your block people, pinch hitting it if possible. If your fandom has less than a thousand fics on the archive, we recommend that you try and recruit friends into the exchange too, so you know that there are people who like the same characters as you in the matching pool. We can't absolutely promise to match on smaller characters, but we have run this exchange twice and we haven't had anyone be entirely unmatchable yet, so fingers crossed that continues.

-Is RPF allowed? While this is intended as a character-focused exchange, we know the lines for that are fuzzy when it comes to off-server events the creators have also done, such as the GIGS Phasmaphobia streams, and it becomes difficult to moderate this line. As we are now able to distinguish between RPF and the server creators using Ao3’s tag sets, so matching is no longer a difficulty, you will be able to request or offer direct RPF from this exchange.

-Is shipping allowed? Yes. Because there is no broad fandom-wide consensus about the appropriateness of that in specific cases (whether it's okay to write beeduo as /r or /p is an obvious case) or between specific fandoms (Lifesteal approach to shipping is different from Empires is different from DSMP), and because of the impossibility of being aware of everyone’s boundaries across the entire internet, the mods will not be policing any specific understanding of boundaries across the event. The event will operate on Don't Like Don't Read, in that everyone will have the chance to opt in for themselves as to if they are comfortable with shipping or NSFW for each specific character relationship they want to work with, and they will be matched based on that.

-Is NSFW allowed? Yes, NSFW is permitted as long as both characters are 18+ and both the giver and the recipient are participating in the 18+ collection. You will only match to people who want NSFW if you have signed up to the 18+ collection. To comply with Tumblr’s TOS and for the comfort of the greatest number of people in the exchange, nothing that would warrant the tags Underage or Adult/Minor Relationship is permitted. 

- Are major archive warnings (noncon/graphic depictions of violence/MCD) allowed? Aside from the content rules governing NSFW (no Underage, for the comfort of the greatest number of participants), major archive warnings are allowed. Depictions of real life horrors such as genocide and slavery are not-uncommon motifs in MCYT fics, along with torture, executions, and abuse in the source material, and the mod team is not interested in legislating which types of horrors, griefs or abuses are inherently worse than others and are therefore off-limits. Because holding writing to a quality standard or saying only survivors can write atrocities is unworkable from a moderation standpoint, the three mentioned major archive warnings (MCD, Graphic Depictions of Violence, Noncon), are permitted to be included in the 18+ collection. The all-ages collection permits MCD and Graphic Depictions of Violence as possible warnings, though gifts cannot go over an M rating if delivered in the all-ages collection, even if your recipient has opted into Graphic Depictions of Violence.

Major Archive Warnings must be explicitly opted into by your recipient in their signup, and gifters are free to not include major archive warnings that their recipient has permitted. Delivering un-asked for major archive warnings is grounds for a ban from this event. The mod team reserves the right to warn other mod teams on both the MCYT and Multi-fandom side about your bad behavior.

-Do you allow dark or violent content? Yes. The lore of many mcyt servers includes death games, abuse, cannibalism, murder-for-hire, and other dark or violent themes. However, all potentially triggering content must be tagged for so viewers and giftees can make an informed choice to get involved or not. We would recommend that you not include particularly dark topics unless requested to by your giftee.

-If I want to opt into e-rated gore, but I don’t want to opt into sexual NSFW, can I do that? To opt into e-rated gore or violence you must be part of the 18+ collection, but you can do so and then say you Do Not Want smut. Note that you cannot demand e-rated gore, in the same way that you cannot demand e-rated smut (or fluff, or anything else for that matter), it is simply an option you are offering your gifter.

-My person requested characters I don't want to write, and one of them is a ship I don't like. What do I do? You are only expected to create a gift for the characters you matched on. If you offered to create for GoodTimesWithScar & Grian (Hermitcraft),  Docm77/Rendog (Hermitcraft), and Grian & PearlescentMoon (Hermitcraft), and you matched to someone requesting GoodTimesWithScar/Grian (Hermitcraft),  Docm77/Rendog (Hermitcraft), and PearlescentMoon/ZombieCleo (Hermitcraft), you are only expected to make a gift with the characters and relationships you matched on, in this case, RenDoc. If you are entirely uncomfortable with your match, you can tell a mod, and we can take it off your hands and get it pinch-hit. You will still receive a gift.

-What is a Pinch Hitter? A pinch hitter is a person who saves the day and steps in when the original creator is unable to deliver their work for whatever reason, making a new work on an accelerated timeline. You can sign up to be a Pinch Hitter in the discord.

-What is a DNW? All participants will have the opportunity to fill out a DNW, which stands for Do Not Want. This is anything that has the potential to ruin a gift for you. DNWs must be phrased politely, (so no "No foster aus because they suck and you suck if you like them"), and they must be reasonable, (so no attempting to box someone into a specific gift, i.e. "DNW anything that isn't a space au where Tommy is a dinosaur-hybrid and Tubbo is a ghost bee and they rampage through the living ship named Las Nevadas"), and they must be clear and defined (so no “no dark kinks”— that is too subjective for someone to try and interpret), but they can be as petty (disliking specific art styles) or as broad-reaching (no modern aus, no specific ships, no crossovers with specific servers) as you like. Deliberately breaking someone's DNW is grounds for a ban from the exchange.

-When do I have to join the discord? You have the option to join the discord and hang out as soon as tag nominations starts on October 28, and you must join the discord so we can communicate with you by November 17. Anyone not in the discord once we start matching will have their sign-ups deleted.

-Is the discord a social server? Can I expect game nights? The discord is primarily an event server, we are not going to be hosting events. 

-What are Treats? Treats are optional bonus gifts that people give once they are done with their original gift! All of the sign-ups are available for people to browse through, and they can find prompts they like and make an extra gift for that person! They are completely optional for someone to make and you cannot ask for treats.

-What's a check-in and how do they work? Check-ins are there to make sure everyone is on track to finish their piece in time, and to communicate any issues with the mods! They take place through a google form and will require a short list of information— your name and if you think you will make the deadline, mostly. If you know that you won’t be able to check in on a specific date (lack of internet, etc), please contact the mods in advance.

-What if I need to drop out? It is your responsibility to communicate with us if you need to drop out of the event for any reason, and we do need that communication. We know that life is no respecter of fic and art deadlines, so no hard feelings if something happens. However, we would hate for anyone to end up having no gift, so please think about this if you are thinking of dropping out close to reveals. Please inform us in advance if you must drop out or think you will not be able to complete your gift on time. Dropping out after the last check-in without informing the mods will result in not being permitted to take part in further events run by this mod team.

I have a question not answered here? Ask us in the discord, send us an ask on tumblr, or contact @antimony-medusa on tumblr or discord!