(Viewing 1 reply thread)
    • #951
      Dee Zynah
      Participant
      @dee
      Up
      0
      Down
      ::

      Seeking advice:
      Hi, my client needs a website to be Accessible – Divi does not seem to be compliant? Looking for advice on how to do this with Divi. Totally new territory – I am finding little information out there on this subject.
      What have you done for your clients?

    • #953
      Anita
      Participant
      @anita
      Up
      0
      Down
      ::

      <div class=”kvgmc6g5 cxmmr5t8 oygrvhab hcukyx3x c1et5uql”>
      <div dir=”auto”>First, what level of compliance is your client seeking? Divi can be compliant when you design for it.</div>
      <div dir=”auto”></div>
      </div>
      <div class=”o9v6fnle cxmmr5t8 oygrvhab hcukyx3x c1et5uql”>
      <div dir=”auto”>A close friend researches compliance as part of his research as a professor. His advice: Given that there are a variety of standards out there, I think the best strategy is for the contract to specify the exact level of compliance, typically WCAG 2.1 AA. There are three different standards: WCAG 2.0, 2.1 and 2.2, which is in draft. There are also three different bars someone can reach: A, AA, and AAA. Most of the time, AA is fine.</div>
      <div dir=”auto”></div>
      </div>
      <div class=”o9v6fnle cxmmr5t8 oygrvhab hcukyx3x c1et5uql”>
      <div dir=”auto”>If it’s a federal government website, or one that gets federal government funding, some people will talk about section 508, which, in the older version, is pretty similar to WCAG. Back in 2017, the US government mandated WCAG 2.0 A/AA compliance. Here is a link to differences between 2.0 and 2.1:
      Accessiblemtrics.com</div>
      </div>

(Viewing 1 reply thread)
  • You must be logged in to reply to this topic.