Understanding Digital Accessibility Regulations

he Twenty-First Century Communications and Video Accessibility Act (CVAA)

The Twenty-First Century Communications and Video Accessibility Act (CVAA) is a law containing groundbreaking protections to enable people with disabilities to access broadband, digital and mobile innovations.

In 2010, President Obama enacted the Twenty-First Century Communications and Video Accessibility Act (CVAA). This legislation updated the existing laws to ensure that all new telecommunications technologies are accessible to people with disabilities.

The CVAA consists of two main sections, each referred to as a title:

Title I – Communications Access
Title II – Video Programming

The CVAA covers a wide range of regulations designed to improve accessibility across communications and media, with specific requirements aimed at web and mobile accessibility:

CVAA requirements for Communications Access

Title I of the accessibility act focuses on ensuring that communications services and products that utilize broadband are fully accessible to people with disabilities. For instance, smartphones must be made usable by individuals who are blind, visually impaired, or who use hearing aids.

CVAA requirements for Video Programming

Title II takes significant steps toward improving accessibility for individuals with disabilities in video programming on both television and the Internet. A key example is that programs initially broadcast with captioning on TV are also required to have captions when streamed online. Both titles include measures to guarantee access to crucial services, such as next-generation 911 services and emergency broadcasts on television for people with disabilities.

Why is the CVAA important?

Around 36 million Americans experience hearing loss, and another 25 million face significant vision impairments. A 2009 FCC study highlighted a notable gap: while 65 percent of the general American population had broadband at home, this number dropped to just 42 percent among those with disabilities. This discrepancy often stems from physical barriers that make internet use challenging for people with disabilities. Recognizing this, the National Broadband Plan of March 2010 urged Congress and the FCC to update accessibility laws to reflect the rapid advancements in broadband technologies. The CVAA was developed in response to this need, ensuring that as technology progresses, the accessibility of broadband, digital and mobile communications are not overlooked.

Reach out to UserWay to explore how we can support your adherence to CVAA compliance requirements.

Section 508 Compliance: Your Questions Answered

Section 508 compliance directly impacts federal organizations, programs, and contractors. This amendment to the Rehabilitation Act of 1973, the first federal law to forbid disability discrimination, requires federal agencies to provide Information and Communications Technology (ICT) accessible to people with disabilities.

Let’s start by learning how Section 508 pertains to ICT.

Which digital assets are affected by Section 508 standards?

Section 508 standards specifically address digital accessibility and all electronic communication, including:

Public-facing website pages
Website forms
Emails sent internally and externally
Software and all apps (including mobile)
Online training materials
Employment application pages
All digital files like PDFs

Which organizations are affected by Section 508 compliance requirements?

Section 508 is a federal legislation, but it may also impact:

Financially assisted (U.S. government) state, county, and civil authorities
Federally assisted universities, museums, galleries, medical centers, and other organizations.
Contractors spanning all sizes and services that work with the U.S. government.

Section 508 guidelines do not, however, apply to agency-operated technology concerning national security systems. The law also excludes conformance that causes extreme burdens or requires a foundational change in the nature of ICT. Nonetheless, in these instances, organizations still must provide alternatives for people with disabilities to access information and services.

What are the Section 508 compliance requirements?

The U.S. Access Board has accessibility guidelines included in Section 508 requirements. Additionally, the board integrated WCAG 2.0 into Section 508 standards in 2017. The latest updates mandate that agencies comply with Level A and Level AA of WCAG.

Understanding the legal obligations related to accessibility relevant to your business requirements is essential. Additionally, being aware of the potential consequences of not adhering to Section 508 standards is vital. The main Section 508 requirements include:

1. Accessibility Standards: Federal agencies must ensure that their electronic and information technology is accessible to people with disabilities. This includes hardware, software, and documentation.

2. Web Accessibility: Websites and digital content need to be accessible, often entailing adherence to the Web Content Accessibility Guidelines (WCAG). These guidelines offer a comprehensive set of recommendations aimed at enhancing the accessibility of web content.

3. Procurement Policies: Section 508 mandates that federal agencies, in the development, procurement, maintenance, or utilization of electronic and information technology, ensure that the technology is accessible to employees and members of the public with disabilities.

4. Equal Access: Individuals with disabilities must have access to and use of information and data that is comparable to the access and use by Federal employees or members of the public who are not individuals with disabilities.

5. Compliance Reporting: Federal agencies are required to report on their compliance with Section 508 and the steps taken to ensure accessibility.

6. Remediation and Enforcement: If a Federal agency fails to comply with Section 508, there are processes in place for remediation and enforcement, which can include complaints and legal action.

7. Guidelines and Standards: The U.S. Access Board develops and maintains accessibility standards which are used as a framework for Section 508 compliance.

8. Training and Awareness: Agencies are also required to provide training and raise awareness about accessibility requirements among their staff.

These requirements are particularly important for IT professionals, web developers, and content creators working with or for Federal agencies, as they must ensure their products and services are compliant with these accessibility standards.

How do Section 508 guidelines differ from the ADA?

Section 508 guidelines concern federally funded agencies and organizations, such as contractors and suppliers. They mandate that such organizations provide digital communications that conform to 508 compliance requirements and comply with Level AA of WCAG.

The (ADA) applies to businesses open to the public, nonprofits, and regional and state governments. Title III of the ADA forbids discrimination against people with disabilities in public places. It’s also important to note that U.S. courts increasingly rule that the ADA applies to websites and mobile apps.

How can I create a Section 508-compliant document?

Creating a 508-compliant document is making a digital document accessible to individuals with disabilities, particularly those using assistive technologies such as screen readers.

The Web Content Accessibility Guidelines (WCAG) are the gold standard for crafting accessible content, mainly focusing on content structure and accessibility features.

These features include structuring content through headings and lists to establish a coherent hierarchy. A seamless reading experience is achieved by meticulously defining the reading order, and non-text components, like images, are thoughtfully paired with descriptive alternative text to provide context for users relying on assistive technologies.

Additionally, when creating 508 compliant documents, it is advisable to ensure that text labels for links and form fields balance brevity and meaningfulness, ultimately enriching the usability for individuals with disabilities.

One effective way to build accessibility into your digital documents is to use specialized tools like UserWay’s automated document accessibility solution. This solution streamlines the process and ensures that your files adhere to the required laws and standards, enhancing inclusivity and facilitating ease of access for all users.

What Is a Voluntary Product Accessibility Template?

A Voluntary Product Accessibility Template (VPAT) shows how (ICT) products comply with revised Section 508 standards. It conveys that digital information and communications must be accessible to all people. Moreover, federal agencies and organizations must provide ICT that conforms to Section 508 accessibility standards.

