Government Code §11546.7 – The requirement that state agency heads certify, every two years, that their agency’s website meets the Web Content Accessibility Guidelines, Version 2.0 or a subsequent version, at Level AA or higher, and the requirements of Sections 11135 and 7405 of the Government Code. Created by AB 434 (Baker, Chapter 780, Statutes of 2017), and sometimes referred to as AB 434.
The Department of Justice’s revised regulations for Titles II and III of the Americans with Disabilities Act of 1990 (ADA) were published in the Federal Register on September 15, 2010. These regulations adopted revised, enforceable accessibility standards called the 2010 ADA Standards for Accessible Design, "2010 Standards." On March 15, 2012, compliance with the 2010 Standards was required for new construction and alterations under Titles II and III. March 15, 2012, is also the compliance date for using the 2010 Standards for program accessibility and barrier removal.
!function(e){function n(t){if(r[t])return r[t].exports;var o=r[t]={i:t,l:!1,exports:{}};return e[t].call(o.exports,o,o.exports,n),o.l=!0,o.exports}var t=window.ansWebpackJsonpFunction;window.ansWebpackJsonpFunction=function(n,r,i){for(var s,u,l=0,a=[];l1)for(var t=1;tp)return!1;if(d>f)return!1;var e=window.require.hasModule("shared/browser")&&window.require("shared/browser");return!e||!e.opera}function u(){var e="";return""==window.Q.subdomainSuffix&&(e+=[window.location.protocol,"//"].join("")),e+="/ajax/log_errors_3RD_PARTY_POST"}function l(){var e=i(h);h=[],0!==e.length&&c(u(),{revision:window.Q.revision,errors:JSON.stringify(e)})}var a=t("./third_party/tracekit.js"),c=t("./shared/basicrpc.js").rpc;a.remoteFetching=!1,a.collectWindowErrors=!0,;var f=10,p=window.Q&&window.Q.errorSamplingRate||1,h=[],d=0,m=o(l,1e3),y=window.console&&!(window.NODE_JS&&window.UNIT_TEST);{try{y&&console.error(e.stack||e),}catch(e){}};var w=function(e,n,t){r({name:n,message:t,source:e,stack:a.computeStackTrace.ofCaller().stack||[]}),y&&console.error(t)};n.logJsError=w.bind(null,"js"),n.logMobileJsError=w.bind(null,"mobile_js")},"./shared/globals.js":function(e,n,t){var r=t("./shared/links.js");(window.Q=window.Q||{}).openUrl=function(e,n){var t=e.href;return r.linkClicked(t,n,e),,!1}},"./shared/links.js":function(e,n){var t=[];n.onLinkClick=function(e){t.push(e)},n.linkClicked=function(e,n,r){for(var o=0;o>>0;if("function"!=typeof e)throw new TypeError;for(arguments.length>1&&(t=n),r=0;r>>0,r=arguments.length>=2?arguments[1]:void 0,o=0;o>>0;if(0===o)return-1;var i=+n||0;if(Math.abs(i)===Infinity&&(i=0),i>=o)return-1;for(t=Math.max(i>=0?i:o-Math.abs(i),0);t>>0;if("function"!=typeof e)throw new TypeError(e+" is not a function");for(arguments.length>1&&(t=n),r=0;r>>0;if("function"!=typeof e)throw new TypeError(e+" is not a function");for(arguments.length>1&&(t=n),r=new Array(s),o=0;o>>0;if("function"!=typeof e)throw new TypeError;for(var r=[],o=arguments.length>=2?arguments[1]:void 0,i=0;i>>0,o=0;if(2==arguments.length)n=arguments[1];else{for(;o=r)throw new TypeError("Reduce of empty array with no initial value");n=t[o++]}for(;o>>0;if(0===o)return-1;for(n=o-1,arguments.length>1&&(n=Number(arguments[1]),n!=n?n=0:0!==n&&n!=1/0&&n!=-1/0&&(n=(n>0||-1)*Math.floor(Math.abs(n)))),t=n>=0?Math.min(n,o-1):o-Math.abs(n);t>=0;t--)if(t in r&&r[t]===e)return t;return-1};t(Array.prototype,"lastIndexOf",c)}if(!Array.prototype.includes){var f=function(e){"use strict";if(null==this)throw new TypeError("Array.prototype.includes called on null or undefined");var n=Object(this),t=parseInt(n.length,10)||0;if(0===t)return!1;var r,o=parseInt(arguments[1],10)||0;o>=0?r=o:(r=t+o)<0&&(r=0);for(var i;r
I am struggling with this right now. Alt text, captions, audio (read to me) options are good. I work with an accounting software app that redesigned its palette to red, black, and gray. No green to signify income. Made no sense to me and their gray text (also very skinny sans serif) made reading many nav bars difficult. Some URLs are accessible from the build-out, but the DIY sites often don't have the same capacity. As with secure sites, I think google will be downgrading those sites with little or no compliance or accessibility add-ons.
Now you know that some types of content and format on webpages can pose barriers for people with disabilities. The next steps are to develop an action plan to fix web content that is currently inaccessible and implement procedures to ensure that all new and modified web content is accessible. The website accessibility checklist included in this section helps you assess what needs to be done.

Before you even begin designing your website, you should consider how you will use it to your advantage upon completion. Some owners make an event out of the launch of their website to create some buzz about their brand. Others line up their best customers to give testimonials on their new site via copy or video content so they, and these customers, have something to say and share on social media.
The fastest, most certain way to be sure your website is in compliance is to contact a qualified web design agency and have them perform an audit of all your online properties. Make sure you interview the agency thoroughly first, as not all agencies are up to speed on ADA website compliance rules. A qualified web design firm will be able to identify any violations of ADA Website Compliance and outline a plan for updating your online content and properties.