[personal profile] jazzyjj
Hi everyone. With today being Global Accessibility Awareness Day, I'm curious whether anybody has tested either the main Dw site or their own journals and/or communities with Wave or any of the other automated tools out there? I don't know enough of the technical details of these tools, but based on my personal use case scenario Dw works great. To that end, I'm also curious whether people here prefer the automated testing tools, manual testing or a combination of both. Sorry if this is a repeat.
http://www.afb.org/blog/afb-blog/celebrating-global-accessibility-awareness-day-2016/12
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
Someone reported that the alt text for icons on the /icons page (for instance, https://denise.dreamwidth.org/icons) is behaving weirdly and labeling every image as "(Default)" when viewed. A bit of investigation has turned up that it has to do with how the function that generates the alt text is called -- it does weird things when it's not called in the context of a comment/post.

The coder who ran down the issue is looking for some guidance on how things should work to fix the problem, and one of the questions raised was: is the alt text even necessary in that context? Alt text for icons is formed by the icon's keyword + description, and all that information is right there with the icon anyway: it's displayed next to the icon, and (if I'm not mistaken) is read out immediately after the icon.

So, screenreader users: Is having the alt text for each icon read to you on that page helpful, given that it's immediately repeated afterwards, or is it annoying? Should we fix the bug so that each icon gets the correct keyword information in the alt text, or should we just blank the alt text (on that page alone, not everywhere!) so you don't have to hear it twice?
deborah: The management regrets that it was unable to find a Gnomic Utterance that was suitably irrelevant. (gnomic)
[personal profile] deborah
I'm having a med reaction that's left me exhausted but jittery and sleepless, so I might as well do something productive with the time. It's been a very long time since I asked people for feature or bug requests for accessibility issues.

What do you wish, in a perfect world, dreamwidth would fix or implement? Note that I'm more clueless about cognitive accessibility, magnification, and visual processing, so I especially welcome clarifications on places we fail on those. No request too large or small, as long as it obeys the laws of thermodynamics.
fayanora: Steph Pensive (Steph Pensive)
[personal profile] fayanora
My roommate is allergic to plastic, which gets in the way of her finding a salt grinder, because apparently every salt grinder she and I have found, no matter what the outside is made of, has plastic gears and/or plastic griding bits, which is ridiculous, really. Why make a salt grinder with a grinding part that is weaker than the material you're grinding? Anyway, she can't use those because little bits of plastic get into the ground up salt.

Does anybody else know where to find a salt grinder that has like, a metal grinder? Granted, she's allergic to lots of metals, too, but metal being stronger than salt means it's unlikely to be a problem the way plastic salt grinders are. Any help would be greatly appreciated, as I don't know where to even begin looking.
jesse_the_k: Photo of baby wearing huge black glasses  (eyeglasses baby)
[personal profile] jesse_the_k
The sub filter manager page here at this URL:
http://www.dreamwidth.org/manage/subscriptions/filters
doesn't work well with my very large default font size
screen shot link to dropbox
https://www.dropbox.com/s/bqfwby8e1cqri2j/Screenshot%202015-08-09%2011.30.07.png?dl=0

1. Note truncated account names due to narrowness of the scrolling lists.
2. Note account names don't enlarge with rest of fonts.
3. Note very small gutter between lists, makes it hard to fixate on which list I'm selecting

GOOD NEWS! DW already has a page which works much better.

The access filter manager page here at this URL:
http://www.dreamwidth.org/manage/circle/editfilters
is much more usable with my very large default font size
screen shot link to dropbox
https://www.dropbox.com/s/n3uajcb2uxl41js/Screenshot%202015-08-09%2011.49.35.png?dl=0
The access-filter scrolling lists seem to adjust width (although some account names are still cut off). I am willing to do a bit of horizontal scrolling to have all three lists, which accomplish a lot!

REQUEST: Remodel following layout of access filter manager
a. Double or triple scroll list width (ideally, since you have lots of room, expand to maximum account-name length +5)
b. Don't hard wire font size.
c. Triple or quadruple gutter between "not in filter" and "filter" lists.

Mods, could I have a "large font" or "large print" tag?

Protocol question: should I post this to [site community profile] dw_suggestions
as well?
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 Library of Congress cataloging numbers for children's literature, technology, and library science (Default)
[personal profile] deborah
I think there's only one accessibility feature in tonight's code push (except that all the various other little clarifications, doc fixes, etc are also accessibility wins, but this is the big one).

Youtube and vimeo video embeds require flash to control. Many of us can't easily access the Flash controls (and many people have problems with flash a number of reasons). This patch puts a plain HTML link to the video outside the Flash, so you can open it up at the Vimeo and Youtube sites, where you might have more control. For example, you might have YouTube configured to autoplay, or configured to use their much more accessible HTML5 player, but that only works if you're at their site.

Also coming imminently but not here tonight, the links will also contain the title of the video, so you know what it is before you follow the link. We just need to finish some paperwork with youtube to enable that functionality.

Examples below the cut.
video links )
deborah: the Library of Congress cataloging numbers for children's literature, technology, and library science (Default)
[personal profile] deborah
There are a few accessibility improvement in last night's code push, detailed here for your viewing pleasure:

  • The form to submit a support request now has labels so it can be reasonably navigated with a screenreader.
  • The UI used by support volunteers now has improved visual indicators so that it doesn't rely on colors to relay information.
  • The cut tag arrows are now higher resolution and scale properly for people using larger font sizes.


There are also two accessibility *ahem* bugs introduced in last night's code push: the new cut tag arrows don't have a white outline so they are difficult or impossible to see on dark backgrounds, and a fix to the contextual userhead hover to fix coloration in certain styles causes viewing problems in certain other styles. Fixes for both of these will be pushed ASAP.
deborah: the Library of Congress cataloging numbers for children's literature, technology, and library science (Default)
[personal profile] deborah

Dreamwidth makes its dropdown menus accessible without a mouse by making the top-level items links to lists of the menu items on a new page. There's been a lot of work lately to make complex dropdowns accessible without page reloading. I'm curious what kinds of dropdown menus are accessible to you, our users, whether your disabilities are mobility, visual, cognitive, or something else.

This poll lists the current system as it stands, as well as links to 15 alternative, keyboard-accessible menus (all but the first two are non-real-world examples from Terrill Thompson's awesome resource). I would love if all y'all could test and see which options have reasonable usability for you, no matter what functionality you use to manipulate and view it.

And if you don't know if you should take this poll? If you think you have accessibility needs in any way, please do! I know it's time consuming but I'll love you forever.

Poll #13618 Accessible dropdowns
Open to: Registered Users, detailed results viewable to: All, participants: 6


Which menus are functional for you?

View Answers

The current system
4 (66.7%)

University if Washington
2 (33.3%)

Adobe (described here)
3 (50.0%)

Interesting Example 1
3 (50.0%)

XHTML Strict
4 (66.7%)

HTML5
4 (66.7%)

Suckerfish
3 (50.0%)

Son of Suckerfish
3 (50.0%)

Superfish
2 (33.3%)

Dropper Dropdown Menu
3 (50.0%)

UDM4
5 (83.3%)

Simply Accessible
4 (66.7%)

YUI
4 (66.7%)

Customized OAA Dropdown
4 (66.7%)

JQuery-ui Menubar Widget
3 (50.0%)

Canadian Government Web Accessibility Toolkit
0 (0.0%)

deborah: the Library of Congress cataloging numbers for children's literature, technology, and library science (Default)
[personal profile] deborah
I was process of fixing an inaccessible form, and went to go swipe some CSS from another form -- and realized that other one also had accessibility problems. Whoops.

So now I'm on a mad dash to do some form accessibility remediation. It's a nice easy task which provides a big net win.

Tell me which forms you have accessibility problems with, and I will add them to my list.

The ones on my current list are the poll creator and the form to submit a support request.

At a minimum, tell me which form causes the problems, and I will play with it. Ideally, tell me
  1. which form causes the problems
  2. the nature of the problems
  3. what browser and browser version you are using
  4. what adaptive tech you are using, if any
foxfirefey: A guy looking ridiculous by doing a fashionable posing with a mouse, slinging the cord over his shoulders. (geek)
[personal profile] foxfirefey
How can you program if you're blind -- a question on StackOverflow that gets some thorough answers from blind programmers. Figured it might be interesting reading for others who, like me, are interested in the tools and processes.
jeshyr: Jeshyr - Dreamwidth Accessibility (Dreamwidth - Accessibility)
[personal profile] jeshyr
[OK I have been meaning to post this for about a month and I keep putting it off on account of not having the right phrasing, but hey ... wrong phrasing will have to do]

My basic question is to those developers/volunteers/users of Dreamwidth who are NOT themselves users of accessibility technology...

I know that a bunch of folks here have become accessibility converts/evangelists. By which I mean that you're not just "doing accessibility" because Dreamwidth requires you to, but you're really understanding why it's necessary and important and often you're pointing this out to others in other contexts away from Dreamwidth too.

I know that a project can require people to "do" accessibility, but a project can't make people *care* about accessibility... and most projects that "do" accessibility at all are in the first category. So ... how did you come to care about accessibility, especially if Dreamwidth was involved??

I have been chatting to Liz Ellcessor who is writing a book about web accessibility specifically and wants to know about Dreamwidth's accessibility from the inside, but it's also just a thing I have been wondering about more generally too. Dreamwidth is known for "doing accessibility" well and part of that is that we have got a bunch of people fired up about it and that's a really hard thing to do!!

So how do you think you caught accessibility?
deborah: the Library of Congress cataloging numbers for children's literature, technology, and library science (Default)
[personal profile] deborah
How do keyboard users feel about the Navigation Strip at the top of reading pages? (The one that, when you're logged in, shows your tiny default userpic and links for Home, Post, Reading, Settings, Inbox. In Bug 3302, there's a request to move the navstrip later in the tab order, so it's not the first thing you interact with, since you so rarely want to interact with those options. But is that true? Is it convenient, inconvenient, or neutral that when you first start tabbing around the page you go to the navstrip first?
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!
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
Gimme your favorite web accessibility discussion blogs, sites, resources, etc!
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
I'm doing a talk on web accessibility at LinuxConf Australia and would like to give specific examples!

So, gimme your best examples of websites with specific accessibility problems that drive you nuts. Use of tabular data where it doesn't make any sense, sites with horrible contrast or that won't let you change font sizes, restaurant websites that are entirely flash-based, etc, etc.

Also, if anybody knows of good illustrative videos of a) people listening to a screenreader and b) people dictating to their computer, point me at 'em?
autisticalice: (Default)
[personal profile] autisticalice
 I think there should be a banner or something saying if maintenance will be at a certain time and to prepare for it. I came up with this idea because of the recent maintenance where it was rather unpredictable and I had no idea it was coming. As a disabled person, I need to have predictability in order to plan my activities wisely so that nothing bad is triggered.
 
Otherwise, unpredictability might trigger a big meltdown. I'm sure there are other users that don't have twitter or ways of knowing when maintenance will happen since they might not check the dw_maintenance constantly to check. What would be effecient is having an estimate of the time for maintenance before it starts, how long it will be and whatever.
 
As I said before, I'm the type of person that needs predictability and proper structure so that a meltdown/outburst isn't triggered by a surprise maintenance closure, especially when I don't know how long that will last, it can cause a lot of distress for me.
 
I don't think there would be any drawbacks, except maybe it might bother some people but it is more beneficial to be aware of what is going to happen. it will give people time to plan what they want to say wisely and possibly know that they have to make an entry before the maintenance starts... or whatever.

(I'm not sure if this is allowed but it is a real problem for me)

denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
Over in [site community profile] dw_suggestions I am floating the first tentative questions about a redesign of the inline commenting form (the one that comes up when you're reading an entry and pick "leave a comment", not the one that you get from the "more options" link or if you load a link with ?replyto=foo on it) and asking people for opinions on whether the "check spelling on preview" tickybox needs to remain in the inline-quick-reply form. If you've got access needs around that workflow, please chime in over there, or at least ticky the "no" option in the poll!
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.
dunvi: blue (Default)
[personal profile] dunvi
I was poking at bug 4385, which hopes to add an option for scaled down images in the shiny new icon browser. What I found when I was playing around was that when the images are scaled (down to 50% width and height, so a quarter of the original size), the meta text feels very squished, and there's a high chance of your keywords or descriptions stretching things around nuttily. [ETA: that comment was based on an example mid-debug - the working version doesn't stretch around, but things get cut off if you have more than about one keyword and two words of description text.] Furthermore, I personally found that mini pictures with meta wasn't any more useful (in fact slightly less so) than just using the drop down selector in the first place, but I wanted to check with wiser people, (especially people with more than just a few icons, or who may be using the site differently than me).

How do people feel about perhaps leaving the option for meta info with scaled images out entirely? What I mean is that, instead of two toggles, one 3-way toggle with options of half sized images, full sized images, and full sized images with meta info.

images below the cut )

Profile

dw_accessibility: Dreamwidth Sheep in a wheelchair with the text "I Dream Of Accessibility" (Default)
The DW Accessibility Project Team

May 2016

S M T W T F S
1234567
891011121314
15161718 192021
22232425262728
293031    

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jul. 31st, 2016 07:14 am
Powered by Dreamwidth Studios