Currently studying for the #cpacc exam and I found the #legal part surprisingly interesting. This topic was also relevant in a workshop I gave, so here's a couple of law suits that are #accessibility related:
On April 8, 2024, the United States Attorney General signed a final rule providing requirements for digital accessibility under Title II of the Americans with Disabilities Act (ADA).
TPGi's David Sloan breaks down the historic and significant event.
I am currently working on #accessibility in #forgejo. And I discovered a problem with focus where it is not possible to navigate the page with "tab", a dropdown makes the focus skip to the end of the page and you end up in a loop.
Can someone recommend ways or tools to debug focus in webbrowsers? I have a hard time to see how the focus skips there. Any hints are welcome.
Accessibility across the web is a complete mess ... you can have all the branding and colours you like, but that doesn't mean all the peeps can see, hear and interact with the various emojis, buttons, controls, sliders, toggles and links, across all browsers, and on all devices. Can't believe we're in 2024 and we haven't solved this yet. 🤦
I've mentioned text-only zoom (separate from browser zoom) in my last two articles, so I wanted to share a bookmarklet I created that helps me test text size! 🧪
The Joys of #WebStandards#WebAccessibility: TIL both Firefox and Safari DO NOT allow a user to zoom or even scroll a standalone SVG document if it has a viewBox attrib defined (Chrome on the other hand does, as expected!)... To enable document scrolling, the viewBox has to be removed and the doc MUST have width and height attribs... Pretty annoying & illogical since that also means an author can't control the initial default view (i.e. to have the browser initially display the whole doc)...
Furthermore, using the above, Firefox now does allow scrolling (but still no zoom). Safari does both, but zooming is (arbitrarily) limited and not guaranteed to fit the entire doc. Honestly, what gives and how is it possible there's no agreement on how to address something so basic in a 20+ years old technology/standard?!?
Example use case, this standalone SVG (an interactive dependency & relationship graph/matrix of #ThingUmbrella packages):
If you're new to making web content accessible and not sure where to start, here's what I recommend! You can make so much impact on these fairly low effort things.
Progressive Web Pages (PWAs) are the future of web development. Explore our board for insights into how PWAs can enhance your online presence and bridge the digital gap.
#WebAccessibility question: I have my name in an h1 heading, and my browser's (Safari) text-to-speech reads it fine. However, when I add text-transform: uppercase; as a style to the heading, text-to-speech now reads out “B-E-N Ramsey.” It spells out “Ben” but not “Ramsey.” Anyone know why?
If I switch to Edge, it spells out the full name, “B-E-N R-A-M-S-E-Y.”
Those who work with screen readers, is this how they work? Do they always spell out words in all-caps?
Was ich in Stellenangeboten zu "Frontend-Development" ganz oft als Anforderungen lese:
"#HTML / #CSS, zig Programmiersprachen, JavaScript-Frameworks, usw."
Attached is the general Swanye page layout; I'd structured tabbing to begin on the right side of the page on the premise that wanting to create a post, etc. would be the first things you might want available to you but, obviously, that then navigates the page right-to-left rather than left-to-right.
For users who'd most use this, is LtR (starting with the posts of the page) preferred? Figured I should probably check before too much is built…
My new project, https://AltTextHallOfFame.org, is a celebration of the effort, ingenuity, and creativity that goes into making the web a friendlier and more inclusive place, one captioned image at a time.
Progressive Web Pages: Bridging the Digital Gap (dadigitalfunda.blogspot.com)
Progressive Web Pages (PWAs) are the future of web development. Explore our board for insights into how PWAs can enhance your online presence and bridge the digital gap.