dansmith65:
I’ve been creating an Accessibility Conformance Report via https://acreditor.section508.gov/ online editor and various accessibility reporting/testing tools. I’m finding that some common elements generated by Klai fail some high-priority accessibility items. To start with, I’m wondering if anyone else has worked on this before in relation to Klai or if accessibility improvements have been discussed internally or are on a roadmap?
Delfs:
We had a FL on Accessibility.
Let us know what specifically you had issues with
dansmith65:
The worst issue so far had to do with 3.3.1 Error Identification. The default validation and display of errors is invisible to NVDA screen reader.
The vueMultiSelect element is similarly unusable by screen readers.
dansmith65:
Do you happen to have a recording of that FL? I searched YouTube but couldn’t find it.
Delfs:
if you pass the feedback we can updat anything missing, may be as simple as adding attributes too.
Here are the best Friday Live matches I found for accessibility:
• Learn Figma for FileMaker Developers — Friday Live registration/recording link — includes Accessibility and Color Contrast in Figma.
• Friday Live registration/recording link — the Jake Johnson / Angel City Data session includes UX Corner: Device Diversity & Accessibility.
• Friday Live registration/recording link — the Tailwind 3 session includes Dark Mode, Accessibility, and Design Systems.
I only found that same official Friday Live link in the available results. If you want, I can next dig for the specific YouTube recording links/timestamps for those sessions.
notw wrong links but those shows I think
dansmith65:
These are the videos I found to match those descriptions:
https://youtu.be/fmAapoRo_G8?si=G53RHXJ0sILxYBK2
• There is some high-level talk about accessibility in general. This doesn’t go into the level of detail I’m looking for, though.
dansmith65:
I hadn’t meant to send that yet; I’m still finding the videos and searching the transcript for accessibility-related terms.
https://youtu.be/aSEFG2BT8g4?si=pp9IJaWBS5dquX9M
• This one only briefly mentioned accessibility, but also doesn’t go into detail.
dansmith65:
https://youtu.be/LA5sra2Fcv0?si=2JAAnh2Cc1ANLfdR&t=3250
In this video, you said:
I didn’t appreciate accessibility until i started going to a couple meetups and i was at this one in amsterdam where they had two present presenters and they showed a person who was blind using using a site and it’s like after that it’s like yeah we got to make things more accessible
This is the essence of what I’m referring to. In it’s current state, it would be impossible for a blind user relying on screen readers to use a form built in Klai that uses validation or thevueMultiSelectelement.
While that video does mention accessibility and the importance of it; that’s about as far as it goes. My goal is to meet all of the Section 508 requirements, but it doesn’t sound like there have been any recorded videos of how to go about doing that.
I’m wondering if what I’ve said already about form validation, and these links to the Error Identification requirements is enough for you to understand the issues related to this item?
These sites offer a better understanding of how to comply with requirements:
• https://www.w3.org/WAI/WCAG22/quickref/?versions=2.1&showtechniques=132%2C133%2C141%2C211%2C241%2C244%2C412%2C331&currentsidebar=%23col_overview#error-identification
◦ https://www.w3.org/WAI/WCAG22/Understanding/error-identification.html
• https://www.browserstack.com/docs/accessibility/references/accessibility-checklist
Delfs:
We definitely have more as Pearson has covered WCAG also
I also thing we have an example age that covers some things