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

Re: Accessible Documents - PDF vs. HTML

From: J. Albert Bowden <jalbertbowden@gmail.com>
Date: Wed, 15 Jun 2016 23:14:23 -0400
Message-ID: <CAPVQ3_dHw8nn5gn6qNzc=Qf4sUTN0G0cuFcE0oeF-NQ=K-ZjnQ@mail.gmail.com>
To: Olaf Drümmer <olaflist@callassoftware.com>
Cc: w3c WAI List <w3c-wai-ig@w3.org>
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/
Received on Thursday, 16 June 2016 03:14:52 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 16 June 2016 03:14:53 UTC