A VPAT thoroughly scrutinizes these agencies’ services to verify their conformance to Section 508. This assessment helps organizations report their products’ compliance, and it’s their responsibility to finalize a VPAT to ensure these products comply.

What’s the Risk of Non-Compliance to Section 508?

Failure to comply with Section 508 or any other digital accessibility law has considerable legal risks. Related lawsuits are increasing rapidly, and the costs can be severe and even crippling for smaller organizations—case and point: more than 3,000 organizations faced accessibility-related lawsuits in 2022 alone.

If the legal penalties aren’t enough to worry about, these lawsuits can be a PR disaster for any organization. Nonetheless, integrating assistive technology tools and following web best practices for conformance can help you avoid these legal impacts and harmful press exposure.

What are six proven tips for Section 508 Compliance?

1. Provide assistive technology that enables people with fine motor skill impairments to function with just a keyboard.

2. Highlight all interactive, on-screen variables.

3. Provide alt text for every non-text variable.

4. Integrate the recommended color contrast ratios and ensure that color isn’t the only variable conveying information's meaning.

5. Organize documents without the need for associated style sheets. In addition, no web page should need a cascading style sheet to view or navigate.

6. Conduct Section 508 testing that checks websites for WCAG compliance and helps improve digital accessibility.

Summary: the true meaning of Section 508

Like all laws that support and enforce digital inclusivity, Section 508 compliance is about creating a barrier-free web for everyone. Unfortunately, people with disabilities have faced exclusion for far too long. Section 508 compliance for websites and digital devices helps organizations reverse this problem. Making a concerted effort to satisfy Section 508 compliance is an excellent way to do your part. See how companies benefit from ongoing compliance support with UserWay.

UserWay: Accessibility & Compliance Solved

UserWay’s AI-powered technologies enable you to comply with Section 508 and all other related laws. Products like the UserWay Widget 4.0 are just one example of how UserWay can help your organization remain accessible and legally protected.

he Twenty-First Century Communications and Video Accessibility Act (CVAA)

The General Data Protection Regulation (GDPR) is a European Union regulation that took effect in 2018 and helps to allow citizens the right to control their personal data. This includes data within the EU as well as data that is transmitted to other regions.

To learn more about how UserWay’s Accessibility Widget complies with GDPR regulations, please contact us.

Understanding the European

Accessibility Act (EAA)

The European Accessibility Act (EAA - DIRECTIVE (EU) 2019/882) is a legislation aimed at improving the accessibility of products and services for people with disabilities within the European Union (EU). It sets guidelines and requirements for Information and Communication Technology (ICT) products and services to make digital content accessible to people with disabilities.

How is the EAA driving accessibility?

The EAA accessibility directive addresses the disparities in accessibility standards among EU member states, striving to ensure equal access to goods and services for people with disabilities.

The EAA highlights the importance of integrating people with disabilities and the elderly into society, improving their participation in education and employment, while reducing the risk of poverty.

By setting a unified EU-wide accessibility standard, the EAA simplifies legal frameworks, reduces costs for industries and replaces the myriad of national regulations. This approach helps to avert the fragmentation of the internal market, ensuring industries benefit from adhering to a singular standard across the EU, boosting competitiveness.

The history of EAA: a legislation timeline

2019: European Accessibility Act (Directive (EU) 2019/882) (EAA): EU accessibility directive requiring products and services to be accessible
2022: EU Member States had until June 2022 to transpose the EAA into their own respective laws
2025: The deadline for compliance is expected to be June 28, 2025. Organizations must ensure that they are taking the necessary measures to make their digital assets accessible
2027: Some EAA obligations will start at the latest from June 28, 2027
2030: EAA requires EU Member States to provide for a transitional period ending June 28, 2030 for products lawfully used by providers for similar services before that date

Which types of digital assets are impacted by the European Accessibility Act?

The European Accessibility Act focuses on products and services deemed crucial for individuals with disabilities, which are also most prone to varying accessibility standards across EU nations.

In its development, the Commission engaged with stakeholders and experts in the field of accessibility and considered the responsibilities stemming from the UN Convention on the Rights of Persons with Disabilities.

The EU directive sets accessibility standards for essential products and services including:

Products

Phones, computers, and terminals for payments or purchasing transit tickets
Consumer banking services
Electronic communication services like phone and internet
Emergency calls to the 112 number
Audiovisual media services access
E-books
E-commerce platforms

Services

Phone services
Banking services
E-commerce
Websites, mobile apps, electronic tickets, and any other information resources for air, bus, rail, and water transportation services
E-books
Access to Audio-visual media services (AVMS)
Calls to the European emergency number 112

Are any organizations exempt from the EAA’s requirements?

Micro-enterprises offering services, along with specific product categories that may be exempt due to size or scope, are not the main targets of the act's objectives, especially when compliance presents a disproportionate burden.

When are private companies expected to adhere to the EAA?

The EAA was officially passed by the EU in 2019. Member States had until 2022 to transpose it into their domestic law. The process of transposition involves incorporating the directive into domestic laws, ensuring that each country's legal framework reflects the EU's standardized requirements.

The vast majority of countries must start enforcing the EAA in June 2025.

What role does the EN 301 549 play in relation to the EAA?

EN 301 549 is a set of standards that outlines the requirements for digital products and services to be accessible to all users, including those with disabilities. It serves as a foundational guideline for designers, developers, and manufacturers, ensuring that their digital assets are navigable and usable for people with various impairments, such as visual, auditory, motor, or cognitive challenges.

In relation to the European Accessibility Act, EN 301 549 plays a critical role. The EU directive aims to improve the accessibility of products and services in the European Union market, and EN 301 549 provides the technical specifications and criteria necessary to meet these objectives. By aligning with EN 301 549, organizations can ensure compliance with the EAA, thereby contributing to a more inclusive digital landscape across the EU.

This alignment highlights the importance of EN 301 549 in setting a unified standard for accessibility, creating barrier-free digital environments for all users.

How does the EAA benefit businesses and consumers?

Benefits to businesses:

Adopting uniform accessibility standards across the EU leads to lower operational costs
Facilitates smoother cross-border trade
Opens up broader markets for accessible products and services, tapping into new customer segments

Benefits to consumers (particularly individuals with disabilities and the elderly):

Improved access to a wider range of accessible products and services
More competitive pricing for accessible options
Easier access to transportation, education, and employment opportunities, contributing to a more inclusive labor market
Increased employment prospects, especially in roles requiring expertise in accessibility

