atw: Re: MS Publisher

Seems I've hit a nerve, huh? 

 

Kind of - I get very bored with all the Microsoft bashing.  I go with the
big name products because they are where the market is.

 

But I must have a different definition for the word  "accessibility".  What
"accessibility issues" are you referring to?

 

Clarifying what I am doing.   I am not producing web content.  I am
producing an executable file that downloads onto someone's computer.  They
read it like a book, except they can only see it one page at a time, cannot
see the code and cannot copy the content.  

 

What "accessibility issues" can occur in this context?  Genuine question - I
need to know if I am to continue down this pathway.  Distributing training
materials electronically using non-specialist tools (ie tools designed for
mainstream rather than "the industry")  is all new to me.

 

Christine

 

From: austechwriter-bounce@xxxxxxxxxxxxx
[mailto:austechwriter-bounce@xxxxxxxxxxxxx] On Behalf Of Deborah Cross
Sent: Wednesday, 21 January 2009 4:42 PM
To: austechwriter@xxxxxxxxxxxxx
Subject: atw: Re: MS Publisher

 

Seems I've hit a nerve, huh? Or perhaps I have not expressed myself
properly.

 

I was trying to help by pointing out that your final product might have
accessibility issues if it is generated through Publisher. 

 

Accessibility of information is no joke and can be quite costly, as groups
like SOCOG will attest to.

Accessible code is actually modern thinking. Standards like WCAG 1 and 2 are
fundamental to ensuring that everyone has access to web content.

 

Given that I work in the web development industry, and am responsible for
implementing and coding web 2.0 (that's one 0) features, I'm not concerned
about being left behind nor taking the professional high ground.

 

  _____  

From: austechwriter-bounce@xxxxxxxxxxxxx
[mailto:austechwriter-bounce@xxxxxxxxxxxxx] On Behalf Of Christine Kent
Sent: Wednesday, 21 January 2009 2:19 PM
To: austechwriter@xxxxxxxxxxxxx
Subject: atw: Re: MS Publisher

Another thing you might want to consider is the usability and accessibility
of web code produced.

 

I don't have experience with Publisher, but if the HTML code it produces is
anything like MS Word, you could be in trouble.

 

Not an issue.  WebCompiler compiles the code into a locked down product for
which the source code can be made invisible.  If it succeeds in compiling,
then the code is OK - that's the sum total of it.

 

I think that we need to be a little bit careful that we are not left behind
taking the professional high ground, while the rest of the world has raced
ahead courtesy of Web 2.00, and all the program spin-offs from Web 2.00 that
are further enabling it.  Frankly, in this context, dirty code is
irrelevant. It is old thinking.

 

Christine

 

From: austechwriter-bounce@xxxxxxxxxxxxx
[mailto:austechwriter-bounce@xxxxxxxxxxxxx] On Behalf Of Deborah Cross
Sent: Wednesday, 21 January 2009 2:10 PM
To: austechwriter@xxxxxxxxxxxxx
Subject: atw: Re: MS Publisher

 

 

Some Publisher resources are available at
http://office.microsoft.com/en-us/publisher/HA012079251033.aspx

 

======================================= 
Deborah Cross 
E: deborah.cross@xxxxxxxxxx  
=======================================

Other related posts: