A cool accessibility side project l've been working on,

Everyone should be able to enjoy audiobooks for free >:3

Fully free offline

Demos audio files are located in the readme :)

And has a self-contained docker image if you want it like that

Hey all,

I’m a young UX designer working on b2b and sometimes b2b software, and I’ve noticed that a lot of the discussions around accessibility tend to come from people who aren’t directly affected by these issues. It’s made me wonder: Are there aspects of accessibility that are frequently misunderstood, overlooked, or implemented in ways that miss the mark?

What are the biggest misconceptions you’ve come across regarding accessibility in software design?

I’d love to hear your experiences and insights—whether as a user, designer, or developer.

Thanks for sharing!

I'm using the free version of the axe devtools extension for Chrome, which I believe is set to WCAG 2.1 AA by default. However, when I run a scan, it says "WCAG 2.2 AAA" and some of the results are flagging AAA requirements. I don't want to see AAA, just AA. Is there a setting that I'm not seeing?

https://imgur.com/iKpTHKK

I’m watching Amphibia on Disney+, and there are several points where the caption seems automatically generated or something. Like, “talking frauds,” instead of, “talking frogs.”

I could understand that for independent creators on YouTube who don’t have a budget for captions, but I’m really surprised that a cartoon on a major streaming service would have flaws like that. I’ve noticed quite a few.

Where do you report things like that so that they can get fixed?

Okay, this might be an incredibly dumb question but I’m trying to evaluate a clickable map that relies only on color to distinguish different areas is accessible or not. My initial thought was no but you can click on the different areas and a pop up open thar gives you distinguishable information. Does CLICKING on something (it opens a pop up and does not take the user to a new screen) and it provides accessible information count as “onscreen text” or does said text actually have to be visible without clicking anything further? Hopefully that makes some sense.

I was unexpectedly asked for my rate and if I was interested in hosting a private session at a company on creating accessible/inclusive eLearning content.

I'm not so sure what the rates are for such an invitation and was hoping to get some guidance.

I have a specific task that I can do manually but can't figure out how to automate. I need to modify the accessibility tags in a PDF so that <Figure> tags are not nested inside of <p> tags (basically replacing the parent with the grandparent).

Manual methods: In Acrobat, this can be done manually by bringing up the accessibility tags panel and moving them. In TextEdit (I'm on Mac), it can be done manually by changing the parent reference in the <Figure> object to the parent of the <p> object.

Automation attempts
JavaScript: I initially wanted to do this with JavaScript and the Acrobat API so that I could make it an Acrobat Action but I don't know JavaScript that well and the documentation doesn't cover working with the structure tree. I did try ChatGPT but it first said it wasn't possible to do and then kept giving me code using a function that, as far as I can tell, doesn't exist to get the root tag.

Python: I am much more comfortable working in Python so I tried both using libraries and working with the decoded binary but in both cases, the saved result had NO tags at all. Just loading and saving a PDF results in the tags and the PDF object containing them disappearing in the new PDF. Is there a way to open the PDF in Python the way that it is opened and modifiable in TextEdit? Using .decode() is not working for me despite trying different encodings.

Given the importance of accessibility in this era, I feel like I can't be the only person who is trying to work with tagged PDFs but I cannot find any information on how to do it.

I have difficulty using the mouse for extended period and I'm looking for a high-quality and precise eye track to use as a mouse replacement. Price does not matter as my work employer will pay for it for accessibility reasons. Thank you! Looking for one that is very precise and accurate and does not result in eye fatigue, preferably for Mac but if not available for Mac then windows

Hi everyone, I am building an AI assisted workflow tool to help write alt-text for PDF images. Open to feedback from the community, but the way it currently works is:

1. You upload a PDF with images.
2. The tool let's you select an image (just like how you'd take a screenshot). Then, click button called: "Create Alt-Text".
3. The AI will read the context and writing style of the surrounding text to generate a 2-3 sensible options for you to choose from.

This works for complex images (charts, graphics) as well descriptive images. The philosophy is that there's still a human in the loop to review the AI output, and you can skip over images that are decorative. You can also configure the output length.

Would anyone be interested in being a beta tester and provide feedback? I can't share the direct link because I incur inference cost to call the AI model, so I have to limit the number of users for now. Thanks.

ETA: I get the sense that my point did not come across well in this post given the comments it has received. It was meant to be similar to the "Creators of the Section 508 DHS TrustedTester Exam should be ashamed " post (which was not my post) from several weeks ago but perhaps less serious. I apologize for not making that clear.

I want to be able to offer both website and PDF remediation services and at the moment I am unable to afford (and lack the recommended amount of experience) to pursue the IAAP accessible documents cert. Neither the CPACC nor Trusted Tester really touched on PDFs so I figured hey, it's free and nothing can be worse than the TT training material, right?

