W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2016

RE: PDF's Exposed via Web Pages and Accessibility

From: Paul Tykodi <ptykodi@tykodi.com>
Date: Wed, 6 Jan 2016 06:28:22 -0500
To: <howard_leicester@btconnect.com>
Cc: <w3c-wai-ig@w3.org>, "'Jonathan Avila'" <jon.avila@ssbbartgroup.com>
Message-ID: <00b001d14875$59e35820$0daa0860$@tykodi.com>
Hi Howard,

 

The customer I am currently assisting is definitely focused on providing a
good customer experience to all via the web. My opinion is that without some
basic regulatory guidelines in place, it is very difficult for an
organization to know what accessibility capabilities it should include in a
web site.

 

That being said, I completely agree with both your comment and Jonathan's as
well. I do believe that more effort needs to be focused on insuring that
content formats used in building web pages are accessible and ultimately the
whole reason for undertaking the effort is to provide an acceptable web
experience for all users. I agree with your observation that working
together as a global community, it would seem to make sense to focus some
attention on how to make the process of building fully accessible web pages
simpler than it is today.

 

Thanks.

 

Best Regards,

 

/Paul

--

Paul Tykodi
Principal Consultant
TCS - Tykodi Consulting Services LLC

Tel/Fax: 603-343-1820
Mobile:  603-866-0712
E-mail:   <mailto:ptykodi@tykodi.com> ptykodi@tykodi.com
WWW:   <http://www.tykodi.com/> http://www.tykodi.com

 

This e-mail reply and any attachments are confidential and may be
privileged.

If you are not the intended recipient, please notify Tykodi Consulting
Services LLC 

immediately by replying to this message and destroying all copies of this
message 

and any attachments. Thank you

 

From: Howard Leicester [mailto:howard_leicester@btconnect.com] 
Sent: Tuesday, January 05, 2016 4:17 PM
To: 'Jonathan Avila' <jon.avila@ssbbartgroup.com>
Cc: ptykodi@tykodi.com; w3c-wai-ig@w3.org
Subject: RE: PDF's Exposed via Web Pages and Accessibility

 

Thanks Jon,

 

I appreciate that there are folk with seious passionate on accessibility.

 

Not so convinced we (around the world) really deliver.

 

508 requirements are US based.

 

We're less focussed in the UK on something so specific, except W3C/WAI
approaches.

 

All seems complicated, anyway, and what actually achieves (regardless of
standard compliance)?

 

Think, actually, we should (internationally) work together and make things
as simple as possible - not the case so far!

 

Makes even more sense in the UK (and US etc?) because > 50% of the adult
population have "literacy proplems".

 

That, plus widespread use of mobiles/tablets, sure makes 'accessibility' a
mainstream issue?!!

 

Big thanks,

Howard

 

 

 

 

----------------------------

Dr Howard Leicester

+44 (0)7789 965202

www.accessible-info.co.uk <http://www.accessible-info.co.uk> 

 

  _____  

From: Jonathan Avila [mailto:jon.avila@ssbbartgroup.com] 
Sent: 05 January 2016 20:43
To: howard_leicester@btconnect.com <mailto:howard_leicester@btconnect.com> 
Cc: ptykodi@tykodi.com <mailto:ptykodi@tykodi.com> ; w3c-wai-ig@w3.org
<mailto:w3c-wai-ig@w3.org> 
Subject: Re: PDF's Exposed via Web Pages and Accessibility

 

Howard, I won't jump into the PDF vs.  HTML discussion but I will say the
issues regarding CMS content applies to other document and content formats
as well and is a general issue this need to be addressed.   

 

Jon

Sent from my iPhone


On Jan 5, 2016, at 3:18 PM, Howard Leicester <howard_leicester@btconnect.com
<mailto:howard_leicester@btconnect.com> > wrote:

Hi Jonathan et al,

 

Interesting exploration.

 

Wondering if any 508 solution actually serves the perpuse of being
accessible for those who need it.

 

I'm from the UK and think, possibly, over concern with formal standards may
miss the true ability to make websites and e-documents as truly accessible
as they might be.

 

Perhaps what I'm saying is:

 

*	What do you find useful? 
*	And 
*	Who is really benefitting? 

 

No worries, but extra best,

Howard

 

 

 

----------------------------

Dr Howard Leicester

T: (UK) 01959 523770

