Rian Rietveld

Just posted a ticket in the trac about the keyboard accessibility of the menu.

If the screen is enlarged by Ctrl+ the Dashboard layout jumps into mobile version.
For people who enlarge the screen and only use a keyboard, the menu of this mobile version is not easy accessible.
A screen reader user can’t see the size of the screen, so when it’s in mobile version, that’s a problem for them too.

The menu button has no label and if selected, the focus stays on the menu button. So the menu can only be reached entering shift-tab. The user than can navigate though the menu from the bottom to the top backwards.

My recommendations

• Add a label to the menu
• Set the focus on the first menu-item after selecting the menu
• For screen reader users: change the style hidden into the class screen-reader-text
• And maybe add an option: disable mobile version with the user settings?

Did anyone find more functionality missing using assistive technology?

Still puzzling about the mobile version of the site.
If the screen is enlarged by Ctrl+ the layout jumps into mobile version.
For people who enlarge the screen and only use a keyboard the menu of this mobile version is not accessible .
I think a setting “disable mobile version” is necessary.
Is it worth a ticket on the trac?

@azaozz is right, If the screen is small, the layout pops into responsive mode, with an entirely different menu-structure. Trying to access the menu and navigate trough it, with keyboard only isn’t that easy, a lot is skipped and the tab order is not logical.

Maybe a quick solution is to add a setting, like “disable mobile version”? To avoid this problem for screen readers for now.

But because a lot of blind people use an iPhone, this is a problem that needs to be solved a the future release I guess.

Isn’t accessible-ready maybe a better tag? I would search for the word accessible…

+ 1, same here, can’t move banners anymore

@andrew, it solved the problem for now. I checked the complete code/database, the rest is clean.
I will move to site to a different provider with a clean WP and plugin install soon.

Thanks for this discussion, removing Facebook/quiknotes solved the javascript injection in one of my sites.

A new version of the Child theme has been added to the github:
https://github.com/RRWD/accessible-twenty-eleven-theme

It should work out of the box now.

Note: it’s not a fully WCAG 2 accessible child theme. I just made some adjustments.
The accessibility work I do next to my job, in my free time. Still trying to get some funding for time to do a decent study on this subject.

If you find more bugs, please let me know.

@ed, thanks for trying out the child theme
@joe, Thanks so much for answering and debugging

This child theme was a rough attempt to make some accessibility improvements, didn’t have a clue that someone would actually use it.
I will make the proper adjustments on the theme at the github.
Kind regards,
Rian

Because i’m building a website that needs to be WCAG 2.0 valid.
And besides that, it’s good practice?

Thanks ??

@maarten Bedankt ??

Hi jen697,
Same problem here but in the breadcrumbs, but i unchecked the Add OpenGraph meta data in the Social tab and the validation error still exists.

Attribute xmlns:v not allowed here.
…s:v=”https://rdf.data-vocabulary.org/#”><span typeof=”v:Breadcrumb”><a href=”ht…

Kind regards,
Rian

Thanks for posting this. At the moment i am building a WordPress installation for 2 blind users, and all kind of input about the problems screen reader users get, are very helpful.

@neomorph
Great! Thanks ??