What happens if you fail to comply with the European Accessibility Act?

The EAA does not specify particular enforcement actions or penalties. Member states have the authority to apply their own sanctions and enforcement strategies to ensure compliance with the EAA, however, the directive mandates Member States to ensure that ‘adequate and effective means exist to ensure compliance’.

The spectrum of penalties for non-compliance is broad, with fines potentially spanning from €1,000 to up to 5% of an entity’s annual turnover, reflecting the gravity of the infringement.

To align with the EAA, every EU nation is mandated to revise its domestic laws to conform to the act's stipulations by a designated deadline. This includes the establishment of national-level mechanisms for the systematic monitoring of compliance and the management of any infractions.

This approach ensures that the objectives of the EAA are uniformly pursued and enforced, with the flexibility for member states to address their unique legal and regulatory landscapes.

UserWay: helping you meet EAA accessibility standards

UserWay’s Accessibility Widget stands as a reliable and tested tool for enhancing digital accessibility and ensuring regulatory adherence. UserWay’s comprehensive suite of digital accessibility products and services help organizations across the globe reach key compliance benchmarks, such as those set by the EAA.

Bring your digital assets into EAA compliance today.

The Accessibility for Ontarians

with Disabilities Act (AODA)

Enacted in 2005 in Ontario, Canada, the AODA outlines specific accessibility requirements and standards in various areas, including customer service, employment, transportation, and information and communications. AODA strives to increase accessibility for those with physical and mental disabilities. Regarding web accessibility, the act requires organizations to ensure that their websites and digital content conform to WCAG 2.0 Level AA.

What organizations does AODA impact, and when must they comply?

Large organizations (50+ employees) must comply with the AODA standards by January 1, 2014. Small organizations (1-49 employees) had until January 1, 2021. In addition, organizations must submit accessibility reports on their compliance efforts, including details on their web accessibility measures.

The AODA standards apply solely to a person or organization that does one or more of the following:

Offers goods, services, or facilities
Is an employer of people in Ontario
Provides accommodation
Owns or occupies a building, structure or premises
Contributes to a business or other relevant activities

What is the WCAG?

The Web Content Accessibility Guidelines (WCAG) are standards created by the World Wide Web Consortium (W3C). This international nonprofit publishes official HTML, CSS, and other web technology specifications. A global community of member organizations, academics, W3C full-time staff, and the public collaborates to develop its guidelines.

WCAG guidelines have detailed instructions on creating websites, digital content, and coding that work with assistive technologies. WCAG’s definition of web content includes website text, images, sounds, and coding languages. Its four main accessibility principles (POUR) convey those websites must be Perceivable, Operable, Understandable, and Robust for end users.

What are the five standards of AODA compliance?

1. The Information and Communications Standards

The Information and Communications Standards provide rules for organizations to create, provide, and receive accessible information and communications for people with disabilities.

2. The Employment Standards

These standards require employers to provide accessible workplaces and practices for potential or current employees with disabilities.

3. The Transportation Standards

These standards mandate that service providers create accessible routes and vehicles for passengers with disabilities. It further requires transportation companies to update the public about the accessibility of their vehicles’ equipment, features, routes, and services.

Some ways to achieve this include:

4. The Design of Public Spaces Standards

This standard covers methods for making more accessible communal spaces (primarily outdoors).

5. The Customer Service Standards

This standard requires service providers to remove physical and technological obstacles that block people with disabilities from necessary services.

Two additional AODA standards are under development:

The Health Care Standards will impact every healthcare organization.
The Education Standards will identify barriers facing students in K-12 as well as universities and colleges.

AODA fines and penalties

Fines for noncompliance can reach up to $50,000 for each day or partial day an offense happens. For corporations, fines can rise to $100,000 for each day or partial day.

Furthermore, all directors and officers of a corporation must make a reasonable effort to prevent the corporation from committing an offense. Failure to do so can result in those individuals being held liable to pay a fine of up to $50,000 for each day or partial day.

What are the main digital accessibility acts in Canada?

The primary legislation that addresses web accessibility in Canada is the Accessible Canada Act (ACA) and the Canadian Human Rights Act (CHRA). The Accessible Canada Act, effective in 2019, aims to create a barrier-free Canada by promoting accessibility and inclusion. It applies to organizations under federal jurisdiction like the federal government, banks, transportation services, and telecommunications companies. Under the ACA, these organizations must ensure their websites and digital content are accessible to people with disabilities. The Canadian Human Rights Act also affects web accessibility. It prohibits discrimination based on disability and mandates that organizations make reasonable accommodations for equal access to services (including digital).

How can you improve your AODA compliance?

UserWay provides a full range of AI-powered accessibility tools, attorney-led legal support, ongoing accessibility monitoring, and more. Learn why organizations worldwide trust UserWay to make measured improvements in accessibility and compliance for a more inclusive digital world.

Understanding EN 301 549: EU accessibility

standards for digital products

EN 301 549 is the European harmonized standard for digital accessibility in the public and private sectors. It sets guidelines and requirements for Information and Communication Technology (ICT) products and services to make digital content accessible to people with disabilities. This critical standard covers various digital products and services, including websites, software apps, mobile apps, electronic documents, and more.

EN 301 549 harmonized standards and requirements

EN 301 549 is based on existing accessibility standards and guidelines, such as the Web Content Accessibility Guidelines (WCAG). WCAG guidelines, developed by the World Wide Web Consortium (W3C), cover text alternatives, keyboard accessibility, and design that supports device independence. EN 301 549 is also a standard required by the European Web Accessibility Directive (WAD) and the European Accessibility Act (EAA).

Notably, there are substantial differences between EN 301 549 and WCAG. For example, EN 301 549 requires that people with disabilities have access to biological data scans like facial recognition or fingerprints. EN 301 549 also includes digital accessibility aspects that extend beyond WCAG, particularly regarding websites. While WCAG focuses on making web content accessible, EN 301 549 more broadly addresses ICT accessibility requirements, including the following website provisions WCAG might not explicitly cover:

