deborah: the Library of Congress cataloging numbers for children's literature, technology, and library science (Default)
[personal profile] deborah
A few infintesimal things and one bigger thing (and if people know about bits I missed please say).

The big thing: at the request of magnification users, primarily, we now have "skip to main content" links, woo! They are invisible in most cases, but they are the first thing on the page if you use a screen reader or if you tab from the top of the page. They currently only work in site schemed pages (pages that look like the DW home page, not pages that look like reading pages or journals; that's probably coming). Caveats by browser:
  • Firefox and Internet Explorer should just work
  • Safari works if you enable tabbed browsing, from the Safari menu pull down and select “Preferences”, Click on the “Advanced” icon and check the box next to “Press tab to highlight each item on a webpage”. Chrome might have the same issue, I'm not sure.
  • Opera, sadly, cannot work, because of implementation issues.

The two small things are alt text now exists on the dreamwidth logo, and the video direct link has moved out of the outlined placeholder box. I haven't fixed the duplicating link, though, so that's still mostly aesthetic.

There's also some FAQ and doc clarification, which is always an accessibility help.

Also come to think of it there is a real cognitive win in the new feature on the beta create entries page, where if you pick a custom access filter it tells you who is on the filter.
deborah: The management regrets that it was unable to find a Gnomic Utterance that was suitably irrelevant. (gnomic)
[personal profile] deborah
just an FYI: the "insert image" pop-up on the HTML version of the post-creation page now has the option to add alternative text, and both the HTML and Rich Text Editor versions of the "insert image" pop-up now link to a (soon to be improved) FAQ explaining what this wacky "short description" field is for. So if you know people who are putting images into their posts without alternative text, you can explain to them how incredibly easy it now is to add alt text.

Of course it now occurs to me that if I really want to make a difference in people's Internet experience, I should go contribute an easy way to add alt text to the tumblr code base.

Somebody, go do that!
deborah: the Library of Congress cataloging numbers for children's literature, technology, and library science (Default)
[personal profile] deborah
As of tonight's code push, entry and reading pages have headers while read in site scheme (example), for better screenreader and other navigation.

Also, as [staff profile] denise mentioned in tonight's news post, we are aware that the new photo hosting doesn't yet have alt text but that is a top priority fix. This is a beta launch, and alt text will come Real Soon Now.
anarres: (Default)
[personal profile] anarres
Hi all, I'm one of the Google Summer of Code students, working on the statistics project. I've written a module that generates graph images, which will be shown on I wanted to get some feedback on the images from an accessibility point of view. I don't know much about accessibility, but I guess the main questions would be, are the colours on the pie chart different enough to be distinguished by people with partial colour-blindness, and is the text visible enough?

The graphs module is found in an uncommitted patch here: Bug 2699 - Create a graphical front-end for the statistics system.
read more )
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
Was thinking about the alt text for user icon heads and how we could change them to be better and more natural for screenreaders. I've opened bug 2037; the first comment says:

The userhead icon alt is [info - user] and the community is [info - community].
Change to [user profile] and [community profile] for more natural flow in

I'm trying to check that this is a change that would be useful. A friend of mine who uses a screenreader says that "user profile" and "community profile" would be the best mix of clarity and brevity and that the best thing to do is to make the first word the key word. But I wanted to post here to make sure that I haven't overlooked anything.

jadelennox: Oracle with a headset: Heroes Use Headsets (gimp: heroes use headsets)
[personal profile] jadelennox
  1. I'm going to add this to the "to document" wiki, but people should understand that the "title" attribute is not a tool to convey accessibility. Most users, screenreader or not, never see title attributes.

    Except in form controls, title attributes are useless to 99% of users -- including sighted users, since most people don't hover long enough to see the tooltip.
  2. WebAIM has published the results of their second screenreader survey. Summary of things that interested me:
    • JAWS is still in the lead, but NVDA and VoiceOver are gaining.
    • IE7 and IE8 are most common browsers, alas.
    • most people have JavaScript on
    • The answers about alt text are complex.
    • The most annoying accessibility problems that would be a problem on dreamwidth are poorly named link text, keyboard access, and bad forms.
    • On a lengthy page, many users navigate via the headings on the page.
    • There is no typical screen reader user.
jeshyr: Standrd glyphs representing disability, blindness, interpreters and information. (Disability)
[personal profile] jeshyr
A comment that reminded me why we're doing all of this, and how great the pay-off is when we get it right:

Made me day, it did.


ETA: Right link now!
Page generated Oct. 22nd, 2017 07:08 pm
Powered by Dreamwidth Studios