Mike Paciello – talks accessibility – fireside
@MikePaciello
Mike Paciello – talks accessibility – fireside
@MikePaciello
from @laura_a11ynews on Instagram.
Want to level up your accessibility auditing game? Join our Section 508 Trusted Tester study group hosted by GDG Vienna!
🗓 When: Every other Friday, at 4 PM CET
📅 Kick‑off: Feb 6 (6‑month journey)
🌐 Where: gdg.community.dev/gdg‑vienna
or search "Google Developer Group Vienna"
this is session1
https://gdg.community.dev/events/details/google-gdg-vienna-presents-dhs-trusted-tester-study-group-1-what-is-section-508-functional-performance-criteria-and-testing-tools/
curriculum
🔹 Session 1 February 6: Section 508 basics & testing tools
🔹 Session 2 March 6: Auto‑playing, auto‑updating & flashing content
🔹 Session 3 March 12 (attention: Thursday 6 pm instead of Friday 4pm): Keyboard access & focus management
🔹 Session 4 March 20: Forms & validation
🔹 Session 5 April 3: Links, images & adjustable time limits
🔹 Session 6 April 17: Repetitive content & structure
🔹 Session 7 May 1: Language, page titles, frames & iFrames
🔹 Session 8 May 15: Sensory contrast & tables
🔹 Session 9 May 29: CSS positioning, audio‑only & video‑only animations
🔹 Session 10 June 12: Synchronized media
🔹 Session 11 June 26: Resizable text, multiple ways & parsing
🔹 Session 12 (final session) July 10: Alternate versions, non‑interference, reporting & Q&A
all the recordings and transcripts are provided.
go here for session 1https://gdg.community.dev/events/details/google-gdg-vienna-presents-dhs-trusted-tester-study-group-1-what-is-section-508-functional-performance-criteria-and-testing-tools/
and Here's Laura Wissiak's substack https://substack.com/@a11ynews
Session 1 of the dhs trusted tester study group on YouTube https://youtu.be/NzBo3sU0ki8?si=cSkEJXCRzUdE7Qli
#wcag #dhs #accessibility #Blind #disability #DigitalAccessibility #WebAccessibility #oer #DHSTrustedTester #a11y #OpenEducation #OnlineLearning #Learning #WebDevelopment#HTML #css #JavaScript #WebDesign #section508 #curriculum #trustedTester
YouTube auto-censors for inflammatory content, resulting in creative verbiage to work around the censoring.
One example is for the word "pedophile" - which results in many people saying "PDF file" as a substitute.
Now every time I make a PDF document 508-conformant, I chuckle to myself about how I could be misinterpreted when talking about how to make your PDF Files conform to US Government requirements.
Suddenly my professional training content seems a little inappropriate and NSFW.
Each day is a new descent into further depths of depravity, shame, and disappointment in my fellow Americans.
Thanks again, Trump...
Ya fucking child-raping scumbag!
Fuck Trump and every disgusting sociopath who supports him.
#a11y #PDF #irony #Section508 #trump #pedophiles #epstein #resist
Making Sense of Accessibility and the Law, by @tempertemper:
https://www.tempertemper.net/blog/making-sense-of-accessibility-and-the-law
Thank you for your interest in speaking for A11yTalks. Before completing this form, you may want to review our Speaker Resources page for how things will work for your event. If you have any questions, please feel free to contact us at [email protected].
Tool: Accessibility Checker (PowerMapper), by (not on Mastodon or Bluesky):
https://www.powermapper.com/products/sortsite/checks/accessibility-checks/
#tools #analysis #accessibility #compliance #wcag #section508 #ada
Thank you for your interest in speaking for A11yTalks. Before completing this form, you may want to review our Speaker Resources page for how things will work for your event. If you have any questions, please feel free to contact us at [email protected].
Folks in the #US who work in #Section508 and #WCAG #Digital #Accessibility : with the ongoing elimination of #DEI, are you noticing any pushback or reduction in investment or efforts to adhere to accessibility? I'm wondering about impacts on #Adobe #PDF remediation and web accessibility.
Please boost for exposure.
#Accessibility Question.
Scenario: Web service has a #Section508 compliant interface readable by most screen readers.
Writing the help guides for how to use the site & including screenshots of the interface showing different buttons highlighted for each step in the instructions.
Is it enough for the #AltText of those screenshots to indicate it shows the button being highlighted, if the location of the button is in the page text? Or should the button location still be in the alt text?