Hardware and software: Requirements for computers, mobile devices, operating systems, and web browsers can affect how end users access websites.
Telecommunications: Standards for making telecommunications services accessible could impact websites offering communication features.
Non-web documents and software: Although WCAG 2.1 and 2.2 have begun to address the accessibility of non-web documents and software accessed via the web, EN 301 549 has specific requirements for documents (like PDFs or office documents) and software used to access or interact with web content.
Compatibility with assistive technologies: EN 301 549 strongly emphasizes the need for websites (and other digital products and services) to be compatible with standard assistive technologies. It transcends WCAG guidelines to ensure people can use websites seamlessly with screen readers, magnification software, and other assistive tools.
Usability: While WCAG includes principles related to website usability for people with disabilities, EN 301 549 often frames these within a broader context of user interface design and interaction. This distinction may provide a more holistic view of how users interact with digital services and content.
Legal and compliance aspects: EN 301 549 adherence often ties to legal and contractual obligations for entities within the European Union, particularly for public sector bodies and services. This connection may introduce additional compliance considerations beyond WCAG technical specifications.

In addition, EN 301 549 outlines various requirements that digital products and services must meet to be considered accessible. These requirements include but are not limited to:

Perceivable: Information and user interface features must be perceivable to users, regardless of their audiovisual and tactile abilities. Requirements include providing alternatives for non-textual content like images, videos, and audio.
Operable: Digital products should be operable through different input methods, including voice commands, keyboard navigation, and gestures. Users should be able to navigate and interact with the content without barriers.
Understandable: Content and controls must be comprehensible to all users, regardless of their cognitive abilities or language proficiency. Clear instructions, error messages, and navigation mechanisms are essential for ensuring comprehension.
Robust: Digital products should be strong enough to withstand technological changes and adapt to different assistive technologies used by people with disabilities. This standard helps ensure that the content stays accessible over time.

History of EN 301 549 standards

The European Telecommunications Standards Institute (ETSI), the European Electrotechnical Committee for Standardization (CENELEC), and the European Committee for Standardization (CEN) launched EN 301 549 in 2014. These official groups are responsible for producing and defining voluntary standards for the European Union and the European Free Trade Association (EFTA).

EN 301 549 has been updated four times, most recently in 2021, to support the European Directive 2016/2102 on the accessibility of public sector bodies' websites and mobile applications (the Web Accessibility Directive - WAD). The 2018 update uses WCAG 2.1 AA standards for its foundational compliance. Twenty-eight European Union member states and other diplomatic organizations and countries, including the European Free Trade Union (EFTA) countries, Iceland, Norway, Turkey, and Australia, adopted EN 301 549. By embracing this standard, these countries simplify trade with the EU and make their products more accessible to everyone.

EN 301 549 revision V4.1.1 is slated for publication in 2025 to support the European Directive (EU)2019/882 concerning accessibility requirements for products and services (the European Accessibility Act).

How EN 301 549 relates to the Web Accessibility Directive & European Accessibility Act

EN 301 549 also meets the public-sector requirements of the Web Accessibility Directive, which improves access to public-service websites and mobile applications for people with disabilities. Similarly, the European Accessibility Act (EAA) uses EN 301 549 as its presumptive conformity standard. Therefore, EN 301 549 also adheres to the EAA, including its current and upcoming private-sector requirements.

EN 301 549 contributes to a more inclusive digital world

EN 301 549 is crucial in promoting accessibility and inclusivity in the digital landscape. Organizations that take the initiative to meet this standard make their digital products and services more accessible to everyone, regardless of their abilities or disabilities. Together, these standards and laws can create a more inclusive digital environment where everyone can fully participate and benefit from technology.

How to meet EN 301 549 harmonized standards

UserWay’s Accessibility Widget is a proven, trusted solution for digital accessibility and regulatory conformance. It can help you make measured improvements toward meeting critical compliance standards, including EN 301 549.

Move towards better compliance today.

Understanding HIPAA (Health Insurance

Portability and Accountability Act)

According to the HIPAA, individuals’ health information should be safeguarded, while allowing the flow of health information needed to provide high-quality health care and protect the public's health and well-being. Passed on August 21, 1996, HIPAA dual goals are to make health care delivery more efficient and increase the number of Americans with health insurance coverage.

What is HIPAA?

The HIPAA security rule applies to organizations or individuals who must follow the rules set by the Health Insurance Portability and Accountability Act (HIPAA) to protect the privacy and security of health information. These entities typically fall into three main categories:

What are the five sections to HIPAA?

The Health Insurance Portability and Accountability Act of 1996 is divided into five sections, known as titles:

Title I: HIPAA Health Insurance Reform
Title II: HIPAA Administrative Simplification
Title III: HIPAA Tax Related Health Provisions
Title IV: Application and Enforcement of Group Health Plan Requirements
Title V: Revenue Offsets

What is the HIPAA Privacy Rule?

Under the HIPAA Privacy Rule, there are clear nationwide standards aimed at protecting individual health records and private health data, which it calls “protected health information.” This rule applies to health plans, healthcare clearinghouses, and healthcare providers that handle certain electronic transactions.

The rule requires these entities to use appropriate safeguards to keep protected health information private. It also sets rules on when and how this information can be shared without a person’s permission. Additionally, it grants people certain rights regarding their health information, such as the right to see and get copies of their health records, to ask for corrections, and to have their information sent electronically to a third party.

A key element of the Privacy Rule is the “minimum necessary” principle, which means that only the smallest amount of information needed for a specific purpose should be used, shared, or requested.

Healthcare providers: This includes doctors, clinics, hospitals, psychologists, dentists, chiropractors, nursing homes, and pharmacies that conduct certain transactions electronically, such as submitting health insurance claims.

Health plans: This category encompasses health insurance companies, HMOs (Health Maintenance Organizations), company health plans, and government programs like Medicare and Medicaid that pay for healthcare.

Healthcare clearinghouses: These are entities that process nonstandard health information they receive from another entity into a standard format or vice versa.

Business associates: They must adhere to certain parts of the HIPAA regulations. These business associates include any organization or person who works in partnership with, or provides services to, a covered entity and handles protected health information in the process. Examples could include billing companies, consultants, IT providers, and attorneys.

What information is protected under HIPAA privacy standards?

Protected Health Information (PHI) encompasses all "individually identifiable health information" held or transmitted in any format—electronic, paper, or verbal—by a covered entity or its business associate. Individually identifiable health information goes beyond the basics. It includes any details that provide insights into:

A person's health history or current health status.
The health care services they've received.
How their health care has been or will be paid for.

This type of information can identify the individual directly or indirectly through various identifiers such as name, address, birth date, and Social Security Number.

**Disclaimer:** This summary is designed to provide a general overview of the Privacy Rule and does not address every detail of HIPAA regulations.

To learn more about how UserWay can help you comply with HIPAA compliance requirements and privacy standards, please contact us.

Authoring Tool Accessibility Guidelines

The Authoring Tool Accessibility Guidelines (ATAG) 2.0 provide detailed accessibility standards for creating web content authoring tools. These guidelines present ways to make tools that are both more accessible to authors with disabilities and that are designed to encourage and promote the creation of more accessible web content by authors using those tools.

