he Web Content Accessibility Guidelines (WCAG) are the global standard for making websites and digital content accessible to people with disabilities.<\/strong><\/i><\/p>\nDeveloped by the Web Accessibility Initiative (WAI)<\/strong> of the World Wide Web Consortium (W3C)<\/strong>, WCAG provides 86 testable success criteria<\/strong> that help website owners, web designers, and content authors create accessible websites. When an organization conforms with WCAG, they have met accessibility standards that remove barriers for users with a wide range of disabilities, including visual, hearing, motor, and cognitive disabilities.<\/p>\nWCAG conformance is sometimes called \u201cWCAG compliance.\u201d WCAG itself is not a law; however, WCAG is the de facto standard for compliance with many U.S. and global laws. With digital accessibility lawsuits remaining widespread, WCAG compliance is no longer optional\u2014it\u2019s a legal and business necessity.<\/p>\nKey insights<\/strong><\/h3>\n\nWCAG compliance means meeting the Web Content Accessibility Guidelines, the international standard for digital accessibility referenced by many accessibility laws.<\/li>\nWCAG 2.2<\/strong> is the current version with 86 success criteria; WCAG 2.1 Level AA<\/strong> is the standard most frequently referenced by laws and regulations.<\/li>\nThe four WCAG principles are Perceivable, Operable, Understandable, and Robust (POUR).<\/li>\nState and local governments must conform with WCAG 2.1 AA by April 24, 2026<\/strong> under the DOJ’s ADA Title II Final Rule.<\/li>\nThe European Accessibility Act<\/strong> took effect June 2025, requiring conformance with EN 301 549\u2014an EU standard that incorporates WCAG\u2014for many businesses selling to EU customers.<\/li>\nAccessibility audits should combine automated tools with manual testing using assistive technology.<\/li>\n<\/ul>\nWhat is WCAG compliance?<\/strong><\/h3>\nWCAG compliance<\/strong> means a website meets the Web Content Accessibility Guidelines\u2014the global standard for web accessibility developed by the World Wide Web Consortium (W3C). The term \u201cWCAG compliance\u201d is really a misnomer: because WCAG is a standard, not a law, the technically correct term is \u201cWCAG conformance.\u201d However, \u201cWCAG compliance\u201d is widely used as a synonym for \u201cWCAG conformance.\u201d<\/p>\nThe WCAG guidelines provide technical success criteria that help website owners make web content accessible to people with disabilities. This includes users who rely on screen readers, keyboard navigation, captions, and other assistive technology. When your website meets WCAG requirements, people with visual, hearing, motor, and cognitive or learning disabilities can perceive, navigate, and interact with your web pages.<\/p>\n\n\n\n\nWCAG version<\/th>\nRelease date<\/th>\nSuccess criteria<\/th>\nStatus<\/th>\n<\/tr>\n<\/thead>\n\n\nWCAG 2.0<\/td>\nDecember 2008<\/td>\n61 criteria<\/td>\nStill referenced in many laws<\/td>\n<\/tr>\n\nWCAG 2.1<\/td>\nJune 2018<\/td>\n78 criteria (+17 new)<\/td>\nCurrent legal standard<\/td>\n<\/tr>\n\nWCAG 2.2<\/td>\nOctober 2023<\/td>\n86 criteria (+9 new)<\/td>\nLatest W3C recommendation<\/td>\n<\/tr>\n\nWCAG 3.0<\/td>\nIn development<\/td>\n174 outcomes (proposed)<\/td>\nExpected 2028 or later<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nWhat does WCAG cover?<\/strong><\/h3>\nWCAG was originally developed for HTML content that people access through web browsers. However, the relevance of these guidelines extends far beyond traditional web pages. WCAG applies broadly to web content and technologies as long as they can be interpreted by user agents, including assistive technologies.<\/p>\n<\/figure>\n\n\n\n\nContent type<\/th>\nExamples<\/th>\nWCAG applies?<\/th>\n<\/tr>\n<\/thead>\n\n\nWebsites<\/td>\nPublic sites, intranets, web applications<\/td>\nYes<\/td>\n<\/tr>\n\nMobile apps<\/td>\niOS and Android applications<\/td>\nYes<\/td>\n<\/tr>\n\nDocuments<\/td>\nPDFs, Word files, spreadsheets<\/td>\nYes<\/td>\n<\/tr>\n\nMultimedia<\/td>\nVideos, podcasts, audio files<\/td>\nYes<\/td>\n<\/tr>\n\nEmail<\/td>\nHTML newsletters, marketing emails<\/td>\nYes<\/td>\n<\/tr>\n\nDigital kiosks<\/td>\nSelf-service terminals, ATMs<\/td>\nYes<\/td>\n<\/tr>\n\nE-learning<\/td>\nOnline courses, training modules<\/td>\nYes<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nLaws referencing WCAG and related standards cover different types of digital experiences. For example, the DOJ’s ADA Title II rule specifically covers web and mobile content (including digital documents) provided by state and local governments. The European Accessibility Act applies to a wide range of consumer products and services, including e-commerce platforms, banking services, and consumer electronics. Any digital content that serves the public should follow WCAG guidelines to ensure people with disabilities can access it.<\/p>\nLaws referencing WCAG and related standards cover different types of digital experiences. For example, the DOJ’s ADA Title II rule specifically covers web and mobile content (including digital documents) provided by state and local governments. The European Accessibility Act applies to a wide range of consumer products and services, including e-commerce platforms, banking services, and consumer electronics. Any digital content that serves the public should follow WCAG guidelines to ensure people with disabilities can access it.<\/p>\nWho needs to comply with WCAG?<\/strong><\/h3>\nAlmost any organization with a digital presence should comply with WCAG. Legal requirements vary by sector, but accessibility benefits all businesses.<\/p>\n\n\n\n\nOrganization type<\/th>\nLegal requirement<\/th>\nWhy comply<\/th>\n<\/tr>\n<\/thead>\n\n\nFederal government agencies<\/td>\nSection 508 (mandatory)<\/td>\nRequired by law<\/td>\n<\/tr>\n\nState and local governments<\/td>\nADA Title II (mandatory)<\/td>\nApril 2026 deadline<\/td>\n<\/tr>\n\nPrivate businesses<\/td>\nADA Title III (court-enforced)<\/td>\nLawsuit prevention<\/td>\n<\/tr>\n\nE-commerce websites<\/td>\nEAA in EU (mandatory)<\/td>\nMarket access<\/td>\n<\/tr>\n\nHealthcare providers<\/td>\nADA + Section 504<\/td>\nPatient access<\/td>\n<\/tr>\n\nEducational institutions<\/td>\nADA + Section 504<\/td>\nStudent access<\/td>\n<\/tr>\n\nNonprofits<\/td>\nADA applies<\/td>\nServe all constituents<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/p>\nEven without a specific legal mandate, website owners benefit from WCAG compliance. Accessible websites reach more users, perform better in search rankings, and reduce legal risk. Over 1 billion people<\/strong> worldwide have disabilities\u2014making websites accessible expands your potential audience significantly.<\/p>\nIs WCAG a legal requirement in the US?<\/strong><\/h3>\nYes, for most organizations.<\/strong> WCAG 2.1 Level AA is the de facto standard for web accessibility under multiple US laws, and courts consistently use WCAG as the benchmark for accessibility compliance.<\/p>\nThe DOJ’s ADA Title II Final Rule<\/strong> formally adopted WCAG 2.1 Level AA for all state and local governments. This covers government websites, mobile apps, digital documents, and online services.<\/p>\n<\/figure>\n\n\n\n\nEntity type<\/th>\nPopulation<\/th>\nCompliance deadline<\/th>\n<\/tr>\n<\/thead>\n\n\nLarge public entities<\/td>\n50,000+ residents<\/td>\nApril 24, 2026<\/td>\n<\/tr>\n\nSmall public entities<\/td>\nUnder 50,000 residents<\/td>\nApril 26, 2027<\/td>\n<\/tr>\n\nSpecial district governments<\/td>\nAny size<\/td>\nApril 26, 2027<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nFor private businesses, Title III of the Americans with Disabilities Act<\/strong> requires website accessibility based on court rulings and DOJ settlement agreements. Section 508<\/strong> of the Rehabilitation Act explicitly requires WCAG compliance for federal government agencies and contractors.<\/p>\nDigital accessibility lawsuits remain widespread. Automated tools now generate complaints at scale, making any business with accessibility issues a potential target.<\/p>\nWhat accessibility laws require WCAG compliance?<\/strong><\/h3>\nDigital accessibility legislation worldwide references WCAG as the technical standard for compliance. Meeting WCAG requirements satisfies most accessibility regulations.<\/p>\n\n\n\n\nLaw \/ regulation<\/th>\nGeographic scope<\/th>\nWCAG standard required<\/th>\nCompliance deadline<\/th>\n<\/tr>\n<\/thead>\n\n\nADA Title II (DOJ Rule)<\/td>\nUS state \/ local governments<\/td>\nWCAG 2.1 AA<\/td>\nApril 2026 \/ 2027<\/td>\n<\/tr>\n\nADA Title III<\/td>\nUS private businesses<\/td>\nWCAG 2.1 AA (de facto standard per courts)<\/td>\nOngoing<\/td>\n<\/tr>\n\nSection 508<\/td>\nUS federal agencies<\/td>\nWCAG 2.0 AA<\/td>\nCurrent<\/td>\n<\/tr>\n\nEuropean Accessibility Act<\/td>\nBusinesses serving EU consumers<\/td>\nEN 301 549 (Incorporates WCAG 2.1 AA)<\/td>\nJune 28, 2025<\/td>\n<\/tr>\n\nAODA<\/td>\nOntario, Canada<\/td>\nWCAG 2.0 AA<\/td>\nCurrent<\/td>\n<\/tr>\n\nEuropean Web Accessibility Directive<\/td>\nEuropean Union public sector<\/td>\nEN 301 549 (Incorporates WCAG 2.1 AA)<\/td>\nCurrent<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nThe European Accessibility Act (EAA) became enforceable on June 28, 2025<\/strong>, requiring WCAG compliance for many businesses selling digital products or services to EU customers. Penalties vary by member state\u2014fines reach \u20ac100,000 in Germany<\/strong> and \u20ac250,000 in France<\/strong>. Non-compliant products can be removed from the market entirely.<\/p>\nWhat are the four principles of WCAG?<\/strong><\/h3>\nThe four principles of WCAG\u2014known as POUR<\/strong>\u2014are Perceivable, Operable, Understandable, and Robust. These principles guide all WCAG success criteria and define what it means for web content to be accessible.<\/p>\n\n\n\n\nPrinciple<\/th>\nWhat It Means<\/th>\nExample Requirement<\/th>\n<\/tr>\n<\/thead>\n\n\nPerceivable<\/td>\nUsers must be able to perceive content through at least one sense.<\/td>\nProvide text alternatives for images; add captions to videos.<\/td>\n<\/tr>\n\nOperable<\/td>\nUsers must be able to operate the interface.<\/td>\nEnable keyboard access; provide enough time to read content.<\/td>\n<\/tr>\n\nUnderstandable<\/td>\nUsers must understand the content and how to use it.<\/td>\nUse clear language; make navigation predictable.<\/td>\n<\/tr>\n\nRobust<\/td>\nContent must work with current and future user agents.<\/td>\nUse valid code; ensure compatibility with assistive technology.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nWhat are the 13 WCAG guidelines?<\/strong><\/h3>\nThe four WCAG principles contain 13 guidelines<\/strong> that provide specific objectives for web accessibility. Each guideline has testable success criteria at three WCAG conformance levels: A, AA, and AAA.<\/p>\nPerceivable guidelines<\/strong><\/h3>\n1.1 Text Alternatives<\/strong> \u2014 Provide text alternatives for non-text content. This includes alt text for images, labels for form fields, and descriptions for icons. Text alternatives let screen reader users understand content they cannot see.<\/p>\n1.2 Time-Based Media<\/strong> \u2014 Provide alternatives for audio and video content. This includes captions for videos, transcripts for audio files, and audio descriptions for visual content.<\/p>\n1.3 Adaptable<\/strong> \u2014 Create content that can be presented in different ways without losing information. Web pages should maintain meaning when users change display settings or use assistive technology.<\/p>\n1.4 Distinguishable<\/strong> \u2014 Make content easy to see and hear. This includes sufficient color contrast, resizable text, and audio controls. Users with low vision or hearing loss depend on these features.<\/p>\nOperable guidelines<\/strong><\/h3>\n2.1 Keyboard Accessible<\/strong> \u2014 Make all functionality available from a keyboard. Users who cannot use a mouse must be able to navigate web content using keyboard access alone.<\/p>\n2.2 Enough Time<\/strong> \u2014 Give users enough time to read and interact with content. Avoid strict time limits, or provide ways to extend them.<\/p>\n2.3 Seizures and Physical Reactions<\/strong> \u2014 Do not design content that causes seizures. Avoid flashing content that could trigger photosensitive epilepsy.<\/p>\n2.4 Navigable<\/strong> \u2014 Help users navigate and find content. Provide clear headings, descriptive link text, and logical focus order.<\/p>\n2.5 Input Modalities<\/strong> \u2014 Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.<\/p>\nUnderstandable guidelines<\/h3>\n3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
Developed by the Web Accessibility Initiative (WAI)<\/strong> of the World Wide Web Consortium (W3C)<\/strong>, WCAG provides 86 testable success criteria<\/strong> that help website owners, web designers, and content authors create accessible websites. When an organization conforms with WCAG, they have met accessibility standards that remove barriers for users with a wide range of disabilities, including visual, hearing, motor, and cognitive disabilities.<\/p>\nWCAG conformance is sometimes called \u201cWCAG compliance.\u201d WCAG itself is not a law; however, WCAG is the de facto standard for compliance with many U.S. and global laws. With digital accessibility lawsuits remaining widespread, WCAG compliance is no longer optional\u2014it\u2019s a legal and business necessity.<\/p>\nKey insights<\/strong><\/h3>\n\nWCAG compliance means meeting the Web Content Accessibility Guidelines, the international standard for digital accessibility referenced by many accessibility laws.<\/li>\nWCAG 2.2<\/strong> is the current version with 86 success criteria; WCAG 2.1 Level AA<\/strong> is the standard most frequently referenced by laws and regulations.<\/li>\nThe four WCAG principles are Perceivable, Operable, Understandable, and Robust (POUR).<\/li>\nState and local governments must conform with WCAG 2.1 AA by April 24, 2026<\/strong> under the DOJ’s ADA Title II Final Rule.<\/li>\nThe European Accessibility Act<\/strong> took effect June 2025, requiring conformance with EN 301 549\u2014an EU standard that incorporates WCAG\u2014for many businesses selling to EU customers.<\/li>\nAccessibility audits should combine automated tools with manual testing using assistive technology.<\/li>\n<\/ul>\nWhat is WCAG compliance?<\/strong><\/h3>\nWCAG compliance<\/strong> means a website meets the Web Content Accessibility Guidelines\u2014the global standard for web accessibility developed by the World Wide Web Consortium (W3C). The term \u201cWCAG compliance\u201d is really a misnomer: because WCAG is a standard, not a law, the technically correct term is \u201cWCAG conformance.\u201d However, \u201cWCAG compliance\u201d is widely used as a synonym for \u201cWCAG conformance.\u201d<\/p>\nThe WCAG guidelines provide technical success criteria that help website owners make web content accessible to people with disabilities. This includes users who rely on screen readers, keyboard navigation, captions, and other assistive technology. When your website meets WCAG requirements, people with visual, hearing, motor, and cognitive or learning disabilities can perceive, navigate, and interact with your web pages.<\/p>\n\n\n\n\nWCAG version<\/th>\nRelease date<\/th>\nSuccess criteria<\/th>\nStatus<\/th>\n<\/tr>\n<\/thead>\n\n\nWCAG 2.0<\/td>\nDecember 2008<\/td>\n61 criteria<\/td>\nStill referenced in many laws<\/td>\n<\/tr>\n\nWCAG 2.1<\/td>\nJune 2018<\/td>\n78 criteria (+17 new)<\/td>\nCurrent legal standard<\/td>\n<\/tr>\n\nWCAG 2.2<\/td>\nOctober 2023<\/td>\n86 criteria (+9 new)<\/td>\nLatest W3C recommendation<\/td>\n<\/tr>\n\nWCAG 3.0<\/td>\nIn development<\/td>\n174 outcomes (proposed)<\/td>\nExpected 2028 or later<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nWhat does WCAG cover?<\/strong><\/h3>\nWCAG was originally developed for HTML content that people access through web browsers. However, the relevance of these guidelines extends far beyond traditional web pages. WCAG applies broadly to web content and technologies as long as they can be interpreted by user agents, including assistive technologies.<\/p>\n<\/figure>\n\n\n\n\nContent type<\/th>\nExamples<\/th>\nWCAG applies?<\/th>\n<\/tr>\n<\/thead>\n\n\nWebsites<\/td>\nPublic sites, intranets, web applications<\/td>\nYes<\/td>\n<\/tr>\n\nMobile apps<\/td>\niOS and Android applications<\/td>\nYes<\/td>\n<\/tr>\n\nDocuments<\/td>\nPDFs, Word files, spreadsheets<\/td>\nYes<\/td>\n<\/tr>\n\nMultimedia<\/td>\nVideos, podcasts, audio files<\/td>\nYes<\/td>\n<\/tr>\n\nEmail<\/td>\nHTML newsletters, marketing emails<\/td>\nYes<\/td>\n<\/tr>\n\nDigital kiosks<\/td>\nSelf-service terminals, ATMs<\/td>\nYes<\/td>\n<\/tr>\n\nE-learning<\/td>\nOnline courses, training modules<\/td>\nYes<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nLaws referencing WCAG and related standards cover different types of digital experiences. For example, the DOJ’s ADA Title II rule specifically covers web and mobile content (including digital documents) provided by state and local governments. The European Accessibility Act applies to a wide range of consumer products and services, including e-commerce platforms, banking services, and consumer electronics. Any digital content that serves the public should follow WCAG guidelines to ensure people with disabilities can access it.<\/p>\nLaws referencing WCAG and related standards cover different types of digital experiences. For example, the DOJ’s ADA Title II rule specifically covers web and mobile content (including digital documents) provided by state and local governments. The European Accessibility Act applies to a wide range of consumer products and services, including e-commerce platforms, banking services, and consumer electronics. Any digital content that serves the public should follow WCAG guidelines to ensure people with disabilities can access it.<\/p>\nWho needs to comply with WCAG?<\/strong><\/h3>\nAlmost any organization with a digital presence should comply with WCAG. Legal requirements vary by sector, but accessibility benefits all businesses.<\/p>\n\n\n\n\nOrganization type<\/th>\nLegal requirement<\/th>\nWhy comply<\/th>\n<\/tr>\n<\/thead>\n\n\nFederal government agencies<\/td>\nSection 508 (mandatory)<\/td>\nRequired by law<\/td>\n<\/tr>\n\nState and local governments<\/td>\nADA Title II (mandatory)<\/td>\nApril 2026 deadline<\/td>\n<\/tr>\n\nPrivate businesses<\/td>\nADA Title III (court-enforced)<\/td>\nLawsuit prevention<\/td>\n<\/tr>\n\nE-commerce websites<\/td>\nEAA in EU (mandatory)<\/td>\nMarket access<\/td>\n<\/tr>\n\nHealthcare providers<\/td>\nADA + Section 504<\/td>\nPatient access<\/td>\n<\/tr>\n\nEducational institutions<\/td>\nADA + Section 504<\/td>\nStudent access<\/td>\n<\/tr>\n\nNonprofits<\/td>\nADA applies<\/td>\nServe all constituents<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/p>\nEven without a specific legal mandate, website owners benefit from WCAG compliance. Accessible websites reach more users, perform better in search rankings, and reduce legal risk. Over 1 billion people<\/strong> worldwide have disabilities\u2014making websites accessible expands your potential audience significantly.<\/p>\nIs WCAG a legal requirement in the US?<\/strong><\/h3>\nYes, for most organizations.<\/strong> WCAG 2.1 Level AA is the de facto standard for web accessibility under multiple US laws, and courts consistently use WCAG as the benchmark for accessibility compliance.<\/p>\nThe DOJ’s ADA Title II Final Rule<\/strong> formally adopted WCAG 2.1 Level AA for all state and local governments. This covers government websites, mobile apps, digital documents, and online services.<\/p>\n<\/figure>\n\n\n\n\nEntity type<\/th>\nPopulation<\/th>\nCompliance deadline<\/th>\n<\/tr>\n<\/thead>\n\n\nLarge public entities<\/td>\n50,000+ residents<\/td>\nApril 24, 2026<\/td>\n<\/tr>\n\nSmall public entities<\/td>\nUnder 50,000 residents<\/td>\nApril 26, 2027<\/td>\n<\/tr>\n\nSpecial district governments<\/td>\nAny size<\/td>\nApril 26, 2027<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nFor private businesses, Title III of the Americans with Disabilities Act<\/strong> requires website accessibility based on court rulings and DOJ settlement agreements. Section 508<\/strong> of the Rehabilitation Act explicitly requires WCAG compliance for federal government agencies and contractors.<\/p>\nDigital accessibility lawsuits remain widespread. Automated tools now generate complaints at scale, making any business with accessibility issues a potential target.<\/p>\nWhat accessibility laws require WCAG compliance?<\/strong><\/h3>\nDigital accessibility legislation worldwide references WCAG as the technical standard for compliance. Meeting WCAG requirements satisfies most accessibility regulations.<\/p>\n\n\n\n\nLaw \/ regulation<\/th>\nGeographic scope<\/th>\nWCAG standard required<\/th>\nCompliance deadline<\/th>\n<\/tr>\n<\/thead>\n\n\nADA Title II (DOJ Rule)<\/td>\nUS state \/ local governments<\/td>\nWCAG 2.1 AA<\/td>\nApril 2026 \/ 2027<\/td>\n<\/tr>\n\nADA Title III<\/td>\nUS private businesses<\/td>\nWCAG 2.1 AA (de facto standard per courts)<\/td>\nOngoing<\/td>\n<\/tr>\n\nSection 508<\/td>\nUS federal agencies<\/td>\nWCAG 2.0 AA<\/td>\nCurrent<\/td>\n<\/tr>\n\nEuropean Accessibility Act<\/td>\nBusinesses serving EU consumers<\/td>\nEN 301 549 (Incorporates WCAG 2.1 AA)<\/td>\nJune 28, 2025<\/td>\n<\/tr>\n\nAODA<\/td>\nOntario, Canada<\/td>\nWCAG 2.0 AA<\/td>\nCurrent<\/td>\n<\/tr>\n\nEuropean Web Accessibility Directive<\/td>\nEuropean Union public sector<\/td>\nEN 301 549 (Incorporates WCAG 2.1 AA)<\/td>\nCurrent<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nThe European Accessibility Act (EAA) became enforceable on June 28, 2025<\/strong>, requiring WCAG compliance for many businesses selling digital products or services to EU customers. Penalties vary by member state\u2014fines reach \u20ac100,000 in Germany<\/strong> and \u20ac250,000 in France<\/strong>. Non-compliant products can be removed from the market entirely.<\/p>\nWhat are the four principles of WCAG?<\/strong><\/h3>\nThe four principles of WCAG\u2014known as POUR<\/strong>\u2014are Perceivable, Operable, Understandable, and Robust. These principles guide all WCAG success criteria and define what it means for web content to be accessible.<\/p>\n\n\n\n\nPrinciple<\/th>\nWhat It Means<\/th>\nExample Requirement<\/th>\n<\/tr>\n<\/thead>\n\n\nPerceivable<\/td>\nUsers must be able to perceive content through at least one sense.<\/td>\nProvide text alternatives for images; add captions to videos.<\/td>\n<\/tr>\n\nOperable<\/td>\nUsers must be able to operate the interface.<\/td>\nEnable keyboard access; provide enough time to read content.<\/td>\n<\/tr>\n\nUnderstandable<\/td>\nUsers must understand the content and how to use it.<\/td>\nUse clear language; make navigation predictable.<\/td>\n<\/tr>\n\nRobust<\/td>\nContent must work with current and future user agents.<\/td>\nUse valid code; ensure compatibility with assistive technology.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nWhat are the 13 WCAG guidelines?<\/strong><\/h3>\nThe four WCAG principles contain 13 guidelines<\/strong> that provide specific objectives for web accessibility. Each guideline has testable success criteria at three WCAG conformance levels: A, AA, and AAA.<\/p>\nPerceivable guidelines<\/strong><\/h3>\n1.1 Text Alternatives<\/strong> \u2014 Provide text alternatives for non-text content. This includes alt text for images, labels for form fields, and descriptions for icons. Text alternatives let screen reader users understand content they cannot see.<\/p>\n1.2 Time-Based Media<\/strong> \u2014 Provide alternatives for audio and video content. This includes captions for videos, transcripts for audio files, and audio descriptions for visual content.<\/p>\n1.3 Adaptable<\/strong> \u2014 Create content that can be presented in different ways without losing information. Web pages should maintain meaning when users change display settings or use assistive technology.<\/p>\n1.4 Distinguishable<\/strong> \u2014 Make content easy to see and hear. This includes sufficient color contrast, resizable text, and audio controls. Users with low vision or hearing loss depend on these features.<\/p>\nOperable guidelines<\/strong><\/h3>\n2.1 Keyboard Accessible<\/strong> \u2014 Make all functionality available from a keyboard. Users who cannot use a mouse must be able to navigate web content using keyboard access alone.<\/p>\n2.2 Enough Time<\/strong> \u2014 Give users enough time to read and interact with content. Avoid strict time limits, or provide ways to extend them.<\/p>\n2.3 Seizures and Physical Reactions<\/strong> \u2014 Do not design content that causes seizures. Avoid flashing content that could trigger photosensitive epilepsy.<\/p>\n2.4 Navigable<\/strong> \u2014 Help users navigate and find content. Provide clear headings, descriptive link text, and logical focus order.<\/p>\n2.5 Input Modalities<\/strong> \u2014 Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.<\/p>\nUnderstandable guidelines<\/h3>\n3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
WCAG conformance is sometimes called \u201cWCAG compliance.\u201d WCAG itself is not a law; however, WCAG is the de facto standard for compliance with many U.S. and global laws. With digital accessibility lawsuits remaining widespread, WCAG compliance is no longer optional\u2014it\u2019s a legal and business necessity.<\/p>\n
WCAG compliance<\/strong> means a website meets the Web Content Accessibility Guidelines\u2014the global standard for web accessibility developed by the World Wide Web Consortium (W3C). The term \u201cWCAG compliance\u201d is really a misnomer: because WCAG is a standard, not a law, the technically correct term is \u201cWCAG conformance.\u201d However, \u201cWCAG compliance\u201d is widely used as a synonym for \u201cWCAG conformance.\u201d<\/p>\nThe WCAG guidelines provide technical success criteria that help website owners make web content accessible to people with disabilities. This includes users who rely on screen readers, keyboard navigation, captions, and other assistive technology. When your website meets WCAG requirements, people with visual, hearing, motor, and cognitive or learning disabilities can perceive, navigate, and interact with your web pages.<\/p>\n\n\n\n\nWCAG version<\/th>\nRelease date<\/th>\nSuccess criteria<\/th>\nStatus<\/th>\n<\/tr>\n<\/thead>\n\n\nWCAG 2.0<\/td>\nDecember 2008<\/td>\n61 criteria<\/td>\nStill referenced in many laws<\/td>\n<\/tr>\n\nWCAG 2.1<\/td>\nJune 2018<\/td>\n78 criteria (+17 new)<\/td>\nCurrent legal standard<\/td>\n<\/tr>\n\nWCAG 2.2<\/td>\nOctober 2023<\/td>\n86 criteria (+9 new)<\/td>\nLatest W3C recommendation<\/td>\n<\/tr>\n\nWCAG 3.0<\/td>\nIn development<\/td>\n174 outcomes (proposed)<\/td>\nExpected 2028 or later<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nWhat does WCAG cover?<\/strong><\/h3>\nWCAG was originally developed for HTML content that people access through web browsers. However, the relevance of these guidelines extends far beyond traditional web pages. WCAG applies broadly to web content and technologies as long as they can be interpreted by user agents, including assistive technologies.<\/p>\n<\/figure>\n\n\n\n\nContent type<\/th>\nExamples<\/th>\nWCAG applies?<\/th>\n<\/tr>\n<\/thead>\n\n\nWebsites<\/td>\nPublic sites, intranets, web applications<\/td>\nYes<\/td>\n<\/tr>\n\nMobile apps<\/td>\niOS and Android applications<\/td>\nYes<\/td>\n<\/tr>\n\nDocuments<\/td>\nPDFs, Word files, spreadsheets<\/td>\nYes<\/td>\n<\/tr>\n\nMultimedia<\/td>\nVideos, podcasts, audio files<\/td>\nYes<\/td>\n<\/tr>\n\nEmail<\/td>\nHTML newsletters, marketing emails<\/td>\nYes<\/td>\n<\/tr>\n\nDigital kiosks<\/td>\nSelf-service terminals, ATMs<\/td>\nYes<\/td>\n<\/tr>\n\nE-learning<\/td>\nOnline courses, training modules<\/td>\nYes<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nLaws referencing WCAG and related standards cover different types of digital experiences. For example, the DOJ’s ADA Title II rule specifically covers web and mobile content (including digital documents) provided by state and local governments. The European Accessibility Act applies to a wide range of consumer products and services, including e-commerce platforms, banking services, and consumer electronics. Any digital content that serves the public should follow WCAG guidelines to ensure people with disabilities can access it.<\/p>\nLaws referencing WCAG and related standards cover different types of digital experiences. For example, the DOJ’s ADA Title II rule specifically covers web and mobile content (including digital documents) provided by state and local governments. The European Accessibility Act applies to a wide range of consumer products and services, including e-commerce platforms, banking services, and consumer electronics. Any digital content that serves the public should follow WCAG guidelines to ensure people with disabilities can access it.<\/p>\nWho needs to comply with WCAG?<\/strong><\/h3>\nAlmost any organization with a digital presence should comply with WCAG. Legal requirements vary by sector, but accessibility benefits all businesses.<\/p>\n\n\n\n\nOrganization type<\/th>\nLegal requirement<\/th>\nWhy comply<\/th>\n<\/tr>\n<\/thead>\n\n\nFederal government agencies<\/td>\nSection 508 (mandatory)<\/td>\nRequired by law<\/td>\n<\/tr>\n\nState and local governments<\/td>\nADA Title II (mandatory)<\/td>\nApril 2026 deadline<\/td>\n<\/tr>\n\nPrivate businesses<\/td>\nADA Title III (court-enforced)<\/td>\nLawsuit prevention<\/td>\n<\/tr>\n\nE-commerce websites<\/td>\nEAA in EU (mandatory)<\/td>\nMarket access<\/td>\n<\/tr>\n\nHealthcare providers<\/td>\nADA + Section 504<\/td>\nPatient access<\/td>\n<\/tr>\n\nEducational institutions<\/td>\nADA + Section 504<\/td>\nStudent access<\/td>\n<\/tr>\n\nNonprofits<\/td>\nADA applies<\/td>\nServe all constituents<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/p>\nEven without a specific legal mandate, website owners benefit from WCAG compliance. Accessible websites reach more users, perform better in search rankings, and reduce legal risk. Over 1 billion people<\/strong> worldwide have disabilities\u2014making websites accessible expands your potential audience significantly.<\/p>\nIs WCAG a legal requirement in the US?<\/strong><\/h3>\nYes, for most organizations.<\/strong> WCAG 2.1 Level AA is the de facto standard for web accessibility under multiple US laws, and courts consistently use WCAG as the benchmark for accessibility compliance.<\/p>\nThe DOJ’s ADA Title II Final Rule<\/strong> formally adopted WCAG 2.1 Level AA for all state and local governments. This covers government websites, mobile apps, digital documents, and online services.<\/p>\n<\/figure>\n\n\n\n\nEntity type<\/th>\nPopulation<\/th>\nCompliance deadline<\/th>\n<\/tr>\n<\/thead>\n\n\nLarge public entities<\/td>\n50,000+ residents<\/td>\nApril 24, 2026<\/td>\n<\/tr>\n\nSmall public entities<\/td>\nUnder 50,000 residents<\/td>\nApril 26, 2027<\/td>\n<\/tr>\n\nSpecial district governments<\/td>\nAny size<\/td>\nApril 26, 2027<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nFor private businesses, Title III of the Americans with Disabilities Act<\/strong> requires website accessibility based on court rulings and DOJ settlement agreements. Section 508<\/strong> of the Rehabilitation Act explicitly requires WCAG compliance for federal government agencies and contractors.<\/p>\nDigital accessibility lawsuits remain widespread. Automated tools now generate complaints at scale, making any business with accessibility issues a potential target.<\/p>\nWhat accessibility laws require WCAG compliance?<\/strong><\/h3>\nDigital accessibility legislation worldwide references WCAG as the technical standard for compliance. Meeting WCAG requirements satisfies most accessibility regulations.<\/p>\n\n\n\n\nLaw \/ regulation<\/th>\nGeographic scope<\/th>\nWCAG standard required<\/th>\nCompliance deadline<\/th>\n<\/tr>\n<\/thead>\n\n\nADA Title II (DOJ Rule)<\/td>\nUS state \/ local governments<\/td>\nWCAG 2.1 AA<\/td>\nApril 2026 \/ 2027<\/td>\n<\/tr>\n\nADA Title III<\/td>\nUS private businesses<\/td>\nWCAG 2.1 AA (de facto standard per courts)<\/td>\nOngoing<\/td>\n<\/tr>\n\nSection 508<\/td>\nUS federal agencies<\/td>\nWCAG 2.0 AA<\/td>\nCurrent<\/td>\n<\/tr>\n\nEuropean Accessibility Act<\/td>\nBusinesses serving EU consumers<\/td>\nEN 301 549 (Incorporates WCAG 2.1 AA)<\/td>\nJune 28, 2025<\/td>\n<\/tr>\n\nAODA<\/td>\nOntario, Canada<\/td>\nWCAG 2.0 AA<\/td>\nCurrent<\/td>\n<\/tr>\n\nEuropean Web Accessibility Directive<\/td>\nEuropean Union public sector<\/td>\nEN 301 549 (Incorporates WCAG 2.1 AA)<\/td>\nCurrent<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nThe European Accessibility Act (EAA) became enforceable on June 28, 2025<\/strong>, requiring WCAG compliance for many businesses selling digital products or services to EU customers. Penalties vary by member state\u2014fines reach \u20ac100,000 in Germany<\/strong> and \u20ac250,000 in France<\/strong>. Non-compliant products can be removed from the market entirely.<\/p>\nWhat are the four principles of WCAG?<\/strong><\/h3>\nThe four principles of WCAG\u2014known as POUR<\/strong>\u2014are Perceivable, Operable, Understandable, and Robust. These principles guide all WCAG success criteria and define what it means for web content to be accessible.<\/p>\n\n\n\n\nPrinciple<\/th>\nWhat It Means<\/th>\nExample Requirement<\/th>\n<\/tr>\n<\/thead>\n\n\nPerceivable<\/td>\nUsers must be able to perceive content through at least one sense.<\/td>\nProvide text alternatives for images; add captions to videos.<\/td>\n<\/tr>\n\nOperable<\/td>\nUsers must be able to operate the interface.<\/td>\nEnable keyboard access; provide enough time to read content.<\/td>\n<\/tr>\n\nUnderstandable<\/td>\nUsers must understand the content and how to use it.<\/td>\nUse clear language; make navigation predictable.<\/td>\n<\/tr>\n\nRobust<\/td>\nContent must work with current and future user agents.<\/td>\nUse valid code; ensure compatibility with assistive technology.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nWhat are the 13 WCAG guidelines?<\/strong><\/h3>\nThe four WCAG principles contain 13 guidelines<\/strong> that provide specific objectives for web accessibility. Each guideline has testable success criteria at three WCAG conformance levels: A, AA, and AAA.<\/p>\nPerceivable guidelines<\/strong><\/h3>\n1.1 Text Alternatives<\/strong> \u2014 Provide text alternatives for non-text content. This includes alt text for images, labels for form fields, and descriptions for icons. Text alternatives let screen reader users understand content they cannot see.<\/p>\n1.2 Time-Based Media<\/strong> \u2014 Provide alternatives for audio and video content. This includes captions for videos, transcripts for audio files, and audio descriptions for visual content.<\/p>\n1.3 Adaptable<\/strong> \u2014 Create content that can be presented in different ways without losing information. Web pages should maintain meaning when users change display settings or use assistive technology.<\/p>\n1.4 Distinguishable<\/strong> \u2014 Make content easy to see and hear. This includes sufficient color contrast, resizable text, and audio controls. Users with low vision or hearing loss depend on these features.<\/p>\nOperable guidelines<\/strong><\/h3>\n2.1 Keyboard Accessible<\/strong> \u2014 Make all functionality available from a keyboard. Users who cannot use a mouse must be able to navigate web content using keyboard access alone.<\/p>\n2.2 Enough Time<\/strong> \u2014 Give users enough time to read and interact with content. Avoid strict time limits, or provide ways to extend them.<\/p>\n2.3 Seizures and Physical Reactions<\/strong> \u2014 Do not design content that causes seizures. Avoid flashing content that could trigger photosensitive epilepsy.<\/p>\n2.4 Navigable<\/strong> \u2014 Help users navigate and find content. Provide clear headings, descriptive link text, and logical focus order.<\/p>\n2.5 Input Modalities<\/strong> \u2014 Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.<\/p>\nUnderstandable guidelines<\/h3>\n3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
The WCAG guidelines provide technical success criteria that help website owners make web content accessible to people with disabilities. This includes users who rely on screen readers, keyboard navigation, captions, and other assistive technology. When your website meets WCAG requirements, people with visual, hearing, motor, and cognitive or learning disabilities can perceive, navigate, and interact with your web pages.<\/p>\n\n\n\n\nWCAG version<\/th>\nRelease date<\/th>\nSuccess criteria<\/th>\nStatus<\/th>\n<\/tr>\n<\/thead>\n\n\nWCAG 2.0<\/td>\nDecember 2008<\/td>\n61 criteria<\/td>\nStill referenced in many laws<\/td>\n<\/tr>\n\nWCAG 2.1<\/td>\nJune 2018<\/td>\n78 criteria (+17 new)<\/td>\nCurrent legal standard<\/td>\n<\/tr>\n\nWCAG 2.2<\/td>\nOctober 2023<\/td>\n86 criteria (+9 new)<\/td>\nLatest W3C recommendation<\/td>\n<\/tr>\n\nWCAG 3.0<\/td>\nIn development<\/td>\n174 outcomes (proposed)<\/td>\nExpected 2028 or later<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nWhat does WCAG cover?<\/strong><\/h3>\nWCAG was originally developed for HTML content that people access through web browsers. However, the relevance of these guidelines extends far beyond traditional web pages. WCAG applies broadly to web content and technologies as long as they can be interpreted by user agents, including assistive technologies.<\/p>\n<\/figure>\n\n\n\n\nContent type<\/th>\nExamples<\/th>\nWCAG applies?<\/th>\n<\/tr>\n<\/thead>\n\n\nWebsites<\/td>\nPublic sites, intranets, web applications<\/td>\nYes<\/td>\n<\/tr>\n\nMobile apps<\/td>\niOS and Android applications<\/td>\nYes<\/td>\n<\/tr>\n\nDocuments<\/td>\nPDFs, Word files, spreadsheets<\/td>\nYes<\/td>\n<\/tr>\n\nMultimedia<\/td>\nVideos, podcasts, audio files<\/td>\nYes<\/td>\n<\/tr>\n\nEmail<\/td>\nHTML newsletters, marketing emails<\/td>\nYes<\/td>\n<\/tr>\n\nDigital kiosks<\/td>\nSelf-service terminals, ATMs<\/td>\nYes<\/td>\n<\/tr>\n\nE-learning<\/td>\nOnline courses, training modules<\/td>\nYes<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nLaws referencing WCAG and related standards cover different types of digital experiences. For example, the DOJ’s ADA Title II rule specifically covers web and mobile content (including digital documents) provided by state and local governments. The European Accessibility Act applies to a wide range of consumer products and services, including e-commerce platforms, banking services, and consumer electronics. Any digital content that serves the public should follow WCAG guidelines to ensure people with disabilities can access it.<\/p>\nLaws referencing WCAG and related standards cover different types of digital experiences. For example, the DOJ’s ADA Title II rule specifically covers web and mobile content (including digital documents) provided by state and local governments. The European Accessibility Act applies to a wide range of consumer products and services, including e-commerce platforms, banking services, and consumer electronics. Any digital content that serves the public should follow WCAG guidelines to ensure people with disabilities can access it.<\/p>\nWho needs to comply with WCAG?<\/strong><\/h3>\nAlmost any organization with a digital presence should comply with WCAG. Legal requirements vary by sector, but accessibility benefits all businesses.<\/p>\n\n\n\n\nOrganization type<\/th>\nLegal requirement<\/th>\nWhy comply<\/th>\n<\/tr>\n<\/thead>\n\n\nFederal government agencies<\/td>\nSection 508 (mandatory)<\/td>\nRequired by law<\/td>\n<\/tr>\n\nState and local governments<\/td>\nADA Title II (mandatory)<\/td>\nApril 2026 deadline<\/td>\n<\/tr>\n\nPrivate businesses<\/td>\nADA Title III (court-enforced)<\/td>\nLawsuit prevention<\/td>\n<\/tr>\n\nE-commerce websites<\/td>\nEAA in EU (mandatory)<\/td>\nMarket access<\/td>\n<\/tr>\n\nHealthcare providers<\/td>\nADA + Section 504<\/td>\nPatient access<\/td>\n<\/tr>\n\nEducational institutions<\/td>\nADA + Section 504<\/td>\nStudent access<\/td>\n<\/tr>\n\nNonprofits<\/td>\nADA applies<\/td>\nServe all constituents<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/p>\nEven without a specific legal mandate, website owners benefit from WCAG compliance. Accessible websites reach more users, perform better in search rankings, and reduce legal risk. Over 1 billion people<\/strong> worldwide have disabilities\u2014making websites accessible expands your potential audience significantly.<\/p>\nIs WCAG a legal requirement in the US?<\/strong><\/h3>\nYes, for most organizations.<\/strong> WCAG 2.1 Level AA is the de facto standard for web accessibility under multiple US laws, and courts consistently use WCAG as the benchmark for accessibility compliance.<\/p>\nThe DOJ’s ADA Title II Final Rule<\/strong> formally adopted WCAG 2.1 Level AA for all state and local governments. This covers government websites, mobile apps, digital documents, and online services.<\/p>\n<\/figure>\n\n\n\n\nEntity type<\/th>\nPopulation<\/th>\nCompliance deadline<\/th>\n<\/tr>\n<\/thead>\n\n\nLarge public entities<\/td>\n50,000+ residents<\/td>\nApril 24, 2026<\/td>\n<\/tr>\n\nSmall public entities<\/td>\nUnder 50,000 residents<\/td>\nApril 26, 2027<\/td>\n<\/tr>\n\nSpecial district governments<\/td>\nAny size<\/td>\nApril 26, 2027<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nFor private businesses, Title III of the Americans with Disabilities Act<\/strong> requires website accessibility based on court rulings and DOJ settlement agreements. Section 508<\/strong> of the Rehabilitation Act explicitly requires WCAG compliance for federal government agencies and contractors.<\/p>\nDigital accessibility lawsuits remain widespread. Automated tools now generate complaints at scale, making any business with accessibility issues a potential target.<\/p>\nWhat accessibility laws require WCAG compliance?<\/strong><\/h3>\nDigital accessibility legislation worldwide references WCAG as the technical standard for compliance. Meeting WCAG requirements satisfies most accessibility regulations.<\/p>\n\n\n\n\nLaw \/ regulation<\/th>\nGeographic scope<\/th>\nWCAG standard required<\/th>\nCompliance deadline<\/th>\n<\/tr>\n<\/thead>\n\n\nADA Title II (DOJ Rule)<\/td>\nUS state \/ local governments<\/td>\nWCAG 2.1 AA<\/td>\nApril 2026 \/ 2027<\/td>\n<\/tr>\n\nADA Title III<\/td>\nUS private businesses<\/td>\nWCAG 2.1 AA (de facto standard per courts)<\/td>\nOngoing<\/td>\n<\/tr>\n\nSection 508<\/td>\nUS federal agencies<\/td>\nWCAG 2.0 AA<\/td>\nCurrent<\/td>\n<\/tr>\n\nEuropean Accessibility Act<\/td>\nBusinesses serving EU consumers<\/td>\nEN 301 549 (Incorporates WCAG 2.1 AA)<\/td>\nJune 28, 2025<\/td>\n<\/tr>\n\nAODA<\/td>\nOntario, Canada<\/td>\nWCAG 2.0 AA<\/td>\nCurrent<\/td>\n<\/tr>\n\nEuropean Web Accessibility Directive<\/td>\nEuropean Union public sector<\/td>\nEN 301 549 (Incorporates WCAG 2.1 AA)<\/td>\nCurrent<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nThe European Accessibility Act (EAA) became enforceable on June 28, 2025<\/strong>, requiring WCAG compliance for many businesses selling digital products or services to EU customers. Penalties vary by member state\u2014fines reach \u20ac100,000 in Germany<\/strong> and \u20ac250,000 in France<\/strong>. Non-compliant products can be removed from the market entirely.<\/p>\nWhat are the four principles of WCAG?<\/strong><\/h3>\nThe four principles of WCAG\u2014known as POUR<\/strong>\u2014are Perceivable, Operable, Understandable, and Robust. These principles guide all WCAG success criteria and define what it means for web content to be accessible.<\/p>\n\n\n\n\nPrinciple<\/th>\nWhat It Means<\/th>\nExample Requirement<\/th>\n<\/tr>\n<\/thead>\n\n\nPerceivable<\/td>\nUsers must be able to perceive content through at least one sense.<\/td>\nProvide text alternatives for images; add captions to videos.<\/td>\n<\/tr>\n\nOperable<\/td>\nUsers must be able to operate the interface.<\/td>\nEnable keyboard access; provide enough time to read content.<\/td>\n<\/tr>\n\nUnderstandable<\/td>\nUsers must understand the content and how to use it.<\/td>\nUse clear language; make navigation predictable.<\/td>\n<\/tr>\n\nRobust<\/td>\nContent must work with current and future user agents.<\/td>\nUse valid code; ensure compatibility with assistive technology.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nWhat are the 13 WCAG guidelines?<\/strong><\/h3>\nThe four WCAG principles contain 13 guidelines<\/strong> that provide specific objectives for web accessibility. Each guideline has testable success criteria at three WCAG conformance levels: A, AA, and AAA.<\/p>\nPerceivable guidelines<\/strong><\/h3>\n1.1 Text Alternatives<\/strong> \u2014 Provide text alternatives for non-text content. This includes alt text for images, labels for form fields, and descriptions for icons. Text alternatives let screen reader users understand content they cannot see.<\/p>\n1.2 Time-Based Media<\/strong> \u2014 Provide alternatives for audio and video content. This includes captions for videos, transcripts for audio files, and audio descriptions for visual content.<\/p>\n1.3 Adaptable<\/strong> \u2014 Create content that can be presented in different ways without losing information. Web pages should maintain meaning when users change display settings or use assistive technology.<\/p>\n1.4 Distinguishable<\/strong> \u2014 Make content easy to see and hear. This includes sufficient color contrast, resizable text, and audio controls. Users with low vision or hearing loss depend on these features.<\/p>\nOperable guidelines<\/strong><\/h3>\n2.1 Keyboard Accessible<\/strong> \u2014 Make all functionality available from a keyboard. Users who cannot use a mouse must be able to navigate web content using keyboard access alone.<\/p>\n2.2 Enough Time<\/strong> \u2014 Give users enough time to read and interact with content. Avoid strict time limits, or provide ways to extend them.<\/p>\n2.3 Seizures and Physical Reactions<\/strong> \u2014 Do not design content that causes seizures. Avoid flashing content that could trigger photosensitive epilepsy.<\/p>\n2.4 Navigable<\/strong> \u2014 Help users navigate and find content. Provide clear headings, descriptive link text, and logical focus order.<\/p>\n2.5 Input Modalities<\/strong> \u2014 Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.<\/p>\nUnderstandable guidelines<\/h3>\n3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
WCAG was originally developed for HTML content that people access through web browsers. However, the relevance of these guidelines extends far beyond traditional web pages. WCAG applies broadly to web content and technologies as long as they can be interpreted by user agents, including assistive technologies.<\/p>\n<\/figure>\n\n\n\n\nContent type<\/th>\nExamples<\/th>\nWCAG applies?<\/th>\n<\/tr>\n<\/thead>\n\n\nWebsites<\/td>\nPublic sites, intranets, web applications<\/td>\nYes<\/td>\n<\/tr>\n\nMobile apps<\/td>\niOS and Android applications<\/td>\nYes<\/td>\n<\/tr>\n\nDocuments<\/td>\nPDFs, Word files, spreadsheets<\/td>\nYes<\/td>\n<\/tr>\n\nMultimedia<\/td>\nVideos, podcasts, audio files<\/td>\nYes<\/td>\n<\/tr>\n\nEmail<\/td>\nHTML newsletters, marketing emails<\/td>\nYes<\/td>\n<\/tr>\n\nDigital kiosks<\/td>\nSelf-service terminals, ATMs<\/td>\nYes<\/td>\n<\/tr>\n\nE-learning<\/td>\nOnline courses, training modules<\/td>\nYes<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nLaws referencing WCAG and related standards cover different types of digital experiences. For example, the DOJ’s ADA Title II rule specifically covers web and mobile content (including digital documents) provided by state and local governments. The European Accessibility Act applies to a wide range of consumer products and services, including e-commerce platforms, banking services, and consumer electronics. Any digital content that serves the public should follow WCAG guidelines to ensure people with disabilities can access it.<\/p>\nLaws referencing WCAG and related standards cover different types of digital experiences. For example, the DOJ’s ADA Title II rule specifically covers web and mobile content (including digital documents) provided by state and local governments. The European Accessibility Act applies to a wide range of consumer products and services, including e-commerce platforms, banking services, and consumer electronics. Any digital content that serves the public should follow WCAG guidelines to ensure people with disabilities can access it.<\/p>\nWho needs to comply with WCAG?<\/strong><\/h3>\nAlmost any organization with a digital presence should comply with WCAG. Legal requirements vary by sector, but accessibility benefits all businesses.<\/p>\n\n\n\n\nOrganization type<\/th>\nLegal requirement<\/th>\nWhy comply<\/th>\n<\/tr>\n<\/thead>\n\n\nFederal government agencies<\/td>\nSection 508 (mandatory)<\/td>\nRequired by law<\/td>\n<\/tr>\n\nState and local governments<\/td>\nADA Title II (mandatory)<\/td>\nApril 2026 deadline<\/td>\n<\/tr>\n\nPrivate businesses<\/td>\nADA Title III (court-enforced)<\/td>\nLawsuit prevention<\/td>\n<\/tr>\n\nE-commerce websites<\/td>\nEAA in EU (mandatory)<\/td>\nMarket access<\/td>\n<\/tr>\n\nHealthcare providers<\/td>\nADA + Section 504<\/td>\nPatient access<\/td>\n<\/tr>\n\nEducational institutions<\/td>\nADA + Section 504<\/td>\nStudent access<\/td>\n<\/tr>\n\nNonprofits<\/td>\nADA applies<\/td>\nServe all constituents<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/p>\nEven without a specific legal mandate, website owners benefit from WCAG compliance. Accessible websites reach more users, perform better in search rankings, and reduce legal risk. Over 1 billion people<\/strong> worldwide have disabilities\u2014making websites accessible expands your potential audience significantly.<\/p>\nIs WCAG a legal requirement in the US?<\/strong><\/h3>\nYes, for most organizations.<\/strong> WCAG 2.1 Level AA is the de facto standard for web accessibility under multiple US laws, and courts consistently use WCAG as the benchmark for accessibility compliance.<\/p>\nThe DOJ’s ADA Title II Final Rule<\/strong> formally adopted WCAG 2.1 Level AA for all state and local governments. This covers government websites, mobile apps, digital documents, and online services.<\/p>\n<\/figure>\n\n\n\n\nEntity type<\/th>\nPopulation<\/th>\nCompliance deadline<\/th>\n<\/tr>\n<\/thead>\n\n\nLarge public entities<\/td>\n50,000+ residents<\/td>\nApril 24, 2026<\/td>\n<\/tr>\n\nSmall public entities<\/td>\nUnder 50,000 residents<\/td>\nApril 26, 2027<\/td>\n<\/tr>\n\nSpecial district governments<\/td>\nAny size<\/td>\nApril 26, 2027<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nFor private businesses, Title III of the Americans with Disabilities Act<\/strong> requires website accessibility based on court rulings and DOJ settlement agreements. Section 508<\/strong> of the Rehabilitation Act explicitly requires WCAG compliance for federal government agencies and contractors.<\/p>\nDigital accessibility lawsuits remain widespread. Automated tools now generate complaints at scale, making any business with accessibility issues a potential target.<\/p>\nWhat accessibility laws require WCAG compliance?<\/strong><\/h3>\nDigital accessibility legislation worldwide references WCAG as the technical standard for compliance. Meeting WCAG requirements satisfies most accessibility regulations.<\/p>\n\n\n\n\nLaw \/ regulation<\/th>\nGeographic scope<\/th>\nWCAG standard required<\/th>\nCompliance deadline<\/th>\n<\/tr>\n<\/thead>\n\n\nADA Title II (DOJ Rule)<\/td>\nUS state \/ local governments<\/td>\nWCAG 2.1 AA<\/td>\nApril 2026 \/ 2027<\/td>\n<\/tr>\n\nADA Title III<\/td>\nUS private businesses<\/td>\nWCAG 2.1 AA (de facto standard per courts)<\/td>\nOngoing<\/td>\n<\/tr>\n\nSection 508<\/td>\nUS federal agencies<\/td>\nWCAG 2.0 AA<\/td>\nCurrent<\/td>\n<\/tr>\n\nEuropean Accessibility Act<\/td>\nBusinesses serving EU consumers<\/td>\nEN 301 549 (Incorporates WCAG 2.1 AA)<\/td>\nJune 28, 2025<\/td>\n<\/tr>\n\nAODA<\/td>\nOntario, Canada<\/td>\nWCAG 2.0 AA<\/td>\nCurrent<\/td>\n<\/tr>\n\nEuropean Web Accessibility Directive<\/td>\nEuropean Union public sector<\/td>\nEN 301 549 (Incorporates WCAG 2.1 AA)<\/td>\nCurrent<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nThe European Accessibility Act (EAA) became enforceable on June 28, 2025<\/strong>, requiring WCAG compliance for many businesses selling digital products or services to EU customers. Penalties vary by member state\u2014fines reach \u20ac100,000 in Germany<\/strong> and \u20ac250,000 in France<\/strong>. Non-compliant products can be removed from the market entirely.<\/p>\nWhat are the four principles of WCAG?<\/strong><\/h3>\nThe four principles of WCAG\u2014known as POUR<\/strong>\u2014are Perceivable, Operable, Understandable, and Robust. These principles guide all WCAG success criteria and define what it means for web content to be accessible.<\/p>\n\n\n\n\nPrinciple<\/th>\nWhat It Means<\/th>\nExample Requirement<\/th>\n<\/tr>\n<\/thead>\n\n\nPerceivable<\/td>\nUsers must be able to perceive content through at least one sense.<\/td>\nProvide text alternatives for images; add captions to videos.<\/td>\n<\/tr>\n\nOperable<\/td>\nUsers must be able to operate the interface.<\/td>\nEnable keyboard access; provide enough time to read content.<\/td>\n<\/tr>\n\nUnderstandable<\/td>\nUsers must understand the content and how to use it.<\/td>\nUse clear language; make navigation predictable.<\/td>\n<\/tr>\n\nRobust<\/td>\nContent must work with current and future user agents.<\/td>\nUse valid code; ensure compatibility with assistive technology.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nWhat are the 13 WCAG guidelines?<\/strong><\/h3>\nThe four WCAG principles contain 13 guidelines<\/strong> that provide specific objectives for web accessibility. Each guideline has testable success criteria at three WCAG conformance levels: A, AA, and AAA.<\/p>\nPerceivable guidelines<\/strong><\/h3>\n1.1 Text Alternatives<\/strong> \u2014 Provide text alternatives for non-text content. This includes alt text for images, labels for form fields, and descriptions for icons. Text alternatives let screen reader users understand content they cannot see.<\/p>\n1.2 Time-Based Media<\/strong> \u2014 Provide alternatives for audio and video content. This includes captions for videos, transcripts for audio files, and audio descriptions for visual content.<\/p>\n1.3 Adaptable<\/strong> \u2014 Create content that can be presented in different ways without losing information. Web pages should maintain meaning when users change display settings or use assistive technology.<\/p>\n1.4 Distinguishable<\/strong> \u2014 Make content easy to see and hear. This includes sufficient color contrast, resizable text, and audio controls. Users with low vision or hearing loss depend on these features.<\/p>\nOperable guidelines<\/strong><\/h3>\n2.1 Keyboard Accessible<\/strong> \u2014 Make all functionality available from a keyboard. Users who cannot use a mouse must be able to navigate web content using keyboard access alone.<\/p>\n2.2 Enough Time<\/strong> \u2014 Give users enough time to read and interact with content. Avoid strict time limits, or provide ways to extend them.<\/p>\n2.3 Seizures and Physical Reactions<\/strong> \u2014 Do not design content that causes seizures. Avoid flashing content that could trigger photosensitive epilepsy.<\/p>\n2.4 Navigable<\/strong> \u2014 Help users navigate and find content. Provide clear headings, descriptive link text, and logical focus order.<\/p>\n2.5 Input Modalities<\/strong> \u2014 Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.<\/p>\nUnderstandable guidelines<\/h3>\n3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
Laws referencing WCAG and related standards cover different types of digital experiences. For example, the DOJ’s ADA Title II rule specifically covers web and mobile content (including digital documents) provided by state and local governments. The European Accessibility Act applies to a wide range of consumer products and services, including e-commerce platforms, banking services, and consumer electronics. Any digital content that serves the public should follow WCAG guidelines to ensure people with disabilities can access it.<\/p>\n
Almost any organization with a digital presence should comply with WCAG. Legal requirements vary by sector, but accessibility benefits all businesses.<\/p>\n\n\n\n\nOrganization type<\/th>\nLegal requirement<\/th>\nWhy comply<\/th>\n<\/tr>\n<\/thead>\n\n\nFederal government agencies<\/td>\nSection 508 (mandatory)<\/td>\nRequired by law<\/td>\n<\/tr>\n\nState and local governments<\/td>\nADA Title II (mandatory)<\/td>\nApril 2026 deadline<\/td>\n<\/tr>\n\nPrivate businesses<\/td>\nADA Title III (court-enforced)<\/td>\nLawsuit prevention<\/td>\n<\/tr>\n\nE-commerce websites<\/td>\nEAA in EU (mandatory)<\/td>\nMarket access<\/td>\n<\/tr>\n\nHealthcare providers<\/td>\nADA + Section 504<\/td>\nPatient access<\/td>\n<\/tr>\n\nEducational institutions<\/td>\nADA + Section 504<\/td>\nStudent access<\/td>\n<\/tr>\n\nNonprofits<\/td>\nADA applies<\/td>\nServe all constituents<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/p>\nEven without a specific legal mandate, website owners benefit from WCAG compliance. Accessible websites reach more users, perform better in search rankings, and reduce legal risk. Over 1 billion people<\/strong> worldwide have disabilities\u2014making websites accessible expands your potential audience significantly.<\/p>\nIs WCAG a legal requirement in the US?<\/strong><\/h3>\nYes, for most organizations.<\/strong> WCAG 2.1 Level AA is the de facto standard for web accessibility under multiple US laws, and courts consistently use WCAG as the benchmark for accessibility compliance.<\/p>\nThe DOJ’s ADA Title II Final Rule<\/strong> formally adopted WCAG 2.1 Level AA for all state and local governments. This covers government websites, mobile apps, digital documents, and online services.<\/p>\n<\/figure>\n\n\n\n\nEntity type<\/th>\nPopulation<\/th>\nCompliance deadline<\/th>\n<\/tr>\n<\/thead>\n\n\nLarge public entities<\/td>\n50,000+ residents<\/td>\nApril 24, 2026<\/td>\n<\/tr>\n\nSmall public entities<\/td>\nUnder 50,000 residents<\/td>\nApril 26, 2027<\/td>\n<\/tr>\n\nSpecial district governments<\/td>\nAny size<\/td>\nApril 26, 2027<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nFor private businesses, Title III of the Americans with Disabilities Act<\/strong> requires website accessibility based on court rulings and DOJ settlement agreements. Section 508<\/strong> of the Rehabilitation Act explicitly requires WCAG compliance for federal government agencies and contractors.<\/p>\nDigital accessibility lawsuits remain widespread. Automated tools now generate complaints at scale, making any business with accessibility issues a potential target.<\/p>\nWhat accessibility laws require WCAG compliance?<\/strong><\/h3>\nDigital accessibility legislation worldwide references WCAG as the technical standard for compliance. Meeting WCAG requirements satisfies most accessibility regulations.<\/p>\n\n\n\n\nLaw \/ regulation<\/th>\nGeographic scope<\/th>\nWCAG standard required<\/th>\nCompliance deadline<\/th>\n<\/tr>\n<\/thead>\n\n\nADA Title II (DOJ Rule)<\/td>\nUS state \/ local governments<\/td>\nWCAG 2.1 AA<\/td>\nApril 2026 \/ 2027<\/td>\n<\/tr>\n\nADA Title III<\/td>\nUS private businesses<\/td>\nWCAG 2.1 AA (de facto standard per courts)<\/td>\nOngoing<\/td>\n<\/tr>\n\nSection 508<\/td>\nUS federal agencies<\/td>\nWCAG 2.0 AA<\/td>\nCurrent<\/td>\n<\/tr>\n\nEuropean Accessibility Act<\/td>\nBusinesses serving EU consumers<\/td>\nEN 301 549 (Incorporates WCAG 2.1 AA)<\/td>\nJune 28, 2025<\/td>\n<\/tr>\n\nAODA<\/td>\nOntario, Canada<\/td>\nWCAG 2.0 AA<\/td>\nCurrent<\/td>\n<\/tr>\n\nEuropean Web Accessibility Directive<\/td>\nEuropean Union public sector<\/td>\nEN 301 549 (Incorporates WCAG 2.1 AA)<\/td>\nCurrent<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nThe European Accessibility Act (EAA) became enforceable on June 28, 2025<\/strong>, requiring WCAG compliance for many businesses selling digital products or services to EU customers. Penalties vary by member state\u2014fines reach \u20ac100,000 in Germany<\/strong> and \u20ac250,000 in France<\/strong>. Non-compliant products can be removed from the market entirely.<\/p>\nWhat are the four principles of WCAG?<\/strong><\/h3>\nThe four principles of WCAG\u2014known as POUR<\/strong>\u2014are Perceivable, Operable, Understandable, and Robust. These principles guide all WCAG success criteria and define what it means for web content to be accessible.<\/p>\n\n\n\n\nPrinciple<\/th>\nWhat It Means<\/th>\nExample Requirement<\/th>\n<\/tr>\n<\/thead>\n\n\nPerceivable<\/td>\nUsers must be able to perceive content through at least one sense.<\/td>\nProvide text alternatives for images; add captions to videos.<\/td>\n<\/tr>\n\nOperable<\/td>\nUsers must be able to operate the interface.<\/td>\nEnable keyboard access; provide enough time to read content.<\/td>\n<\/tr>\n\nUnderstandable<\/td>\nUsers must understand the content and how to use it.<\/td>\nUse clear language; make navigation predictable.<\/td>\n<\/tr>\n\nRobust<\/td>\nContent must work with current and future user agents.<\/td>\nUse valid code; ensure compatibility with assistive technology.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nWhat are the 13 WCAG guidelines?<\/strong><\/h3>\nThe four WCAG principles contain 13 guidelines<\/strong> that provide specific objectives for web accessibility. Each guideline has testable success criteria at three WCAG conformance levels: A, AA, and AAA.<\/p>\nPerceivable guidelines<\/strong><\/h3>\n1.1 Text Alternatives<\/strong> \u2014 Provide text alternatives for non-text content. This includes alt text for images, labels for form fields, and descriptions for icons. Text alternatives let screen reader users understand content they cannot see.<\/p>\n1.2 Time-Based Media<\/strong> \u2014 Provide alternatives for audio and video content. This includes captions for videos, transcripts for audio files, and audio descriptions for visual content.<\/p>\n1.3 Adaptable<\/strong> \u2014 Create content that can be presented in different ways without losing information. Web pages should maintain meaning when users change display settings or use assistive technology.<\/p>\n1.4 Distinguishable<\/strong> \u2014 Make content easy to see and hear. This includes sufficient color contrast, resizable text, and audio controls. Users with low vision or hearing loss depend on these features.<\/p>\nOperable guidelines<\/strong><\/h3>\n2.1 Keyboard Accessible<\/strong> \u2014 Make all functionality available from a keyboard. Users who cannot use a mouse must be able to navigate web content using keyboard access alone.<\/p>\n2.2 Enough Time<\/strong> \u2014 Give users enough time to read and interact with content. Avoid strict time limits, or provide ways to extend them.<\/p>\n2.3 Seizures and Physical Reactions<\/strong> \u2014 Do not design content that causes seizures. Avoid flashing content that could trigger photosensitive epilepsy.<\/p>\n2.4 Navigable<\/strong> \u2014 Help users navigate and find content. Provide clear headings, descriptive link text, and logical focus order.<\/p>\n2.5 Input Modalities<\/strong> \u2014 Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.<\/p>\nUnderstandable guidelines<\/h3>\n3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
<\/p>\n
Even without a specific legal mandate, website owners benefit from WCAG compliance. Accessible websites reach more users, perform better in search rankings, and reduce legal risk. Over 1 billion people<\/strong> worldwide have disabilities\u2014making websites accessible expands your potential audience significantly.<\/p>\nIs WCAG a legal requirement in the US?<\/strong><\/h3>\nYes, for most organizations.<\/strong> WCAG 2.1 Level AA is the de facto standard for web accessibility under multiple US laws, and courts consistently use WCAG as the benchmark for accessibility compliance.<\/p>\nThe DOJ’s ADA Title II Final Rule<\/strong> formally adopted WCAG 2.1 Level AA for all state and local governments. This covers government websites, mobile apps, digital documents, and online services.<\/p>\n<\/figure>\n\n\n\n\nEntity type<\/th>\nPopulation<\/th>\nCompliance deadline<\/th>\n<\/tr>\n<\/thead>\n\n\nLarge public entities<\/td>\n50,000+ residents<\/td>\nApril 24, 2026<\/td>\n<\/tr>\n\nSmall public entities<\/td>\nUnder 50,000 residents<\/td>\nApril 26, 2027<\/td>\n<\/tr>\n\nSpecial district governments<\/td>\nAny size<\/td>\nApril 26, 2027<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nFor private businesses, Title III of the Americans with Disabilities Act<\/strong> requires website accessibility based on court rulings and DOJ settlement agreements. Section 508<\/strong> of the Rehabilitation Act explicitly requires WCAG compliance for federal government agencies and contractors.<\/p>\nDigital accessibility lawsuits remain widespread. Automated tools now generate complaints at scale, making any business with accessibility issues a potential target.<\/p>\nWhat accessibility laws require WCAG compliance?<\/strong><\/h3>\nDigital accessibility legislation worldwide references WCAG as the technical standard for compliance. Meeting WCAG requirements satisfies most accessibility regulations.<\/p>\n\n\n\n\nLaw \/ regulation<\/th>\nGeographic scope<\/th>\nWCAG standard required<\/th>\nCompliance deadline<\/th>\n<\/tr>\n<\/thead>\n\n\nADA Title II (DOJ Rule)<\/td>\nUS state \/ local governments<\/td>\nWCAG 2.1 AA<\/td>\nApril 2026 \/ 2027<\/td>\n<\/tr>\n\nADA Title III<\/td>\nUS private businesses<\/td>\nWCAG 2.1 AA (de facto standard per courts)<\/td>\nOngoing<\/td>\n<\/tr>\n\nSection 508<\/td>\nUS federal agencies<\/td>\nWCAG 2.0 AA<\/td>\nCurrent<\/td>\n<\/tr>\n\nEuropean Accessibility Act<\/td>\nBusinesses serving EU consumers<\/td>\nEN 301 549 (Incorporates WCAG 2.1 AA)<\/td>\nJune 28, 2025<\/td>\n<\/tr>\n\nAODA<\/td>\nOntario, Canada<\/td>\nWCAG 2.0 AA<\/td>\nCurrent<\/td>\n<\/tr>\n\nEuropean Web Accessibility Directive<\/td>\nEuropean Union public sector<\/td>\nEN 301 549 (Incorporates WCAG 2.1 AA)<\/td>\nCurrent<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nThe European Accessibility Act (EAA) became enforceable on June 28, 2025<\/strong>, requiring WCAG compliance for many businesses selling digital products or services to EU customers. Penalties vary by member state\u2014fines reach \u20ac100,000 in Germany<\/strong> and \u20ac250,000 in France<\/strong>. Non-compliant products can be removed from the market entirely.<\/p>\nWhat are the four principles of WCAG?<\/strong><\/h3>\nThe four principles of WCAG\u2014known as POUR<\/strong>\u2014are Perceivable, Operable, Understandable, and Robust. These principles guide all WCAG success criteria and define what it means for web content to be accessible.<\/p>\n\n\n\n\nPrinciple<\/th>\nWhat It Means<\/th>\nExample Requirement<\/th>\n<\/tr>\n<\/thead>\n\n\nPerceivable<\/td>\nUsers must be able to perceive content through at least one sense.<\/td>\nProvide text alternatives for images; add captions to videos.<\/td>\n<\/tr>\n\nOperable<\/td>\nUsers must be able to operate the interface.<\/td>\nEnable keyboard access; provide enough time to read content.<\/td>\n<\/tr>\n\nUnderstandable<\/td>\nUsers must understand the content and how to use it.<\/td>\nUse clear language; make navigation predictable.<\/td>\n<\/tr>\n\nRobust<\/td>\nContent must work with current and future user agents.<\/td>\nUse valid code; ensure compatibility with assistive technology.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nWhat are the 13 WCAG guidelines?<\/strong><\/h3>\nThe four WCAG principles contain 13 guidelines<\/strong> that provide specific objectives for web accessibility. Each guideline has testable success criteria at three WCAG conformance levels: A, AA, and AAA.<\/p>\nPerceivable guidelines<\/strong><\/h3>\n1.1 Text Alternatives<\/strong> \u2014 Provide text alternatives for non-text content. This includes alt text for images, labels for form fields, and descriptions for icons. Text alternatives let screen reader users understand content they cannot see.<\/p>\n1.2 Time-Based Media<\/strong> \u2014 Provide alternatives for audio and video content. This includes captions for videos, transcripts for audio files, and audio descriptions for visual content.<\/p>\n1.3 Adaptable<\/strong> \u2014 Create content that can be presented in different ways without losing information. Web pages should maintain meaning when users change display settings or use assistive technology.<\/p>\n1.4 Distinguishable<\/strong> \u2014 Make content easy to see and hear. This includes sufficient color contrast, resizable text, and audio controls. Users with low vision or hearing loss depend on these features.<\/p>\nOperable guidelines<\/strong><\/h3>\n2.1 Keyboard Accessible<\/strong> \u2014 Make all functionality available from a keyboard. Users who cannot use a mouse must be able to navigate web content using keyboard access alone.<\/p>\n2.2 Enough Time<\/strong> \u2014 Give users enough time to read and interact with content. Avoid strict time limits, or provide ways to extend them.<\/p>\n2.3 Seizures and Physical Reactions<\/strong> \u2014 Do not design content that causes seizures. Avoid flashing content that could trigger photosensitive epilepsy.<\/p>\n2.4 Navigable<\/strong> \u2014 Help users navigate and find content. Provide clear headings, descriptive link text, and logical focus order.<\/p>\n2.5 Input Modalities<\/strong> \u2014 Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.<\/p>\nUnderstandable guidelines<\/h3>\n3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
Yes, for most organizations.<\/strong> WCAG 2.1 Level AA is the de facto standard for web accessibility under multiple US laws, and courts consistently use WCAG as the benchmark for accessibility compliance.<\/p>\nThe DOJ’s ADA Title II Final Rule<\/strong> formally adopted WCAG 2.1 Level AA for all state and local governments. This covers government websites, mobile apps, digital documents, and online services.<\/p>\n<\/figure>\n\n\n\n\nEntity type<\/th>\nPopulation<\/th>\nCompliance deadline<\/th>\n<\/tr>\n<\/thead>\n\n\nLarge public entities<\/td>\n50,000+ residents<\/td>\nApril 24, 2026<\/td>\n<\/tr>\n\nSmall public entities<\/td>\nUnder 50,000 residents<\/td>\nApril 26, 2027<\/td>\n<\/tr>\n\nSpecial district governments<\/td>\nAny size<\/td>\nApril 26, 2027<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nFor private businesses, Title III of the Americans with Disabilities Act<\/strong> requires website accessibility based on court rulings and DOJ settlement agreements. Section 508<\/strong> of the Rehabilitation Act explicitly requires WCAG compliance for federal government agencies and contractors.<\/p>\nDigital accessibility lawsuits remain widespread. Automated tools now generate complaints at scale, making any business with accessibility issues a potential target.<\/p>\nWhat accessibility laws require WCAG compliance?<\/strong><\/h3>\nDigital accessibility legislation worldwide references WCAG as the technical standard for compliance. Meeting WCAG requirements satisfies most accessibility regulations.<\/p>\n\n\n\n\nLaw \/ regulation<\/th>\nGeographic scope<\/th>\nWCAG standard required<\/th>\nCompliance deadline<\/th>\n<\/tr>\n<\/thead>\n\n\nADA Title II (DOJ Rule)<\/td>\nUS state \/ local governments<\/td>\nWCAG 2.1 AA<\/td>\nApril 2026 \/ 2027<\/td>\n<\/tr>\n\nADA Title III<\/td>\nUS private businesses<\/td>\nWCAG 2.1 AA (de facto standard per courts)<\/td>\nOngoing<\/td>\n<\/tr>\n\nSection 508<\/td>\nUS federal agencies<\/td>\nWCAG 2.0 AA<\/td>\nCurrent<\/td>\n<\/tr>\n\nEuropean Accessibility Act<\/td>\nBusinesses serving EU consumers<\/td>\nEN 301 549 (Incorporates WCAG 2.1 AA)<\/td>\nJune 28, 2025<\/td>\n<\/tr>\n\nAODA<\/td>\nOntario, Canada<\/td>\nWCAG 2.0 AA<\/td>\nCurrent<\/td>\n<\/tr>\n\nEuropean Web Accessibility Directive<\/td>\nEuropean Union public sector<\/td>\nEN 301 549 (Incorporates WCAG 2.1 AA)<\/td>\nCurrent<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nThe European Accessibility Act (EAA) became enforceable on June 28, 2025<\/strong>, requiring WCAG compliance for many businesses selling digital products or services to EU customers. Penalties vary by member state\u2014fines reach \u20ac100,000 in Germany<\/strong> and \u20ac250,000 in France<\/strong>. Non-compliant products can be removed from the market entirely.<\/p>\nWhat are the four principles of WCAG?<\/strong><\/h3>\nThe four principles of WCAG\u2014known as POUR<\/strong>\u2014are Perceivable, Operable, Understandable, and Robust. These principles guide all WCAG success criteria and define what it means for web content to be accessible.<\/p>\n\n\n\n\nPrinciple<\/th>\nWhat It Means<\/th>\nExample Requirement<\/th>\n<\/tr>\n<\/thead>\n\n\nPerceivable<\/td>\nUsers must be able to perceive content through at least one sense.<\/td>\nProvide text alternatives for images; add captions to videos.<\/td>\n<\/tr>\n\nOperable<\/td>\nUsers must be able to operate the interface.<\/td>\nEnable keyboard access; provide enough time to read content.<\/td>\n<\/tr>\n\nUnderstandable<\/td>\nUsers must understand the content and how to use it.<\/td>\nUse clear language; make navigation predictable.<\/td>\n<\/tr>\n\nRobust<\/td>\nContent must work with current and future user agents.<\/td>\nUse valid code; ensure compatibility with assistive technology.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nWhat are the 13 WCAG guidelines?<\/strong><\/h3>\nThe four WCAG principles contain 13 guidelines<\/strong> that provide specific objectives for web accessibility. Each guideline has testable success criteria at three WCAG conformance levels: A, AA, and AAA.<\/p>\nPerceivable guidelines<\/strong><\/h3>\n1.1 Text Alternatives<\/strong> \u2014 Provide text alternatives for non-text content. This includes alt text for images, labels for form fields, and descriptions for icons. Text alternatives let screen reader users understand content they cannot see.<\/p>\n1.2 Time-Based Media<\/strong> \u2014 Provide alternatives for audio and video content. This includes captions for videos, transcripts for audio files, and audio descriptions for visual content.<\/p>\n1.3 Adaptable<\/strong> \u2014 Create content that can be presented in different ways without losing information. Web pages should maintain meaning when users change display settings or use assistive technology.<\/p>\n1.4 Distinguishable<\/strong> \u2014 Make content easy to see and hear. This includes sufficient color contrast, resizable text, and audio controls. Users with low vision or hearing loss depend on these features.<\/p>\nOperable guidelines<\/strong><\/h3>\n2.1 Keyboard Accessible<\/strong> \u2014 Make all functionality available from a keyboard. Users who cannot use a mouse must be able to navigate web content using keyboard access alone.<\/p>\n2.2 Enough Time<\/strong> \u2014 Give users enough time to read and interact with content. Avoid strict time limits, or provide ways to extend them.<\/p>\n2.3 Seizures and Physical Reactions<\/strong> \u2014 Do not design content that causes seizures. Avoid flashing content that could trigger photosensitive epilepsy.<\/p>\n2.4 Navigable<\/strong> \u2014 Help users navigate and find content. Provide clear headings, descriptive link text, and logical focus order.<\/p>\n2.5 Input Modalities<\/strong> \u2014 Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.<\/p>\nUnderstandable guidelines<\/h3>\n3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
The DOJ’s ADA Title II Final Rule<\/strong> formally adopted WCAG 2.1 Level AA for all state and local governments. This covers government websites, mobile apps, digital documents, and online services.<\/p>\n<\/figure>\n\n\n\n\nEntity type<\/th>\nPopulation<\/th>\nCompliance deadline<\/th>\n<\/tr>\n<\/thead>\n\n\nLarge public entities<\/td>\n50,000+ residents<\/td>\nApril 24, 2026<\/td>\n<\/tr>\n\nSmall public entities<\/td>\nUnder 50,000 residents<\/td>\nApril 26, 2027<\/td>\n<\/tr>\n\nSpecial district governments<\/td>\nAny size<\/td>\nApril 26, 2027<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nFor private businesses, Title III of the Americans with Disabilities Act<\/strong> requires website accessibility based on court rulings and DOJ settlement agreements. Section 508<\/strong> of the Rehabilitation Act explicitly requires WCAG compliance for federal government agencies and contractors.<\/p>\nDigital accessibility lawsuits remain widespread. Automated tools now generate complaints at scale, making any business with accessibility issues a potential target.<\/p>\nWhat accessibility laws require WCAG compliance?<\/strong><\/h3>\nDigital accessibility legislation worldwide references WCAG as the technical standard for compliance. Meeting WCAG requirements satisfies most accessibility regulations.<\/p>\n\n\n\n\nLaw \/ regulation<\/th>\nGeographic scope<\/th>\nWCAG standard required<\/th>\nCompliance deadline<\/th>\n<\/tr>\n<\/thead>\n\n\nADA Title II (DOJ Rule)<\/td>\nUS state \/ local governments<\/td>\nWCAG 2.1 AA<\/td>\nApril 2026 \/ 2027<\/td>\n<\/tr>\n\nADA Title III<\/td>\nUS private businesses<\/td>\nWCAG 2.1 AA (de facto standard per courts)<\/td>\nOngoing<\/td>\n<\/tr>\n\nSection 508<\/td>\nUS federal agencies<\/td>\nWCAG 2.0 AA<\/td>\nCurrent<\/td>\n<\/tr>\n\nEuropean Accessibility Act<\/td>\nBusinesses serving EU consumers<\/td>\nEN 301 549 (Incorporates WCAG 2.1 AA)<\/td>\nJune 28, 2025<\/td>\n<\/tr>\n\nAODA<\/td>\nOntario, Canada<\/td>\nWCAG 2.0 AA<\/td>\nCurrent<\/td>\n<\/tr>\n\nEuropean Web Accessibility Directive<\/td>\nEuropean Union public sector<\/td>\nEN 301 549 (Incorporates WCAG 2.1 AA)<\/td>\nCurrent<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nThe European Accessibility Act (EAA) became enforceable on June 28, 2025<\/strong>, requiring WCAG compliance for many businesses selling digital products or services to EU customers. Penalties vary by member state\u2014fines reach \u20ac100,000 in Germany<\/strong> and \u20ac250,000 in France<\/strong>. Non-compliant products can be removed from the market entirely.<\/p>\nWhat are the four principles of WCAG?<\/strong><\/h3>\nThe four principles of WCAG\u2014known as POUR<\/strong>\u2014are Perceivable, Operable, Understandable, and Robust. These principles guide all WCAG success criteria and define what it means for web content to be accessible.<\/p>\n\n\n\n\nPrinciple<\/th>\nWhat It Means<\/th>\nExample Requirement<\/th>\n<\/tr>\n<\/thead>\n\n\nPerceivable<\/td>\nUsers must be able to perceive content through at least one sense.<\/td>\nProvide text alternatives for images; add captions to videos.<\/td>\n<\/tr>\n\nOperable<\/td>\nUsers must be able to operate the interface.<\/td>\nEnable keyboard access; provide enough time to read content.<\/td>\n<\/tr>\n\nUnderstandable<\/td>\nUsers must understand the content and how to use it.<\/td>\nUse clear language; make navigation predictable.<\/td>\n<\/tr>\n\nRobust<\/td>\nContent must work with current and future user agents.<\/td>\nUse valid code; ensure compatibility with assistive technology.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nWhat are the 13 WCAG guidelines?<\/strong><\/h3>\nThe four WCAG principles contain 13 guidelines<\/strong> that provide specific objectives for web accessibility. Each guideline has testable success criteria at three WCAG conformance levels: A, AA, and AAA.<\/p>\nPerceivable guidelines<\/strong><\/h3>\n1.1 Text Alternatives<\/strong> \u2014 Provide text alternatives for non-text content. This includes alt text for images, labels for form fields, and descriptions for icons. Text alternatives let screen reader users understand content they cannot see.<\/p>\n1.2 Time-Based Media<\/strong> \u2014 Provide alternatives for audio and video content. This includes captions for videos, transcripts for audio files, and audio descriptions for visual content.<\/p>\n1.3 Adaptable<\/strong> \u2014 Create content that can be presented in different ways without losing information. Web pages should maintain meaning when users change display settings or use assistive technology.<\/p>\n1.4 Distinguishable<\/strong> \u2014 Make content easy to see and hear. This includes sufficient color contrast, resizable text, and audio controls. Users with low vision or hearing loss depend on these features.<\/p>\nOperable guidelines<\/strong><\/h3>\n2.1 Keyboard Accessible<\/strong> \u2014 Make all functionality available from a keyboard. Users who cannot use a mouse must be able to navigate web content using keyboard access alone.<\/p>\n2.2 Enough Time<\/strong> \u2014 Give users enough time to read and interact with content. Avoid strict time limits, or provide ways to extend them.<\/p>\n2.3 Seizures and Physical Reactions<\/strong> \u2014 Do not design content that causes seizures. Avoid flashing content that could trigger photosensitive epilepsy.<\/p>\n2.4 Navigable<\/strong> \u2014 Help users navigate and find content. Provide clear headings, descriptive link text, and logical focus order.<\/p>\n2.5 Input Modalities<\/strong> \u2014 Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.<\/p>\nUnderstandable guidelines<\/h3>\n3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
For private businesses, Title III of the Americans with Disabilities Act<\/strong> requires website accessibility based on court rulings and DOJ settlement agreements. Section 508<\/strong> of the Rehabilitation Act explicitly requires WCAG compliance for federal government agencies and contractors.<\/p>\nDigital accessibility lawsuits remain widespread. Automated tools now generate complaints at scale, making any business with accessibility issues a potential target.<\/p>\nWhat accessibility laws require WCAG compliance?<\/strong><\/h3>\nDigital accessibility legislation worldwide references WCAG as the technical standard for compliance. Meeting WCAG requirements satisfies most accessibility regulations.<\/p>\n\n\n\n\nLaw \/ regulation<\/th>\nGeographic scope<\/th>\nWCAG standard required<\/th>\nCompliance deadline<\/th>\n<\/tr>\n<\/thead>\n\n\nADA Title II (DOJ Rule)<\/td>\nUS state \/ local governments<\/td>\nWCAG 2.1 AA<\/td>\nApril 2026 \/ 2027<\/td>\n<\/tr>\n\nADA Title III<\/td>\nUS private businesses<\/td>\nWCAG 2.1 AA (de facto standard per courts)<\/td>\nOngoing<\/td>\n<\/tr>\n\nSection 508<\/td>\nUS federal agencies<\/td>\nWCAG 2.0 AA<\/td>\nCurrent<\/td>\n<\/tr>\n\nEuropean Accessibility Act<\/td>\nBusinesses serving EU consumers<\/td>\nEN 301 549 (Incorporates WCAG 2.1 AA)<\/td>\nJune 28, 2025<\/td>\n<\/tr>\n\nAODA<\/td>\nOntario, Canada<\/td>\nWCAG 2.0 AA<\/td>\nCurrent<\/td>\n<\/tr>\n\nEuropean Web Accessibility Directive<\/td>\nEuropean Union public sector<\/td>\nEN 301 549 (Incorporates WCAG 2.1 AA)<\/td>\nCurrent<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nThe European Accessibility Act (EAA) became enforceable on June 28, 2025<\/strong>, requiring WCAG compliance for many businesses selling digital products or services to EU customers. Penalties vary by member state\u2014fines reach \u20ac100,000 in Germany<\/strong> and \u20ac250,000 in France<\/strong>. Non-compliant products can be removed from the market entirely.<\/p>\nWhat are the four principles of WCAG?<\/strong><\/h3>\nThe four principles of WCAG\u2014known as POUR<\/strong>\u2014are Perceivable, Operable, Understandable, and Robust. These principles guide all WCAG success criteria and define what it means for web content to be accessible.<\/p>\n\n\n\n\nPrinciple<\/th>\nWhat It Means<\/th>\nExample Requirement<\/th>\n<\/tr>\n<\/thead>\n\n\nPerceivable<\/td>\nUsers must be able to perceive content through at least one sense.<\/td>\nProvide text alternatives for images; add captions to videos.<\/td>\n<\/tr>\n\nOperable<\/td>\nUsers must be able to operate the interface.<\/td>\nEnable keyboard access; provide enough time to read content.<\/td>\n<\/tr>\n\nUnderstandable<\/td>\nUsers must understand the content and how to use it.<\/td>\nUse clear language; make navigation predictable.<\/td>\n<\/tr>\n\nRobust<\/td>\nContent must work with current and future user agents.<\/td>\nUse valid code; ensure compatibility with assistive technology.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nWhat are the 13 WCAG guidelines?<\/strong><\/h3>\nThe four WCAG principles contain 13 guidelines<\/strong> that provide specific objectives for web accessibility. Each guideline has testable success criteria at three WCAG conformance levels: A, AA, and AAA.<\/p>\nPerceivable guidelines<\/strong><\/h3>\n1.1 Text Alternatives<\/strong> \u2014 Provide text alternatives for non-text content. This includes alt text for images, labels for form fields, and descriptions for icons. Text alternatives let screen reader users understand content they cannot see.<\/p>\n1.2 Time-Based Media<\/strong> \u2014 Provide alternatives for audio and video content. This includes captions for videos, transcripts for audio files, and audio descriptions for visual content.<\/p>\n1.3 Adaptable<\/strong> \u2014 Create content that can be presented in different ways without losing information. Web pages should maintain meaning when users change display settings or use assistive technology.<\/p>\n1.4 Distinguishable<\/strong> \u2014 Make content easy to see and hear. This includes sufficient color contrast, resizable text, and audio controls. Users with low vision or hearing loss depend on these features.<\/p>\nOperable guidelines<\/strong><\/h3>\n2.1 Keyboard Accessible<\/strong> \u2014 Make all functionality available from a keyboard. Users who cannot use a mouse must be able to navigate web content using keyboard access alone.<\/p>\n2.2 Enough Time<\/strong> \u2014 Give users enough time to read and interact with content. Avoid strict time limits, or provide ways to extend them.<\/p>\n2.3 Seizures and Physical Reactions<\/strong> \u2014 Do not design content that causes seizures. Avoid flashing content that could trigger photosensitive epilepsy.<\/p>\n2.4 Navigable<\/strong> \u2014 Help users navigate and find content. Provide clear headings, descriptive link text, and logical focus order.<\/p>\n2.5 Input Modalities<\/strong> \u2014 Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.<\/p>\nUnderstandable guidelines<\/h3>\n3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
Digital accessibility lawsuits remain widespread. Automated tools now generate complaints at scale, making any business with accessibility issues a potential target.<\/p>\n
Digital accessibility legislation worldwide references WCAG as the technical standard for compliance. Meeting WCAG requirements satisfies most accessibility regulations.<\/p>\n\n\n\n\nLaw \/ regulation<\/th>\nGeographic scope<\/th>\nWCAG standard required<\/th>\nCompliance deadline<\/th>\n<\/tr>\n<\/thead>\n\n\nADA Title II (DOJ Rule)<\/td>\nUS state \/ local governments<\/td>\nWCAG 2.1 AA<\/td>\nApril 2026 \/ 2027<\/td>\n<\/tr>\n\nADA Title III<\/td>\nUS private businesses<\/td>\nWCAG 2.1 AA (de facto standard per courts)<\/td>\nOngoing<\/td>\n<\/tr>\n\nSection 508<\/td>\nUS federal agencies<\/td>\nWCAG 2.0 AA<\/td>\nCurrent<\/td>\n<\/tr>\n\nEuropean Accessibility Act<\/td>\nBusinesses serving EU consumers<\/td>\nEN 301 549 (Incorporates WCAG 2.1 AA)<\/td>\nJune 28, 2025<\/td>\n<\/tr>\n\nAODA<\/td>\nOntario, Canada<\/td>\nWCAG 2.0 AA<\/td>\nCurrent<\/td>\n<\/tr>\n\nEuropean Web Accessibility Directive<\/td>\nEuropean Union public sector<\/td>\nEN 301 549 (Incorporates WCAG 2.1 AA)<\/td>\nCurrent<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nThe European Accessibility Act (EAA) became enforceable on June 28, 2025<\/strong>, requiring WCAG compliance for many businesses selling digital products or services to EU customers. Penalties vary by member state\u2014fines reach \u20ac100,000 in Germany<\/strong> and \u20ac250,000 in France<\/strong>. Non-compliant products can be removed from the market entirely.<\/p>\nWhat are the four principles of WCAG?<\/strong><\/h3>\nThe four principles of WCAG\u2014known as POUR<\/strong>\u2014are Perceivable, Operable, Understandable, and Robust. These principles guide all WCAG success criteria and define what it means for web content to be accessible.<\/p>\n\n\n\n\nPrinciple<\/th>\nWhat It Means<\/th>\nExample Requirement<\/th>\n<\/tr>\n<\/thead>\n\n\nPerceivable<\/td>\nUsers must be able to perceive content through at least one sense.<\/td>\nProvide text alternatives for images; add captions to videos.<\/td>\n<\/tr>\n\nOperable<\/td>\nUsers must be able to operate the interface.<\/td>\nEnable keyboard access; provide enough time to read content.<\/td>\n<\/tr>\n\nUnderstandable<\/td>\nUsers must understand the content and how to use it.<\/td>\nUse clear language; make navigation predictable.<\/td>\n<\/tr>\n\nRobust<\/td>\nContent must work with current and future user agents.<\/td>\nUse valid code; ensure compatibility with assistive technology.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nWhat are the 13 WCAG guidelines?<\/strong><\/h3>\nThe four WCAG principles contain 13 guidelines<\/strong> that provide specific objectives for web accessibility. Each guideline has testable success criteria at three WCAG conformance levels: A, AA, and AAA.<\/p>\nPerceivable guidelines<\/strong><\/h3>\n1.1 Text Alternatives<\/strong> \u2014 Provide text alternatives for non-text content. This includes alt text for images, labels for form fields, and descriptions for icons. Text alternatives let screen reader users understand content they cannot see.<\/p>\n1.2 Time-Based Media<\/strong> \u2014 Provide alternatives for audio and video content. This includes captions for videos, transcripts for audio files, and audio descriptions for visual content.<\/p>\n1.3 Adaptable<\/strong> \u2014 Create content that can be presented in different ways without losing information. Web pages should maintain meaning when users change display settings or use assistive technology.<\/p>\n1.4 Distinguishable<\/strong> \u2014 Make content easy to see and hear. This includes sufficient color contrast, resizable text, and audio controls. Users with low vision or hearing loss depend on these features.<\/p>\nOperable guidelines<\/strong><\/h3>\n2.1 Keyboard Accessible<\/strong> \u2014 Make all functionality available from a keyboard. Users who cannot use a mouse must be able to navigate web content using keyboard access alone.<\/p>\n2.2 Enough Time<\/strong> \u2014 Give users enough time to read and interact with content. Avoid strict time limits, or provide ways to extend them.<\/p>\n2.3 Seizures and Physical Reactions<\/strong> \u2014 Do not design content that causes seizures. Avoid flashing content that could trigger photosensitive epilepsy.<\/p>\n2.4 Navigable<\/strong> \u2014 Help users navigate and find content. Provide clear headings, descriptive link text, and logical focus order.<\/p>\n2.5 Input Modalities<\/strong> \u2014 Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.<\/p>\nUnderstandable guidelines<\/h3>\n3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
The European Accessibility Act (EAA) became enforceable on June 28, 2025<\/strong>, requiring WCAG compliance for many businesses selling digital products or services to EU customers. Penalties vary by member state\u2014fines reach \u20ac100,000 in Germany<\/strong> and \u20ac250,000 in France<\/strong>. Non-compliant products can be removed from the market entirely.<\/p>\nWhat are the four principles of WCAG?<\/strong><\/h3>\nThe four principles of WCAG\u2014known as POUR<\/strong>\u2014are Perceivable, Operable, Understandable, and Robust. These principles guide all WCAG success criteria and define what it means for web content to be accessible.<\/p>\n\n\n\n\nPrinciple<\/th>\nWhat It Means<\/th>\nExample Requirement<\/th>\n<\/tr>\n<\/thead>\n\n\nPerceivable<\/td>\nUsers must be able to perceive content through at least one sense.<\/td>\nProvide text alternatives for images; add captions to videos.<\/td>\n<\/tr>\n\nOperable<\/td>\nUsers must be able to operate the interface.<\/td>\nEnable keyboard access; provide enough time to read content.<\/td>\n<\/tr>\n\nUnderstandable<\/td>\nUsers must understand the content and how to use it.<\/td>\nUse clear language; make navigation predictable.<\/td>\n<\/tr>\n\nRobust<\/td>\nContent must work with current and future user agents.<\/td>\nUse valid code; ensure compatibility with assistive technology.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nWhat are the 13 WCAG guidelines?<\/strong><\/h3>\nThe four WCAG principles contain 13 guidelines<\/strong> that provide specific objectives for web accessibility. Each guideline has testable success criteria at three WCAG conformance levels: A, AA, and AAA.<\/p>\nPerceivable guidelines<\/strong><\/h3>\n1.1 Text Alternatives<\/strong> \u2014 Provide text alternatives for non-text content. This includes alt text for images, labels for form fields, and descriptions for icons. Text alternatives let screen reader users understand content they cannot see.<\/p>\n1.2 Time-Based Media<\/strong> \u2014 Provide alternatives for audio and video content. This includes captions for videos, transcripts for audio files, and audio descriptions for visual content.<\/p>\n1.3 Adaptable<\/strong> \u2014 Create content that can be presented in different ways without losing information. Web pages should maintain meaning when users change display settings or use assistive technology.<\/p>\n1.4 Distinguishable<\/strong> \u2014 Make content easy to see and hear. This includes sufficient color contrast, resizable text, and audio controls. Users with low vision or hearing loss depend on these features.<\/p>\nOperable guidelines<\/strong><\/h3>\n2.1 Keyboard Accessible<\/strong> \u2014 Make all functionality available from a keyboard. Users who cannot use a mouse must be able to navigate web content using keyboard access alone.<\/p>\n2.2 Enough Time<\/strong> \u2014 Give users enough time to read and interact with content. Avoid strict time limits, or provide ways to extend them.<\/p>\n2.3 Seizures and Physical Reactions<\/strong> \u2014 Do not design content that causes seizures. Avoid flashing content that could trigger photosensitive epilepsy.<\/p>\n2.4 Navigable<\/strong> \u2014 Help users navigate and find content. Provide clear headings, descriptive link text, and logical focus order.<\/p>\n2.5 Input Modalities<\/strong> \u2014 Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.<\/p>\nUnderstandable guidelines<\/h3>\n3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
The four principles of WCAG\u2014known as POUR<\/strong>\u2014are Perceivable, Operable, Understandable, and Robust. These principles guide all WCAG success criteria and define what it means for web content to be accessible.<\/p>\n\n\n\n\nPrinciple<\/th>\nWhat It Means<\/th>\nExample Requirement<\/th>\n<\/tr>\n<\/thead>\n\n\nPerceivable<\/td>\nUsers must be able to perceive content through at least one sense.<\/td>\nProvide text alternatives for images; add captions to videos.<\/td>\n<\/tr>\n\nOperable<\/td>\nUsers must be able to operate the interface.<\/td>\nEnable keyboard access; provide enough time to read content.<\/td>\n<\/tr>\n\nUnderstandable<\/td>\nUsers must understand the content and how to use it.<\/td>\nUse clear language; make navigation predictable.<\/td>\n<\/tr>\n\nRobust<\/td>\nContent must work with current and future user agents.<\/td>\nUse valid code; ensure compatibility with assistive technology.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nWhat are the 13 WCAG guidelines?<\/strong><\/h3>\nThe four WCAG principles contain 13 guidelines<\/strong> that provide specific objectives for web accessibility. Each guideline has testable success criteria at three WCAG conformance levels: A, AA, and AAA.<\/p>\nPerceivable guidelines<\/strong><\/h3>\n1.1 Text Alternatives<\/strong> \u2014 Provide text alternatives for non-text content. This includes alt text for images, labels for form fields, and descriptions for icons. Text alternatives let screen reader users understand content they cannot see.<\/p>\n1.2 Time-Based Media<\/strong> \u2014 Provide alternatives for audio and video content. This includes captions for videos, transcripts for audio files, and audio descriptions for visual content.<\/p>\n1.3 Adaptable<\/strong> \u2014 Create content that can be presented in different ways without losing information. Web pages should maintain meaning when users change display settings or use assistive technology.<\/p>\n1.4 Distinguishable<\/strong> \u2014 Make content easy to see and hear. This includes sufficient color contrast, resizable text, and audio controls. Users with low vision or hearing loss depend on these features.<\/p>\nOperable guidelines<\/strong><\/h3>\n2.1 Keyboard Accessible<\/strong> \u2014 Make all functionality available from a keyboard. Users who cannot use a mouse must be able to navigate web content using keyboard access alone.<\/p>\n2.2 Enough Time<\/strong> \u2014 Give users enough time to read and interact with content. Avoid strict time limits, or provide ways to extend them.<\/p>\n2.3 Seizures and Physical Reactions<\/strong> \u2014 Do not design content that causes seizures. Avoid flashing content that could trigger photosensitive epilepsy.<\/p>\n2.4 Navigable<\/strong> \u2014 Help users navigate and find content. Provide clear headings, descriptive link text, and logical focus order.<\/p>\n2.5 Input Modalities<\/strong> \u2014 Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.<\/p>\nUnderstandable guidelines<\/h3>\n3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
The four WCAG principles contain 13 guidelines<\/strong> that provide specific objectives for web accessibility. Each guideline has testable success criteria at three WCAG conformance levels: A, AA, and AAA.<\/p>\nPerceivable guidelines<\/strong><\/h3>\n1.1 Text Alternatives<\/strong> \u2014 Provide text alternatives for non-text content. This includes alt text for images, labels for form fields, and descriptions for icons. Text alternatives let screen reader users understand content they cannot see.<\/p>\n1.2 Time-Based Media<\/strong> \u2014 Provide alternatives for audio and video content. This includes captions for videos, transcripts for audio files, and audio descriptions for visual content.<\/p>\n1.3 Adaptable<\/strong> \u2014 Create content that can be presented in different ways without losing information. Web pages should maintain meaning when users change display settings or use assistive technology.<\/p>\n1.4 Distinguishable<\/strong> \u2014 Make content easy to see and hear. This includes sufficient color contrast, resizable text, and audio controls. Users with low vision or hearing loss depend on these features.<\/p>\nOperable guidelines<\/strong><\/h3>\n2.1 Keyboard Accessible<\/strong> \u2014 Make all functionality available from a keyboard. Users who cannot use a mouse must be able to navigate web content using keyboard access alone.<\/p>\n2.2 Enough Time<\/strong> \u2014 Give users enough time to read and interact with content. Avoid strict time limits, or provide ways to extend them.<\/p>\n2.3 Seizures and Physical Reactions<\/strong> \u2014 Do not design content that causes seizures. Avoid flashing content that could trigger photosensitive epilepsy.<\/p>\n2.4 Navigable<\/strong> \u2014 Help users navigate and find content. Provide clear headings, descriptive link text, and logical focus order.<\/p>\n2.5 Input Modalities<\/strong> \u2014 Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.<\/p>\nUnderstandable guidelines<\/h3>\n3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
1.1 Text Alternatives<\/strong> \u2014 Provide text alternatives for non-text content. This includes alt text for images, labels for form fields, and descriptions for icons. Text alternatives let screen reader users understand content they cannot see.<\/p>\n1.2 Time-Based Media<\/strong> \u2014 Provide alternatives for audio and video content. This includes captions for videos, transcripts for audio files, and audio descriptions for visual content.<\/p>\n1.3 Adaptable<\/strong> \u2014 Create content that can be presented in different ways without losing information. Web pages should maintain meaning when users change display settings or use assistive technology.<\/p>\n1.4 Distinguishable<\/strong> \u2014 Make content easy to see and hear. This includes sufficient color contrast, resizable text, and audio controls. Users with low vision or hearing loss depend on these features.<\/p>\nOperable guidelines<\/strong><\/h3>\n2.1 Keyboard Accessible<\/strong> \u2014 Make all functionality available from a keyboard. Users who cannot use a mouse must be able to navigate web content using keyboard access alone.<\/p>\n2.2 Enough Time<\/strong> \u2014 Give users enough time to read and interact with content. Avoid strict time limits, or provide ways to extend them.<\/p>\n2.3 Seizures and Physical Reactions<\/strong> \u2014 Do not design content that causes seizures. Avoid flashing content that could trigger photosensitive epilepsy.<\/p>\n2.4 Navigable<\/strong> \u2014 Help users navigate and find content. Provide clear headings, descriptive link text, and logical focus order.<\/p>\n2.5 Input Modalities<\/strong> \u2014 Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.<\/p>\nUnderstandable guidelines<\/h3>\n3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
1.2 Time-Based Media<\/strong> \u2014 Provide alternatives for audio and video content. This includes captions for videos, transcripts for audio files, and audio descriptions for visual content.<\/p>\n1.3 Adaptable<\/strong> \u2014 Create content that can be presented in different ways without losing information. Web pages should maintain meaning when users change display settings or use assistive technology.<\/p>\n1.4 Distinguishable<\/strong> \u2014 Make content easy to see and hear. This includes sufficient color contrast, resizable text, and audio controls. Users with low vision or hearing loss depend on these features.<\/p>\nOperable guidelines<\/strong><\/h3>\n2.1 Keyboard Accessible<\/strong> \u2014 Make all functionality available from a keyboard. Users who cannot use a mouse must be able to navigate web content using keyboard access alone.<\/p>\n2.2 Enough Time<\/strong> \u2014 Give users enough time to read and interact with content. Avoid strict time limits, or provide ways to extend them.<\/p>\n2.3 Seizures and Physical Reactions<\/strong> \u2014 Do not design content that causes seizures. Avoid flashing content that could trigger photosensitive epilepsy.<\/p>\n2.4 Navigable<\/strong> \u2014 Help users navigate and find content. Provide clear headings, descriptive link text, and logical focus order.<\/p>\n2.5 Input Modalities<\/strong> \u2014 Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.<\/p>\nUnderstandable guidelines<\/h3>\n3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
1.3 Adaptable<\/strong> \u2014 Create content that can be presented in different ways without losing information. Web pages should maintain meaning when users change display settings or use assistive technology.<\/p>\n1.4 Distinguishable<\/strong> \u2014 Make content easy to see and hear. This includes sufficient color contrast, resizable text, and audio controls. Users with low vision or hearing loss depend on these features.<\/p>\nOperable guidelines<\/strong><\/h3>\n2.1 Keyboard Accessible<\/strong> \u2014 Make all functionality available from a keyboard. Users who cannot use a mouse must be able to navigate web content using keyboard access alone.<\/p>\n2.2 Enough Time<\/strong> \u2014 Give users enough time to read and interact with content. Avoid strict time limits, or provide ways to extend them.<\/p>\n2.3 Seizures and Physical Reactions<\/strong> \u2014 Do not design content that causes seizures. Avoid flashing content that could trigger photosensitive epilepsy.<\/p>\n2.4 Navigable<\/strong> \u2014 Help users navigate and find content. Provide clear headings, descriptive link text, and logical focus order.<\/p>\n2.5 Input Modalities<\/strong> \u2014 Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.<\/p>\nUnderstandable guidelines<\/h3>\n3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
1.4 Distinguishable<\/strong> \u2014 Make content easy to see and hear. This includes sufficient color contrast, resizable text, and audio controls. Users with low vision or hearing loss depend on these features.<\/p>\nOperable guidelines<\/strong><\/h3>\n2.1 Keyboard Accessible<\/strong> \u2014 Make all functionality available from a keyboard. Users who cannot use a mouse must be able to navigate web content using keyboard access alone.<\/p>\n2.2 Enough Time<\/strong> \u2014 Give users enough time to read and interact with content. Avoid strict time limits, or provide ways to extend them.<\/p>\n2.3 Seizures and Physical Reactions<\/strong> \u2014 Do not design content that causes seizures. Avoid flashing content that could trigger photosensitive epilepsy.<\/p>\n2.4 Navigable<\/strong> \u2014 Help users navigate and find content. Provide clear headings, descriptive link text, and logical focus order.<\/p>\n2.5 Input Modalities<\/strong> \u2014 Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.<\/p>\nUnderstandable guidelines<\/h3>\n3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
2.1 Keyboard Accessible<\/strong> \u2014 Make all functionality available from a keyboard. Users who cannot use a mouse must be able to navigate web content using keyboard access alone.<\/p>\n2.2 Enough Time<\/strong> \u2014 Give users enough time to read and interact with content. Avoid strict time limits, or provide ways to extend them.<\/p>\n2.3 Seizures and Physical Reactions<\/strong> \u2014 Do not design content that causes seizures. Avoid flashing content that could trigger photosensitive epilepsy.<\/p>\n2.4 Navigable<\/strong> \u2014 Help users navigate and find content. Provide clear headings, descriptive link text, and logical focus order.<\/p>\n2.5 Input Modalities<\/strong> \u2014 Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.<\/p>\nUnderstandable guidelines<\/h3>\n3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
2.2 Enough Time<\/strong> \u2014 Give users enough time to read and interact with content. Avoid strict time limits, or provide ways to extend them.<\/p>\n2.3 Seizures and Physical Reactions<\/strong> \u2014 Do not design content that causes seizures. Avoid flashing content that could trigger photosensitive epilepsy.<\/p>\n2.4 Navigable<\/strong> \u2014 Help users navigate and find content. Provide clear headings, descriptive link text, and logical focus order.<\/p>\n2.5 Input Modalities<\/strong> \u2014 Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.<\/p>\nUnderstandable guidelines<\/h3>\n3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
2.3 Seizures and Physical Reactions<\/strong> \u2014 Do not design content that causes seizures. Avoid flashing content that could trigger photosensitive epilepsy.<\/p>\n2.4 Navigable<\/strong> \u2014 Help users navigate and find content. Provide clear headings, descriptive link text, and logical focus order.<\/p>\n2.5 Input Modalities<\/strong> \u2014 Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.<\/p>\nUnderstandable guidelines<\/h3>\n3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
2.4 Navigable<\/strong> \u2014 Help users navigate and find content. Provide clear headings, descriptive link text, and logical focus order.<\/p>\n2.5 Input Modalities<\/strong> \u2014 Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.<\/p>\nUnderstandable guidelines<\/h3>\n3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
2.5 Input Modalities<\/strong> \u2014 Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.<\/p>\nUnderstandable guidelines<\/h3>\n3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
3.1 Readable<\/strong> \u2014 Make text readable and understandable. Use clear language and define unusual terms or abbreviations.<\/p>\n3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
3.2 Predictable<\/strong> \u2014 Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.<\/p>\n3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
3.3 Input Assistance<\/strong> \u2014 Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.<\/p>\nRobust guidelines<\/strong><\/h3>\n4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
4.1 Compatible<\/strong> \u2014 Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.<\/p>\nWhat are the three WCAG conformance levels?<\/strong><\/h3>\nWCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
WCAG has three conformance levels\u2014Level A, Level AA, and Level AAA<\/strong>\u2014that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.<\/p>\n\n\n\n\nLevel<\/th>\nDescription<\/th>\nSuccess Criteria<\/th>\nLegal Status<\/th>\n<\/tr>\n<\/thead>\n\n\nLevel A<\/td>\nMinimum accessibility\u2014addresses the most critical accessibility barriers.<\/td>\n30 criteria<\/td>\nRequired for compliance<\/td>\n<\/tr>\n\nLevel AA<\/td>\nStandard accessibility\u2014removes barriers for most people with disabilities.<\/td>\n20 additional criteria<\/td>\nRequired by most laws<\/td>\n<\/tr>\n\nLevel AAA<\/td>\nHighest accessibility\u2014provides enhanced access but is not always achievable.<\/td>\n28 additional criteria<\/td>\nAspirational; not legally required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\nEach level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\nFor WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
Each level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.<\/p>\n
For WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria.<\/strong> Level AAA conformance is optional because some criteria cannot be met for all content types.<\/p>\nHow success criteria differ by level<\/strong><\/h3>\nThe same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
The same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:<\/p>\n<\/figure>\n
![\"Search\"](\"https:\/\/stage-barriano.projectbeta.biz\/wp-content\/uploads\/2026\/07\/search.svg\" "\\"search\\"")
<\/span><\/div><\/div><\/div>