- From: Katherine Mancuso <kmancuso@gmail.com>
- Date: Fri, 13 Mar 2015 13:43:46 -0700
- To: Char Easter <ceaster@seattletimes.com>
- Cc: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
- Message-ID: <CANetDcXwD9ik1Cg77zaih4T_jMLz-=GBHWnsLcEEz0Dd5MTSMA@mail.gmail.com>
Hi Char - There's a WordPress accessibility group actively working on improving the accessibility of WordPress and this is a jumping-off point to the pretty extensive documentation: http://codex.wordpress.org/Accessibility. Katherine On Fri, Mar 13, 2015 at 11:28 AM, Char Easter <ceaster@seattletimes.com> wrote: > Hello, Has there been discussion on accessibility in WordPress? > > > > Here are a few things I learned from my tests for Alt attributes, but > would love to know more about all accessibility WP characteristics. > > > > 1. Through the CMS, you cannot enter code, so you can’t add a null > alt (alt=""). We have captions for most our images, so leaving the Alt Text > field blank because the screen reader is reading the Caption and a caption > and alt text would be overload. > > 2. You can add the alt attribute via the code if the images were > added in the code > > 3. If images were entered outside the CMS (via the page code), > however, you cannot add alt attribute via the CMS field. > > 4. Screenreaders do not read the filename (thankfully) > > > > Thanks, > > > > *Char Easter* > > User Experience Designer > > w: 206.464.2945 > > c: 206.779.2427 > > ceaster@seattletimes.com > > [image: STC_letsworktogether] > > >
Attachments
- image/jpeg attachment: image001.jpg
Received on Friday, 13 March 2015 20:44:38 UTC