Authoring tools can enable, encourage, and assist users in the creation of accessible web content through proper standards, designs, prompts, alerts, QA and repair functions, help files, and other automated and self-assist capabilities. It is just as important that all people be able to author content (ATAG) as it is for all people to have access to content (WCAG).

The tools used to create this information must, therefore, be accessible. The adoption of these guidelines will contribute to the proliferation of web content that can be read by a broader range of readers and authoring tools that can be used by a broader range of authors. ATAG guidelines are relevant for the following editing tools:

Tools designed to produce web content (e.g., WYSIWYG HTML and XML editors);
Tools that save content in web formats (e.g., word processors or desktop publishing apps);
Tools that convert documents into web formats (e.g., DOCX to HTML converters);
Tools that produce multimedia that is used on the web (e.g., video editors);
Tools for website management, including CMS platforms and website publishing tools (e.g., WordPress, Wix, SquareSpace);
Tools for layout design and formatting (e.g., CSS authoring tools).

The Family Educational Rights and Privacy Act

The Family Educational Rights and Privacy Act (FERPA) is a law passed in 1974 that oversees who can access a person's educational information and related records. In part, the law helps give current and former students the right to a certain level of privacy when it comes to their educational information. Institutions may need prior consent to divulge certain information about a person's educational history or records.

To learn more about how UserWay’s Accessibility Widget complies with FERPA regulations, please contact us.

ADA Compliance Guidelines for Websites:

A Checklist for Accessibility

According to the ADA, a person with a disability has a physical or mental condition that significantly hinders their daily life skills. Therefore, ADA compliance is essential to providing an equitable world to people with disabilities because it ensures they can participate in our shared society. Yet the ADA requirements don’t refer to every potential situation, including specific language concerning websites. Nonetheless, ADA accessibility guidelines from the government and courts continually help protect people with disabilities to the full extent of the law.

What is ADA and What Does it Impact?

The Americans with Disabilities Act (ADA) of 1990 constitutes a series of protective measures for individuals with disabilities. This legislation was necessitated by the tendency of numerous businesses to only fulfill the bare minimum standards, coupled with the prevalent attitude among many business proprietors that the expenses associated with ensuring accessibility do not warrant the investment.

In addition, the ADA protects people with disabilities from discrimination and guarantees them equal opportunity in the public and private sectors.

For example, Title III impacts a business’s customer service practices, which explains why accessibility legislation is commonly called ADA Title III. ADA Title III refers to public regions and public accommodations like schools, eating establishments, hospitality locations, physician facilities, retail outlets, museums, and every employment environment.

What Criteria Do ADA Compliance Standards Cover?

1. Employers must accommodate staff members with disabilities, including accessible entryways, restrooms, and proper office furniture and devices.

2. All business types must enable access to their services for customers with disabilities. In addition, they must provide “reasonable modifications” to their buildings, which accommodate people with disabilities, including:

Wheelchair ramps
Accessible restrooms
American Sign Language explanations
Service animal provisions

Businesses must meet these ADA compliance requirements:

Ramp access for wheelchairs and other mobility devices
Interface mechanisms for visually impaired
Interpretive devices for the hearing impaired or qualified interpreters
Service animal provisions

What is ADA Website Accessibility?

Physical access elements of the ADA are most familiar to the general public, including wheelchair ramps, smooth crosswalk transitions, and convenient parking spots. However, the law also applies to many overlooked aspects by people without disabilities.

Concerning website disability compliance, ADA legal standards require government and businesses to provide accessible reading alternatives for people with disabilities. Necessary online services must be accessible to everyone, just like a physical door. The law strives to empower all members of society to participate in our digital and physical spaces. Unfortunately, not everyone understands the importance of digital accessibility— especially those who’ve never been denied access because of a disability.

Websites didn’t exist when the ADA became law in 1990, which explains why its original guidelines only describe physical spaces. Subsequently, this focus on physical space has caused much ambiguity on whether the legislation applies to the digital world and to what extent.

Unfortunately, Congress hasn’t updated or amended the ADA—still, the U.S. Department of Justice (DOJ) and federal district and circuit courts have stepped in and interpreted the law inclusively. This lack of clarity has resulted in many businesses and government agencies being found liable for inaccessible websites.

How Did Accessibility Become the New Standard?

For decades, people with disabilities faced frequent discrimination regarding employment, housing, schooling, and other social functions. Historically, they generally didn’t and couldn’t get equitable treatment. So, not surprisingly, disability rights emerged around the same time as the American civil rights movement of the 1960s. These efforts continued into the 1970s when activists pressured Congress to encompass civil rights language for people with disabilities. As a result, The Rehabilitation Act of 1973 was passed, prohibiting discrimination against individuals with disabilities in the federal sector.

It’s also important to note that the National Council on Disability, a crucial federal measure, wasn’t formed until 1981. This group’s policy proposal was the foundation of the ADA, which became law nine years later. Congress still needs to pass an amendment to the ADA. Independent bodies provide and update guidelines, and courts tend to accept these standards, making them close to de facto law.

Accessibility isn’t just a disability rights concern for the DOJ—they also see it as a civil rights issue. Congress enacted the requirements for ADA compliance to ensure people with disabilities are treated equally to everyone else in society. As many ADA guidelines also include terms like discrimination, integration, and segregation, it’s no coincidence that these words are in tandem with the civil rights movement.

Currently, the Web Content Accessibility Guidelines (WCAG), developed by the W3C, is the best standard cited by the U.S. Courts. In addition, other governments and independent accessibility organizations have created global standards that resemble WCAG.

What Are The 5 Titles of The ADA?

Let’s take a brief dip into the five sections of the ADA so you can get a better picture of the law’s intent.

Title I: Employment Law

Title I prevents companies, governments, and unions from discriminating against people with disabilities concerning employment app practices, salary, training, etc. Additionally, Title 1 affects any company with 15+ employees (this includes staffing companies).

Title II: Public Services, State and Local Government:

Title II applies to state and local government entities and public transportation. It ensures that public and government services or programs don’t exclude people with disabilities. One of the essential parts of Title II is the integration mandate, which prevents local and state governments from segregating people with disabilities. The integration mandate extends the prohibition on discrimination established by section 504 of the Rehabilitation Act of 1973 to all activities of state and local governments regardless of whether they receive federal financial assistance.

Title III: Public Accommodations and Services Operated by Private Entities

