Amanda Rush

Hi Matthias,

I have post-content setting set to the default (content), and the activity-object-type set to note. So I’m assuming that if there’s nothing in the content field of the edit post screen, then nothing will be published via ActivityPub? Definitely thing that being able to map post kinds to objects would be a good idea, but if there’s a way to accomplish this outside the plugin, like through .htaccess, that would be fine too. I think it’s mostly accessible but will go in and fork this on Github to provide some assistance there if you’d like.

@diondesigns you are a life-saver and I owe you a drink. Along with being one of those old-timy “get-off-my-lawn” developers, I also use a screen reader, and at the moment Codemirror is completely inaccessible if you use any assistive technology, although they are working on fixing it. And despite my being one of the loudest advisors against so-called cowboy coding, there are rare occasions when I actually need to do it. So thank you a ton for answering this question. Disabling syntax highlighting reverts things back.

Hi @bodieskneaded,

YOu can find themes that have been vetted for accessibility according to internationally recognized standards by browsing the accessibility ready tag in the theme repository. Once you have an accessible theme, you’ll need to ensure that the content of the website you’re working on is accessible, (things like alternative text for images, closed captions for videos), and that the plugins you have installed are not contributing to any accessibility issues you may have on the site. I would suggest taking accessibility one step at a time. Learn as you go, and fix things as you learn. Taking this approach will make accessibility in general, and the accessibility of your site in particular, a lot less daunting.

Hi @lattesandstories,

Can you deactivate all of your plugins, and then see if the edit posts/pages problem still persists? If it doesn’t, reactivate each plugin until the problem reoccurs.

Amanda

Hi @lattesandstories,

When I click on the link you’ve provided, I get a notification that yours is a members-only site. Exploring the site a bit, I can click on the blog, and access each blog post, even when clicking on its title/headline.

It also appears, (based on the full address you’ve given in your link), that you have a custom permalink structure. This could be either because you’ve set this yourself, or because of a plugin or your theme adding a custom post type. Have you tried going to settings/permalinks and re-saving those settings? If not, can you try this and post again in this topic to let us know if the problem is either resolved, or if the problem is still unresolved?

Amanda

Hi @klt708

Can you be more specific about what kind of plugins you’re looking for? What kind of functionality? Several of the more popular WordPress plugins are translation ready, and/or are already translated into Hebrew, and while there is no official categorization of plugins based on accessibility, some are quite accessible, although not compliant with WCAG 2.0 or any country-specific accessibility standards.

Looking forward to your response,

Amanda

Hi @jonathansimeone and everyone else,

Regarding accessible web hosting, No hosting provider at this point that I am aware of has a control panel that is WCAG compliant or accessible according to standards/best practices. That being said, Cpanel is useable, once you spend some time familiarizing yourself with the interface. Most hosts will use Cpanel. There are, however, some things you’ll want to avoid. PHPMyAdmin, (a database management graphical user interface), is completely unuseable with a screen reader at this point, and I’m not aware of anyone involved with that project who is working to make it accessible. PHPMyAdmin usually come standard, but there is a separate database manager you can use to create and delete databases. Anything involving database operations other than these you’ll either need to learn the command line for, or get someone to help you with. I personally use WPEngine, and their support staff is really good about helping when I run into an accessibility issue with their control panel. They’re a managed host, which means that they take care of a lot of the WordPress-specific security and maintenance for you. This can be a good thing if you’re just starting out. I use a managed host because of the convenience. If you go with a host that uses Cpanel, also avoid the file manager that’s built in. It’s almost unuseable. You’ll want to get yourself an FTP client.

Hope this helps,

Amanda

Hi clansink,

I am using WordPress 4.7.3 as well. If you’re seeing display:none on that div, that would prevent your screen reader from seeing those tab panels. Unfortunately, when I inspect these elements, I’m not able to reproduce what you’re seeing. Would it be possible for you to create a temporary WordPress instance running WordPress 4.7.3, with no plugins installed and a fresh database, and then post here with the results?

Amanda

Hi clansink,

I use NVDA as my primary screen reader, and I am able to see both the screen options button and the menu open/close button. However, I am using Firefox with NVDA as NVDA is coded to work best with Firefox. I can also see these using Jaws and Internet Explorer, and would recommend using Jaws with Internet Explorer because it is best paired with IE as opposed to other browsers. One thing I always make sure to do is to ensure that my browser window is maximized. I am also using the latest stable version of NVDA and the latest stable version of Firefox.

Let me know if that helps.

Amanda

Hi @mertzsor,

