Re: Accessible Documents - PDF vs. HTML

Yes ... for developers, and web support staff. But content owners and
content authors will not be using text editors ... they will either be
using ms word or a wysiwg editing environment within a web application to
edit or create content.

So ... maybe the question is what building blocks exist to create an
editing environment yhat will generate accessible content assuming the
templates and themese used by a web application meet accessibility
requirements?

A.

On Thursday, 16 June 2016, J. Albert Bowden <jalbertbowden@gmail.com> wrote:
> tools for working with HTML: any editor....literally any editor. you can
use notepad in windows even! and i mean notepad, not notepad++, simply save
the .txt document as .html instead.
>
> jedit has been my go to for nearly a decade now, sublime text is probably
one of the most popular on the market, atom is editor created by github,
brackets was created by adobe....just to name a few.
>
> tools for creating accessible HTML documents: w3c validators, tenion.io,
accessibility project's resouces: http://a11yproject.com/resources.html and
w3c's web accessibility evaluation tools https://www.w3.org/WAI/ER/tools/,
to name a few.
>
> pro tip: using HTML properly will get you closer to accessible than
anything else...not to take away from some of these tools, but properly
using HTML reinforces accessibility, because HTML has some accessibility
already baked in.
>
>
>
> On Wed, Jun 15, 2016 at 3:33 PM, Olaf Drümmer <olaflist@callassoftware.com>
wrote:
>>
>> It seems there is some agreement that HTML is  a good option, but Word
is not the right tool to create HTML.
>>
>> Can anybody share which tools they use to make their accessible HTML
files?
>>
>> Olaf
>
>
>
> --
> J. Albert Bowden II
>
> jalbertbowden@gmail.com
>
> http://bowdenweb.com/
>
>

-- 
Andrew Cunningham
andj.cunningham@gmail.com