Title III applies to privately-run organizations. It requires that spaces within privately-run organizations used for public services be accessible to people with disabilities. This requirement includes locations that fall into numerous ADA classifications, like eating establishments, educational facilities, corporate offices, etc. Additionally, these entities’ services must accommodate people of all abilities.

Even though the accessibility of physical buildings is the most notable result of this title, it’s also been a catalyst for subsequent regulations concerning ADA compliant websites. Many businesses aren’t sure how to make their websites accessible or what level of accessibility is enough—partly because there are so many different types of disabilities.

Title IV: Telecommunications

Title IV targets telephone and television access for people with hearing and speech disabilities. Telephone companies must also provide telecommunications relay services (TRS). These services enable those who rely on teletypewriters (TTYs) to make voice calls. This title also mandates that PSAs with federal funding provide closed captioning.

Title V: Miscellaneous Provisions

Title V covers various ADA elements but primarily forbids retribution against anyone who pursues their ADA rights.

What is the Department of Justice’ update to Title II?

On April 24, 2024, the DOJ published a regulation applying to Title II of the ADA requiring state and local government websites and mobile apps to comply with WCAG 2.1 AA.

State and local entities covering areas with 50,000 or more people must comply by April 24, 2026, while those with less than 50,000 have until April 26, 2027.

The rule sets a higher standard than the federal government's own requirements under Section 508, which mandates WCAG 2.0 AA compliance.

What are the consequences of non-compliance for state and local governments?

If a state or local government doesn't fully meet WCAG 2.1, Level AA, they might argue that the minor deviation is so insignificant it doesn't affect access for people with disabilities. However, this does not excuse them from making efforts to comply with the standards. They must prove that any noncompliance does not significantly affect accessibility to avoid violating the rule.

For example, a state’s online renewal form that doesn’t meet WCAG 2.1, Level AA can cause significant problems for users with manual dexterity disabilities, requiring more time and assistance to complete tasks, violating the DOJ’s rule. Conversely, a minor deviation like a slightly lower color contrast ratio on a park information page might not prevent most users with vision disabilities from accessing the content, and the state could argue this does not constitute a violation.

Why Is There A Rise In ADA Compliance Lawsuits?

Website requirements for ADA compliance is a serious matter for any responsible business owner, especially considering the proliferation of related lawsuits in recent years. And, although the ADA does not explicitly call out website requirements, the DOJ has proactively enforced web accessibility laws. Moreover, federal and state courts have ruled that the ADA and related state statutes apply to inaccessible websites.

Why are we seeing more lawsuits related to website accessibility?

The surge in website accessibility lawsuits is largely due to the increasing necessity of the internet for daily activities, requiring that digital spaces be accessible to people with disabilities. Additionally, the lack of specific regulatory guidelines under the ADA for web accessibility leaves room for legal challenges as organizations struggle to meet varied standards of compliance.

Statistics reveal a dramatic uptick in legal action:

Over 4,000 lawsuits in 2021 – 79% against retail/e-commerce.
816 ADA Title III lawsuits in 2017
2,200 Title III cases in 2018 (180% increase)

While there was a decline in ADA Title III lawsuits in federal courts, the count still topped 8,200 for the second straight year. From 2013 to 2021, there was a steady climb in these cases, peaking at a significant 11,452 in 2021. Navigating this evolving landscape requires staying informed on ADA guidelines and proactively making web accessibility a priority.

Navigating ADA Compliance: 7 Key Guidelines and Tips for Your Website

The tips below will help you develop an ADA compatible website.

1. Integrate Keyboard Navigation

People with diminished mobility struggle to navigate websites with a mouse. Keyboard navigation enables users to scan and jump to content that matters most to them.

2. Provide Alt Text for Website Imagery

Alt text provides hearable image descriptions to screen-readers users with visual disabilities. It also helps users who turn off images due to sluggish internet connections. Concise and straightforward alt text can also positively impact SEO results.

3. Provide Appropriate Website Forms

Identify labels clearly and provide visual cues for form fields that show the information end users need to provide. Users who rely on screen readers also must know if their verifying information is valid or invalid—make sure your forms can report successful submissions or point site visitors back to the incorrect field.

4. Modify Timed Variables Accordingly

End users who use keyboard navigation typically need more time to use a website. Therefore, implement measures that stop time-outs from disrupting the end-user experience.

5. Provide Simple Imagery

Web pages crammed with too much visual content are among the most significant pain points for people with disabilities. Provide more open space and optimize color contrast to ensure digestible content for people of all abilities.

6. Audio and Video Alternatives

Provide corresponding transcripts for audio-only content and captions for all video elements. You can also integrate sign language interpretation for people with various hearing disabilities.

7. Remove Elements That May Cause Seizures

It’s best to avoid flashing imagery that may trigger serious episodes for people with epilepsy or similar medical challenges.

Rely on UserWay For Your ADA Compliance Needs

The AI-Powered UserWay Accessibility Widget can help your website comply with the ADA, the WCAG, and all other related standards. This ADA compliance software also ensures all your new content conforms with legal regulations. In addition, meeting the Americans With Disabilities Act guidelines, as defined by the DOJ, can help enhance your online sales. But at its core, accessibility is about opening your website to all end users, regardless of their abilities, because everyone should experience the digital world equally.

Please reach out for more details on the UserWay Accessibility Widget or click the link below to start a free trial.

The Children’s Online Privacy

Protection Rule (COPPA)

Implemented in 2000, the Children's Online Privacy Protection Rule (COPPA) applies to websites or online service operators (including apps, games, online social networks,VOIP services, IoT devices, and ad services) that knowingly collect, use, or disclose personal information from or about children under 13. Nonprofit entities engaged in non commercial activities are exempt from complying with COPPA.

Numerous factors determine, on a case-by-case basis, if a website or online service is aimed at children, including:

Subject matter
Visual content
Use of animated characters or child-related activities & incentives
Music and audio content
Age of models
Presence of celebrities that appeal to children
Language and other characteristics
Advertising appearing on the website or online service
Evidence concerning the audience composition and the intended audience

What is required according to COPPA?

Websites or online service operators must:

Provide notice on their website or online service concerning the information they collect from children, how it is used, and their disclosure practices (regulations include specific requirements for different types of notices, such as direct notice to parents and notices on the site).
Post clear and comprehensive online privacy policies detailing their practices for collecting, using and disclosing personal information from children.
Before collecting children's information, directly notify parents and obtain their verifiable consent (some exceptions apply for prior parental consent).
Give parents the option to consent to the collection and internal use of the child’s information while prohibiting unnecessary disclosure to third parties.
Give parents access to their child’s collected personal information and the ability to delete it.
Give parents the option to prevent further use or online collection of their child’s personal information.
Maintain confidentiality, security, and integrity of personal information collected from children, including ensuring that third parties to whom they disclose such information can also maintain the same level of privacy and security.
Delete personal information collected from children in a manner that protects against unauthorized access or use.
Retain personal information collected from children only as long as is necessary to fulfill its intended purpose.
Ensure that a child’s participation in an online activity is not conditioned on them providing more information than reasonably required for that activity.