To better assist with sorting out what problem your client is having with Jaws for Windows and WordPress, a little more information is required. What version of Jaws for Windows is your client using, and what browser and version of that browser is being used. Second, while we are making every attempt to ensure that WordPress and its bundled themes and plugins work out of the box with assistive technologies and browsers, we cannot guarantee that third-party plugins will not introduce conflicts. Based on the list of active plugins you’ve posted here, and based on having worked with some of these as a screen reader user, I can foresee some issues. I would suggest that, if your client has not already done so, she ensure that she is using the latest version of Internet Explorer, (IE 11), and the latest version of Jaws for Windows, (version 18). Screen readers like Jaws are hard-coded to work best with specific browsers, and the browser that Jaws for Windows works best with is Internet Explorer. Should upgrading either the browser or screen reader not be possible, (Jaws upgrades get expensive), the next best option is to switch and use Fire Fox latest and NVDA instead. If neither of these are an option, I would still suggest deactivating all plugins, and then re-activating one at a time, testing the problem points before each re-activation. Going through your list of active plugins, I’ll make some notes.

Contact Form 7 (ver 4.6.1) Contact Form 7 can create accessible forms, and so Contact Form 7 Accessible Defaults (ver 1.1.4) is not necessary. I’m noting this in case this particular plugin happens to be the one creating the conflict.
ET (Elegant Themes) Shortcodes (ver 1.2) This is a premium plugin, and so, (should it be the plugin causing the conflict), the licensee wil need to contact Elogent Themes support to try to resolve the issue.
JetPack (3.9.4) The latest version of Jetpack is 4.6, and I would recommend updating to the latest version. I use this plugin across multiple sites, (including client sites), and it does not cause the problems with Jaws that you are experiencing.
Meta Slider (3.4.1) At this point in time, there are no up-to-date accessible slider plugins, and so if this is the plugin that’s creating the issue you will either need to code your own slider or test and then use another plugin.
Recent Posts Widget Extender (0.9.9.5) This plugin does not yet have an update for 4.7.2, and so if it is the one causing the conflict, you may want to consider disabling it until an update is available, or finding another plugin that does the same thing this one does.
RSS Image Feed (4.2.5) is compatible up to 4.5.6, and has not been updated to work with 4.7.2. You will want to look for either another plugin, or customize the site’s theme via a child theme to add this functionality if this plugin is causing the conflict.
Widgets on Pages (0.0.12) is also only compatible up to 4.5.6, and you’ll want to either find a comparable plugin to add this functionality, or customize the site’s theme via child theme to add widget areas to the site. These last two, (images in RSS feeds and being able to add widgets where you need them), are theme territory according to WordPress best practice.

If there’s anything I haven’t covered in this reply that you think is missing, feel free to reply with further questions, and I or someone else will try to help as best we can.

Good luck,

Amanda

Hi @adityashevle

To put it briefly, the reason you can’t easily increase the number of items on a page to above 999 is because anything above that number is going to increase the load time of your site, significantly, and, depending on your hosting situation, increase the load on PHP itself as well as the database. So I think the first question to ask is why you want to display 5,000 items on a single page, as opposed to having site visitors page through sets of say 25 or 50. That option doesn’t effect the number of pages created, just what gets displayed at one time. So if you set that number to something like what I’ve suggested above, site visitors can still access the earlier content by moving back through older posts, they just wouldn’t see all your posts at once. Given that this is a forum dedicated to working with assistive technologies in combination with WordPress, as well as other web accessibility concerns with regard to WordPress, I’m wondering if you’re trying to mimmick infinite scroll functionality. If so, infinite scroll creates some particular issues for those who use assistive technologies, as well as those for whom accessibility is a necessity but don’t use assistive technologies, and is very difficult to get right in those senarios. Please feel free to reply to this topic if you have any further questions, or if there’s something I’ve missed in your post.

Amanda

Agreeing with Andrew on this one. Users who need to can and should change CSS and fonts in their browser, and we’re better off working towards everyone building accessible websites with WordPress in the first place, rather than duplicating features that are present in every modern browser. That would be a nightmare to maintain.

See this post: Dre Armeda where the source generated prints the emoji directly instead of a link to an image.

Also, here are some resources for making inline SVG accessible.

Using Aria to enhance the accessibility of SVG, and Tips for creating accessible SVG.

Amanda

If I’m not mistaken, the graphics generated are SVG, so you’ll need to use aria-label, and handle the translation aspects with a PHP function. The JS would contain the aria-label with a value pointing at the PHP function. Let me go create a post with an emoji in it so I can see what the markup looks like and get back to you.

Amanda

Hi,

There is currently not a plugin to fix this. The problem is that the images generated by the emojis have no accessible name for the screen reader to announce, which is why the screen readers speak nothing other than “graphic” when the user comes across one of these images. This is a known issue and is under discussion by the WordPress Accessibility Team.

Thanks,

Amanda