toad.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server operated by David Troy, a tech pioneer and investigative journalist addressing threats to democracy. Thoughtful participation and discussion welcome.

Administered by:

Server stats:

325
active users

#screenreaders

4 posts4 participants0 posts today

For #Accountants and #Bookkeepers of #Mastodon, do most companies use Excel for accounting/bookkeeping? or is quickbooks the main driver? if excel is used, is there some sort of template specifically made for accounting and how would I gain access to it? I'd like to know how to make 4 documents and credit and debit each, statement of financial position, Income statements, Statement of cashflows, and invoices. It would really help because I'm #Blind and Excel is very #Accessible with #ScreenReaders, and I would love to get back into accounting if at all possible, as it was my favorite subject in College and if I could gain employment in that field, I'd gladly do it again. Thank you for your assistance, and if you don't know the answer, please boost for reach.

👀 "ARIA Notify is designed to address scenarios where a visual change that’s not tied to a DOM change and not accessible to assistive technology users, happens in the page. Examples include changing the format of text in a document, or when a person joins a video conference call."

#ARIA #WebDev #accessibility #screenReaders

blogs.windows.com/msedgedev/20

Microsoft Edge Blog · Creating a more accessible web with Aria NotifyWe're excited to announce the availability, as a developer and origin trial, of ARIA Notify, a new API that's designed to make web content

🫡 “complications can arise with event handling, because screen readers intercept events, and don’t necessarily pass them on to the browser. Even then, events don’t always match the input type, since desktop screen readers are typically controlled with a keyboard, yet keyboard actions might fire mouse events.”

by @siblingpastry

#screenReaders #JavaScript #a11y

tpgi.com/event-handling-in-jaw

TPGi · Event handling in JAWS and NVDA - TPGiComplications can arise with JavaScript event handling in screen readers, because the virtual cursor intercepts or modifies page events.

To other #blind #students, what tools have you used to help you format your papers with #APA styling and #citations? My #university provides #Perrla for free to students, but it doesn't seem to be the most #accessible with #ScreenReaders, at least not the online version. I haven't tried the add-on for #MicrosoftWord. With the online version, though, I don't see any keyboard shortcuts, and when you move into the edit box to start writing a paper, focus gets trapped there and it's hard to get out, so I don't think it's the best tool for me. The only other tool I know of is the reference manager built into Microsoft Word, but it seems to have fewer features and doesn't really help you format your paper like Perrla does, something I was looking forward to since all the APA rules for styling seem hard to remember.
#College #CollegeStudent #accessibility #JAWS #ScreenReaders #writing
@mastoblind @main

Adding more alt texts

In the early days of the dial up internet, alt text could be your friend, sort of, as it kinda told you if the wait for the image to load would be useful. But then, the webs got bigger and faster, and images "just loaded fine" most of the time. As a sighted person, I never realized that the alt texts could and would be beneficial to people with less sight than I have... I neglected the alt texts when I shared things, many of the newer social media bits didn't even offer the option anymore. Everyone just assumed that others could "just" see it... 🤔 When I joined Mastodon during the great migration of November '22, I learned the importance of alt texts again. Heck, I became someone that doesn't boost (re-share) messages that don't contain the alt texts, as I want the content to be enjoyable by everyone, so including those that need screen readers. […]

cynnisblog.wordpress.com/?p=15

For anyone who reads scholarly texts frequently, as I do, footnotes are commonplace. Given a document received in Microsoft Word format, I sought to access the footnotes using several word processors and screen readers. Findings:

Microsoft Word for Windows (Print layout) - the footnotes appear at the bottom of each page and can be reached using ordinary cursor navigation. An option to move from the footnote text to the footnote mark in the body of the document is available in a context menu. However, I couldn't find a command to move from the footnote mark directly to the footnote text.

Microsoft Word for Mac - VoiceOver didn't read the footnote text at all - not good, obviously.

Apple Pages - each footnote mark was treated as a link, so I could navigate directly to the footnote text. However, there was no obvious way to move back from the footnote text to the footnote mark.

Google Docs - I haven't tested recently, but when I last tried it with multiple screen readers under different operating systems, the screen readers ignored the footnote marks in the document entirely, unless the cursor was placed directly on the footnote mark, which is unlikely to happen by accident.

LibreOffice Writer (Linux) - when last I tested, there wasn't a keyboard binding for the command to move to the footnote area. I reported this as a bug. It may have been fixed since then.

#accessibility #ScreenReaders #WordProcessors

Question for folks who use screen readers: what is your preferred way for someone to write individual letters? Example, spelling out the letters on a sign that do not add up to a real word.

I did alt text for a picture of signs that were badly made. When describing the text layout, I went with "Capital Letter space Capital Letter". How well does that work versus maybe "Capital Letter dash Capital Letter"? Or is there a better option?

If something I boost has image(s) without alt text, please check the following posts in the thread. I don’t boost posts without providing alt text (and often I just don’t boost posts without alt text that I might have otherwise unless I think they’re worth the time/effort for me to do it).

If I do this for one of your posts, please edit the post and copy/paste the text I’ve provided into the image descriptions so people who rely on screen readers can know what’s in them too.

Let’s keep the fediverse accessible.

Thanks 💕

Continued thread

Thinking about the wasteful nature of #LLMs got me thinking about waste in my own development. While it can be convenient to use the large, enterprise-grade frameworks to deliver a minimalist website in 2025 - it's absurd.

Do I really need #laravel with #react, #jquery, #tailwind, #webFonts, #postgres to host some simple #markdown?

Do I need to re-render a bunch of static content at every hit? Does every simple article require 64 connections to the server to display?

I think not.

I want my material to be available to anyone who wants it - regardless of the device they are using or the robustness of their connection.

I want to respect users who disable #javascript for their personal protection.

I want to respect #ScreenReaders and users of assistive technology, without unnecessary complexity.

Everything we need is built into the HTML and CSS specs.

Attention, blind Akkoma users! I will be writing to the developer with my concerns about a few problems with accessibility on this platform. Most should be easy to resolve. Please let me know if you find any more, and also state what browser and screen reader you are using. Note: This is in reference to the site itself, not to your client of choice. I will post about that separately. For the record, I use NVDA with Firefox.

  1. Many buttons are unlabelled and simply say "button". This is true on the main page as well as when viewing posts and tabs in profiles. Most work once pressed. They just need to be labelled.
  2. Searching for people, tags, groups, and posts is inaccessible. I can enter the edit field and write my text, but then, there are two unlabelled buttons next to that. The first simply takes me back to the edit field. The second does nothing. I am assuming this is a submit button that doesn't work via the keyboard.
  3. It is impossible to view followers, as well as those whom I follow. I can see the numbers of each but not the people and groups themselves.
  4. I cannot read my own profile without editing it. There appears to be no link where I can simply view it, either as myself or anonymously. If I go to my page and am not logged in, however, I can view it. I can also easily edit it when logged in.
  5. The page renders very differently in Chrome than in Firefox. In Chrome, I can't see anything but my notifications, so I can't get to my page or the other timelines.

#accessibility #Akkoma #blind #Blob.cat #Chrome #Fediverse #fediverse #Firefox #JAWS #NVDA #html #ScreenReaders #SemanticHtml #Supermium #Windows