What led to the Children’s Online Privacy Protection Rule?

Congress enacted COPPA in 1998, requiring the FTC to enforce corresponding children’s online privacy regulations. The original COPPA Rule took effect in 2000. The FTC updated the Rule in January 2013, with the revised rule taking effect in July of the same year.

How is the law enforced under COPPA?

The FTC treats COPPA violations like violations of FTC rules. Courts can impose penalties of up to $51,744 per violation, depending on the specifics of each case. COPPA also grants enforcement authority to states and certain federal agencies.

Choose UserWay for all of your compliance needs

Organizations worldwide trust UserWay for industry-leading accessibility and compliance. Learn about UserWay’s complete framework of products and services, from AI-powered tools and comprehensive accessibility checking to attorney-led legal support and enterprise solutions.

WCAG 2.2 Compliance:

A Guide to Best Conformance

The Web Content Accessibility Guidelines (WCAG) are the gold standard for inclusive design to make websites and digital content more accessible for people with disabilities. As technology and trends evolve, WCAG undergoes periodic evaluation and updates by the World Wide Web Consortium’s (W3C) Web Accessibility Initiative (WAI) and working groups in the disability community. The latest update is WCAG 2.2. When a business or agency has achieved “WCAG 2.2 compliance,” they have applied design principles that provide a high level of accessibility to their web content.

“Guidelines” are a set of recommendations or best practices designed to help organizations, or individuals achieve a certain goal or standard. They are not legally binding in and of themselves, and organizations or individuals are not required to follow them, so we generally speak of conforming with them. Laws, on the other hand, are binding rules or regulations that are established by a government or other legal authority. We “comply” with laws.

While the WCAG are not legally binding in and of themselves, the guidelines are widely recognized as the international standard for web accessibility, and many laws and regulations reference the WCAG as the benchmark for complying with the law. This is why people speak of WCAG compliance as a synonym for WCAG conformance.

What are the WCAG 2.2 compliance guidelines?

WCAG contains technical instructions and success criteria for website owners, designers, and developers. These criteria help them optimize websites to accommodate specific needs, such as assistive technology, screen readers, keyboard-only navigation, and more.

The WCAG 2.2 guidelines require websites to include the following:

Strong contrast between text and background color
Descriptive alt text for all graphics and images
Closed captions and transcriptions for video content
Form labels for all input fields
Appropriate descriptive tags for all navigation links and buttons

Nearly all digital accessibility regulations worldwide are based explicitly or implicitly on WCAG.

Why Should I Care About Compliance with WCAG 2.2 AA Standards?

Organizations and their design teams should be familiar with the WCAG 2.2 guidelines and continually monitor web content to ensure it meets requirements.

There are three commonly cited reasons to strive for WCAG compliance:

Ensuring inclusion for more people
Optimizing website performance and functionality
Compliance with federal and international regulations

Inclusion

Making websites accessible means removing barriers users face when navigating content. Expanding access means including people with disabilities related to vision, hand motor skills, and neurodiversity. Accessibility also refers to providing access to content from a variety of devices, including mobile phones, tablets, and assistive technology.

Disabilities impact everyone. More than 1 billion people worldwide have a disability. This doesn’t include the countless others who may experience changes in their ability to perform everyday tasks due to age, injury, illness, and even situational limitations.

Optimization

Creating content that adheres to WCAG principles and success criteria results in a well-structured and streamlined website that works for more people. This means a better user experience, more traffic, more conversions, increased sales, fewer abandoned carts, less churn, and a lower bounce rate.

For example, WCAG requires alternative and descriptive text for all non-text content. For an e-Commerce website, coding alt text tags and including transcripts for product marketing material will ensure people who have vision disabilities can buy things from your website. Additionally, keywords used in alternative text and transcripts can help better your SEO.

Regulations

The Web Content Accessibility Guidelines are the basis for nearly all digital accessibility regulations worldwide. Organizations that fail to comply with digital accessibility laws expose themselves to significant liabilities, including fines and civil lawsuits.

In the U.S, WCAG 2.0 compliance is explicitly required for government agencies and federal contractors under Section 508 of the Rehabilitation Act. According to many court rulings and the outcomes of U.S. Department of Justice actions, private U.S. businesses and organizations are also subject to website accessibility laws under Title III of the Americans with Disabilities Act (ADA). Based on numerous consent orders and settlement agreements, the ADA implicitly requires these private entities to meet WCAG standards.

WCAG 2.1 Level AA is required under EN 301 549 for the European Union.
The Accessibility for Ontarians with Disabilities Act (AODA) requires WCAG 2.0 Level AA compliance.
In Australia, the Web Accessibility National Transition Strategy requires all government agencies comply with WCAG. Private organizations are recommended to apply the WCAG to meet requirements under the Australian Disability Discrimination Act (DDA).
The Israel Standard (IS) 5568 applies to most businesses and requires them to adhere to WCAG standards.

With so many laws and regulations pointing directly to the WCAG, conforming with the guidelines means complying with the related law.

What does WCAG 2.2 AA Compliance Mean?

To understand what “WCAG 2.2 AA” or “WCAG 2.2 AAA” mean, we need to break down the terminology.

WCAG Versions

WCAG is a set of guidelines that has been published and maintained by the World Wide Web Consortium (W3C) for nearly 30 years and has undergone a number of revisions since WCAG 1.0, which is now obsolete. The WCAG guidelines are created with input from a diverse, global group of member organizations, academics, W3C staff, and the general public. Members of the UserWay team also contribute to the development of W3C standards.

WCAG 1.0 - May 5, 1999 (obsolete)
WCAG 2.0 - December, 2008
WCAG 2.1 - June 5, 2018
WCAG 2.2 - October, 2023

WCAG 2.0 and 2.1 are the most commonly referenced versions by laws and international regulations. WCAG 2.1 added 17 new success criteria. WCAG 2.2 expands on 2.1 further with more criteria around mobile interface accessibility, as well as a focus on people with cognitive or learning disabilities and users with low vision. WCAG 2.2 guidelines are the latest update for WCAG standards as of August 2023.