I mean technically yes, that's correct -- it's not worse, IMO. But how can they (DHS/FAA) put out a course where two of the five PDF module videos do not play within the course content itself (had to find the videos in the course resource section), the formatting of the course documents is incredibly inconsistent from one course to another (PowerPoint vs. Excel vs. PDF -- haven't gotten to the Word course yet) -- with some including visuals and others requiring me to take screenshots of such poor quality I am going to hope they are helpful to me when I refer back to them, and inconsistencies between the course documents and the video content (leaving me confused as to which is the most up to date information).

And perhaps the most ironic part of it all... requiring Adobe Acrobat Pro in order to use any the tools and techniques from the course. The most expensive of the Acrobat products. Making accessibility inaccessible.

I also wonder how the FAA was put in charge of this one. But that's just a curiosity on my end. 😂

Anyone else taken this set of courses recently? What were your thoughts?

I am part of a group that is attempting to insure accessibility for all our members, and communications etc. Since we are new to the administrative side of accessibility, I am interested to gather some input on preferred tools for testing accessibility within various documents. I am familiar with the Accessibility checkers within MS Office, LibreOffice/OpenOffice, Grackle Docs for Google Docs, and the PAC tool for PDF's

I also realize that the best methodology would be to train users to create documents thata are accessible in the first place as opposed to remediation etc. ( this is an ongoing battle with those who are volunteers and not employees most of whom have never been exposed to accessibility issues.. although that is also in the works.

I would be appreciative of your thoughts on which tools you have used/prefer to use.. etc..

Thank you in advance,

Mark

I’m testing a web page with a jump link to a section of the same page. However, when the link is activated, the keyboard/screenreader focus doesn’t move. Obviously, something isn’t working right and that could be an accessibility barrier, but I’m struggling to place it under a specific success criteria. It’s not bypassing a navigation block, just jumping to the Q&A section of a shop’s product page. Is there one this should fall under? It’s a common issue I encounter.

Trying to stay on top of my continuing education :)

TD;LR: Will the CXD training portal being down for maintenance stall TR certification exam attempts?

I'm working through the DHS Trusted Tester certification program materials. There's a notice that says the CXD training portal will be down for maintenance for 3 weeks from the morning of Mon 12/23 until Mon 1/13 -- and I'm trying to figure out if this will pause my progress, seeing that it'd be a stretch for me to finish everything before the maintenance starts.

I'm assuming that I'll take the exam in the portal, and so I won't be able to access it during the maintenance window. I'm also thinking I'd have to pass the practice exam (which I haven't gotten to yet) and have them enroll me in the final exam before close of business on Friday, in order to do the final exam over the weekend.

But, since I haven't unlocked those steps yet, I'm unsure if I'm right about any of this. Can folks who've already taken the exam clarify what I can expect?

It's not the end of the world if I have to wait out the maintenance window in order to finish this certificate; it'd just be a bit of a bummer for my momentum.

Thanks to anyone who can chip in!

Hi!

I'm a web dev and I work for an angency. We're trying to make our sites compliants. Do better, in short.

I've watched videos about web accessibility, I've read articles and blog posts, searched on Reddit, but except learning how poorly the subject is treated most of the time, I feel I'm missing a lot.

I now know widgets are not a good solutions.

I tried to read the WCAG but oh boy is it heavy (especially since English isn't my mother tongue. And no, reading the WCAG in another language won't help at all, since most site also translate technical terms which turns the information useless)

So where can I start?

Thanks.

Using Autism as an Excuse is Harmful

