CINXE.COM

<!DOCTYPE html> <html class="no-js" lang="en" dir="ltr" prefix="og: http://ogp.me/ns#"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <script> document.documentElement.className = document.documentElement.className.replace('no-js', 'has-js'); function downloadJSAtOnload() { var element = document.createElement("script"); element.src = "/WAI/assets/scripts/main.js?1732807903713432608"; document.body.appendChild(element); } window.addEventListener("load", downloadJSAtOnload, false); </script> <link rel="stylesheet" href="/WAI/assets/css/style.css?1732807903713432608"> <title> Developing Organizational Policies on Web Accessibility | Web Accessibility Initiative (WAI) | W3C</title> <meta name="generator" content="Jekyll v4.3.3" /> <meta property="og:title" content="Developing Organizational Policies on Web Accessibility" /> <meta name="author" content="W3C Web Accessibility Initiative (WAI)" /> <meta property="og:locale" content="en" /> <meta name="description" content="Accessibility resources free online from the international standards organization: W3C Web Accessibility Initiative (WAI)." /> <meta property="og:description" content="Accessibility resources free online from the international standards organization: W3C Web Accessibility Initiative (WAI)." /> <link rel="canonical" href="https://www.w3.org/WAI/planning/org-policies/" /> <meta property="og:url" content="https://www.w3.org/WAI/planning/org-policies/" /> <meta property="og:site_name" content="Web Accessibility Initiative (WAI)" /> <meta property="og:type" content="website" /> <meta name="twitter:card" content="summary_large_image" /> <meta property="twitter:title" content="Developing Organizational Policies on Web Accessibility" /> <meta name="twitter:site" content="@w3c_wai" /> <meta name="twitter:creator" content="@W3C Web Accessibility Initiative (WAI)" /> <script type="application/ld+json"> {"@context":"https://schema.org","@type":"WebPage","author":{"@type":"Person","name":"W3C Web Accessibility Initiative (WAI)"},"description":"Accessibility resources free online from the international standards organization: W3C Web Accessibility Initiative (WAI).","headline":"Developing Organizational Policies on Web Accessibility","url":"https://www.w3.org/WAI/planning/org-policies/"}</script>  <meta name="twitter:image" property="og:image" content="https://www.w3.org/WAI/assets/images/social-sharing-default.jpg"> <link rel="alternate" type="application/rss+xml" href="/WAI/feed.xml"> </head> <body id="top" class="page-developing-organizational-policies-on-web-accessibility "> <nav aria-label="Skip Link and Language Selector" id="controls" class="default-grid"> <ul> <li><a href="#main">Skip to Content</a></li> <li class="opt"> <a href="/WAI/meta/customize/">Change Text Size or Colors</a> </li> <li class="opt"> <a href="/WAI/translations/">All Translations <svg focusable="false" aria-hidden="true" class="icon-translations "><use xlink:href="/WAI/assets/images/icons.svg#icon-translations"></use></svg></a> </li> </ul></nav> <header id="site-header" class="default-grid with-gap"> <div class="logos"> <a lang="en" class="home w3c" href="https://www.w3.org/"> <svg role="img" aria-label="W3C" viewBox="0 0 68 34" xmlns="http://www.w3.org/2000/svg"><g><path d="m16.117 1.006 5.759 19.58 5.759-19.58h4.17 11.444v1.946l-5.879 10.128c2.065.663 3.627 1.868 4.686 3.615 1.059 1.748 1.589 3.799 1.589 6.155 0 2.914-.775 5.363-2.324 7.348s-3.555 2.978-6.017 2.978c-1.854 0-3.469-.589-4.845-1.767-1.377-1.178-2.396-2.773-3.058-4.786l3.256-1.35c.477 1.218 1.106 2.178 1.887 2.879.781.702 1.701 1.052 2.76 1.052 1.112 0 2.052-.622 2.82-1.866.768-1.245 1.152-2.74 1.152-4.489 0-1.933-.411-3.429-1.231-4.488-.954-1.244-2.45-1.867-4.489-1.867h-1.588v-1.906l5.56-9.612h-6.712l-.382.65-8.163 27.548h-.397l-5.958-19.937-5.957 19.937h-.397l-9.53-32.168h4.17l5.759 19.58 3.892-13.185-1.906-6.395z"/><path d="m64.92 1.006c-.819 0-1.554.295-2.111.861-.591.6-.92 1.376-.92 2.178s.313 1.545.887 2.128c.583.591 1.334.912 2.145.912.793 0 1.562-.321 2.161-.903.574-.557.887-1.3.887-2.136 0-.811-.321-1.57-.878-2.136-.584-.592-1.344-.904-2.171-.904zm2.643 3.065c0 .701-.271 1.351-.768 1.832-.524.507-1.174.777-1.892.777-.675 0-1.342-.278-1.84-.785s-.777-1.157-.777-1.849.287-1.368.802-1.891c.481-.49 1.131-.751 1.84-.751.726 0 1.376.271 1.883.785.49.489.752 1.147.752 1.882zm-2.559-1.807h-1.3v3.445h.65v-1.469h.642l.701 1.469h.726l-.769-1.57c.498-.102.785-.439.785-.929 0-.625-.472-.946-1.435-.946zm-.118.422c.608 0 .886.169.886.591 0 .405-.278.549-.87.549h-.549v-1.14z"/><path d="m59.807.825.676 4.107-2.391 4.575s-.918-1.941-2.443-3.015c-1.285-.905-2.122-1.102-3.431-.832-1.681.347-3.587 2.357-4.419 4.835-.995 2.965-1.005 4.4-1.04 5.718-.056 2.113.277 3.362.277 3.362s-1.452-2.686-1.438-6.62c.009-2.808.451-5.354 1.75-7.867 1.143-2.209 2.842-3.535 4.35-3.691 1.559-.161 2.791.59 3.743 1.403 1 .854 2.01 2.721 2.01 2.721z"/><path d="m60.102 24.063s-1.057 1.889-1.715 2.617c-.659.728-1.837 2.01-3.292 2.651s-2.218.762-3.656.624c-1.437-.138-2.772-.97-3.24-1.317s-1.664-1.369-2.34-2.322-1.733-2.859-1.733-2.859.589 1.91.958 2.721c.212.467.864 1.894 1.789 3.136.863 1.159 2.539 3.154 5.086 3.604 2.547.451 4.297-.693 4.73-.97s1.346-1.042 1.924-1.66c.603-.645 1.174-1.468 1.49-1.962.231-.36.607-1.092.607-1.092z"/></g></svg> </a> <a lang="en" class="home" href="/WAI/"> <span class="wai"><span class="wa">Web Accessibility</span> <span class="i"><span class="initieative">Initiative</span> <span>WAI</span></span></span> </a> <div class="claim"> <span>Strategies, standards, resources to make the Web accessible to people with disabilities</span> </div> <button class="button button-menu" aria-haspopup="true" aria-expanded="false" id="openmenu"><span><svg focusable="false" aria-hidden="true" class="icon-menu "><use xlink:href="/WAI/assets/images/icons.svg#icon-menu"></use></svg> Menu</span></button> </div> <div class="navigations"> <nav class="metanav" aria-label="Meta & Search" lang="en"> <ul> <li><a href="/WAI/about/participating/">Get Involved</a></li> <li><a href="/WAI/about/">About W3C WAI</a></li> <li> <form action="/WAI/search/" role="search"> <div> <label for="header-search"> <span class="visuallyhidden">Search:</span> <input id="header-search" type="search" name="q" placeholder="Search" aria-label="Search"> </label> <button class="button button-icon button-nobg button-noborder"><span><svg focusable="false" aria-label="Submit Search" class="icon-search "><use xlink:href="/WAI/assets/images/icons.svg#icon-search"></use></svg></span></button> </div> </form> </li> </ul> </nav> </div> </header><nav class="mainnav" aria-label="Main" lang="en"><ul><li><a lang="en" href="/WAI/fundamentals/"><span>Accessibility Fundamentals</span></a></li><li><a lang="en" href="/WAI/planning/"><span>Planning & Policies</span></a></li><li><a lang="en" href="/WAI/design-develop/"><span>Design & Develop</span></a></li><li><a lang="en" href="/WAI/test-evaluate/"><span>Test & Evaluate</span></a></li><li><a lang="en" href="/WAI/teach-advocate/"><span>Teach & Advocate</span></a></li><li><a lang="en" href="/WAI/standards-guidelines/"><span>Standards/<wbr>Guidelines</span></a></li></ul></nav><nav class="default-grid breadcrumb" aria-label="Breadcrumb" lang="en"> <ul style="align-self: center;"> <li><a href="/WAI/" lang="en">Home</a></li><li><a lang="en" href="/WAI/planning/"><span>Planning & Policies</span></a></li><li><a lang="en" href="/WAI/planning/org-policies/" aria-current="page"><span>Developing an Organizational Policy</span></a></li></ul> </nav> <div class="default-grid with-gap leftcol"> <div class="sidenav"><nav class="sn-contents" aria-label="Secondary"> <ul class="sidenav--list"> <li> <a lang="en" href="/WAI/planning/" class="page-link"><span>Planning & Policies</span></a></li><li> <a lang="en" href="/WAI/planning/interim-repairs/" class="page-link"><span>Approaches for Interim Repairs</span></a></li><li> <a lang="en" href="/WAI/planning-and-managing/" class="page-link"><span>Planning and Managing Accessibility</span></a><ul><li> <a lang="en" href="/WAI/planning-and-managing/initiate/" class="page-link"><span>Initiate</span></a></li><li> <a lang="en" href="/WAI/planning-and-managing/plan/" class="page-link"><span>Plan</span></a></li><li> <a lang="en" href="/WAI/planning-and-managing/implement/" class="page-link"><span>Implement</span></a></li><li> <a lang="en" href="/WAI/planning-and-managing/sustain/" class="page-link"><span>Sustain</span></a></li><li> <a lang="en" href="/WAI/tools-list/authoring/" class="page-link"><span>Authoring Tools List</span></a></li></ul></li><li> <a lang="en" href="/WAI/planning/org-policies/" aria-current="page" class="page-link"><span>Developing an Organizational Policy</span></a><ul><li> <a lang="en" href="/WAI/planning/org-policies/example/" class="page-link"><span>Example</span></a></li></ul></li><li> <a lang="en" href="/WAI/planning/statements/" class="page-link"><span>Developing an Accessibility Statement</span></a><ul><li> <a lang="en" href="/WAI/planning/statements/generator/" class="page-link"><span>Generator Tool</span></a></li><li> <a lang="en" href="/WAI/planning/statements/minimal-example/" class="page-link"><span>Minimal Example</span></a></li><li> <a lang="en" href="/WAI/planning/statements/complete-example/" class="page-link"><span>Complete Example</span></a></li></ul></li><li> <a lang="en" href="/WAI/planning/involving-users/" class="page-link"><span>Involving Users for Better Accessibility</span></a></li><li> <a lang="en" href="/WAI/policies/" class="page-link"><span>International Laws & Policies</span></a></li></ul></nav> </div> <main id="main" lang="en"> <header> <h1> Developing Organizational Policies on Web Accessibility </h1></header> <aside class="box box-full"><header class="box-h box-h-full"> <h2> Summary </h2></header><div class="box-i"> <p>This page helps you develop a policy for creating, managing, and delivering accessible websites.</p> <p>To learn about how such policies form part of a broader approach to implementing accessibility, see <a href="/WAI/planning-and-managing/">Planning and Managing Web Accessibility</a>.</p> </div></aside> <nav class="box box-simple box-simple box-full" aria-labelledby="tocheading" id="toc"> <header id="tocheading" class="box-h box-h-simple box-h-simple box-h-full"> Page Contents</header> <div class="box-i"> <ul id="markdown-toc"> <li><a href="#reference" id="markdown-toc-reference">Reference standards</a></li> <li><a href="#conformance" id="markdown-toc-conformance">Define conformance levels</a></li> <li><a href="#scope" id="markdown-toc-scope">Define scope of policy</a></li> <li><a href="#milestones" id="markdown-toc-milestones">Set conformance milestones</a></li> <li><a href="#thirdparty" id="markdown-toc-thirdparty">Consider third-party content</a></li> <li><a href="#monitor" id="markdown-toc-monitor">Define monitoring and review process</a></li> <li><a href="#examples" id="markdown-toc-examples">Example policies</a></li> <li><a href="#template" id="markdown-toc-template">Policy template</a></li> <li><a href="#maintain" id="markdown-toc-maintain">Next steps: Maintaining your policy</a></li> <li><a href="#strategic" id="markdown-toc-strategic">Longer term: Strategic planning</a></li> </ul> </div> </nav> <h3 id="about">Designing a policy</h3> <p>Your web accessibility policy may be standalone or integrated into other policies. The accessibility policy could be part of a non-discrimination or equal opportunity policy. Other related documents should also mention web accessibility. For example, brand guidelines, coding standards, and project management frameworks. This helps considering accessibility as a core feature, rather than an afterthought.</p> <p>Your organizational policy may not be suitable for the public if it is an internal document. Consider providing a public accessibility statement that reflects your policy, goals, and achievements. This will communicate your efforts towards improving accessibility.</p> <aside class="box box-example"><header class="box-h box-h-example"> Example of simple policy</header><div class="box-i"> <p>ACME Inc. is committed to ensuring that its website is accessible to people with disabilities. All the pages on our website will meet W3C WAI鈥檚 <a href="/TR/WCAG/">Web Content Accessibility Guidelines</a> 2.1, Level AA conformance. Report any issues to <a href="mailto:accessibility@acme.inc">accessibility@acme.inc</a>.</p> </div></aside> <h2 id="reference">Reference standards</h2> <p>Reference specific standards in policy documents to ensure clear criteria for accessibility. The W3C Web Accessibility Initiative (WAI) provides a set of accessibility standards that are commonly recognized by governments and organizations from around the world. These include:</p> <ul> <li><strong>Web Content Accessibility Guidelines (WCAG)</strong> applies to all web content and applications. This includes content on mobile, television, and other delivery channels. The <a href="/WAI/standards-guidelines/wcag/">WCAG Overview</a> provides more background.</li> <li><strong>Authoring Tool Accessibility Guidelines (ATAG)</strong> applies to websites that provide users the opportunity to generate content. For example, adding comments, posting to forums, or uploading images or videos. ATAG is also relevant if your organization provides tools, such as CMS鈥檚, for staff or customers to manage websites and content. The <a href="/WAI/standards-guidelines/atag/">ATAG Overview</a> provides more background.</li> <li><strong>User Agent Accessibility Guidelines (UAAG)</strong> applies when additional plugins are provided to deliver additional content. Media players are a good example of this. UAAG also applies when custom controls are used to provide non-standard functionality. UAAG may also be relevant where mobile applications deliver web content as part of the application. It may also be relevant to the procurement process if your organization provides browsers for staff. The <a href="/WAI/standards-guidelines/uaag/">UAAG Overview</a> provides more background.</li> </ul> <h3 id="referencing-approaches">Referencing Approaches</h3> <p>As technologies and standards continually evolve, it is important to keep policies current. The text of policies that include accessibility requirements tend to quickly become outdated. This introduces gaps between current accessibility standards and older policies. Ideally, a policy would reference the W3C/WAI standards. It should also define a mechanism to transition to newer versions of the standards when they become available.</p> <p><a href="/WAI/standards-guidelines/linking/#trs">Referencing Guidelines and Other Technical Specifications</a> Explains options relating to referencing.</p> <h2 id="conformance">Define conformance levels</h2> <p>W3C WAI guidelines provide three levels of conformance: A, AA, and AAA. The generally accepted level of conformance in many countries is Level AA. It is critical for the success of your policy to select a conformance level you can realistically achieve. Once selected, specify what level of conformance is to be achieved for each referenced standard.</p> <h3 id="ex1">Examples</h3> <aside class="box box-example"><header class="box-h box-h-example"> Simple example of referencing WCAG</header><div class="box-i"> <p>ACME Inc. seeks to make sure our website conforms to W3C WAI <a href="/TR/WCAG20/">WCAG</a> 2.1 Level AA.</p> </div></aside> <aside class="box box-example"><header class="box-h box-h-example"> Example of reference to WCAG and ATAG</header><div class="box-i"> <p>At ACME Inc. we seek to ensure all of our websites and web applications, conform to all Level AA success criteria of W3C WAI <a href="/TR/WCAG21/">WCAG 2.1</a>. This applies to both customer-facing and for internal use. We also aim to ensure that our authoring tools conform to all Level AA criteria of <a href="/TR/ATAG/">ATAG</a>.</p> </div></aside> <h2 id="scope">Define scope of policy</h2> <p>Clearly state the scope of your policy, and how it applies to different parts of the websites in scope. This includes third-party, legacy, and mobile content. It also applies to applications provided as part of these websites. Your policy may apply to websites internal to the organization, such as intranets, and to websites for external audiences. It also includes the tools used to create and to access your website.</p> <p>Note that broader policies may impact your scope considerations. For example, public websites and services could be different from access to the workplace.</p> <h3 id="ex2">Examples</h3> <aside class="box box-example"><header class="box-h box-h-example"> Simple example of content scope</header><div class="box-i"> <p>This policy applies to all new, updated, and existing web content on http://www.acme.inc/ and all content provided internally at http://intranet.acme.inc/.</p> </div></aside> <h2 id="milestones">Set conformance milestones</h2> <p>For all items in scope of your policy, define clear and measureable milestones, including dates, by which each will be met. If the policy is already achieved, then say when the content was last reviewed. Deadlines should be realistic but issues should not be left too long.</p> <p>In some cases, a phased approach might be appropriate. First, quickly fix significant accessibility barriers. Then implement fixes for other issues. You could do this as part of a planned maintenance update. Clearly outline any details of this type of approach in your policy.</p> <h3 id="ex3">Examples</h3> <aside class="box box-example"><header class="box-h box-h-example"> Simple example of conformance milestone</header><div class="box-i"> <p>By February 1, 20XX, ACME Inc鈥檚 web content will meet WCAG 2.1, Level AA conformance.</p> </div></aside> <aside class="box box-example"><header class="box-h box-h-example"> Example of staged conformance milestones</header><div class="box-i"> <p>By November 1, 20XX, ACME Inc鈥檚 websites will meet WCAG 2.1, Level A conformance. By May 1, 20XX web content will meet WCAG 2.1, Level AA conformance.</p> </div></aside> <aside class="box box-example"><header class="box-h box-h-example"> Example of supplier milestone</header><div class="box-i"> <p>By June 1, 20XX, all vendors of content management systems (CMS) used by ACME Inc鈥檚 should provide information regarding their plans for ATAG 2.0 conformance in future versions of their software. By June 1, 20XX ACME Inc. will preferentially purchase ATAG conformant authoring tools.</p> </div></aside> <h2 id="thirdparty">Consider third-party content</h2> <p>Your accessibility policy needs to consider procured or syndicated third-party content. This is particularly relevant for third-party content that provides essential parts of a website. For example, this could include credit card payment services, video streaming channels, or online mapping services.</p> <p>Site owners are responsible for ensuring accessibility or for providing accessible alternatives. This is true even if site owners don鈥檛 have full control over such content and services. For example, social media feeds may need to be monitored or moderated to ensure accessibility. See the WCAG 2.1 conformance requirement for <a href="/TR/WCAG21/#cc3">complete processes</a> and the concept of <a href="/TR/WCAG21/#conforming-alternate-versiondef">conforming alternate version</a> for more background.</p> <h3 id="ex4">Examples</h3> <aside class="box box-example"><header class="box-h box-h-example"> Example including third-party content scope</header><div class="box-i"> <p>This policy applies to all web content produced or updated by ACME Inc. ACME Inc. will also ensure third-party content providers are aware of our web accessibility policy. ACME Inc. will also favor providers based on their accessibility conformance claims.</p> </div></aside> <h2 id="monitor">Define monitoring and review process</h2> <p>Regularly review progress towards policy goals. Update the policy when there are changes to the timescale or when you meet milestones</p> <p>To maintain the target level of accessibility, specify a process and schedule to review content and tools in scope.</p> <p>Feedback from users who might find accessibility barriers can help you identify issues. Your policy should include information on how you will gather feedback. It should also include information on how your organization will handle and respond to feedback.</p> <h3 id="ex5">Examples</h3> <aside class="box box-example"><header class="box-h box-h-example"> Example simple review policy</header><div class="box-i"> <p>ACME Inc. will review all area of the website every year. We will use the process described at <a href="/TR/WCAG-EM/">Website Accessibility Conformance Evaluation Methodology</a>. Reviews are the responsibility of the ICT department. Accessibility checks will be incorporated into the publishing workflow for all new content.</p> </div></aside> <aside class="box box-example"><header class="box-h box-h-example"> Example of feedback policy</header><div class="box-i"> <p>Each page of the website will include a link to a form allowing users to submit feedback on the site. We will compile and consider this information during the review process. We will respond to any feedback within 48 hours of submission.</p> </div></aside> <h2 id="examples">Example policies</h2> <aside class="box box-example"><header class="box-h box-h-example"> Example of simple policy</header><div class="box-i"> <p>ACME Inc. is committed to ensuring the accessibility of its web content to people with disabilities. All of the content on our website will meet W3C WAI鈥檚 <a href="/TR/WCAG/">Web Content Accessibility Guidelines</a> 2.1, Level AA conformance. Report any issues should to <a href="mailto:accessibility@acme.inc">accessibility@acme.inc</a>.</p> </div></aside> <h3 id="comprehensive-policies">Comprehensive policies</h3> <p>More comprehensive policies may capture broader information. For example, how to implement the policy, or who or what departments are responsible, specific exclusions.</p> <p>An <a href="/WAI/planning/org-policies/example/">example comprehensive policy</a> is provided.</p> <h2 id="template">Policy template</h2> <p>In the template below, the <mark>[hints]</mark> in brackets are sections for you to complete.</p> <aside class="box box-example"><header class="box-h box-h-example"> Example Policy Template</header><div class="box-i"> <p><mark>[Organization name]</mark> is committed to ensuring accessibility of its website and intranet to people with disabilities. New and updated web content produced by our organization will meet <mark>[link to standard]</mark> <mark>[version number]</mark>, <mark>[level of conformance]</mark>, by <mark>[compliance date]</mark>.</p> <p>Existing web content produced by our organization will meet our standard by <mark>[existing content compliance date]</mark>.</p> <p>Content provided for our site by third-party developers will meet <mark>[third-party content standard]</mark> <mark>[version number]</mark> by <mark>[third-party content compliance date]</mark>. This <mark>[does/does not]</mark> include user-generated content.</p> <p>We aim to ensure that our authoring tools and processes meet <mark>[authoring tools standard]</mark> <mark>[version number]</mark> by <mark>[authoring tools compliance date]</mark>. By <mark>[preferential purchasing date]</mark> we will preferentially purchase authoring tools that meet or exceed our web accessibility policy.</p> <p>We will review this policy <mark>[review period]</mark> on or before the <mark>[policy review date]</mark>. This policy was last reviewed on <mark>[last review date]</mark>, by <mark>[reviewer]</mark>.</p> </div></aside> <h2 id="maintain">Next steps: Maintaining your policy</h2> <p>Keep your policy accurate and up to date. Regularly review your policy if it includes milestones. This is also true if it references particular standards by version number. Reviews should check that milestones have been met. It should also check if changes are required due to new or updated standards.</p> <p>You may need to adjust your policy鈥檚 scope if you have new content. You may also need to adjust the scope if you make significant changes to the structure of your website. Changes in authoring tools or processes may also need to be thought about.</p> <h2 id="strategic">Longer term: Strategic planning</h2> <p>An accessibility policy is one part of a broader strategic approach to accessibility. Making accessibility an integral part of your web development strategy is more cost effective and efficient than considering it in isolation. You can do several things to help your organization create more accessible websites as standard.</p> <p><a href="/WAI/planning-and-managing/">Planning and Managing Web Accessibility</a> outlines how to integrate accessibility throughout your web development. When you plan a redesign or updates, include accessibility from the start of the project. Accessibility is cheaper when tackled at the start of a project, rather than at the end. It will also take less time and resources to include accessibility from the get-go.</p> <aside class="box box-icon box-space-above" id="helpimprove" aria-label="feedback"><header class="box-h box-h-icon box-h-space-above box-h-icon"> <svg focusable="false" aria-hidden="true" class="icon-comments "><use xlink:href="/WAI/assets/images/icons.svg#icon-comments"></use></svg> <h2> Help improve this page </h2></header><div class="box-i"><p>Please share your ideas, suggestions, or comments via e-mail to the publicly-archived list <a href="mailto:wai@w3.org?body=%5Binclude%20a%20relevant%20email%20Subject%5D%0A%0A%5Bput%20comment%20here...%5D%0A%0AI%20give%20permission%20to%20share%20this%20to%20a%20publicly-archived%20e-mail%20list.">wai@w3.org</a> or via GitHub.</p> <div class="button-group"> <a href="mailto:wai@w3.org?body=%5Binclude%20a%20relevant%20email%20Subject%5D%0A%0A%5Bput%20comment%20here...%5D%0A%0AI%20give%20permission%20to%20share%20this%20to%20a%20publicly-archived%20e-mail%20list." class="button"><span>E-mail</span></a><a href=" https://github.com/w3c/wai-website/edit/main/pages/planning-policies/org-policies/index.md " class="button"><span>Fork & Edit on GitHub</span></a><a href="https://github.com/w3c/wai-website/issues/new?template=content-issue.yml&wai-resource-id=wai-org-policies&wai-url=https://www.w3.org/WAI/planning/org-policies/" class="button"><span>New GitHub Issue</span></a></div></div></aside> <a class="button button-backtotop" href="#top"><span><svg focusable="false" aria-hidden="true" class="icon-arrow-up "><use xlink:href="/WAI/assets/images/icons.svg#icon-arrow-up"></use></svg> Back to Top</span></a> </main> </div> <footer id="wai-site-footer" class="page-footer default-grid" aria-label="Page"> <div class="inner"><p><strong>Updated:</strong> 5 June 2016.<br /> First published October 2002.</p><p><strong>Editors:</strong> <a href="https://www.w3.org/People/#kevin">Kevin White</a> and <a href="https://www.w3.org/People/shadi/">Shadi Abou-Zahra</a>. Contributors: <a href="https://www.w3.org/People/Brewer/">Judy Brewer</a>, <a href="https://www.w3.org/People/Shawn/">Shawn Lawton Henry</a>, and <a href="https://www.w3.org/WAI/EO/EOWG-members">EOWG Participants</a>.</p> <p>Developed by the Education and Outreach Working Group (<a href="https://www.w3.org/WAI/EO/">EOWG</a>). Updated with support from <a href="https://www.w3.org/WAI/ACT/"><abbr title="Web Accessibility Initiative - Cooperation Framework for Guidance on Advanced Technologies, Evaluation Methodologies, and Research Agenda Setting to Support eAccessibility">WAI-ACT</abbr></a>, a project of the European Commission <abbr title="Information Society Technologies">IST</abbr> Programme.</p> </div> </footer> <footer class="site-footer grid-4q" aria-label="Site"> <div class="q1-start q3-end about"> <div> <p><a class="largelink" href="https://www.w3.org/WAI/" lang="en" dir="auto" translate="no">W3C Web Accessibility Initiative (WAI)</a></p> <p>Strategies, standards, and supporting resources to make the Web accessible to people with disabilities.</p> </div> <div class="social" lang="en" dir="auto" translate="no"> <ul> <li><a href="https://w3c.social/@wai"><svg focusable="false" aria-hidden="true" class="icon-mastodon "><use xlink:href="/WAI/assets/images/icons.svg#icon-mastodon"></use></svg> Mastodon</a></li> <li><a href="https://www.linkedin.com/company/w3c-wai/"><svg focusable="false" aria-hidden="true" class="icon-linkedin "><use xlink:href="/WAI/assets/images/icons.svg#icon-linkedin"></use></svg> LinkedIn</a></li> <li><a href="https://www.w3.org/WAI/feed.xml"><svg focusable="false" aria-hidden="true" class="icon-rss "><use xlink:href="/WAI/assets/images/icons.svg#icon-rss"></use></svg> Feed</a></li> <li><a href="https://www.youtube.com/channel/UCU6ljj3m1fglIPjSjs2DpRA/playlists/"><svg focusable="false" aria-hidden="true" class="icon-youtube "><use xlink:href="/WAI/assets/images/icons.svg#icon-youtube"></use></svg> YouTube</a></li> <li><a href="https://www.w3.org/WAI/news/subscribe/" class="button">Get News in Email</a></li> </ul> </div> <div lang="en" dir="auto" translate="no"> <p>Copyright 漏 2024 World Wide Web Consortium (<a href="https://www.w3.org/">W3C</a><sup>庐</sup>). See <a href="/WAI/about/using-wai-material/">Permission to Use WAI Material</a>.</p> </div> </div> <div lang="en" dir="auto" translate="no" class="q4-start q4-end"> <ul style="margin-bottom:0"> <li><a href="/WAI/about/contacting/">Contact WAI</a></li> <li><a href="/WAI/sitemap/">Site Map</a></li> <li><a href="/WAI/news/">News</a></li> <li><a href="/WAI/sitemap/#archive">Archive</a></li> <li><a href="/WAI/about/accessibility-statement/">Accessibility Statement</a></li> <li><a href="/WAI/translations/"> Translations</a></li> <li><a href="/WAI/roles/">Resources for Roles</a></li> </ul> </div> </footer> <script src="/WAI/assets/scripts/details4everybody.js?1732807903713432608"></script>  <script src="/WAI/assets/scripts/svg4everybody.js?1732807903713432608"></script> <script> svg4everybody(); </script><script> var translationStrings = {}; </script> </body> </html>