Re: Re[2]: Automated A11y non-issues and SC Parsing 4.1.1

4.1.1 says "In content implemented using markup languages,..." so PDF is
not covered in 4.1.1
​, it's all about markup languages. I think we can have that kind of
specificity here.​

Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*
Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>

On Mon, Jul 18, 2016 at 9:41 AM, White, Jason J <jjwhite@ets.org> wrote:

>
>
>
>
> *From:* Jonathan Avila [mailto:jon.avila@ssbbartgroup.com]
> *Sent:* Monday, July 18, 2016 9:36 AM
>
>
>
> The term visible in the DOM tree is problematic.  Do you mean visible with
> the current CSS or do you mean exists in the DOM tree?  I would prefer a
> term that was more clear that we were talking about being present in the
> DOM tree.
>
> *[Jason] The entire proposal is very technology-specific in any case. It
> wouldn’t address PDF documents, for instance, which have tags but no DOM
> tree, or contexts in which the author is writing in XML.*
>
> *One of the principal objectives of WCAG 2.0 was to avoid HTML-specific
> technical assumptions in the guidelines and success criteria.*
>
> ------------------------------
>
> This e-mail and any files transmitted with it may contain privileged or
> confidential information. It is solely for use by the individual for whom
> it is intended, even if addressed incorrectly. If you received this e-mail
> in error, please notify the sender; do not disclose, copy, distribute, or
> take any action in reliance on the contents of this information; and delete
> it from your system. Any other use of this e-mail is prohibited.
>
> Thank you for your compliance.
> ------------------------------
>