So a quick update on where we're at for folks not following the discord. The stability issues plaguing us over the last couple of days seem to have been fixed, touch wood. Thanks to Arch and VictiniStar101 on our Discord for keeping me moving forward when I was out of ideas, spinning in circles, and becoming unproductive.
However, in order to get the latest accessibility fixes, we're still running development code. I'm not comfortable with that for any kind of official release, and I would warn you all to continue to expect weird issues moving forward.
Known Issues
- Two factor doesn't work. Turning it on will just lock you out of your account.
- The jump to main content link isn't a link and doesn't work. This is a symptom of running untested development code with unfinished features, in order to get the upvote toggles and nested lists for comments.
- The theme is really bad for screen magnification users. We can and will fix that locally.
- A ton of issues on mobile Android.
Next Steps
Assuming things remain stable, our next steps are:
- Get back onto an official release that includes the accessibility fixes when it becomes available.
- Icons and Banners: we need to find someone who can make us an Icon and Banner. This matters not just for sighted friends, but for our friends using screen magnification who need a unique icon to help them find the tab amidst all the other open tabs they might have.
- Theming: we need a custom default theme that looks better when magnified, and has better out of the box contrast. We'd also like to offer several accessible choices, to fit everyone's needs.
- Get things working on Android with talkback.
- A few more labels: a couple of unlabeled links and buttons remain. Also, some of the heading levels are strange (heading level 5 for posts? Why?). However, I currently don't see these remaining screen reader niggles as a blocker on us opening up more widely, the way the other issues are.
If you want to help with any of these next steps, reach out! Especially on the more visual aspects, all assistance is appreciated.
Will also add on android devices you cannot log in with talkback running on Firefox, Opera, or Duck Duck Go browsers as the login button will not activate. I have to test this again on Brave, but I know this is not an issue on Chrome or Edge.
Thanks, I forgot about that! We're getting dangerously close to needing our own issue tracker, instead of everything just living in my head. I might through something up on github.
I’m just baffled as to why it's an issue on Opera and the like which are chromium based like Chrome and Edge, I get it on Firefox as that's a different architecture so makes sense it might have some different issues from those others.
I'm wondering if they handle tracking or privacy protection differently, and that's blocking some script Lemmy needs, because they think it's a tracking or ad script when it isn't?
I’m guessing cookies may be an issue.