www.accessible-info.co.uk <http://www.accessible-info.co.uk> 

 


  _____  


From: Jonathan Avila [mailto:jon.avila@ssbbartgroup.com] 
Sent: 05 January 2016 17:47
To: ptykodi@tykodi.com <mailto:ptykodi@tykodi.com> ; w3c-wai-ig@w3.org
<mailto:w3c-wai-ig@w3.org> 
Subject: RE: PDF's Exposed via Web Pages and Accessibility

 

*  I have been reviewing the proposed refresh of the United States of
America Section 508 regulation, which specifically calls out using PDF/UA
when embedding PDF files into web pages:
http://www.access-board.gov/guidelines-and-standards/communications-and-it/a
bout-the-ict-refresh

 

Based on my questions to the Access Board during the public hearing, the
Board indicated authors can choose to use PDF/UA or WCAG for PDF document
conformance.

 

Yes, you are correct that a mechanism should be in place to allow the
promotion of compliant content and block non-compliant content.  Within
PDF/UA some items still must be manually tested as the standard cannot be
validated completely by an automated tool.

 

Products like our Accessibility Management Platform can scan websites and
identify and test PDF documents for a number of automatic checks - one of
which could be the PDF/UA designation.  API access is also available on
various platforms to allow a CMS to upload a file for review to get a
response.

 

Best Regards,

 

Jonathan

 

Jonathan Avila

Chief Accessibility Officer
SSB BART Group 
jon.avila@ssbbartgroup.com <mailto:jon.avila@ssbbartgroup.com> 

703.637.8957 (o) 
Follow us:  <http://www.facebook.com/#!/ssbbartgroup> Facebook |
<http://twitter.com/#!/SSBBARTGroup> Twitter |
<http://www.linkedin.com/company/355266?trk=tyah> LinkedIn |
<http://www.ssbbartgroup.com/blog> Blog |  <http://eepurl.com/O5DP>
Newsletter

 

From: Paul Tykodi [mailto:ptykodi@tykodi.com] 
Sent: Tuesday, January 05, 2016 11:58 AM
To: w3c-wai-ig@w3.org <mailto:w3c-wai-ig@w3.org> 
Subject: PDF's Exposed via Web Pages and Accessibility

 

Hi,

 

I am currently working on a Customer Communications Management architecture
project for a financial services firm. One of the issues I have been asked
to investigate, from an architectural perspective, is the use of PDF files
embedded within a publicly available web page.

 

I have been reviewing the proposed refresh of the United States of America
Section 508 regulation, which specifically calls out using PDF/UA when
embedding PDF files into web pages:
http://www.access-board.gov/guidelines-and-standards/communications-and-it/a
bout-the-ict-refresh

 

In looking at this issue from an architectural perspective, it seems like
placing some form of validator in the delivery channels from PDF creator to
web page delivery would likely be necessary to insure all PDF's made
available for web page deployment were PDF/UA compliant.

 

I am hoping that subscribers to this W3C list with experience in this area
might be able to comment on best practices for embedding PDF files in web
pages and maintaining accessibility conformance (Examples: WCAG 2.0 and the
ISO Standard known as PDF/UA) going forward.

 

Thanks.

 

Best Regards,

 

/Paul

 

 

<image002.jpg>

Paul Tykodi
Principal Consultant


Tykodi Consulting Svcs LLC

Phone:

(603) 343-1820

 


 

3 Lowell Ave

Cell:

(603) 866-0712


 

Dover, NH 03820

Fax:

(603) 343-1820


 

USA

E-mail: 

 <mailto:ptykodi@tykodi.com> ptykodi@tykodi.com


 

 <http://www.tykodi.com/> www.tykodi.com

Skype:

Tykodiconsultingservices


 

 

 

 

 

 

 

 

Co-Chair               - IEEE-ISTO PWG IPP Working Group

Vice-Chair             - IEEE-ISTO PWG Semantic Model Working Group

 

This e-mail message and any attachments are confidential and may be
privileged.

If you are not the intended recipient, please notify Tykodi Consulting
Services LLC 

immediately by replying to this message and destroying all copies of this
message 

and any attachments. Thank you

 
Received on Wednesday, 6 January 2016 11:28:56 UTC

This archive was generated by hypermail 2.3.1 : Friday, 29 January 2016 16:39:04 UTC