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

Re: Accessible Documents - PDF vs. HTML

From: Graham Armfield <graham.armfield@coolfields.co.uk>
Date: Thu, 16 Jun 2016 13:07:20 +0100
Message-ID: <CAKr-9+mjPHswNBSdU00o3NCSSt+i24vMiQfcLu4CWpC29PVTOA@mail.gmail.com>
To: w3c WAI List <w3c-wai-ig@w3.org>
Since HTML is clearly the favourite choice in this discussion, then it may
be worth investigating building your resource with a CMS like WordPress (or
Drupal).

Within the WordPress admin screens page editor it's possible to paste in
text and add images, headings, links etc without needing to know HTML, and
to get fairly good HTML out on your website as a result.

If your transcripts are already in MS Word with simple properly formatted
lists and headings etc, then you can paste directly from Word into the
WordPress editor, and get sensible content out. But if there are more
complex elements, tables, colour changes, etc then things can start to get
messy.

Out of the box, WordPress can't deliver multiple choice interaction, but
there may be a plugin to help with that. But watch out for plugins that
compromise accessibility. There is currently no accessibility review built
into the WP plugin review process - something that is there (albeit
optional) within the WP theme review process.

Whilst I have knowledge of WordPress, I imagine Drupal to be capable in a
similar way.

Regards
Graham Armfield

coolfields.co.uk <http://www.coolfields.co.uk/>
M:07905 590026
T: 01483 856613
@coolfields <https://twitter.com/coolfields>

On Thu, Jun 16, 2016 at 11:34 AM, Andrew Cunningham <
andj.cunningham@gmail.com> wrote:

> 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
>
>
Received on Thursday, 16 June 2016 12:08:09 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 16 June 2016 12:08:09 UTC