WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: WCAG2ICT question

for

From: L Snider
Date: Aug 2, 2017 7:04AM

Hi Jonathan,

Thanks for your reply. Yes, they basically repackaged WCAG, like they did
for PDFs. It is useful for sure.

I have seen others refer to WCAG 2.0 specifically for documents (Word,
PDF), but I haven't seen people reference WCAG2ICT specifically in reports,
audits or talk a huge amount about it online (I find it here and there).
That is why I was wondering about it in particular. I thought that people
would just reference WCAG, as many people would recognize it (and it is
used in legislation unlike WCAG2ICT), even if they did use WCAG2ICT (if
that makes sense?).

Cheers

Lisa

On Tue, Aug 1, 2017 at 9:47 PM, Jonathan Avila < <EMAIL REMOVED> >
wrote:

> > I don't find many people talk about WCAG2ICT and wondered if it was used
> a lot, and who uses it.
>
> In summation -- WCAG 2 is technology neutral and applies very well to
> software and native apps including native mobile. It is functional based
> and thus nearly all of the success criteria are still very relevant today.
> There are some gaps that are being addressed for touch and small screens
> usage and some additional success criteria have been proposed to address
> issues for certain disabilities that can be better addressed today. These
> additions will not affect WCAG 2 but will be included in separate WCAG 2.1
> document that allows for backwards compatibility and includes the existing
> criteria from WCAG 2.0 as well.
>
> More specifically around WCAG to non-web ICT -- for the most part the
> changes are in wording only (document instead of web page, software rather
> than web page, etc.). There are four criteria that apply to sets of
> documents and sets of applications rather than sets of web pages. These
> include bypass blocks, consistent navigation, consistent identification,
> and multiple ways. Other SC such as 4.1.1 parsing are already scoped to
> only apply to content generated with markup languages -- so if a markup
> language is not used then it doesn't apply.
>
> The real question is around knowing how you met the success criteria.
> There are sufficient and failure techniques for a number of technologies.
> There are some for Flash and Silverlight because these technologies were
> delivered through the web browser. But really these technologies are more
> similar to native content and in many cases can be run out of the browser
> as well. So you could look at the types of techniques used for these
> technologies and document similar techniques for the technology platform
> you are developing with.
>
> Jonathan
>
> Jonathan Avila
> Chief Accessibility Officer
> Level Access, inc. (formerly SSB BART Group, inc.)
> (703) 637-8957
> <EMAIL REMOVED>
> Visit us online: Website | Twitter | Facebook | LinkedIn | Blog
> Looking to boost your accessibility knowledge? Check out our free webinars!
>
> The information contained in this transmission may be attorney privileged
> and/or confidential information intended for the use of the individual or
> entity named above. If the reader of this message is not the intended
> recipient, you are hereby notified that any use, dissemination,
> distribution or copying of this communication is strictly prohibited.
>
>