A problem with applevis edit fields on Windows

Applevis devs, come on, we need an applevis bugs/suggestions forum. This is just getting silly, even if it's rarely used; at least it will be there.

To those reading, the applevis devs have actually told me off for suggesting this before, I don't understand why, it makes no sense at all.

Personally I think they think that if they add a forum like that; Apple will see it and want applevis shut down at once, apart from that, I really can't see a reason as to why you can't just add another forum topic, surely it isn't that hard.

You could make a form where you'd fill out all the info and everyone can comment on it, it's a win win for all of us, we are validaded because the bug exists and you would have proof on your side too.

This really does need to be a thing Devs and honestly at this moment; I don't even care if you ban me, this is silly and makes no sense, humans make mistakes/would like changes, your website is not perfect and your old way of doing this, contacting you, is just that' old,, there are better ways these days, use them.

Brad, I think it’s time to move on. The AppleVis development team, along with their volunteers, have made it clear that they won’t be creating a new forum for bug reports or site feedback. This approach is quite common and I respect their decision. It’s important to trust in their process; they’ve consistently shown dedication to improving the site. Remember, these individuals generously donate their time and do a remarkable job. There’s no need to question their commitment. Let’s honor their request to direct any issues through the channels they’ve provided. A big shout-out to the AppleVis team for their hard work—keep it up! Regarding the bug you mentioned, it could be related to a combination of Windows and a screen reader, or perhaps it’s an issue with Google’s Chromium platform, though I’m not certain.

Is this the issue where some words seem to be hyphenated, or otherwise splitting into 2 separate words, during editing? If so, I am also experiencing it on the latest Firefox browser, which I do not believe is Chromium.

Just my 2 cents. 😇

rubarb rubarb rubarb

Alright fine, i'm done with this, I don't care anymore, I won't be contacting the team about any bugs though. Childish, yep, but I'm done caring.

Also, I wasn't attacking the team, I do like the site and i know they do a great job.

Jaws released an update yesterday July second it fixed the issue.

Possibly CSS is to blame. If nothing else, CSS could be tweaked to patch the site, so to speak. 🙂

Using Safari on the Mac and VoiceOver, if I am typing a comment with any remotely long words, VoiceOver will often tell me that they are misspelt and will split the words in two. But if I use option+left/right the words are actually fine. It's pretty annoying. It feels to me like there is some sort of hyphenation thing specified in the CSS.

Might not be the same bug but feels similar.

I also think a forum for discussing the site would be a good idea. But I'm sure they have their reasons for not creating one. It doesn't feel right to be overly critical considering that we get all this plus their time for free (unless we choose to donate).

I've got the newest jaws; using microsoft edge on Windows 10, and the navigation/editing of posts on here is as messed up as it's been for however long this has been going on. I've tried JAWS and NVDA; didn't try Narrator, but since someone else has indicated that the issue happens with Narrator as well, I trust their judgement. It's weird that this issue seems to be unique to Applevis. On the other hand, I don't do a lot of trying to write long posts on other web sites, so maybe this does happen elsewhere? I remember someone on another thread here mentioned that they write out everything they want to say in notepad or something so that they can edit before posting. This seems like a reasonable sollution, at least in the short term. The trick is remembering to do it. *smile* Anyway, just wanted to jump in here and say that at least for me, the JAWS update on Wednesday hasn't changed anything. I wonder if there are some settings I should try adjusting, but wouldn't know which ones to try, and if this is happening with other screen readers and web browsers, then messing with my jaws settings probably wouldn't make any difference.

Just a quick note to say that I haven't been ignoring this thread. I'm currently not available to investigate the potential website issue mentioned here. I'll look into it as soon as I'm able to do so. Thanks for your patience and understanding.

I have typed lot of long posts on Applevis so far, and I don't recall facing this issue before. It seems to have started in last few weeks or days.

Could be that chrome or NVDA updated, and changed how edit fields are handled. I haven't really tried any other edit-box, typing out a long post there.

I would say that, yes, I think a fairly recent update is what started this issue. As I have mentioned, I am on Windows 11 with Firefox, and I too experience this.

It seems to matter not, which browser or screen reader is being used to view the website, which leads back to my previous post that it is perhaps something in the backend code, i.e. CSS, etc.

Hopefully the editorial team can figure it out. 🙂

Same problem with Edge and NVDA. Seems to also have started recently.

I know the error you are talking about. The problem came from a new version of drupal around that time and I think they fixed it.
By the way. Someone said this website is created on WordPress but it is not, The website is created with drupal and this is my favorite CMS, Lol.
You should stay calm about any mistakes. Drupal is a constantly updated platform and sometimes accessibility bugs will still exist, But the drupal Community fixes it quickly and I stopped having the error that @TheBlindGuy07 mentioned.

You can check the meta tag of the website, It will tell you the platform it is using. Anyway applevis choosing drupal is right in my opinion, Because drupal community is the most accessibility compliant CMS till date.
I realized this about 4 years ago, I am a drupal developer after all.