{"id":7612,"date":"2026-11-13T04:15:39","date_gmt":"2026-11-13T04:15:39","guid":{"rendered":"https:\/\/www.originux.com\/resources\/?p=7612"},"modified":"2026-11-13T04:15:42","modified_gmt":"2026-11-13T04:15:42","slug":"accessibility-checklist-what-to-review-before-you-launch","status":"publish","type":"post","link":"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/","title":{"rendered":"Accessibility Checklist: What to Review Before You Launch"},"content":{"rendered":"<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_81 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#Why_Accessibility_Matters\" >Why Accessibility Matters<\/a><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#Benefits_of_reviewing_accessibility_before_launch\" >Benefits of reviewing accessibility before launch<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#Understanding_the_Standards\" >Understanding the Standards<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#How_to_Use_This_Checklist\" >How to Use This Checklist<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#1_Visual_Design_and_Color\" >1. Visual Design and Color<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#2_Keyboard_Accessibility\" >2. Keyboard Accessibility<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#3_Screen_Reader_and_Semantic_Structure\" >3. Screen Reader and Semantic Structure<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#4_Images_Icons_and_Graphics\" >4. Images, Icons and Graphics<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#5_Forms_and_Inputs\" >5. Forms and Inputs<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#6_Video_Audio_and_Motion\" >6. Video, Audio and Motion<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#7_Content_and_Language\" >7. Content and Language<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#8_Navigation_and_Wayfinding\" >8. Navigation and Wayfinding<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#9_Mobile_and_Touch_Accessibility\" >9. Mobile and Touch Accessibility<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#10_Components_and_Design_Systems\" >10. Components and Design Systems<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#11_Testing_Methods\" >11. Testing Methods<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-16\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#12_Documentation_and_Accessibility_Statement\" >12. Documentation and Accessibility Statement<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-17\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#Common_Accessibility_Mistakes\" >Common Accessibility Mistakes<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-18\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#Prioritizing_Fixes_Before_Launch\" >Prioritizing Fixes Before Launch<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-19\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#Learning_from_Real_Users\" >Learning from Real Users<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-20\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#Final_Pre-Launch_Accessibility_Checklist\" >Final Pre-Launch Accessibility Checklist<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-21\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#Getting_Started\" >Getting Started<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-22\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#Final_Thoughts\" >Final Thoughts<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-23\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#FAQs\" >FAQs<\/a><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-24\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#What_should_an_accessibility_checklist_include\" >What should an accessibility checklist include?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-25\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#Which_accessibility_standard_should_I_follow\" >Which accessibility standard should I follow?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-26\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#Can_automated_tools_test_accessibility_completely\" >Can automated tools test accessibility completely?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-27\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#When_should_I_start_thinking_about_accessibility\" >When should I start thinking about accessibility?<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n\n<p class=\"wp-block-paragraph\">A team is ready to launch a new website. The design is sleek, the animations are smooth and the copy is sharp. Then a user who navigates with a keyboard tries to reach the main menu and gets stuck in a carousel. Another user with low vision cannot read the light gray text on a white background. A screen reader user hears \u201cbutton, button, button\u201d with no explanation of what any of them do. The site looks finished, but many people cannot use it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Accessibility problems are easier and cheaper to fix before launch than after. This checklist walks through the most important areas to review, from visual design and keyboard use to forms, media, mobile and testing, so you can launch with confidence.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Why_Accessibility_Matters\"><\/span><strong>Why Accessibility Matters<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Accessibility means making products usable by people with a wide range of abilities, devices and situations. That includes people with visual, hearing, motor and cognitive disabilities, as well as people using small screens, slow connections, bright sunlight or a single hand.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Benefits_of_reviewing_accessibility_before_launch\"><\/span><strong>Benefits of reviewing accessibility before launch<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Wider audience:<\/strong> more people can use and buy from your product.<\/li>\n\n\n\n<li><strong>Better usability for everyone:<\/strong> clear structure, readable text and logical flows help all users.<\/li>\n\n\n\n<li><strong>Lower legal and reputational risk:<\/strong> many regions have accessibility laws and expectations, so check what applies to you.<\/li>\n\n\n\n<li><strong>Better SEO and performance:<\/strong> semantic structure, descriptive text and clean code often help search engines too.<\/li>\n\n\n\n<li><strong>Lower cost:<\/strong> fixing issues early is much cheaper than rebuilding later.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Understanding_the_Standards\"><\/span><strong>Understanding the Standards<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Most teams use the <strong>Web Content Accessibility Guidelines (WCAG)<\/strong> as the main reference. WCAG organizes requirements around four principles, often summarized as POUR.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Principle<\/th><th>Meaning<\/th><th>Example<\/th><\/tr><\/thead><tbody><tr><td>Perceivable<\/td><td>Users can perceive content<\/td><td>Text alternatives for images, captions for video<\/td><\/tr><tr><td>Operable<\/td><td>Users can operate the interface<\/td><td>Full keyboard access, enough time, no seizure triggers<\/td><\/tr><tr><td>Understandable<\/td><td>Content and behavior are clear<\/td><td>Predictable navigation, helpful error messages<\/td><\/tr><tr><td>Robust<\/td><td>Content works across technologies<\/td><td>Valid code that works with assistive tools<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">WCAG has conformance levels (A, AA and AAA), and many organizations target Level AA. Standards and legal requirements change and differ by region, so confirm which version and level apply to your product with qualified specialists.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_to_Use_This_Checklist\"><\/span><strong>How to Use This Checklist<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Review in layers:<\/strong> design, content, code and testing.<\/li>\n\n\n\n<li><strong>Test with real tools:<\/strong> use a keyboard, a screen reader and zoom.<\/li>\n\n\n\n<li><strong>Combine automated and manual checks:<\/strong> automated tools catch only a portion of issues.<\/li>\n\n\n\n<li><strong>Include people with disabilities:<\/strong> their feedback is the most valuable.<\/li>\n\n\n\n<li><strong>Record and prioritize issues:<\/strong> label them critical, important or minor.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"1_Visual_Design_and_Color\"><\/span><strong>1. Visual Design and Color<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Check<\/th><th>What good looks like<\/th><\/tr><\/thead><tbody><tr><td>Text contrast<\/td><td>Body text and important UI text meet recommended contrast ratios against their backgrounds<\/td><\/tr><tr><td>Non-text contrast<\/td><td>Buttons, input borders and icons are distinguishable from the background<\/td><\/tr><tr><td>Color is not the only signal<\/td><td>Errors, status and links are also conveyed with text, icons or patterns<\/td><\/tr><tr><td>Readable type<\/td><td>Comfortable font sizes, line height and spacing<\/td><\/tr><tr><td>Text resizing<\/td><td>Content remains usable when text is enlarged significantly<\/td><\/tr><tr><td>Responsive layout<\/td><td>No loss of content or function when zoomed or on small screens<\/td><\/tr><tr><td>Visual clarity<\/td><td>Clear hierarchy, spacing and grouping<\/td><\/tr><tr><td>Dark mode<\/td><td>Contrast and readability hold in both light and dark themes<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"2_Keyboard_Accessibility\"><\/span><strong>2. Keyboard Accessibility<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Many users cannot use a mouse, so every action must work with a keyboard.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>All interactive elements are reachable:<\/strong> links, buttons, menus, forms and custom controls.<\/li>\n\n\n\n<li><strong>Logical tab order:<\/strong> focus moves in a sensible, predictable sequence.<\/li>\n\n\n\n<li><strong>Visible focus indicator:<\/strong> users always know where they are.<\/li>\n\n\n\n<li><strong>No keyboard traps:<\/strong> users can move in and out of modals, menus and widgets.<\/li>\n\n\n\n<li><strong>Skip links:<\/strong> a way to jump past repeated navigation to the main content.<\/li>\n\n\n\n<li><strong>Custom components behave like native ones:<\/strong> correct keys for menus, tabs, dialogs and sliders.<\/li>\n\n\n\n<li><strong>Shortcuts do not conflict:<\/strong> avoid single-key shortcuts that interfere with assistive technology, or allow them to be turned off.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"3_Screen_Reader_and_Semantic_Structure\"><\/span><strong>3. Screen Reader and Semantic Structure<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Screen reader users depend on code that describes content accurately.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Check<\/th><th>What good looks like<\/th><\/tr><\/thead><tbody><tr><td>Page titles<\/td><td>Each page has a unique, descriptive title<\/td><\/tr><tr><td>Headings<\/td><td>Logical heading hierarchy that outlines the content<\/td><\/tr><tr><td>Landmarks<\/td><td>Regions such as header, navigation, main and footer are defined<\/td><\/tr><tr><td>Links<\/td><td>Link text makes sense out of context, not \u201cclick here\u201d<\/td><\/tr><tr><td>Buttons<\/td><td>Buttons have clear, descriptive names<\/td><\/tr><tr><td>Lists and tables<\/td><td>Real list and table markup is used, with headers for data tables<\/td><\/tr><tr><td>Language<\/td><td>The page language is declared<\/td><\/tr><tr><td>Dynamic updates<\/td><td>Changes such as alerts and loading states are announced appropriately<\/td><\/tr><tr><td>Hidden content<\/td><td>Decorative or hidden elements are not read unnecessarily<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Use native HTML elements wherever possible, since they come with built-in accessibility. Add ARIA attributes carefully, only when needed, because incorrect ARIA can make things worse.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"4_Images_Icons_and_Graphics\"><\/span><strong>4. Images, Icons and Graphics<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Meaningful alt text:<\/strong> describes the purpose or content of informative images.<\/li>\n\n\n\n<li><strong>Decorative images are hidden from assistive tools:<\/strong> use empty alt text where appropriate.<\/li>\n\n\n\n<li><strong>Icons have labels:<\/strong> icon-only buttons have accessible names.<\/li>\n\n\n\n<li><strong>Complex images have descriptions:<\/strong> charts and diagrams include a text alternative or summary.<\/li>\n\n\n\n<li><strong>Text in images is avoided:<\/strong> use real text whenever possible.<\/li>\n\n\n\n<li><strong>Logos have appropriate alt text:<\/strong> usually the organization\u2019s name.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"5_Forms_and_Inputs\"><\/span><strong>5. Forms and Inputs<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Forms are where accessibility problems often cause the most harm.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Check<\/th><th>What good looks like<\/th><\/tr><\/thead><tbody><tr><td>Visible labels<\/td><td>Every field has a clear label that stays visible<\/td><\/tr><tr><td>Programmatic labels<\/td><td>Labels are properly associated with inputs<\/td><\/tr><tr><td>Instructions<\/td><td>Formats and requirements are explained before input<\/td><\/tr><tr><td>Required fields<\/td><td>Clearly marked, not only by color<\/td><\/tr><tr><td>Error messages<\/td><td>Specific, polite and placed near the field, with a summary at the top for long forms<\/td><\/tr><tr><td>Error prevention<\/td><td>Confirmations for important actions and easy correction<\/td><\/tr><tr><td>Autocomplete<\/td><td>Appropriate attributes help users fill common fields quickly<\/td><\/tr><tr><td>Input types<\/td><td>Correct types bring the right mobile keyboards<\/td><\/tr><tr><td>Time limits<\/td><td>Users can extend or avoid timeouts<\/td><\/tr><tr><td>CAPTCHA alternatives<\/td><td>Provide accessible alternatives to purely visual or audio challenges<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"6_Video_Audio_and_Motion\"><\/span><strong>6. Video, Audio and Motion<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Check<\/th><th>What good looks like<\/th><\/tr><\/thead><tbody><tr><td>Captions<\/td><td>Accurate captions for videos with speech<\/td><\/tr><tr><td>Transcripts<\/td><td>Text alternatives for audio and video content<\/td><\/tr><tr><td>Audio descriptions<\/td><td>Provided where visuals carry important information<\/td><\/tr><tr><td>Autoplay<\/td><td>No unexpected auto-playing audio, with controls to pause and mute<\/td><\/tr><tr><td>Media controls<\/td><td>Keyboard-accessible players with labeled controls<\/td><\/tr><tr><td>Animation<\/td><td>No content that flashes more than allowed thresholds<\/td><\/tr><tr><td>Reduced motion<\/td><td>Respects user preferences for reduced motion<\/td><\/tr><tr><td>Pause, stop and hide<\/td><td>Users can control moving, scrolling or auto-updating content<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"7_Content_and_Language\"><\/span><strong>7. Content and Language<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Plain language:<\/strong> short sentences, familiar words and clear structure.<\/li>\n\n\n\n<li><strong>Descriptive headings and labels:<\/strong> make scanning easy.<\/li>\n\n\n\n<li><strong>Consistent terminology and navigation:<\/strong> reduces cognitive load.<\/li>\n\n\n\n<li><strong>Abbreviations explained:<\/strong> spell out unusual terms on first use.<\/li>\n\n\n\n<li><strong>Link purpose is clear:<\/strong> from the link text or its context.<\/li>\n\n\n\n<li><strong>Avoid vague instructions:<\/strong> do not rely on \u201csee the green button\u201d or \u201con the right.\u201d<\/li>\n\n\n\n<li><strong>Reading level suits the audience:<\/strong> consider simplified summaries for complex content.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"8_Navigation_and_Wayfinding\"><\/span><strong>8. Navigation and Wayfinding<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Consistent navigation:<\/strong> appears in the same place across pages.<\/li>\n\n\n\n<li><strong>Multiple ways to find content:<\/strong> menus, search and sitemaps where appropriate.<\/li>\n\n\n\n<li><strong>Clear current location:<\/strong> active states and breadcrumbs help orientation.<\/li>\n\n\n\n<li><strong>Predictable behavior:<\/strong> links and controls do what users expect.<\/li>\n\n\n\n<li><strong>Meaningful page titles and headings:<\/strong> help users confirm they are in the right place.<\/li>\n\n\n\n<li><strong>Helpful 404 and error pages:<\/strong> guide users back to useful content.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"9_Mobile_and_Touch_Accessibility\"><\/span><strong>9. Mobile and Touch Accessibility<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Check<\/th><th>What good looks like<\/th><\/tr><\/thead><tbody><tr><td>Touch target size<\/td><td>Buttons and links are large enough and spaced to avoid accidental taps<\/td><\/tr><tr><td>Orientation<\/td><td>Works in both portrait and landscape unless essential otherwise<\/td><\/tr><tr><td>Gestures<\/td><td>Complex gestures have simple alternatives<\/td><\/tr><tr><td>Zoom and scaling<\/td><td>Pinch zoom is not disabled<\/td><\/tr><tr><td>Screen reader support<\/td><td>Tested with built-in mobile screen readers<\/td><\/tr><tr><td>Input methods<\/td><td>Works with touch, keyboard, voice control and switch devices where relevant<\/td><\/tr><tr><td>Responsive reflow<\/td><td>Content adapts without horizontal scrolling at typical zoom levels<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"10_Components_and_Design_Systems\"><\/span><strong>10. Components and Design Systems<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Reusable components multiply accessibility, for better or worse.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Build accessibility into components:<\/strong> states, focus styles, labels and keyboard behavior.<\/li>\n\n\n\n<li><strong>Document usage:<\/strong> include guidance on contrast, content and behavior.<\/li>\n\n\n\n<li><strong>Test components in isolation and in context.<\/strong><\/li>\n\n\n\n<li><strong>Avoid copying inaccessible patterns:<\/strong> review carousels, modals, tooltips, accordions and custom dropdowns carefully.<\/li>\n\n\n\n<li><strong>Maintain a pattern library:<\/strong> so fixes propagate everywhere.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"11_Testing_Methods\"><\/span><strong>11. Testing Methods<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No single test finds every problem, so combine methods.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Method<\/th><th>What it finds<\/th><th>Notes<\/th><\/tr><\/thead><tbody><tr><td>Automated scanners<\/td><td>Common technical issues such as missing alt text and low contrast<\/td><td>Catch only part of the problems<\/td><\/tr><tr><td>Keyboard-only testing<\/td><td>Focus order, traps and unreachable controls<\/td><td>Quick and highly valuable<\/td><\/tr><tr><td>Screen reader testing<\/td><td>Naming, structure and announcement issues<\/td><td>Test with at least one common screen reader<\/td><\/tr><tr><td>Zoom and text scaling<\/td><td>Layout and reflow problems<\/td><td>Test at high zoom levels and with larger text settings<\/td><\/tr><tr><td>Color and contrast checks<\/td><td>Visibility issues<\/td><td>Include checks for color blindness simulation<\/td><\/tr><tr><td>Manual expert review<\/td><td>Nuanced issues across WCAG criteria<\/td><td>Useful before launch and after major changes<\/td><\/tr><tr><td>Usability testing with people with disabilities<\/td><td>Real-world barriers<\/td><td>The most valuable source of insight<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">A structured <strong><a href=\"https:\/\/www.originux.com\/services\/ux-audit\">UX audit<\/a><\/strong> can combine expert review with usability findings to identify accessibility and usability issues across the whole experience before launch.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"12_Documentation_and_Accessibility_Statement\"><\/span><strong>12. Documentation and Accessibility Statement<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Accessibility statement:<\/strong> describe your commitment, known limitations and contact methods.<\/li>\n\n\n\n<li><strong>Feedback channel:<\/strong> make it easy for users to report problems.<\/li>\n\n\n\n<li><strong>Response process:<\/strong> know who handles reports and how quickly.<\/li>\n\n\n\n<li><strong>Internal guidelines:<\/strong> document standards for designers, developers and content writers.<\/li>\n\n\n\n<li><strong>Training:<\/strong> help teams understand accessibility basics.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Common_Accessibility_Mistakes\"><\/span><strong>Common Accessibility Mistakes<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Mistake<\/th><th>Why it hurts<\/th><th>Better approach<\/th><\/tr><\/thead><tbody><tr><td>Relying only on automated tools<\/td><td>Misses many issues<\/td><td>Combine automated, manual and user testing<\/td><\/tr><tr><td>Low-contrast text for style<\/td><td>Hard to read for many users<\/td><td>Check contrast during design<\/td><\/tr><tr><td>Removing focus outlines<\/td><td>Keyboard users get lost<\/td><td>Provide clear, visible focus styles<\/td><\/tr><tr><td>Missing or poor alt text<\/td><td>Screen reader users miss content<\/td><td>Write purposeful descriptions<\/td><\/tr><tr><td>Placeholder-only form labels<\/td><td>Labels vanish when typing<\/td><td>Use visible, persistent labels<\/td><\/tr><tr><td>Inaccessible custom components<\/td><td>Block keyboard and screen reader users<\/td><td>Use native elements or follow established patterns<\/td><\/tr><tr><td>Autoplay media and motion<\/td><td>Distracting and sometimes harmful<\/td><td>Provide controls and respect user preferences<\/td><\/tr><tr><td>Treating accessibility as a final step<\/td><td>Costly late fixes<\/td><td>Build it into design and development<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Prioritizing_Fixes_Before_Launch\"><\/span><strong>Prioritizing Fixes Before Launch<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Priority<\/th><th>Examples<\/th><th>Action<\/th><\/tr><\/thead><tbody><tr><td>Critical<\/td><td>Keyboard traps, inaccessible checkout or sign-in, missing form labels<\/td><td>Fix before launch<\/td><\/tr><tr><td>High<\/td><td>Low contrast on key content, missing alt text on important images, no captions<\/td><td>Fix before or immediately after launch<\/td><\/tr><tr><td>Medium<\/td><td>Inconsistent headings, unclear link text<\/td><td>Schedule soon after launch<\/td><\/tr><tr><td>Low<\/td><td>Minor wording or structure improvements<\/td><td>Add to the backlog<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">A collaborative <strong><a href=\"https:\/\/www.originux.com\/design-thinking-workshops\">design thinking workshop<\/a><\/strong> can help teams align on accessibility priorities and build shared responsibility across design, development and content.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Learning_from_Real_Users\"><\/span><strong>Learning from Real Users<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Checklists catch known issues, but real people reveal surprises. <strong><a href=\"https:\/\/www.originux.com\/services\/ux-research\">UX research<\/a><\/strong> that includes participants with diverse abilities shows how people actually use your product, which guides better fixes than guesswork.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Final_Pre-Launch_Accessibility_Checklist\"><\/span><strong>Final Pre-Launch Accessibility Checklist<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Does text and key UI meet contrast requirements?<\/li>\n\n\n\n<li>Is color never the only way to convey meaning?<\/li>\n\n\n\n<li>Can every function be used with a keyboard, with visible focus?<\/li>\n\n\n\n<li>Are headings, landmarks and links meaningful for screen reader users?<\/li>\n\n\n\n<li>Do all images, icons and graphics have appropriate text alternatives?<\/li>\n\n\n\n<li>Are forms labeled, with clear instructions and helpful errors?<\/li>\n\n\n\n<li>Do videos have captions, transcripts and, where needed, audio descriptions?<\/li>\n\n\n\n<li>Is motion controllable and respectful of user preferences?<\/li>\n\n\n\n<li>Does the experience work on mobile with touch, zoom and screen readers?<\/li>\n\n\n\n<li>Are components documented and tested for accessibility?<\/li>\n\n\n\n<li>Have you tested with automated tools, manual checks and real users?<\/li>\n\n\n\n<li>Do you have an accessibility statement and a way for users to report issues?<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Getting_Started\"><\/span><strong>Getting Started<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">You do not need to fix everything at once. Run keyboard and screen reader checks on your most important journeys, fix critical issues first and build accessibility into your design and development process going forward. If you want expert help reviewing your product and turning research into inclusive, polished experiences, a specialist team offering <strong><a href=\"https:\/\/www.originux.com\/services\/ui-ux-design-services\">UI\/UX design services<\/a><\/strong> can help you move faster with less risk.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Final_Thoughts\"><\/span><strong>Final Thoughts<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Accessibility is not a final polish step. It is part of building products that work for the people who use them. Review visual design, keyboard access, structure, forms, media, mobile experience and content, test with a mix of tools and real people, and keep improving after launch. Teams that treat accessibility as a continuous practice build products that are more usable, more trusted and open to more people.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"FAQs\"><\/span><strong>FAQs<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_should_an_accessibility_checklist_include\"><\/span><strong>What should an accessibility checklist include?<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">It should cover visual design and contrast, keyboard access, screen reader support, semantic structure, images and alt text, forms, media captions, motion, mobile use, content clarity and testing with real users.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Which_accessibility_standard_should_I_follow\"><\/span><strong>Which accessibility standard should I follow?<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Most teams follow WCAG, often targeting Level AA. Legal requirements vary by region and industry, so confirm what applies to you with qualified specialists.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Can_automated_tools_test_accessibility_completely\"><\/span><strong>Can automated tools test accessibility completely?<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">No. Automated tools catch only a portion of issues, so combine them with manual checks, keyboard and screen reader testing and feedback from people with disabilities.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"When_should_I_start_thinking_about_accessibility\"><\/span><strong>When should I start thinking about accessibility?<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">At the very beginning, during research and design. Building accessibility in from the start is far cheaper and more effective than fixing issues after launch.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A team is ready to launch a new website. The design is sleek, the animations are smooth and the copy is sharp. Then a user who navigates with a keyboard tries to reach the main menu and gets stuck in a carousel. Another user with low vision cannot read the light gray text on a&hellip; <a class=\"more-link\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/\">Continue reading <span class=\"screen-reader-text\">Accessibility Checklist: What to Review Before You Launch<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-7612","post","type-post","status-publish","format-standard","hentry","category-blog","entry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Accessibility Checklist: What to Review Before You Launch<\/title>\n<meta name=\"description\" content=\"Use this website accessibility checklist to review contrast, keyboard use, screen readers, forms, media, mobile, content and testing before launch, with WCAG tips, tables and common mistakes.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Accessibility Checklist: What to Review Before You Launch\" \/>\n<meta property=\"og:description\" content=\"Use this website accessibility checklist to review contrast, keyboard use, screen readers, forms, media, mobile, content and testing before launch, with WCAG tips, tables and common mistakes.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/\" \/>\n<meta property=\"og:site_name\" content=\"OriginUX Studio\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-13T04:15:39+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-13T04:15:42+00:00\" \/>\n<meta name=\"author\" content=\"master.origin\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"master.origin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"10 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/\"},\"author\":{\"name\":\"master.origin\",\"@id\":\"https:\/\/www.originux.com\/resources\/#\/schema\/person\/735b211d8a21c6181bb758144923ef3c\"},\"headline\":\"Accessibility Checklist: What to Review Before You Launch\",\"datePublished\":\"2026-11-13T04:15:39+00:00\",\"dateModified\":\"2026-11-13T04:15:42+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/\"},\"wordCount\":2134,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/www.originux.com\/resources\/#organization\"},\"articleSection\":[\"Blog\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/\",\"url\":\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/\",\"name\":\"Accessibility Checklist: What to Review Before You Launch\",\"isPartOf\":{\"@id\":\"https:\/\/www.originux.com\/resources\/#website\"},\"datePublished\":\"2026-11-13T04:15:39+00:00\",\"dateModified\":\"2026-11-13T04:15:42+00:00\",\"description\":\"Use this website accessibility checklist to review contrast, keyboard use, screen readers, forms, media, mobile, content and testing before launch, with WCAG tips, tables and common mistakes.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.originux.com\/resources\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Accessibility Checklist: What to Review Before You Launch\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.originux.com\/resources\/#website\",\"url\":\"https:\/\/www.originux.com\/resources\/\",\"name\":\"OriginUX Studio\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/www.originux.com\/resources\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.originux.com\/resources\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.originux.com\/resources\/#organization\",\"name\":\"OriginUX Studio\",\"url\":\"https:\/\/www.originux.com\/resources\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.originux.com\/resources\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.originux.com\/resources\/wp-content\/uploads\/2022\/05\/origin-logo.png\",\"contentUrl\":\"https:\/\/www.originux.com\/resources\/wp-content\/uploads\/2022\/05\/origin-logo.png\",\"width\":120,\"height\":120,\"caption\":\"OriginUX Studio\"},\"image\":{\"@id\":\"https:\/\/www.originux.com\/resources\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.originux.com\/resources\/#\/schema\/person\/735b211d8a21c6181bb758144923ef3c\",\"name\":\"master.origin\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/356acc98edd1351e180a192318e3335999f553b20c01c8a00391239e394d4727?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/356acc98edd1351e180a192318e3335999f553b20c01c8a00391239e394d4727?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/356acc98edd1351e180a192318e3335999f553b20c01c8a00391239e394d4727?s=96&d=mm&r=g\",\"caption\":\"master.origin\"},\"sameAs\":[\"https:\/\/www.originux.com\"],\"url\":\"https:\/\/www.originux.com\/resources\/author\/master-origin\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Accessibility Checklist: What to Review Before You Launch","description":"Use this website accessibility checklist to review contrast, keyboard use, screen readers, forms, media, mobile, content and testing before launch, with WCAG tips, tables and common mistakes.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/","og_locale":"en_US","og_type":"article","og_title":"Accessibility Checklist: What to Review Before You Launch","og_description":"Use this website accessibility checklist to review contrast, keyboard use, screen readers, forms, media, mobile, content and testing before launch, with WCAG tips, tables and common mistakes.","og_url":"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/","og_site_name":"OriginUX Studio","article_published_time":"2026-11-13T04:15:39+00:00","article_modified_time":"2026-11-13T04:15:42+00:00","author":"master.origin","twitter_card":"summary_large_image","twitter_misc":{"Written by":"master.origin","Est. reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#article","isPartOf":{"@id":"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/"},"author":{"name":"master.origin","@id":"https:\/\/www.originux.com\/resources\/#\/schema\/person\/735b211d8a21c6181bb758144923ef3c"},"headline":"Accessibility Checklist: What to Review Before You Launch","datePublished":"2026-11-13T04:15:39+00:00","dateModified":"2026-11-13T04:15:42+00:00","mainEntityOfPage":{"@id":"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/"},"wordCount":2134,"commentCount":0,"publisher":{"@id":"https:\/\/www.originux.com\/resources\/#organization"},"articleSection":["Blog"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/","url":"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/","name":"Accessibility Checklist: What to Review Before You Launch","isPartOf":{"@id":"https:\/\/www.originux.com\/resources\/#website"},"datePublished":"2026-11-13T04:15:39+00:00","dateModified":"2026-11-13T04:15:42+00:00","description":"Use this website accessibility checklist to review contrast, keyboard use, screen readers, forms, media, mobile, content and testing before launch, with WCAG tips, tables and common mistakes.","breadcrumb":{"@id":"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.originux.com\/resources\/blog\/accessibility-checklist-what-to-review-before-you-launch\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.originux.com\/resources\/"},{"@type":"ListItem","position":2,"name":"Accessibility Checklist: What to Review Before You Launch"}]},{"@type":"WebSite","@id":"https:\/\/www.originux.com\/resources\/#website","url":"https:\/\/www.originux.com\/resources\/","name":"OriginUX Studio","description":"","publisher":{"@id":"https:\/\/www.originux.com\/resources\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.originux.com\/resources\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.originux.com\/resources\/#organization","name":"OriginUX Studio","url":"https:\/\/www.originux.com\/resources\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.originux.com\/resources\/#\/schema\/logo\/image\/","url":"https:\/\/www.originux.com\/resources\/wp-content\/uploads\/2022\/05\/origin-logo.png","contentUrl":"https:\/\/www.originux.com\/resources\/wp-content\/uploads\/2022\/05\/origin-logo.png","width":120,"height":120,"caption":"OriginUX Studio"},"image":{"@id":"https:\/\/www.originux.com\/resources\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.originux.com\/resources\/#\/schema\/person\/735b211d8a21c6181bb758144923ef3c","name":"master.origin","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/356acc98edd1351e180a192318e3335999f553b20c01c8a00391239e394d4727?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/356acc98edd1351e180a192318e3335999f553b20c01c8a00391239e394d4727?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/356acc98edd1351e180a192318e3335999f553b20c01c8a00391239e394d4727?s=96&d=mm&r=g","caption":"master.origin"},"sameAs":["https:\/\/www.originux.com"],"url":"https:\/\/www.originux.com\/resources\/author\/master-origin\/"}]}},"_links":{"self":[{"href":"https:\/\/www.originux.com\/resources\/wp-json\/wp\/v2\/posts\/7612","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.originux.com\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.originux.com\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.originux.com\/resources\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.originux.com\/resources\/wp-json\/wp\/v2\/comments?post=7612"}],"version-history":[{"count":1,"href":"https:\/\/www.originux.com\/resources\/wp-json\/wp\/v2\/posts\/7612\/revisions"}],"predecessor-version":[{"id":7613,"href":"https:\/\/www.originux.com\/resources\/wp-json\/wp\/v2\/posts\/7612\/revisions\/7613"}],"wp:attachment":[{"href":"https:\/\/www.originux.com\/resources\/wp-json\/wp\/v2\/media?parent=7612"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.originux.com\/resources\/wp-json\/wp\/v2\/categories?post=7612"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.originux.com\/resources\/wp-json\/wp\/v2\/tags?post=7612"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}