E-mail List Archives
Re: WordPress Accessibility
From: Colleen Gratzer
Date: Aug 10, 2019 12:08PM
- Next message: Starry Sky: "Accessible survey assist request"
- Previous message: Philip Kiff: "Re: WordPress Accessibility"
- Next message in Thread: Philip Kiff: "Re: WordPress Accessibility"
- Previous message in Thread: Philip Kiff: "Re: WordPress Accessibility"
- View all messages in this Thread
Pamela made great points. To add to those
When we build accessible sites, we provide training so the client
understand more about properly formatting content. We do live training
and provide a PDF of guidelines.
A huge advantage to WordPress, though is the ability to customize the
back end. For example, for sites we build, we:
- remove the client's ability to add an H1 to the page content since
that's reserved for the page title.
- add the ability for them to make text *look* like a heading but it is
really just a P *styled* that way.
- add custom fields for where we want them to enter screen reader text.
- put instructions next to those custom fields in the editor, with
guidelines. One example would be instructing them to add screen reader
text to hyperlinks where there might be multiple "read more" links on
the same page.
Certified Branding Expert + Accessibility Specialist, Gratzer Graphics LLC
Design Mentor and Host of the Design Domination podcast
On 8/10/19 1:08 AM, Pamela Riesmeyer wrote:
> the biggest challenges to accessibility were the content creators. When we trained people
to create accessible content, our WordPress sites were accessible, from
the front end.
> There are great advantages to database driven sites, over hand-coded static
> HTML pages.