Terry Loerch (https://uniteddisabilities.com/)

12/11/2024

Recent controversies surrounding Gregg Wallace, a television presenter best known for co-hosting MasterChef, have sparked outrage and critical conversations about accountability and the misuse of neurodiversity as a defense for inappropriate behavior. Wallace has been accused of making sexually inappropriate comments over 17 years. His alleged defense? A suggestion from a close therapist friend that he may exhibit traits of autism, implies that his behavior could be tied to undiagnosed neurodiversity.

This rationale is not only offensive but also fundamentally flawed. Autism, or any form of neurodiversity, does not serve as an excuse for misconduct. Suggesting otherwise perpetuates harmful stereotypes about autistic individuals and undermines the integrity of genuine neurodiversity advocacy. Many within the autistic community have rightfully condemned this narrative, emphasizing that autism does not inherently strip someone of empathy, social awareness, or the ability to respect boundaries.

Autistic individuals often face significant challenges in navigating a society built for neurotypical norms. However, they are also deeply aware of the expectations surrounding personal behavior. To paint autism as a contributing factor to inappropriate actions diminishes the voices of those in the neurodiverse community who work tirelessly to break down misconceptions and biases. It also reinforces the false idea that being neurodiverse is synonymous with poor behavior or a lack of moral responsibility.

This defense is not only harmful to the neurodiverse community but also disrespectful to the victims of such misconduct. Excusing harmful actions by attributing them to autism shifts the focus away from the seriousness of the allegations and the harm caused. It minimizes the accountability of the individual responsible and sets a dangerous precedent for others who may try to use similar excuses.

Organizations like Ambitious About Autism have recognized the damage caused by these justifications. The charity severed ties with Wallace following the accusations, signaling a firm stance that being neurodiverse is not a shield for inappropriate or predatory behavior. Their decision reflects a broader understanding that personal responsibility must always come first, regardless of an individual's neurodiverse status.

Blaming bad behavior on neurodiversity is a disservice to everyone those who are neurodiverse, the victims of harmful actions, and society as a whole. Autism is not a scapegoat, and using it as one not only reinforces damaging stereotypes but also trivializes the lived experiences of individuals on the spectrum.

Accountability should never be overshadowed by excuses, and the neurodiverse community deserves better than to be used as a convenient defense for actions that are inexcusable. Gregg Wallace's situation serves as a reminder that while understanding and support for neurodiversity are essential, they must not come at the expense of justice or integrity.

We have a page that has a grid of speaker names, with a headshot of the speaker next to each name.

The headshots are uploaded by the speaker themselves, and we ask them for a description of the headshot to put in the alt text. People sometimes carefully pick their headshot to communicate a certain vibe about themselves, so we want to give them the opportunity to communicate some of that vibe to people using a screenreader.

However, despite encouragement not everyone adds the alt text and we don't always have capacity to add one ourselves. What should we put as the alt text in these cases?

My instinct is to use an empty alt tag, as "Headshot of <person name>" doesn't add any useful information when it's next to the name.

However, it occurs to me that visually we add a placeholder image if they haven't uploaded a headshot image. This is to add symmetry and prevent a missing image from visually looking like it is trying to communicate something. Does the same apply for people using screenreaders? Would it be jarring to have some people have an image alt text read out, and some where it doesn't communicate that there is an image at all?

tl;dr which approach is better between:

<ul>
<li><img src="person1.png" alt="A white man leaning casually against a wall wearing a baseball cap">Joe Bloggs</li>
<li><img src="person2.png" alt="A black woman sitting in a dimly lit room reading a book">Ntombi Lerato</li>
<!-- No description available, so use an empty alt. -->
<li><img src="person3.png" alt=""> Shirley Raven</li>
<li><img src="person4.png" alt="A person with dyed pink hair and thick rimmed glasses">Pip Laurie</li>
<ul>

and

<ul>
<li><img src="person1.png" alt="A white man leaning casually against a wall wearing a baseball cap">Joe Bloggs</li>
<li><img src="person2.png" alt="A black woman sitting in a dimly lit room reading a book">Ntombi Lerato</li>
<!-- No description available, so use a generic alt. -->
<li><img src="person3.png" alt="Headshot of Shirley Raven"> Shirley Raven</li>
<li><img src="person4.png" alt="A person with dyed pink hair and thick rimmed glasses">Pip Laurie</li>
<ul>

TabPanelWidget.com list of features:

POSH

The Widget relies on Plain Old Semantic HTML (no jump-links needed!).
Progressive Enhancement for the win.

ACCESSIBLE

First class support for screen-reader users!
ARIA controls the rendering of their non-visual experience.

MARKUP AGNOSTIC

Authors can use any heading they want to structure their content, they can even use a Definition List if they wish (dt / dd pairs).

ADAPTIVE

The TabPanel becomes an Accordion if the tabs cannot "fit" horizontally.
Note that ARIA attributes will change accordingly.

VERSATILE

Can work as an Accordion out-of-the-box.
Accordion's icons can either be displayed to the right or left of the text.

RTL FRIENDLY

Tabs flow according to script direction (ltr, rtl).
Icon's positioning will obey script direction too.

BOOKMARK FRIENDLY (NEW!!)

The state of the panels is carried through the URL.
Saving or sharing a URL will reflect that state.

KEYBOARD FRIENDLY

Supports keyboard navigation.
Users can skip the entire Widget or reach the first tab/header.

Hi, I’m looking for a solution that creates accessible PDFs.

I was wondering if anyone here has used Equidox? Any idea on their pricing?

This is the coolest Accessibility operation. We need.

I want to add custom screenreader support for inaccessible software, including custom announcements, interactions, and so forth, starting from the absolute basics. I don’t know much about programming. Does anyone know of good resources to help me out

Not sure if it’s okay to ask here. I tried to ask on blind and it was removed.

I am a sighted person who is working on a contract document for work. I’ve been trying to make things more accessible, but I’m going off of online guides and haven’t had formal training in it. I’ve read that it’s proper to use the Strong style for semantic emphasis for screen readers whereas bold is just for stylistic purposes. I’ve also seen other guides say it’s no longer important to use strong because readers now pick up on bold and italics. Do you have a preference for one or the other?

I’m also having difficulty deciding when to use strong and when to use bold. When is it important to you to have strong style? I’m worried about overusing it.