WordPress.org

Make WordPress Core

Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#12380 closed task (blessed) (fixed)

Menus need to work without javascript for accessibility

Reported by: ptahdunbar Owned by: ptahdunbar
Milestone: 3.0 Priority: high
Severity: normal Version: 3.0
Component: Accessibility Keywords: needs-patch
Focuses: Cc:

Description

Working ticket for all things accessibility for the menu management administrative page. See #11817.

Attachments (3)

posting without JS or styles.png (57.8 KB) - added by edward mindreantre 4 years ago.
document outline - comments.png (18.0 KB) - added by edward mindreantre 4 years ago.
no css.png (55.6 KB) - added by edward mindreantre 4 years ago.

Download all attachments as: .zip

Change History (14)

comment:1 dremeda4 years ago

  • Cc dremeda added

comment:2 voyagerfan57614 years ago

  • Cc WordPress@… added

edward mindreantre4 years ago

comment:3 follow-up: edward mindreantre4 years ago

  • Cc edward mindreantre added

I have a question: has anyone with a screen reader actually tried to admin Wordpress?

I've attached three files that show pretty much what a screen reader sees. There's the document outline with missing headings, an enormous amount of text when posting, an enormous amount of text when doing anything at all, etc...

If blind people are satisfied with how the admin part works then that's great and I ain't gonna say nothing more. But if nobody has actually heard a blind person say "wordpress admin is really easy using a screen reader", then maybe we should stop and think a little about what the screens actually look like for them.

I work with accessible websites and I test my sites using the following: Install Firefox, Firevox, Orca (Linux). Switch off styles and javascript. I then close my eyes and let Orca do the reading.

I don't even have to start Orca to know that the admin pages are gonna be hell to understand for a blind person.

Do we perhaps need a separate blind-interface that doesn't have all the unnecessary fluff of the visual interface?

comment:4 in reply to: ↑ 3 voyagerfan57614 years ago

Replying to edward mindreantre:

Do we perhaps need a separate blind-interface that doesn't have all the unnecessary fluff of the visual interface?

It certainly couldn't hurt. Google Reader has a separate ARIA-enhanced version.

comment:5 jane4 years ago

We need to make every screen accessible when there is no JS not just for the blind, but for people with JS turned off. Last weekend at WordCamp Ireland I had to help someone with her widgets, and she and the two guys she was with all had no JS. It was painful, but it worked. Menus need the same ability, not a separate UI altogether. (That said, a super-accessible admin theme optimized for people with disabilities is in the works, but it doesn't affect the need for a no-JS version of everything to be built in.

comment:6 follow-up: edward mindreantre4 years ago

Jane... Who is developing that non-JS admin menu?

I figure if there's something I'm good at it's accessibility, so I can help probably help there.

comment:7 in reply to: ↑ 6 ptahdunbar4 years ago

Replying to edward mindreantre:

Jane... Who is developing that non-JS admin menu?

I figure if there's something I'm good at it's accessibility, so I can help probably help there.

We could definitely use another developer who knows accessibility. What's the best way to contact you so we can collaborate on this? You can catch me in #wordpress-dev as pthdnbr.

comment:8 batmoo4 years ago

  • Cc batmoo@… added

comment:9 nacin4 years ago

  • Type changed from defect (bug) to task (blessed)

comment:10 markmcwilliams4 years ago

  • Version set to 3.0

Related with #12713 patch?

comment:11 ptahdunbar4 years ago

  • Resolution set to fixed
  • Status changed from new to closed

Fixed in r14248

Note: See TracTickets for help on using tickets.