#42344 closed defect (bug) (invalid)
Accessibility of Wordpress.com
Reported by: | tiittapauppi | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 4.9 |
Component: | General | Keywords: | |
Focuses: | ui, accessibility | Cc: |
Description
Hi!
I am Riikka Böök and I study at Haaga-Halia University of applied sciences in Helsinki, Finland.
I am currently writing my thesis regarding accessability of free online blog enviroments and during this process I also reviewed Wordpress.com. Sadly the result was, that Wordpress.com is not accessible by blind people when creating a website.
The issue is following:
When creating new Wordpress site, and it is time to choose the address of your wordpress site, you can write the name of the wordpress site. At that point it gives you options for the addresses. These addresses can not be accessed with tab key. As it is not possible to choose the address of the Wordpress site with the tab key, the site is not accessible for the blind.
I hope you will consider this in your future development plan and make your website more accessible. You can find more information about accessibility requirements from Web Content Accessibility Guidelines by W3. (http://www.w3.org/TR/WCAG20/)
Best regards,
Riikka Böök
riikka.book@…
Attachments (1)
Change History (4)
#2
@
6 years ago
- Keywords close removed
- Milestone Awaiting Review deleted
- Resolution set to invalid
- Status changed from new to closed
#3
@
6 years ago
Thank you for raising this, tiittapauppi -- I'll follow up with you via email or Slack later. I work on WordPress.com specifically and can answer questions about it.
Tracking it here: https://github.com/Automattic/wp-calypso/issues/19194
Hi @tiittapauppi - welcome to Core Trac!
WordPress.com is a separate, hosted version of WordPress and isn't managed here. This is for Core development of the self hosted WordPress product instead. The suggestion for WordPress.com being more accessible should be directed here ( https://wordpress.com/help/contact ) instead as it'll be able to be addressed there for potential improvements.