This latest update builds off several pillars of accessible web design that seek to help developers create content that is inclusive for people with visual, hearing, motor, and cognitive impairments. The Working Group responsible for WCAG continues to develop the standard, and WCAG 3.0 is already being drafted.

WCAG Levels

Now that we know about different versions of WCAG, we can begin to explain what someone means when they say that websites should comply with WCAG 2.2 AA standards.

WCAG (Web Content Accessibility Guidelines) has three levels of conformance: Level A, Level AA, and Level AAA. These levels are used to define the accessibility standards for web content. Each level has specific criteria that need to be met to ensure better accessibility for people with disabilities. The higher the level, the more inclusive and accessible the content becomes.

These levels include:

Level A: This is the basic level of accessibility. It includes guidelines that address the most fundamental barriers for users with disabilities. Meeting Level A ensures that some basic accessibility needs are addressed. Example: Providing alternative text for images so that screen readers can read aloud what the image is about. This helps people with visual impairments understand the content of the images.
Level AA: This is an intermediate level of accessibility, more comprehensive than Level A. Meeting Level AA means going a step further to accommodate a broader range of disabilities. It includes all Level A requirements and additional criteria. Example: Providing audio descriptions for videos to make them accessible to people who are blind or low vision. This ensures that everyone can understand the content of the videos, not just those who can visually perceive the video.
Level AAA: This is the highest level of accessibility. Meeting Level AAA indicates a very high standard of inclusivity and provides the best possible experience for users with disabilities. It includes all Level A and Level AA requirements, as well as more demanding criteria. Example: Providing users with text transcript, audio description, sign language interpretation, and robust audio descriptions for streaming media. This helps people with different disabilities like low vision, blind, deaf, and hard of hearing perceive content.

The difference between the levels is in the scope of accessibility they cover. While Level A addresses some basic accessibility needs, Level AA builds upon that to cater to a broader range of users. Level AAA goes even further, ensuring an exceptionally inclusive experience for users with various disabilities. Meeting Level AAA is generally more challenging and may require substantial design and development efforts compared to Level A or AA. However, all three levels are essential for creating a web environment that is truly accessible and usable by everyone. For WCAG compliance, businesses must conform to Level A and Level AA success criteria. AAA conformance is optional but represents the highest level of accessibility.

Success criteria under most WCAG guidelines determine whether content meets WCAG 2.2 Level A, AA, or AAA profiles. For instance, the guidelines for website navigation outlined in Success Criterion 1.2 provide different levels of WCAG classification based on their design and usage. Notice how the granularity increases as the criteria move from A to AAA.

SC 1.2

To get a clear understanding of the distinctions among Level A, Level AA, and Level AAA, let's explore an illustrative example. In this case, we will focus on success criteria associated with video content to demonstrate how each criterion encompasses unique requirements for achieving success.

Level A - 1.2.3 Audio Description or Media Alternative
Level AA - 1.2.5 Audio Description (Prerecorded)
Level AAA - 1.2.8 - Media Alternative (Prerecorded)

1. Success Criterion 1.2.3 (Level A): Videos with significant visual content must also have another way to perceive for people with visual impairments. This can be done with an audio description or a text alternative.

2. Success Criterion 1.2.5 (Level AA): This criterion focuses on providing audio descriptions for prerecorded video content. It ensures that people who cannot see the video can still comprehend its content by listening to the audio descriptions.

3. Success Criterion 1.2.8 (Level AAA): This success criterion asks to provide a text transcript of all the audio content, including the audio description. This helps users who have disabilities related to vision and hearing challenges, such as low vision individuals who cannot perceive captions/visual content, and users who have hearing challenges and cannot perceive audio content.

As the WCAG levels progress from A to AA to AAA, the success criteria become more stringent, requiring additional accessibility measures. By meeting the success criteria at each level, websites become increasingly accessible, making information and multimedia content available to a diverse audience of different abilities.

The Four WCAG Principles

The four principles that guide WCAG serve as the ultimate goals for web accessibility. The following principles provide a philosophy for achieving accessibility on websites globally.

1. Perceivable: To ensure that users can access and understand the information and interface elements of a website, it is important to present content in a way that can be perceived through at least one of the user's senses.

2. Operable: It is essential that user interface elements and navigation are fully operable by users. This means that users must be able to easily interact with the interface, and should not be required to perform actions they are unable to do.

3. Understandable: Users must be able to understand the information presented, and should know how to effectively use and navigate the website.

4. Robust: A wide range of user agents, including assistive technologies, should be able to access website information and use the interface. This means that users should be able to continue accessing content even as technologies change.

13 High Level Guidelines in the WCAG Principles

There are also 13 guidelines that fall within the four WCAG principles explained above. A good way to think about their relationship is how these measurable objectives can be used to meet general goals. They are described below and grouped with the principle they support.

Perceivable

Text Alternatives - Text alternatives are equivalent replacements for non-text elements, such as providing a label for a form field or a description for an image. These alternatives enable users who cannot see or interact with the non-text content to understand its purpose and context.
Time-Based Media - Alt text, transcripts, and closed captions should synchronize with interactive media.
Adaptable - All content should be capable of adjusting without losing information when the display size of a website is changed.
Distinguishable - Content should be formatted with appropriate spacing and text size. This includes strong contrast of foreground text with background color and images.

Operable

Keyboard Accessible - Websites should be completely and easily operable through keyboard-only navigation. This means websites should not disrupt typical functions of keystrokes or short-cut commands.
Enough Time - Ample time should be programmed for all time-based media and access without losing the chance to read or enter respective responses.
Seizures and Physical Reactions - All display content and website design should avoid excessive flashing and other typical triggers for seizures.
Navigable - A website should offer users straightforward and logical ways to discover and find content. Navigation menus and drop-downs should make sense and be easy to use. Heading and subheading tags should be used to break up long text boxes.
Input Modalities - Users should have a similar website experience even with different options for input beyond just a keyboard and mouse. This includes switch controls, eye trackers, and voice commands.

Understandable

Readable - All writing should be clear and understandable, avoiding jargon, unusual words and having limited acronyms. Where unfamiliar language is required, it should be qualified with definitions and the full unabbreviated phrase.
Predictable - Websites and content should be built to function as people expect them to, with vertical scroll orientation and all navigation links included in the heading and footer margins.
Input Assistance - Users should be able to use saved browser input information to avoid mistakes and ensure accuracy when attempting to fill out login fields and sign-up forms.

Robust

Compatible - Websites should strive to be as compatible as possible with current and future user agents, including assistive technologies, in order to provide the best user experience for all users.