Now I see that output can be made accessible... but there is need to have also the backend accessible for people with disabilities.
there is no a lot of work... but for the next versions I think this will be developed with accessibility in mind (otherwise will be difficult in future to make it conform to the new national laws like italian law and the new Section 508)
Make an accessible backend
-
rscano
MemberPosted: 5 years ago # -
ramseyp
MemberI work with accessibility experts and disabled users. I did a cursory look at WordPress's posting interface and it looks like two things can be done right off the bat to improve the accessibility of WP's backend.
Looking at post-new.php, specifically:
1) Add a label tag associated with the post title:
'<div id="titlewrap">
<label for="title">Enter / Edit your Post Title</label>
<input id="title" type="text" autocomplete="off" value="" tabindex="1" size="30" name="post_title"/>
</div>'A style can then be used to position the label outside the viewport for design considerations, but it's still in the DOM and accessible.
2) If adding a label tag is not kosher, then a meaningful title attribute can be used with the input for the post title:
'<div id="titlewrap">
<input id="title" type="text" title="Title of New Post" autocomplete="off" value="" tabindex="1" size="30" name="post_title"/>
</div>'I know JAWS will recognize the title attribute when in forms mode, relaying the input's purpose to the user.
3) The TinyMCE editor has some useful keyboard shortcuts that are not made known to novice WordPress users: Alt+Shift+Q (Toolbar), Alt+Shift+Z (Editor)
An internal anchor could be placed near the top of the post-new.php body, acting like a skipnav.
Style it with CSS to position off the viewport.
These edits would greatly enhance the accessibility of WordPress as a publishing platform for those using screen readers. Thoughts?
Posted: 4 years ago # -
cooms13
MemberHi. I work for a gov't agency who is using WordPress. We would love to have a fully-accessible backend. Based on our initial scans, the fixes would be relatively easy. The problems are scattered throughout 22 different backend pages, but they ALL have to do with input fields not containing a <label> tag or alt attribute. 90% of them are checkboxes (like on the edit posts page). The remaining issues are for "file" and "text" inputs. We're thinking about contributing the fixed code ourselves, but we haven't done anything like it before.
Posted: 4 years ago # -
Stephanie Leary
MemberI think most of these issues have been fixed since this thread began.
If there are remaining accessibility issues, you can use the wp-accessibility mailing list to discuss ideas or report specific problems by filing tickets in Trac under the accessibility component.
Posted: 3 years ago #
Topic Closed
This topic has been closed to new replies.
